x264 LAVF/FFMS input public beta test (v2.1) - Page 7

Darkwhisperer · 3rd February 2010, 13:17

If your'll don't mind my asking, how are the tests going? Is there a planned release date perhaps?

J_Darnley · 3rd February 2010, 13:47

Why does something that was committed need updating?

burfadel · 3rd February 2010, 15:09

The all-in-one x264 is a great idea, however it does rely on a third party decoder that is under continual development. Since the third party tool is under continual development x264 will need to have that component continually updated to include the features added/fixed in the third party provision. The solution would be to simply update those components each time x264 components are updated, in order to stay current.

smok3 · 14th February 2010, 21:06

do we have osx and/or ubuntu-karmic builds?

Audionut · 15th February 2010, 02:59

Quote:

Originally Posted by smok3

do we have osx and/or ubuntu-karmic builds?

http://doom10.org/index.php?topic=3.0

hajj_3 · 16th February 2010, 13:09

Does this mean we could have a 64bit of MeGUI and use a 64bit of x264.exe with LAVF/FFMS integrated into it? Do we know what kind of speed improvements we would get using this x264 beta compared to using regular x264.exe and avisynth 2.5.8 or 2.6.0 MT alpha?

Blue_MiSfit · 16th February 2010, 13:17

I'm having great results with these new features! I've been doing lots of high speed transcodes of my movie / TV backups to baseline profile H.264 (for the iPhone).

Being able to directly open files in x264 without help from AviSynth, all in "pure" 64 bit is extremely convenient, and is pretty durn cool too

~MiSfit

rack04 · 16th February 2010, 16:42

I'm trying to mux a 264 stream generated by x264 using LAVF as the input method. The source file is mov. When I try to mux to mkv using eac3to it complains that the stream does not contain fps information. Is this intentional or a bug? Using avs input the file muxes without error. I am using this build.

Here is a sample, x264 stats, and vui_parameters:

Code:

