The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Three problems here; they may be related:
1. FFMPEG throws invalid parameter error as below:
export MALLOC_CHECK_=1; ffmpeg -v 0 -y -i 'sites/default/files/storage2/1' -f flv -vcodec flv -b k -r -g 0 -s 0x0 -an -pass 1 -passlogfile /home/[sitename]/public_html/sites/default/files/temp/qe7Ytn /home/ackerman/public_html/sites/default/files/temp/GDCeUk 2>&1 malloc: using debugging hooks FFmpeg version SVN-r20882, Copyright (c) 2000-2009 Fabrice Bellard, et al. built on Dec 16 2009 10:51:32 with gcc 4.1.2 20080704 (Red Hat 4.1.2-46) configuration: --enable-libmp3lame --disable-mmx --enable-shared --enable-gpl --enable-postproc --enable-nonfree --enable-postproc --enable-libfaad --enable-avfilter --enable-pthreads --enable-libxvid --enable-libx264 --enable-libfaac --disable-ffserver --disable-ffplay --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb libavutil 50. 7. 0 / 50. 7. 0 libavcodec 52.43. 0 / 52.43. 0 libavformat 52.43. 0 / 52.43. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter 1.12. 0 / 1.12. 0 libswscale 0. 7. 2 / 0. 7. 2 libpostproc 51. 2. 0 / 51. 2. 0 Seems stream 1 codec frame rate differs from container frame rate: 1000.00 (1000/1) -> 30.00 (30/1) Input #0, asf, from 'sites/default/files/storage2/1': Metadata: Application : Windows Movie Maker 2.1.4026.0 ParentalRating : WMFSDKVersion : 10.00.00.4332 WMFSDKNeeded : 0.0.0.0000 IsVBR : 0 title : author : copyright : comment : Duration: 00:00:11.63, start: 5.000000, bitrate: 333 kb/s Stream #0.0(eng): Audio: wmav2, 32000 Hz, 2 channels, s16, 32 kb/s Stream #0.1(eng): Video: wmv3, yuv420p, 320x240, 272 kb/s, 30 tbr, 1k tbn, 1k tbc [NULL @ 0x8972020]Unable to parse option value "k": undefined constant or missing ( Invalid value 'k' for option 'b'
2. Transcoding was set to FLV and saved; settings still indicate MP4 (although it seems like FLV was, indeed, invoked.) Similarly, Maximum video height setting indicates 640 pixels, even though 480 pixels was the saved value. So it looks like settings aren't "sticking."
3. Status report indicates the following - this looks like it all may be related.
warning: Division by zero in /home/[sitename]/public_html/sites/all/modules/bd_video/includes/ffmpeg.inc on line 489.
Conversion failed.
Line 489 is: if($dirty_params['width'] / $dirty_params['height'] > $info['width'] / $info['height']) {
On a brighter note, the Illegal Offset errors seem to be fixed in the latest dev versions of Storage API.
Comments
Comment #1
bcobin commentedHas there been any progress here? I've had to fall back to a different video encoding system (I won't say which) and I miss my BDV!
Anxiously awaiting... thanks!
Comment #2
bcobin commentedPoking around to see what the problem might be and I came across what looks like an error in transcoder.inc on line 145.
I'm pretty sure it should be BD_VIDEO_DEFAULT_HEIGHT instead of WIDTH.
That's not my main problem, though - in looking at the error I'm getting, it looks like the VBITRATE value (the -b switch) isn't getting passed through, so all we're left with is the 'k' appended to a non-existent value.
Command:
export MALLOC_CHECK_=1; ffmpeg -v 0 -y -i 'sites/default/files/storage2/2' -f flv -vcodec flv -b k -r -g 0 -s 0x0 -an -pass 1 -passlogfile...The bitrate command should be -b 320k, I would assume.
So we end up with:
Unable to parse option value "k": undefined constant or missing ( Invalid value 'k' for option 'b'Which makes total sense if the VBITRATE value fails to be set.
Any ideas would be greatly appreciated - BDV is the best thing out there when it's working!
After further investigation: The bd_video_params table is empty, so I can confirm settings are not being saved to the database - FFMPEG is running with the default parameters and a valid video bitrate isn't being sent. Hope this helps in narrowing things down.
Comment #3
jbrown commentedhttp://drupal.org/cvs?commit=307422
Comment #4
bcobin commentedBrilliant! Everything works again - thanks much! I'll note here that caches must be aggressively cleared and you may have to delete cron_semaphore to reset cron in case it got "stuck" along the way, but we are back in business!
Great work!