Closed (won't fix)
Project:
Blue Droplet Video
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
8 May 2009 at 17:32 UTC
Updated:
14 Nov 2010 at 18:05 UTC
Hi everyone.
Well here is my problem.
My website is hosted on Dreamhost. Dreamhost supports FFMpeg natively, and lets its users to compile their own versions.
See : http://wiki.dreamhost.com/FFmpeg
Blue Droplet doesn't recognize the path to my FFmpeg-directory.
I always get this error: FFmpeg not available - transcoding will fail.
I'm sure about the path I used, as it works with other modules.
I tried strings like : (I carefully replaced 'username' with my real username :))
home/username/bin/ffmpeg
/home/username/bin/ffmpeg
home/username/bin/ffmpeg
/home/username/bin/ffmpeg
Any help would be great! Thank you!
Julien
Comments
Comment #1
dmjossel commentedThe same here.
When I do "which ffmpeg" I get:
/usr/bin/ffmpeg
I put this path in BD's configuration and I still get the message:
FFmpeg not available - transcoding will fail.
Comment #2
dmjossel commentedHere's the output of ffmpeg -version and ffmpeg -formats:
Comment #3
dmjossel commentedI'll continue to add more information in the hopes that it will help.
On each of three systems I've tried (OS X 10.5, Ubuntu 8.04 and FreeBSD 4) the version of FFmpeg installed according to BD's instructions works under Drupal 5.x and version 2.6 of the OpenPackage video modules. I've built ffmpeg from trunk, installed a static version specifically for OS X and Ubuntu, and installed from the Medibuntu repository. All produce the same result.
Upgrading to 3.x and higher, either under Drupal 5.x or 6.x, produces the "FFmpeg not available" error, regardless of the version of FFmpeg installed, the host OS, or the permissions of the target executable.
I tried using Deadwood to port the 2.6 version of OpenPackage to Drupal 6.x but so far I've had little success (perhaps to be expected).
Is there something that changed between 2.6 and 3.x of the op_video / bd_video modules where the former would regard a particular version of FFmpeg as acceptable where the latter will not?
Will the module attempt to transcode even if the admin page shows the "not available" error? Should I just attempt to disable the error checking?
Attempting to configure the module and attempting to transcode video put no entries I can see either into watchdog, php's error log, apache's error log, or the system's messages log. Is there anywhere else I should be looking for more specific information about why FFmpeg is classified "not available" when I can easily find it from the CLI and use it without problem?
Comment #4
dmjossel commentedJust another note-- the same compiled FFMpeg binary reported "unavailable" by bd_video is usable by FFMpeg Wrapper, on the same machine, on the same site, at the same path.
Comment #5
nikolaynag commentedI've the same problem on Ubuntu 8.04 with default ffmpeg installation. I readed bd_video code and found out that it reports "FFmpeg not available - transcoding will fail." just when "ffmpeg -version" command exits with nonzero status. I checked it by bash - ffmpeg really exits with exit code 1!
Then I downloaded source code for ffmpeg with apt-src command. There is a function named "show_version" and in this function i found "exit(1)". This is definitely bug in ffmpeg and in fresh version, that I downloaded from svn it is already fixed. It is also fixed in version, that comes in Ubuntu 9.04.
Comment #6
dmjossel commentedYes I read in many places that the default version of ffmpeg in Ubuntu, especially older ones, doesn't work. However, in this case, bd_video claims "unavailable" even when it does work, when it gives the proper output to ffmpeg -version and ffmpeg -formats (as above) and when it works fine in other modules, such as the 5.x-2.6 version of bd/op_video, and FFMpegWrapper.
In short, this is not a bug in FFMpeg, because in versions of the executable that support all required features and do not exit when giving the -version command, still claims FFmpeg is "unavailable".
I've actually now moved to Media Mover and Embedded Media Field and the same FFMpeg executable, at the same path, works fine with it.
Is this module still being actively developed? I cross-posted this in their support forum last week; no replies as of yet. In fact it's been about two months since the developers made any reply to a forum post, and longer since they answered one that was not related to using the bluedroplet.com service as part of the module.
Comment #7
nikolaynag commentedI don't know about activity in developing of blue droplet, I've tryed it yesterday first time. But it can not find ffmpeg exactly because of bug (look https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/380165). The problem is not in ffmpeg -version output, but in ffmpeg -version return value. You can point it out by using echo $? in bash:
Normal program must return 0 if there is no errors, as for example ls does:
Different modules can use different mechanisms for cheching ffmpeg, so they can work fine.
Comment #8
dmjossel commentedAh, I see what you're saying now. Thanks for that.
Has this been in FFmpeg long?
I first installed op_video 2.6 almost a year ago with a copy of FFMpeg compiled at that time, and the latest bd_video failed with that version, also. That was on Mac OS X 10.4. Don't remember the FFmpeg version, and now I've gotten rid of it and compiled from source anyway.
This error, if it is indeed the cause of bd_video's "FFmpeg not available" response, is also present at least in FFmpegX 0.9x and 0.9y, as well as Medibuntu's package.
Although the real bug here may be in FFmpeg I still think bd_video is being too pedantic in this case. None of the other wrapper modules seem to check for this, and it seems conceivable to me that FFmpeg could be in a state that legitimately would report an exit state (1) due to some missing libraries, but this might not have directly affected the particular requirements of bd_video. If ffmpeg was not in the path, then I could see "FFmpeg not available" being a proper response, but a response to exit(1) should be something else. At least it would have made it easier to track down.
Comment #9
dmjossel commentedChanging to "feature request" to reflect a suggested change in bd_video's handling of response codes from ffmpeg -version rather than an actual bug.
Comment #10
dmjossel commentedComment #11
jbrown commentedIf you are using FFmpeg, then you should use the latest version (currently 0.5).
Typically you want to hand compile it, along with libx264, faac and other codecs to get maximum codec support.
Note that the FFmpeg interrogation on the admin page is just informative. If you think it is wrong, just go ahead and try a transcoding.
Comment #12
jbrown commented