ffms [info]: 848x480p 0:1 @ 24000/1001 fps (vfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
x264 [info]: profile High, level 3.1
x264 [info]: frame I:51    Avg QP:18.35  size: 41968
x264 [info]: frame P:1235  Avg QP:23.91  size:  8045
x264 [info]: frame B:2309  Avg QP:28.10  size:  2366
x264 [info]: consecutive B-frames:  6.5% 18.9%  6.3% 63.8%  2.0%  2.5%
x264 [info]: mb I  I16..4: 31.8% 18.9% 49.2%
x264 [info]: mb P  I16..4:  8.4%  8.3%  3.9%  P16..4: 22.0%  8.9%  4.6%  0.0%  0.0%    skip:43.9%
x264 [info]: mb B  I16..4:  0.8%  1.5%  1.0%  B16..8: 20.0%  1.4%  1.6%  direct: 1.6%  skip:72.1%  L0:39.1% L1:47.7% BI:13.2%
x264 [info]: 8x8 transform intra:38.7% inter:59.2%
x264 [info]: direct mvs  spatial:99.3% temporal:0.7%
x264 [info]: coded y,uvDC,uvAC intra: 48.0% 59.4% 29.1% inter: 7.3% 10.9% 3.6%
x264 [info]: i16 v,h,dc,p: 44% 27% 11% 18%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 17% 19% 18%  6%  7%  8%  8%  7% 10%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19% 20% 11%  6%  9%  8%  9%  7% 10%
x264 [info]: Weighted P-Frames: Y:7.9%
x264 [info]: ref P L0: 72.3%  9.1%  9.2%  2.9%  2.6%  1.5%  1.0%  0.5%  0.5%  0.4%  0.0%  0.0%
x264 [info]: ref B L0: 90.8%  4.4%  2.1%  0.9%  0.6%  0.5%  0.4%  0.2%  0.1%
x264 [info]: ref B L1: 98.5%  1.5%
x264 [info]: kb/s:935.79

encoded 3595 frames, 10.60 fps, 935.79 kb/s

Code:

   vui_parameters_present_flag: 1
    aspect_ratio_info_present_flag: 0
    overscan_info_present_flag: 0
    video_signal_info_present_flag: 0
    chroma_loc_info_present_flag: 0
    timing_info_present_flag: 1
     num_units_in_tick: 1
     time_scale: 5994
     fixed_frame_scale: 0
    nal_hrd_parameters_present_flag: 0
    vcl_hrd_parameters_present_flag: 0
    pic_struct_present_flag: 0
    motion_vectors_over_pic_boundaries_flag: 1
    max_bytes_per_pic_denom: 0
    max_bits_per_mb_denom: 0
    log2_max_mv_length_horizontal: 11
    log2_max_mv_length_vertical: 11
    num_reorder_frames: 2
     max_dec_frame_buffering: 10

Dark Shikari · 16th February 2010, 18:26

In VFR mode x264 does not write fixed_frame_rate_flag for obvious reasons.

You can use --force-cfr to get Avisynth's behavior in LAVF/FFMS.

lucassp · 17th February 2010, 08:01

Why does it always default to VFR?

Snowknight26 · 17th February 2010, 08:50

Quote:

Originally Posted by kemuri-_9

http://doom10.org/index.php?topic=133.msg1151#msg1151

5char.

PowerGamer · 19th February 2010, 09:49

Currently (x264 rev. 1442) FFMS can't handle raw H.264 streams. x264 opens them with LAVF but is not able to determine total amount of frames in the video being encoded. I wonder if that (inability to determine total amount of frames) has any negative effect on quality/speed of the encoding process (because if it has I can always specify total amount of frames with --frames switch)?

Dark Shikari · 19th February 2010, 10:01

Quote:

Originally Posted by PowerGamer

Currently (x264 rev. 1442) FFMS can't handle raw H.264 streams. x264 opens them with LAVF but is not able to determine total amount of frames in the video being encoded. I wonder if that (inability to determine total amount of frames) has any negative effect on quality/speed of the encoding process (because if it has I can always specify total amount of frames with --frames switch)?

No negative effect currently. In the future this may in theory change when using 1-pass ABR mode.

bnshrdr · 23rd February 2010, 04:26

Hey where can I get a completely up-to-date version of ffmpeg so that I can compile x264 with lavf support?
I would have thought git clone git://git.ffmpeg.org/ffmpeg/ would be as up-to-date as it is needed to be but keep getting this warning from x264's ./configure:

Code:

Warning: libavformat is too old, update to ffmpeg r18351+

Dark Shikari · 23rd February 2010, 04:38

Quote:

Originally Posted by bnshrdr

Hey where can I get a completely up-to-date version of ffmpeg so that I can compile x264 with lavf support?
I would have thought git clone git://git.ffmpeg.org/ffmpeg/ would be as up-to-date as it is needed to be but keep getting this warning from x264's ./configure:

Code:

Warning: libavformat is too old, update to ffmpeg r18351+

You likely have an older ffmpeg installed that x264 is trying to link to.

bnshrdr · 23rd February 2010, 05:02

Well I actually opened up the x264 ./configure file and saw that it was checking for the function avcodec_decode_video2 in one of the libavformat header files. I went and checked, and what do you know, x264 is right. Is there a chance that the master ffmpeg revision isn't truly the master revision.

Mr VacBob · 23rd February 2010, 06:36

ffmpeg git is up to date (r21977). You probably have an older version installed somewhere else.

bnshrdr · 23rd February 2010, 06:45

As much as I understand your logic, I am using a clean system and have not installed anything.

On line 529 of x264's configure script, it checks for most likely a critical function:

Code:

        if cc_check libavformat/avformat.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then
            lavf_input="yes"
            define LAVF_INPUT
        else
            echo "Warning: libavformat is too old, update to ffmpeg r18351+"

I took the liberty of opening libavformat/avformat.h myself to search for this function prototype and it cannot be found. In fact I scanned the whole source code tree to find out where it actually appears, and found it to be in the header file libavcodec/avcodec.h.

I'll try editing the configure script to check that file instead of the other header file and see what happens.

Edit: I seemed to have tricked it successfully. I compiled x264 with lavf support and tested it and it works. Might wanna take a look at that configure script.

Needs a diff that basically does this:

Code:

-if cc_check libavformat/avformat.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then
+if cc_check libavcodec/avcodec.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then

kemuri-_9 · 23rd February 2010, 14:02

Quote:

Originally Posted by bnshrdr

Needs a diff that basically does this:

Code:

-if cc_check libavformat/avformat.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then
+if cc_check libavcodec/avcodec.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then

A) libavformat/avformat.h includes "libavcodec/avcodec.h"
B) we're specifically using both libavformat and libavcodec
C) you removed the check to see if the critically required libavformat/avformat.h header is actually available/correct

so your change is incorrect and can cause issues. fix your installation rather than hack the configure.

smok3 · 23rd February 2010, 15:08

Quote:

Originally Posted by Audionut

http://doom10.org/index.php?topic=3.0

http://doom10.org/index.php?topic=220.0

i have to do everything myself.

3rd February 2010, 13:17	#121 \| Link
Darkwhisperer Registered User Join Date: Jan 2005 Posts: 79	An update perhaps? If your'll don't mind my asking, how are the tests going? Is there a planned release date perhaps?

3rd February 2010, 13:47	#122 \| Link
J_Darnley Registered User Join Date: May 2006 Posts: 957	Why does something that was committed need updating? __________________ x264 log explained \|\| x264 deblocking how-to preset -> tune -> user set options -> fast first pass -> profile -> level Doom10 - Of course it's better, it's one more.

16th February 2010, 13:17	#127 \| Link
Blue_MiSfit Derek Prestegard IRL Join Date: Nov 2003 Location: Los Angeles Posts: 6,017	I'm having great results with these new features! I've been doing lots of high speed transcodes of my movie / TV backups to baseline profile H.264 (for the iPhone). Being able to directly open files in x264 without help from AviSynth, all in "pure" 64 bit is extremely convenient, and is pretty durn cool too ~MiSfit __________________ These are all my personal statements, not those of my employer :)

