
Recherche avancée
Médias (2)
-
Core Media Video
4 avril 2013, par
Mis à jour : Juin 2013
Langue : français
Type : Video
-
Video d’abeille en portrait
14 mai 2011, par
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (44)
-
Demande de création d’un canal
12 mars 2010, parEn fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...) -
Gestion de la ferme
2 mars 2010, parLa ferme est gérée dans son ensemble par des "super admins".
Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
Dans un premier temps il utilise le plugin "Gestion de mutualisation" -
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...)
Sur d’autres sites (6042)
-
Ode to the Gravis Ultrasound
1er août 2011, par Multimedia Mike — GeneralWARNING : This post is a bunch of nostalgia. Feel free to follow along if you recall the DOS days of the early-mid 1990s.
I finally let go of my Gravis Ultrasound MAX sound card a little while ago. It felt like the end of an era for me, even though I had scarcely used the card in recent memory.
The Beginning
What is the Gravis Ultrasound ? Only the finest PC sound card from the classic DOS days. Back in the day (very early 1990s), most consumer PC sound cards were Yamaha OPL FM synthesizers paired with a basic digital to analog converter (DAC). Gravis, a company known for game controllers, dared to break with the dominant paradigm of Sound Blaster clones and create a sound card that had 32 digital channels.
I heard about the GUS sometime in 1992 through one of the dominant online services at the time, Prodigy. Through the message boards, I learned of a promotion with Electronic Arts in which customers could pre-order a GUS at a certain discount along with 2 EA games from a selected catalog (with progressive discounts when ordering more games from the list). I know I got the DOS version of PowerMonger ; I think the other was Night Shift, though that doesn’t seem to be an EA title.Anyway, 1992 saw many maddening delays of the GUS hardware. Finally, reports of GUS shipments began to trickle into the Prodigy message forums. Then one day in November, 1992, mine arrived. Into the 286 machine it went and a valiant attempt at software installation was made. A friend and I fought with the software late into the evening, trying to make this thing work reasonably. I remember grabbing a pair of old headphones sitting near the computer that were used for an ancient (even for the time) portable radio. That was the only means of sound reproduction we had available at that moment. And it still sounded incredible.
After graduating to progressively superior headphones, I would later return to that original pair only to feel my ears were being physically assaulted. Strange, they sounded fine that first night I was trying to make the GUS work. I guess this was my first understanding that the degree to which one is a snobby audiophile is all a matter of hard-earned experience.
Technology
The GUS was powered by something called a GF1 which was supposed to use a technology called wavetable synthesis. In the early days, I thought (and I wasn’t alone in this) that this meant that the GF1 chip had a bunch of digitized instrument samples stored in the ASIC. That wasn’t it.However, it did feature 32 digital channels at a time when most PC audio cards had 2 (plus that Yamaha FM synthesizer). There was some hemming and hawing about how the original GUS couldn’t drive all 32 channels at a full 44.1 kHz ("CD quality") playback rate. It’s true— if 14 channels were enabled, all could be played at 44.1 kHz. Enabling more channels started progressive degradation and with all 32 channels, each was only playing at around 19 kHz. Still, from my emerging game programmer perspective, that allowed for 8-channel tracker music and 6 channels of sound effects, all at the vaunted CD level of quality.
Games and Compatibility
The primary reason to have a discrete sound card was for entertainment applications — ahem, games. GUS support was pretty sketchy out of the gate (ostensibly a major reason for the card’s delay). While many sound cards offered Sound Blaster emulation by basically having the same hardware as Sound Blaster cards, the GUS took a software route towards emulating the SB. To do this required a program called the Sound Blaster Operating System, or SBOS.Oh, how awesome it was to hear the program exclaim "SBOS installed !" And how harshly it grated on your nerves after the 200th time hearing it due to so many reboots and fiddling with options to make your games work. Also, I’ve always wondered if there’s something special about sampling an ’s’ sound — does it strain the sampling frequency range ? Perhaps the phrase was sampled at too low a bitrate because the ’s’ sounds didn’t come through very clearly, which is something you notice after hundreds of iterations when there are 3 ’s’ sounds in the phrase.
Fortunately, SBOS became less relevant with the advent of Mega-Em, a separate emulator which intercepted calls to Roland MIDI systems and routed them to the very capable GUS. Roland-supporting games sounded beautiful.
Eventually, more and more DOS games were released with native Gravis support, sometimes with the help of The Miles Sound System (from our friends at Rad Game Tools — you know, the people behind Smacker and Bink). The library changelog is quite the trip down PC memory lane.
An important area where the GUS shined brightly was that of demos and music trackers. The emerging PC demo scene embraced the powerful GUS (aided, no doubt, by Gravis’ sponsorship of the community) and the coolest computer art and music of the time natively supported the card.
Programming
At this point in my life, I was a budding programmer in high school and was fairly intent on programming video games. So far, I had figured out how to make a few blips using a borrowed Sound Blaster card. I went to great lengths to learn how to program the Gravis Ultrasound.Oh you kids today, with your easy access to information at the tips of your fingers thanks to Google and the broader internet. I had to track down whatever information I could find through a combination of Prodigy message boards and local dialup BBSes and FidoNet message bases. Gravis was initially tight-lipped about programming information for its powerful card, as was de rigueur of hardware companies (something that largely persists to this day). But Gravis eventually saw an opportunity to one-up encumbent Creative Labs and released a full SDK for the Ultrasound. I wanted the SDK badly.
So it was early-mid 1993. Gravis released an SDK. I heard that it was available on their support BBS. Their BBS with a long distance phone number. If memory serves, the SDK was only in the neighborhood of 1.5 Mbytes. That takes a long time to transfer via a 2400 baud modem at a time when long distance phone charges were still a thing and not insubstantial.
Luckily, they also put the SDK on something called an ’FTP site’. Fortunately, about this time, I had the opportunity to get some internet access via the local university.
Indeed, my entire motivation for initially wanting to get on the internet was to obtain special programming information. Is that nerdy enough for you ?
I see that the GUS SDK is still available via the Gravis FTP site. The file GUSDK222.ZIP is dated 1998 and is less than a megabyte.
Next Generation : CD Support
So I had my original GUS by the end of 1992. That was just the first iteration of the Gravis Ultrasound. The next generation was the GUS MAX. When I was ready to get into the CD-ROM era, this was what I wanted in my computer. This is because the GUS MAX had CD-ROM support. This is odd to think about now when all optical drives have SATA interfaces and (P)ATA interfaces before that— what did CD-ROM compatibility mean back then ? I wasn’t quite sure. But in early 1995, I headed over to Computer City (R.I.P.) and bought a new GUS MAX and Sony double-speed CD-ROM drive to install in the family’s PC.
About the "CD-ROM compatibility" : It seems that there were numerous competing interfaces in the early days of CD-ROM technology. The GUS MAX simply integrated 3 different CD-ROM controllers onto the audio card. This was superfluous to me since the Sony drive came with an appropriate controller card anyway, though I didn’t figure out that the extra controller card was unnecessary until after I installed it. No matter ; computers of the day were rife with expansion ports.
The 3 different CD-ROM controllers on the GUS MAX
Explaining The Difference
It was difficult to explain the difference in quality to those who didn’t really care. Sometime during 1995, I picked up a quasi-promotional CD-ROM called "The Gravis Ultrasound Experience" from Babbage’s computer store (remember when that was a thing ?). As most PC software had been distributed on floppy discs up until this point, this CD-ROM was an embarrassment of riches. Tons of game demos, scene demos, tracker music, and all the latest GUS drivers and support software.Further, the CD-ROM had a number of red book CD audio tracks that illustrated the difference between Sound Blaster cards and the GUS. I remember loaning this to a tech-savvy coworker who disbelieved how awesome the GUS was. The coworker took it home, listened to it, and wholly agreed that the GUS audio sounded better than the SB audio in the comparison — and was thoroughly confused because she was hearing this audio emanating from her Sound Blaster. It was the difference between real-time and pre-rendered audio, I suppose, but I failed to convey that message. I imagine the same issue comes up even today regarding real-time video rendering vs., e.g., a pre-rendered HD cinematic posted on YouTube.
Regrettably, I can’t find that CD-ROM anymore which leads me to believe that the coworker never gave it back. Too bad, because it was quite the treasure trove.
Aftermath
According to folklore I’ve heard, Gravis couldn’t keep up as the world changed to Windows and failed to deliver decent drivers. Indeed, I remember trying to keep my GUS in service under Windows 95 well into 1998 but eventually relented and installed some kind of more appropriate sound card that was better supported under Windows.Of course, audio output capability has been standard issue for any PC for at least 10 years and many people aren’t even aware that discrete sound cards still exist. Real-time audio rendering has become less essential as full musical tracks can be composed and compressed into PCM format and delivered with the near limitless space afforded by optical storage.
A few years ago, it was easy to pick up old GUS cards on eBay for cheap. As of this writing, there are only a few and they’re pricy (but perhaps not selling). Maybe I was just viewing during the trough of no value a few years ago.
Nowadays, of course, anyone interested in studying the old GUS or getting a nostalgia fix need only boot up the always-excellent DOSBox emulator which provides remarkable GUS emulation support.
-
Android ffmpeg very slow to transcode
23 mars 2016, par NatIn Android phones (different phone models) it takes ffmpeg 5x the length of the video to transcode. A 1-minute video takes near 5 minutes to transcode. I have tried the following to improve performance and nothing has helped,
-b:v 16K to 1024K
-s 180x120 to 1920x1080
-preset ultrafast
-profile:v baseline
-r 24 to 100
maxrate 64K to 512K
rate 64K to 512K
-threads 0 to 16Nothing seems to help. Of course, some of them bring the speed up to 3x from 5x.
Please help as I have run out of options.
My current code is,
ffmpeg -y -i /storage/emulated/0/DCIM/Camera/VID_20150819_220414.mp4 -strict experimental -s 480x270 -vcodec libx264 -r 24 -c:a copy /storage/emulated/0/Android/data/<myapp>/cache/VID_-K-qMCldTSzZomKakNzq.mp4
</myapp>Console log -----
configuration: --arch=arm --cpu=cortex-a8 --target-os=linux --enable-runtime-cpudetect --prefix=/data/data/info.guardianproject.ffmpeg/app_opt --enable-pic --disable-shared --enable-static --cross-prefix=/home/n8fr8/dev/android/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/arm-linux-androideabi- --sysroot=/home/n8fr8/dev/android/ndk/platforms/android-16/arch-arm --extra-cflags='-I../x264 -mfloat-abi=softfp -mfpu=neon -fPIE -pie' --extra-ldflags='-L../x264 -fPIE -pie' --enable-version3 --enable-gpl --disable-doc --enable-yasm --enable-decoders --enable-encoders --enable-muxers --enable-demuxers --enable-parsers --enable-protocols --enable-filters --enable-avresample --enable-libfreetype --disable-indevs --enable-indev=lavfi --disable-outdevs --enable-hwaccels --enable-ffmpeg --disable-ffplay --disable-ffprobe --disable-ffserver --disable-network --enable-libx264 --enable-zlib
libavutil 51. 54.100 / 51. 54.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libavcodec 54. 23.100 / 54. 23.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libavformat 54. 6.100 / 54. 6.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libavdevice 54. 0.100 / 54. 0.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libavfilter 2. 77.100 / 2. 77.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libswscale 2. 1.100 / 2. 1.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libswresample 0. 15.100 / 0. 15.100
10-05 10:29:22.288: V/VideoEditor(7655): shellOut: libpostproc 52. 0.100 / 52. 0.100
10-05 10:29:22.740: V/VideoEditor(7655): shellOut: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/DCIM/Camera/VID_20151002_152817.mp4':
10-05 10:29:22.740: V/VideoEditor(7655): shellOut: Metadata:
10-05 10:29:22.741: V/VideoEditor(7655): shellOut: major_brand : mp42
10-05 10:29:22.741: V/VideoEditor(7655): shellOut: minor_version : 0
10-05 10:29:22.742: V/VideoEditor(7655): shellOut: compatible_brands: isommp42
10-05 10:29:22.742: V/VideoEditor(7655): shellOut: creation_time : 2015-10-02 22:29:32
10-05 10:29:22.743: V/VideoEditor(7655): shellOut: Duration: 00:01:14.13, start: 0.000000, bitrate: 17112 kb/s
10-05 10:29:22.745: V/VideoEditor(7655): shellOut: Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1920x1080, 16991 kb/s, SAR 65536:65536 DAR 16:9, 29.84 fps, 29.85 tbr, 90k tbn, 180k tbc
10-05 10:29:22.745: V/VideoEditor(7655): shellOut: Metadata:
10-05 10:29:22.747: V/VideoEditor(7655): shellOut: creation_time : 2015-10-02 22:29:32
10-05 10:29:22.748: V/VideoEditor(7655): shellOut: handler_name : VideoHandle
10-05 10:29:22.749: V/VideoEditor(7655): shellOut: Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono, s16, 96 kb/s
10-05 10:29:22.749: V/VideoEditor(7655): shellOut: Metadata:
10-05 10:29:22.750: V/VideoEditor(7655): shellOut: creation_time : 2015-10-02 22:29:32
10-05 10:29:22.751: V/VideoEditor(7655): shellOut: handler_name : SoundHandle
10-05 10:29:22.760: V/VideoEditor(7655): shellOut: [buffer @ 0xb5caa0a0] w:1920 h:1080 pixfmt:yuv420p tb:1/90000 sar:65536/65536 sws_param:flags=2
10-05 10:29:22.760: V/VideoEditor(7655): shellOut: [buffersink @ 0xb5caa0d0] No opaque field provided
10-05 10:29:22.802: V/VideoEditor(7655): shellOut: [scale @ 0xb5caa100] w:1920 h:1080 fmt:yuv420p sar:65536/65536 -> w:720 h:404 fmt:yuv420p sar:404/405 flags:0x4
10-05 10:29:22.803: V/VideoEditor(7655): shellOut: [libx264 @ 0xb5c28000] using SAR=1/1
10-05 10:29:22.818: V/VideoEditor(7655): shellOut: [libx264 @ 0xb5c28000] using cpu capabilities: ARMv6 NEON
10-05 10:29:22.904: V/VideoEditor(7655): shellOut: [libx264 @ 0xb5c28000] profile High, level 3.0
shellOut: [libx264 @ 0xb5c28000] 264 - core 125 r680+1521 37be552 - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=24 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=512 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
10-05 10:29:22.909: V/VideoEditor(7655): shellOut: Output #0, mp4, to '/storage/emulated/0/Android/data/com.myapp/cache/VID_-K-t2E4MtV_RTw4a1JXb.mp4':
10-05 10:29:22.910: V/VideoEditor(7655): shellOut: Metadata:
10-05 10:29:22.911: V/VideoEditor(7655): shellOut: major_brand : mp42
10-05 10:29:22.912: V/VideoEditor(7655): shellOut: minor_version : 0
10-05 10:29:22.913: V/VideoEditor(7655): shellOut: compatible_brands: isommp42
10-05 10:29:22.913: V/VideoEditor(7655): shellOut: creation_time : 2015-10-02 22:29:32
10-05 10:29:22.914: V/VideoEditor(7655): shellOut: encoder : Lavf54.6.100
10-05 10:29:22.916: V/VideoEditor(7655): shellOut: Stream #0:0(eng): Video: h264 (![0][0][0] / 0x0021), yuv420p, 720x404 [SAR 1:1 DAR 180:101], q=-1--1, 512 kb/s, 24 tbn, 24 tbc
10-05 10:29:22.916: V/VideoEditor(7655): shellOut: Metadata:
10-05 10:29:22.917: V/VideoEditor(7655): shellOut: creation_time : 2015-10-02 22:29:32
10-05 10:29:22.918: V/VideoEditor(7655): shellOut: handler_name : VideoHandle
10-05 10:29:22.919: V/VideoEditor(7655): shellOut: Stream #0:1(eng): Audio: aac (@[0][0][0] / 0x0040), 48000 Hz, mono, 96 kb/s
10-05 10:29:22.920: V/VideoEditor(7655): shellOut: Metadata:
10-05 10:29:22.921: V/VideoEditor(7655): shellOut: creation_time : 2015-10-02 22:29:32
10-05 10:29:22.922: V/VideoEditor(7655): shellOut: handler_name : SoundHandle
10-05 10:29:22.922: V/VideoEditor(7655): shellOut: Stream mapping:
10-05 10:29:22.923: V/VideoEditor(7655): shellOut: Stream #0:0 -> #0:0 (h264 -> libx264)
10-05 10:29:22.924: V/VideoEditor(7655): shellOut: Stream #0:1 -> #0:1 (copy)
10-05 10:29:22.924: V/VideoEditor(7655): shellOut: Press [q] to stop, [?] for help
10-05 10:29:23.637: V/VideoEditor(7655): shellOut: frame= 6 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate= 0.0kbits/s
10-05 10:29:24.205: V/VideoEditor(7655): shellOut: frame= 12 fps= 10 q=0.0 size= 0kB time=00:00:00.00 bitrate= 0.0kbits/s
10-05 10:29:24.735: I/chromium(7655): [INFO:CONSOLE(25)] "No Content-Security-Policy meta tag found. Please add one when using the cordova-plugin-whitelist plugin.", source: file:///android_asset/www/plugins/cordova-plugin-whitelist/whitelist.js (25)
10-05 10:29:24.756: V/VideoEditor(7655): shellOut: frame= 17 fps=9.8 q=0.0 size= 0kB time=00:00:00.00 bitrate= 0.0kbits/s dup=0 drop=1
10-05 10:29:25.327: V/VideoEditor(7655): shellOut: frame= 22 fps=9.5 q=0.0 size= 0kB time=00:00:00.00 bitrate= 0.0kbits/s dup=0 drop=2
10-05 10:29:25.904: V/VideoEditor(7655): shellOut: frame= 26 fps=9.1 q=0.0 size= 0kB time=00:00:00.00 bitrate= 0.0kbits/s dup=0 drop=4 -
Android : FFMpeg (video creation) crashes with no exception when loading binaries in lower APIs (18 in my case) but works in newer ones
6 mai 2019, par Diego PerezI have an app that uses FFMpeg for video creation (these next lines are the relevant build.gradle plugin files) :
//writingminds
api 'com.writingminds:FFmpegAndroid:0.3.2'
//JavaCV video
api group: 'org.bytedeco', name: 'javacv', version: '1.4.4'
api group: 'org.bytedeco.javacpp-presets', name: 'opencv', version: '4.0.1-1.4.4', classifier: 'android-arm'
api group: 'org.bytedeco.javacpp-presets', name: 'ffmpeg', version: '4.1-1.4.4', classifier: 'android-arm'And my app is working (and creating video) just fine in my phone with a newer Android 8 version but I’m having weird problems in my old API 18 tablet (where, as a note, I had to install multidex).
These next lines are the main part of FFMpeg video creation, where binaries are loaded, and, in fact, binaries load are where app crashes in my tablet in the line "
ffmpeg.loadBinary(new LoadBinaryResponseHandler()...
"As you can see, I have a try/catch where the app crashes, but it crashes with no aparent exception, as catch blocks are never hit.
public static String recordVideo(JSONObject objJSON) {
String strReturn = Enum.Result.OK;
try {
fileName = objJSON.has("file_name") ? String.valueOf(objJSON.getString("file_name")) : "";
videoPath = objJSON.has("video_path") ? String.valueOf(objJSON.getString("video_path")) : "";
} catch (JSONException e) {
ExceptionHandler.logException(e);
}
FFmpeg ffmpeg = FFmpeg.getInstance(ApplicationContext.get());
try {
ffmpeg.loadBinary(new LoadBinaryResponseHandler() {
@Override
public void onStart() {}
@Override
public void onFailure() {}
@Override
public void onSuccess() {}
@Override
public void onFinish() {}
});
} catch (FFmpegNotSupportedException e) {
// Handle if FFmpeg is not supported by device
} catch (Exception e) {
}
...These next lines are the relevant part of the LogCat, but I cannot figure out where the problem resides, maybe an out of memory problem ?
Any help will be much appreciated.
04-28 21:44:45.873 13743-13964/com.artandwords.thoughtoftheday A/libc: Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 13964 (AsyncTask #4)
04-28 21:44:45.973 144-144/? I/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-28 21:44:45.983 144-144/? I/DEBUG: Build fingerprint: 'asus/WW_epad/ME302C:4.3/JSS15Q/WW_epad-V5.0.21-20140701:user/release-keys'
04-28 21:44:45.983 144-144/? I/DEBUG: Revision: '0'
04-28 21:44:45.983 144-144/? I/DEBUG: pid: 13743, tid: 13964, name: AsyncTask #4 >>> com.artandwords.thoughtoftheday <<<
04-28 21:44:45.983 144-144/? I/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
04-28 21:44:46.003 144-144/? I/DEBUG: eax 00000000 ebx 000000c6 ecx 00000000 edx 00000000
04-28 21:44:46.003 144-144/? I/DEBUG: esi 00000e59 edi 00000000
04-28 21:44:46.003 144-144/? I/DEBUG: xcs 00000073 xds 0000007b xes 0000007b xfs 00000043 xss 0000007b
04-28 21:44:46.003 144-144/? I/DEBUG: eip 784ed378 ebp 2200ff0c esp 2200fec4 flags 00210246
04-28 21:44:46.003 144-144/? I/DEBUG: backtrace:
04-28 21:44:46.003 144-144/? I/DEBUG: #00 pc 00087378 /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.003 144-144/? I/DEBUG: #01 pc 00085d0e /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.003 144-144/? I/DEBUG: #02 pc 00073328 /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.003 144-144/? I/DEBUG: #03 pc 0006f7ff /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.003 144-144/? I/DEBUG: #04 pc 0006f3bf /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.003 144-144/? I/DEBUG: #05 pc 000b92de /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.003 144-144/? I/DEBUG: #06 pc ffffffff <unknown>
04-28 21:44:46.003 144-144/? I/DEBUG: #07 pc 001445aa /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.013 144-144/? I/DEBUG: stack:
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436850 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436854 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436858 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b43685c 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436860 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436864 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436868 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b43686c 3822676c /system/lib/arm/libc.so
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436870 7b436a98
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436874 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436878 7b4368c8
04-28 21:44:46.013 144-144/? I/DEBUG: 7b43687c 7b436a98
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436880 383003a0 /system/lib/arm/libdl.so
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436884 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436888 7b4368c8
04-28 21:44:46.013 144-144/? I/DEBUG: 7b43688c 785aa5ab /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.013 144-144/? I/DEBUG: #07 7b436890 7b4368a0
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436894 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b436898 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b43689c 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368a0 7b4368c8
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368a4 7b436890
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368a8 785aa59d /system/lib/libhoudini.so.3.4.7.44914
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368ac 7b436a98
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368b0 7b437930
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368b4 220001d0
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368b8 7b436a70
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368bc 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368c0 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368c4 00000000
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368c8 7b436a88
04-28 21:44:46.013 144-144/? I/DEBUG: 7b4368cc 785f3141 /system/lib/libhoudini.so.3.4.7.44914
--------- beginning of /dev/log/system
04-28 21:44:46.063 450-470/? I/BootReceiver: Copying /data/tombstones/tombstone_03 to DropBox (SYSTEM_TOMBSTONE)
04-28 21:44:46.063 450-13973/? W/ActivityManager: Force finishing activity com.artandwords.thoughtoftheday/.activities.DisplayThoughtActivity
04-28 21:44:46.073 145-862/? E/IMGSRV: :0: PVRDRMOpen: TP3, ret = 75
04-28 21:44:46.093 450-13973/? E/JavaBinder: !!! FAILED BINDER TRANSACTION !!!
04-28 21:44:46.093 450-483/? W/InputDispatcher: channel '21edd9e8 com.artandwords.thoughtoftheday/com.artandwords.thoughtoftheday.activities.main.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
04-28 21:44:46.093 450-483/? E/InputDispatcher: channel '21edd9e8 com.artandwords.thoughtoftheday/com.artandwords.thoughtoftheday.activities.main.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
04-28 21:44:46.093 155-13945/? W/TimedEventQueue: Event 25 was not found in the queue, already cancelled?
04-28 21:44:46.093 155-3134/? W/AudioFlinger: session id 324 not found for pid 155
04-28 21:44:46.103 450-450/? W/InputDispatcher: Attempted to unregister already unregistered input channel '21edd9e8 com.artandwords.thoughtoftheday/com.artandwords.thoughtoftheday.activities.main.MainActivity (server)'
04-28 21:44:46.103 450-755/? I/WindowState: WIN DEATH: Window{21b33a28 u0 com.artandwords.thoughtoftheday/com.artandwords.thoughtoftheday.activities.DisplayThoughtActivity}
04-28 21:44:46.103 450-13973/? W/ActivityManager: Exception thrown during pause
android.os.TransactionTooLargeException
at android.os.BinderProxy.transact(Native Method)
at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:642)
at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:1007)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:3905)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:3837)
at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:8588)
at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:8465)
at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:9170)
at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:8699)
at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
04-28 21:44:46.103 450-450/? I/WindowState: WIN DEATH: Window{21edd9e8 u0 com.artandwords.thoughtoftheday/com.artandwords.thoughtoftheday.activities.main.MainActivity}
04-28 21:44:46.103 450-636/? I/WindowState: WIN DEATH: Window{21be0690 u0 com.artandwords.thoughtoftheday/com.artandwords.thoughtoftheday.activities.DisplayThoughtActivity}
04-28 21:44:46.113 450-13973/? I/WindowManager: computeScreenConfigurationLocked() Enter {1.15 ?mcc?mnc ?locale ?layoutDir ?swdp ?wdp ?hdp ?density ?lsize ?long ?orien ?uimode ?night ?touch ?keyb/?/? ?nav/?}
04-28 21:44:46.113 450-13973/? I/WindowManager: dw=1200, dh=1920
04-28 21:44:46.113 450-13973/? I/WindowManager: appWidth=1200, appHeight=1848
04-28 21:44:46.113 450-13973/? I/WindowManager: tempdm=DisplayMetrics{density=1.5, width=1200, height=1848, scaledDensity=1.5, xdpi=221.201, ydpi=220.591}
04-28 21:44:46.113 450-13973/? I/WindowManager: dm=DisplayMetrics{density=1.5, width=1200, height=1848, scaledDensity=1.5, xdpi=221.201, ydpi=220.591}, ro.product.device=ME302C
04-28 21:44:46.113 450-13973/? I/WindowManager: getConfigDisplayWidth=1200, getConfigDisplayHeight=1810
04-28 21:44:46.113 450-13973/? I/WindowManager: screenWidthDp=800, screenHeightDp=1206
04-28 21:44:46.113 450-13973/? I/WindowManager: computeScreenConfigurationLocked() Leave {1.15 ?mcc?mnc ?locale ?layoutDir sw800dp w800dp h1206dp 240dpi xlrg port ?uimode ?night finger -keyb/v/h -nav/h}
04-28 21:44:46.113 450-13973/? I/ActivityManager: Restarting because process died: ActivityRecord{21ab1f80 u0 com.artandwords.thoughtoftheday/.activities.main.MainActivity}
04-28 21:44:46.113 450-13973/? W/ActivityManager: Exception when starting activity com.artandwords.thoughtoftheday/.activities.main.MainActivity
android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.app.ApplicationThreadProxy.scheduleLaunchActivity(ApplicationThreadNative.java:730)
at com.android.server.am.ActivityStack.realStartActivityLocked(ActivityStack.java:733)
at com.android.server.am.ActivityStack.startSpecificActivityLocked(ActivityStack.java:840)
at com.android.server.am.ActivityStack.resumeTopActivityLocked(ActivityStack.java:1790)
at com.android.server.am.ActivityStack.resumeTopActivityLocked(ActivityStack.java:1449)
at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:1058)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:3905)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:3837)
at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:8588)
at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:8465)
at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:9170)
at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:8699)
at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
04-28 21:44:46.123 450-13973/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1396 com.android.server.am.ActivityStack.sendActivityBroadcastLocked:4923 com.android.server.am.ActivityStack.removeActivityFromHistoryLocked:4089 com.android.server.am.ActivityStack.removeHistoryRecordsForAppLocked:4346 com.android.server.am.ActivityManagerService.handleAppDiedLocked:3163
04-28 21:44:46.123 450-13973/? I/ActivityManager: Start proc com.artandwords.thoughtoftheday for activity com.artandwords.thoughtoftheday/.activities.main.MainActivity: pid=13975
</unknown>Edit 1 :
Still investigating and entered FFmpeg.java to the method loadBinary while debugging, which code I’ll paste below and the line making the crash is switch (CpuArchHelper.getCpuArch())
@Override
public void loadBinary(FFmpegLoadBinaryResponseHandler ffmpegLoadBinaryResponseHandler) throws FFmpegNotSupportedException {
String cpuArchNameFromAssets = null;
switch (CpuArchHelper.getCpuArch()) {
case x86:
Log.i("Loading FFmpeg for x86 CPU");
cpuArchNameFromAssets = "x86";
break;
case ARMv7:
Log.i("Loading FFmpeg for armv7 CPU");
cpuArchNameFromAssets = "armeabi-v7a";
break;
case NONE:
throw new FFmpegNotSupportedException("Device not supported");
}
if (!TextUtils.isEmpty(cpuArchNameFromAssets)) {
ffmpegLoadLibraryAsyncTask = new FFmpegLoadLibraryAsyncTask(context, cpuArchNameFromAssets, ffmpegLoadBinaryResponseHandler);
ffmpegLoadLibraryAsyncTask.execute();
} else {
throw new FFmpegNotSupportedException("Device not supported");
}
}I’ll keep on investigating...
Edit 2 :
Further debugging has just lead me to the exact line where app crashes, and it’s CpuArchHelper.java from FFmpeg library :
The line causing the crash is the next :
String archInfo = cpuNativeArchHelper.cpuArchFromJNI();
and I cannot even go inside cpuArchFromJNI() with F7 as it just crashes.
package com.github.hiteshsondhi88.libffmpeg;
import android.os.Build;
class CpuArchHelper {
static CpuArch getCpuArch() {
Log.d("Build.CPU_ABI : " + Build.CPU_ABI);
// check if device is x86 or x86_64
if (Build.CPU_ABI.equals(getx86CpuAbi()) || Build.CPU_ABI.equals(getx86_64CpuAbi())) {
return CpuArch.x86;
} else {
// check if device is armeabi
if (Build.CPU_ABI.equals(getArmeabiv7CpuAbi())) {
ArmArchHelper cpuNativeArchHelper = new ArmArchHelper();
String archInfo = cpuNativeArchHelper.cpuArchFromJNI();
// check if device is arm v7
if (cpuNativeArchHelper.isARM_v7_CPU(archInfo)) {
// check if device is neon
return CpuArch.ARMv7;
}
// check if device is arm64 which is supported by ARMV7
} else if (Build.CPU_ABI.equals(getArm64CpuAbi())) {
return CpuArch.ARMv7;
}
}
return CpuArch.NONE;
}
static String getx86CpuAbi() {
return "x86";
}
static String getx86_64CpuAbi() {
return "x86_64";
}
static String getArm64CpuAbi() {
return "arm64-v8a";
}
static String getArmeabiv7CpuAbi() {
return "armeabi-v7a";
}
}This is ArmArchHelper.java class :
package com.github.hiteshsondhi88.libffmpeg;
class ArmArchHelper {
static {
System.loadLibrary("ARM_ARCH");
}
native String cpuArchFromJNI();
boolean isARM_v7_CPU(String cpuInfoString) {
return cpuInfoString.contains("v7");
}
boolean isNeonSupported(String cpuInfoString) {
// check cpu arch for loading correct ffmpeg lib
return cpuInfoString.contains("-neon");
}
}Edit 3 :
Reading carefully LogCat I’ve noticed there is a TransactionTooLarge Exception :
04-28 21:44:46.103 450-13973/? W/ActivityManager: Exception thrown during pause
android.os.TransactionTooLargeException
at android.os.BinderProxy.transact(Native Method)
at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:642)
at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:1007)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:3905)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:3837)
at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:8588)
at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:8465)
at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:9170)
at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:8699)
at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)Maybe this is what makes my app to crash, but I don’t know what to do with that, as it happens inside the FFMpeg library :s
Edit 3 :
As a note, I’ve tried in an old Android 4.2.2 (API 17) phone I also own and it’s working just fine, the video is generated without crashing.