I know there are other threads referencing this error, but they seem to be dealing with malformed URLs using Flowplayer or with providing a direct path to ffmpeg for transcoding - neither is applicable in my case.

I am successfully encoding mp4, Flash and .ogv, using modified presets.

For mp4 (one-pass - two-pass encoding preset doesn't work):

!cmd_path -i !videofile -vcodec libx264 -vpre medium -b 500k -acodec libfaac -ab 128k -ac 2 -crf 22 -threads 0 !convertfile

For Flash (slightly better fidelity - not done here yet):

!cmd_path -i !videofile -s !widthx!height -r 15 -b 500 -ar 44100 -ab 48 !convertfile

With these two only, the video plays fine with Flowplayer 3 via SWF Tools (with patch and newest js files for iPad/iPhone) - only problem here is that in iPhone, the video uses QT player, starts automatically and controls don't work. Not acceptable. VideoJS Player fails entirely.

So we need ogv/ogg.

.ogv preset doesn't work; here's what does:

!cmd_path -i !videofile -vcodec libtheora -b 2000k -acodec libvorbis -ac 2 -ab 128k !convertfile

But this generates the following error (in all players) - no video plays anywhere:

200, Stream not found, NetStream.Play.StreamNotFound, clip: '[Clip] 'http://[base_url]/[subdirectory]/sites/default/files/videos/converted/test_vid.ogv''

The file, indeed, exists exactly where it's supposed to be - correctly encoded and no malformed URL - so I'm stumped here. Has anybody gotten this to work? Any help much appreciated...

Comments

bcobin’s picture

bcobin commented

I think I may have found a possible cause - I'm on Mac OSX 10.4.11 (hey, if it ain't broke...) and it looks like a system library is incompatible with ogg/ogv encoding with ffmpeg2theora. Running ffmpeg2theora from command line produces the following:

$ ffmpeg2theora
dyld: Library not loaded: /usr/lib/libiconv.2.dylib
Referenced from: /usr/local/bin/ffmpeg2theora
Reason: Incompatible library version: ffmpeg2theora requires version 7.0.0 or later, but libiconv.2.dylib provides version 5.0.0
Trace/BPT trap

Trying to upgrade the library in question hosed my system - it looks like I'll have to upgrade to 10.5. The disk is on the way, I'll deal with it this weekend and report back. This doesn't necessarily explain the direct ffmpeg ogg/ogv encoding issue, but if ffmpeg2theora works, that's just fine with me.

Hoping this may prove helpful to others who may run into this.

bcobin’s picture

bcobin commented

OK - I did the upgrade to 10.5 (it took me two full days to get my server environment working again) - I did this for one reason: to see if ffmpeg2theora encoding would solve this problem.

It doesn't. I get the same error message.

The good news is that the ffmpeg2theora encoding seems to work nicely (you need to change the preset to point to /usr/local/bin/ffmpeg2theora on my system). The converted file looks and sounds fine when played in VLC. And the HTML 5 player doesn't play either, so it's not an SWF Tools issue. It has to do with how Video is handling .ogg/.ogv files.

Any ideas here? I literally have spent months trying to solve this - has anyone been seeing the same problem?

(BTW - I see a lot of similar posts where a "solution" is presented by putting a direct path to ffmpeg.exe in the preset. Not only would this be applicable only to people running Windoze boxes, it does not fix the problem; my transcoding now works fine.)

Assistance greatly appreciated... thanks!

Jorrit’s picture

Jorrit commented
Status: Active » Postponed (maintainer needs more info)

Is this problem still present?

bcobin’s picture

bcobin commented

This issue evidently related to my own server environment - on a "real" host, I was able to get ffmpeg2theora working.

Actually getting everything to play properly in iPhone, though, is another story, but insofar as that doesn't directly relate, you can consider this issue "solved," I guess - at last as far as I'm concerned.

Thanks for checking in, Joritt!

Jorrit’s picture

Jorrit commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Thanks for your replies. If this issue appears again on an environment that's currently functional, please reopen or open a new issue.