5 Pints of Stout
You're getting that error because libx264 is an encoder, not a decoder:Originally Posted by TwistedNRG
The EV indicates that libx264 is an Encoder, Video Format. The H.264 decoder is called h264.Code:$ ffmpeg -formats | grep libx264 EV libx264 libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
First Cup of Ubuntu
oh ok I didn't realize that was the case. Thanks a lot
First Cup of Ubuntu
new error ...
I am using the following command to decode a video ..
ffmpeg -r 30 -vcodec h264 -s 480x320 -f video4linux -i /home/phil/Desktop/iphone.avi http://localhost:8090/broadcast_feed.ffm
and I get the following error when I add in -f video4linux flag .. if I take that flag out there are no errors...
FFmpeg version SVN-r19605, Copyright (c) 2000-2009 Fabrice Bellard, et al.
configuration: --enable-gpl --enable-nonfree --enable-pthreads --enable-libfaac --enable-libfaad --enable-libmp3lame --enable-libx264
libavutil 50. 3. 0 / 50. 3. 0
libavcodec 52.32. 0 / 52.32. 0
libavformat 52.37. 0 / 52.37. 0
libavdevice 52. 2. 0 / 52. 2. 0
libswscale 0. 7. 1 / 0. 7. 1
built on Aug 6 2009 13:44:14, gcc: 4.1.3 20080623 (prerelease) (Ubuntu 4.1.2-24ubuntu1)
[video4linux @ 0xa684450]VIDIOCGCAP: Inappropriate ioctl for device
/home/phil/Desktop/iphone.avi: I/O error occurred
Usually that means that input file is truncated and/or corrupted.
any help is greatly appreciated. Thank you.
5 Pints of Stout
You can use FFmpeg to encode your video to H.264/AAC MP4, upload it to your server, and use a Flash player such as JW Player or Flowplayer to display your video to your audience. Here is a very simple example with no player controls.
Alternatively, you can use "YouTube Clones" like VidiScript or PHPmotion, but I have absolutely no experience with them and I'm not sure if they even use FFmpeg.
5 Pints of Stout
This looks more like a video4linux issue, but I've only used it once myself. I recommend heading to the #ffmpeg IRC channel and asking there. Make sure to pastebin your full command and full FFmpeg output when asking questions. If that fails to give an answer you can try the ffmpeg-user mailing list. Maybe someone with more experience with video4linux can help you.
First Cup of Ubuntu
Ok great, thanks a lot. I shall do just that.
First Cup of Ubuntu
Hi
Sametime with this command
I get this error:Code:ffmpeg -i myfile -acodec libfaac -ab 128k -ac 2 -vcodec libx264 -vpre hq -crf 22 -threads 0 test.1.mp4
[libx264 @ 0x2a21280]b-pyramid + mb-tree is not supported
[libx264 @ 0x2a21280]using SAR=1/1
[libx264 @ 0x2a21280]using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
[libx264 @ 0x2a21280]profile High, level 3.1
Output #0, mp4, to 'test.1.mp4':
Stream #0.0(und): Video: libx264, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], q=10-51, 200 kb/s, 25 tbn, 25 tbc
Stream #0.1(und): Audio: aac, 48000 Hz, 2 channels, s16, 128 kb/s
Stream mapping:
Stream #0.0 -> #0.0
Stream #0.1 -> #0.1
Press [q] to stop encoding
x264 [error]: malloc of size 4214784 failedtime=1.05 bitrate= 0.4kbits/s
Video encoding failed
5 Pints of Stout
You have encountered a new error. x264 has a new option: mb-tree. This option is going to dramatically increase video quality of some sources, but it is very new and there are some problems to be aware of:
1. For now it is incompatible with the b-pyramid option. Some -vpre presets currently enable b-pyramid, and mb-tree is enabled by default and causes your error. You can disable b-pyramid by adding -flags2 -bpyramid after -vpre hq:
Right now the option to disable mb-tree hasn't been mapped to FFmpeg yet, but it should be soon.Code:ffmpeg -i myfile -acodec libfaac -ab 128k -ac 2 -vcodec libx264 -vpre hq -flags2 -bpyramid -crf 22 -threads 0 test.1.mp4
2. The mb-tree option currently does a bad job with fades (video going to or from light and black) and makes them look blocky, but this is being worked on.[see post below]
When using the latest FFmpeg and x264 you get the advantage of bugfixes and recent additions, but once in a while you will encounter errors as new features are introduced. This is an exciting new option and should be watched closely. More info:
x264 "Macroblock Tree Ratecontrol" testing (committed)
A tree of thought
Update: This is the more important error:
I am guessing that you ran out of memory because of mb-tree. You can either wait until you can disable mb-tree through FFmpeg, or revert to an earlier x264 before that option was enabled by default (revision 1196 and earlier).Code:x264 [error]: malloc of size 4214784 failedtime=1.05 bitrate= 0.4kbits/s Video encoding failed
Last edited by FakeOutdoorsman; August 17th, 2009 at 06:48 PM.
5 Cups of Ubuntu
That's not an error; x264 will simply disable B-pyramid if it's on and MB-tree isn't turned off.
Don't spread misinformation; if such a problem existed, I wouldn't have committed MB-tree. MB-tree simply doesn't help fades, so it's possible for them to look relatively worse if the rest of the video got a lot better.
Or encode at a lower resolution, or upgrade to 64-bit.
That error seems odd, since I can encode 1080p with -vpre hq just fine on 32-bit Windows despite the overhead of Avisynth input, so I suspect something may be weird/broken on your end, like a miscompiled ffmpeg and rc-lookahead being set to a very large value (you can tell how large rc-lookahead is by the number of frames x264 buffers before it starts encoding).
Additionally note that the malloc-checking was added only recently; prior to that, x264 would have just silently crashed.
Last edited by Dark Shikari; August 14th, 2009 at 08:32 PM.
5 Pints of Stout
I stand corrected. I shouldn't believe everything I read in #ffmpeg.
Adv Reply
Bookmarks