16th February 2010, 18:26	#129 \| Link
Dark Shikari x264 developer Join Date: Sep 2005 Posts: 8,666	In VFR mode x264 does not write fixed_frame_rate_flag for obvious reasons. You can use --force-cfr to get Avisynth's behavior in LAVF/FFMS. __________________ Follow x264 development progress \| akupenguin quotes \| x264 git status ffmpeg and x264-related consulting/coding contracts \| Doom10

17th February 2010, 08:01	#130 \| Link
lucassp Registered User Join Date: Jan 2007 Location: Romania, Timisoara Posts: 223	Why does it always default to VFR? __________________ [Intel] Core i5 8500\|[ASUS] ROG STRIX Z390-I GAMING\|[Noctua] NH-U12S\|[GSkill] DDR4 2400 2x16GB\|[MSI] RTX2060 Super Gaming X\|[Samsung] 970 Pro 512Gb\|[Seasonic] Focus SGX 650\|[NZXT] H400\|[LG] 27GL850

3rd February 2010, 15:09	#123 \| Link
burfadel Registered User Join Date: Aug 2006 Posts: 2,229	The all-in-one x264 is a great idea, however it does rely on a third party decoder that is under continual development. Since the third party tool is under continual development x264 will need to have that component continually updated to include the features added/fixed in the third party provision. The solution would be to simply update those components each time x264 components are updated, in order to stay current.

14th February 2010, 21:06	#124 \| Link
smok3 brontosaurusrex Join Date: Oct 2001 Posts: 2,392	do we have osx and/or ubuntu-karmic builds?

16th February 2010, 13:09	#126 \| Link
hajj_3 Registered User Join Date: Mar 2004 Posts: 1,239	Does this mean we could have a 64bit of MeGUI and use a 64bit of x264.exe with LAVF/FFMS integrated into it? Do we know what kind of speed improvements we would get using this x264 beta compared to using regular x264.exe and avisynth 2.5.8 or 2.6.0 MT alpha?

19th February 2010, 09:49	#132 \| Link
PowerGamer Registered User Join Date: Jan 2010 Posts: 20	Currently (x264 rev. 1442) FFMS can't handle raw H.264 streams. x264 opens them with LAVF but is not able to determine total amount of frames in the video being encoded. I wonder if that (inability to determine total amount of frames) has any negative effect on quality/speed of the encoding process (because if it has I can always specify total amount of frames with --frames switch)?

23rd February 2010, 04:26	#134 \| Link
bnshrdr Registered User Join Date: Jun 2009 Location: Indianapolis, IN Posts: 103	Hey where can I get a completely up-to-date version of ffmpeg so that I can compile x264 with lavf support? I would have thought git clone git://git.ffmpeg.org/ffmpeg/ would be as up-to-date as it is needed to be but keep getting this warning from x264's ./configure: Code: Warning: libavformat is too old, update to ffmpeg r18351+

23rd February 2010, 05:02	#136 \| Link
bnshrdr Registered User Join Date: Jun 2009 Location: Indianapolis, IN Posts: 103	Well I actually opened up the x264 ./configure file and saw that it was checking for the function avcodec_decode_video2 in one of the libavformat header files. I went and checked, and what do you know, x264 is right. Is there a chance that the master ffmpeg revision isn't truly the master revision.

23rd February 2010, 06:36	#137 \| Link
Mr VacBob Registered User Join Date: Feb 2005 Posts: 140	ffmpeg git is up to date (r21977). You probably have an older version installed somewhere else.

23rd February 2010, 06:45	#138 \| Link
bnshrdr Registered User Join Date: Jun 2009 Location: Indianapolis, IN Posts: 103	As much as I understand your logic, I am using a clean system and have not installed anything. On line 529 of x264's configure script, it checks for most likely a critical function: Code: if cc_check libavformat/avformat.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then lavf_input="yes" define LAVF_INPUT else echo "Warning: libavformat is too old, update to ffmpeg r18351+" I took the liberty of opening libavformat/avformat.h myself to search for this function prototype and it cannot be found. In fact I scanned the whole source code tree to find out where it actually appears, and found it to be in the header file libavcodec/avcodec.h. I'll try editing the configure script to check that file instead of the other header file and see what happens. Edit: I seemed to have tricked it successfully. I compiled x264 with lavf support and tested it and it works. Might wanna take a look at that configure script. Needs a diff that basically does this: Code: -if cc_check libavformat/avformat.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then +if cc_check libavcodec/avcodec.h "$LAVF_CFLAGS $LAVF_LIBS" "avcodec_decode_video2( NULL, NULL, NULL, NULL );" ; then Last edited by bnshrdr; 23rd February 2010 at 06:56.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode