Current Patches, Where to get them, How they affect speed/output - Page 105

moviefan · 30th July 2009, 19:05

Ehm, basically... yes ;-). OK... I will redo the tracing. I closed the terminal this morning, but the information were as I mentioned. I started another encode with imk's build using DirectShowSource of the same source this morning and up to now there have not been any errors. Do you definitely expect more information than I posted, so that I missed something? In that case I do the tracing again.

Edit: Actually, the DirectShowSource encode failed too, but for other, unknown reasons... I've just started the backtrace again.
Edit: OK, an error occurred again. I now paste exactly what is shown in the terminal:

Code:

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
warning: Process detach: hModule = 0x10000000, gRefCnt = 2

Program exited with code 03.
(gdb) bt
No stack.

This message is different to the one from this morning. However, there is an error and I hope this helps with debugging.

Edit: The issue might have been caused by using SetMTMode(2) at the very beginning of the avs-script, especially before AVCSource/DirectShowSource. When I put it after source loading, the encodes seem to be stable. I have already encoded about 33000 frames and the crashes were always at a few 1000 frames.

juGGaKNot · 1st August 2009, 21:07

I want to modify x264.c to make a custom profile

cmd now :

Quote:

--profile high --preset placebo --tune animation --bitrate %btratex264% --stats %myx264stats% --level %mylevel% --fullrange on --no-fast-pskip --bframes 4 --psy-rd 1.0:00 --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 20000 --vbv-maxrate 20000 --qcomp 1.0 --aq-mode 2 --aq-strength 1.0 --nal-hrd --sar 1:1 --aud --no-dct-decimate

cmd after

Quote:

--profile high --preset juggaknot --bitrate %btratex264% --stats %myx264stats% --level %mylevel%

so i want to include all these settings

Quote:

--fullrange on --no-fast-pskip --bframes 4 --psy-rd 1.0:00 --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 20000 --vbv-maxrate 20000 --qcomp 1.0 --aq-mode 2 --aq-strength 1.0 --nal-hrd --sar 1:1 --aud --no-dct-decimate

in a preset, so far i got :

Quote:

H0( " --preset Use a preset to select encoding settings [medium]\n" );
H0( " Overridden by user settings\n");
H1( " - ultrafast,veryfast,fast,medium\n"
" - slow,slower,placebo,juggaknot\n" );
else H0( " - ultrafast,veryfast,fast,medium,slow,slower,placebo\n" );

Quote:

else if( !strcasecmp( optarg, "juggaknot" ) )
{
param->i_frame_reference > 1 ? param->i_frame_reference*2 : 1;
param->i_deblocking_filter_alphac0 = 1;
param->i_deblocking_filter_beta = 1;
param->analyse.f_psy_rd = 1.0;
param->rc.f_aq_strength = 1.0;
param->i_bframe = 4;
param->rc.f_qcompress = 1.0;

How can i add the rest of the cvars ? can i add all of them ?

J_Darnley · 1st August 2009, 23:41

You can discover the variable names by looking at common/common.c and the function x264_param_parse then add them to your preset. You don't have to add your preset name to the help if it is for your use.

LoRd_MuldeR · 2nd August 2009, 00:15

juGGaKNot, try this:

Code:

            else if( !strcasecmp( optarg, "juggaknot" ) )
            {
                param->analyse.i_me_method = X264_ME_TESA;
                param->analyse.i_subpel_refine = 10;
                param->analyse.i_me_range = 24;
                param->i_frame_reference = 16;
                param->i_bframe_adaptive = X264_B_ADAPT_TRELLIS;
                param->analyse.i_direct_mv_pred = X264_DIRECT_PRED_AUTO;
                param->analyse.inter |= X264_ANALYSE_PSUB8x8;
                param->analyse.b_fast_pskip = 0; // --no-fast-pskip
                param->analyse.i_trellis = 2;
                param->i_bframe = 16; // --bframes 4
                param->rc.f_qcompress = 1.0f // --qcomp 1.0
                param->rc.i_vbv_max_bitrate = 20000; // --vbv-maxrate 20000
                param->rc.i_vbv_buffer_size = 20000; // --vbv-bufsize 20000
                param->rc.b_aud = 1; // --aud
                param->b_dct_decimate = 0; // --no-dct-decimate
                param->vui.b_fullrange = 1; // --fullrange on
                param->analyse.f_psy_rd = 1.0f; // --psy-rd 1.0:00
                param->analyse.f_psy_trellis = 0.0f; // --psy-rd 1.0:00
                param->rc.i_aq_mode = X264_AQ_AUTOVARIANCE; // --aq-mode 2
                param->rc.f_aq_strength = 1.0f; // --aq-strength 1.0
                param->rc.f_ip_factor = 1.1f; // --ipratio 1.1
                param->rc.f_pb_factor = 1.1f; // --pbratio 1.1
                param->vui.i_sar_height = 1; //--sar 1:1
                param->vui.i_sar_width = 1; //--sar 1:1
                param->b_nal_hrd = 1; // --nal-hrd 
            }

Diff: http://pastie.org/568166

Note that some lines are superfluous, as they simply represent the default. But I included them anyway, just for completeness

juGGaKNot · 2nd August 2009, 09:29

Quote:

Originally Posted by J_Darnley

You can discover the variable names by looking at common/common.c and the function x264_param_parse then add them to your preset. You don't have to add your preset name to the help if it is for your use.

thnx, it is for use in my exe thingy.

Quote:

Originally Posted by LoRd_MuldeR

juGGaKNot, try this:

thnx.

LE

error on the diff

Code:

***************
*** 593,598 ****
                  param->analyse.i_trellis = 2;
                  param->i_bframe = 16;
              }
              else
              {
                  fprintf( stderr, "x264 [error]: invalid preset: %s\n", optarg );
--- 593,626 ----
                  param->analyse.i_trellis = 2;
                  param->i_bframe = 16;
              }
+             else if( !strcasecmp( optarg, "juggaknot" ) )
+             {
+                 param->analyse.i_me_method = X264_ME_TESA;
+                 param->analyse.i_subpel_refine = 10;
+                 param->analyse.i_me_range = 24;
+                 param->i_frame_reference = 16;
+                 param->i_bframe_adaptive = X264_B_ADAPT_TRELLIS;
+                 param->analyse.i_direct_mv_pred = X264_DIRECT_PRED_AUTO;
+                 param->analyse.inter |= X264_ANALYSE_PSUB8x8;
+                 param->analyse.b_fast_pskip = 0; // --no-fast-pskip
+                 param->analyse.i_trellis = 2;
+                 param->i_bframe = 16; // --bframes 4
+                 param->rc.f_qcompress = 1.0f // --qcomp 1.0
+                 param->rc.i_vbv_max_bitrate = 20000; // --vbv-maxrate 20000
+                 param->rc.i_vbv_buffer_size = 20000; // --vbv-bufsize 20000
+                 param->rc.b_aud = 1; // --aud
+                 param->b_dct_decimate = 0; // --no-dct-decimate
+                 param->vui.b_fullrange = 1; // --fullrange on
+                 param->analyse.f_psy_rd = 1.0f; // --psy-rd 1.0:00
+                 param->analyse.f_psy_trellis = 0.0f; // --psy-rd 1.0:00
+                 param->rc.i_aq_mode = X264_AQ_AUTOVARIANCE; // --aq-mode 2
+                 param->rc.f_aq_strength = 1.0f; // --aq-strength 1.0
+                 param->rc.f_ip_factor = 1.1f; // --ipratio 1.1
+                 param->rc.f_pb_factor = 1.1f; // --pbratio 1.1
+                 param->vui.i_sar_height = 1; //--sar 1:1
+                 param->vui.i_sar_width = 1; //--sar 1:1
+                 param->b_nal_hrd = 1; // --nal-hrd 
+             }
              else
              {
                  fprintf( stderr, "x264 [error]: invalid preset: %s\n", optarg );

Quote:

$ patch -p1 < /d/jugg.diff
patching file x264.c
Hunk #1 FAILED at 593.
1 out of 1 hunk FAILED -- saving rejects to file x264.c.rej

LE :

if i copy the code in x264.c ( replace placebo with juggaknot )

i get errors on aud

jpsdr · 2nd August 2009, 10:45

Hello.

I'm totaly new in h264.
I've try to encode videos in h264, and import
them in scenarist. After faillure and research,
it seems that standard x264 built lack some "4-slice"
support in produced stream to be BD compliant, at
least in scenarist (v4.3.0) aspect.
I've found that maybe it exist some patched version
wich add these "slice".
I hope i'm in the right place to ask this.
If these versions exist, where can i find them,
and what specific command line option do i have
to add in MeGUI ?

Thanks.

nurbs · 2nd August 2009, 11:32

You can try to compile x264 with this patch and then add the appropriate custom command line options in megui.

juGGaKNot · 2nd August 2009, 11:44

Quote:

param->analyse.i_me_method = X264_ME_TESA;
param->analyse.i_subpel_refine = 10;
param->analyse.i_me_range = 32;
param->i_frame_reference = 16;
param->i_bframe_adaptive = X264_B_ADAPT_TRELLIS;
param->analyse.i_direct_mv_pred = X264_DIRECT_PRED_AUTO;
param->analyse.inter |= X264_ANALYSE_PSUB8x8;
param->analyse.b_fast_pskip = 0;
param->analyse.i_trellis = 2;
param->i_bframe = 4;
param->rc.f_qcompress = 1.0f;
param->rc.i_vbv_max_bitrate = 20000;
param->rc.i_vbv_buffer_size = 20000;
param->vui.b_fullrange = 1;
param->analyse.f_psy_rd = 1.0f;
param->analyse.f_psy_trellis = 0.0f;
param->rc.i_aq_mode = X264_AQ_AUTOVARIANCE;
param->rc.f_aq_strength = 1.0f;
param->rc.f_ip_factor = 1.1f;
param->rc.f_pb_factor = 1.1f;
param->vui.i_sar_height = 1;
param->vui.i_sar_width = 1;
param->i_deblocking_filter_alphac0 = 1;
param->i_deblocking_filter_beta = 1;
param->analyse.b_dct_decimate = 0;

param->rc.b_aud = 1; does not work.

moviefan · 2nd August 2009, 11:55

Referring to jpsdr's post, is slicing actually needed to be BD compliant? And are there disadvantages using the multislice-patch?

Dark Shikari · 2nd August 2009, 12:20

Quote:

Originally Posted by moviefan

Referring to jpsdr's post, is slicing actually needed to be BD compliant? And are there disadvantages using the multislice-patch?

Slightly lower compression (a few %).

Technically, BD does require slicing, but I have yet to receive a report of a player not taking an unsliced stream.

Some authoring software checks it anyways though.

moviefan · 2nd August 2009, 12:25

OK, if the patch is used, is x264 in its current development stage capable of 100% BD compliance (official requirements)? (speaking of encoding 1080p material, using Level 4.1 and the correct settings to be within BD specs)

Dark Shikari · 2nd August 2009, 12:32

Quote:

Originally Posted by moviefan

OK, if the patch is used, is x264 in its current development stage capable of 100% BD compliance (official requirements)? (speaking of encoding 1080p material, using Level 4.1 and the correct settings to be within BD specs)

Maybe. We don't really know; the spec is secret.

juGGaKNot · 2nd August 2009, 13:09

Quote:

Originally Posted by juGGaKNot

param->rc.b_aud = 1; does not work.

Quote:

x264.c: In function 'Parse':
x264.c:610: error: 'struct <anonymous>' has no member named 'b_aud'
make[1]: *** [x264.o] Error 1
make[1]: Leaving directory `/d/x264'
make: *** [fprofiled] Error 2

Administrator@LastXP15 /d/x264
$

What is the right param ?

LoRd_MuldeR · 2nd August 2009, 13:13

Quote:

Originally Posted by juGGaKNot

What is the right param ?

Try this

Code:

param->b_aud = 1;

juGGaKNot · 2nd August 2009, 13:17

LOL, i tried it and it did not work, now it does.

thnx

anyway a download link for x264_win_zone_parse_fix_05.diff ?

LoRd_MuldeR · 2nd August 2009, 13:19

Let me google that for you:
http://lmgtfy.com/?q=x264_win_zone_p...iletype%3Adiff

juGGaKNot · 2nd August 2009, 13:29

filetype:xxx, good tip

i get one error

hrd also got errors, 13 modified, 14 and 15 :

Code:

$ patch -p1 < /d/x264_win_zone_parse_fix_05.diff
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 638.
Hunk #2 FAILED at 649.
2 out of 2 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej

$ patch -p1 < /d/x264_hrd_pulldown.13_interlace.diff
patching file common/bs.h
Hunk #1 FAILED at 169.
1 out of 1 hunk FAILED -- saving rejects to file common/bs.h.rej
patching file common/common.c
Hunk #1 FAILED at 141.
Hunk #2 FAILED at 370.
Hunk #3 FAILED at 585.
3 out of 3 hunks FAILED -- saving rejects to file common/common.c.rej
patching file common/common.h
Hunk #1 FAILED at 279.
1 out of 1 hunk FAILED -- saving rejects to file common/common.h.rej
patching file common/frame.c
Hunk #1 FAILED at 109.
1 out of 1 hunk FAILED -- saving rejects to file common/frame.c.rej
patching file common/frame.h
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file common/frame.h.rej
patching file common/set.h
Hunk #1 FAILED at 125.
1 out of 1 hunk FAILED -- saving rejects to file common/set.h.rej
patching file encoder/encoder.c
Hunk #1 FAILED at 383.
Hunk #2 FAILED at 702.
Hunk #3 FAILED at 908.
Hunk #4 FAILED at 1309.
Hunk #5 FAILED at 1358.
Hunk #6 FAILED at 1368.
Hunk #7 FAILED at 1390.
Hunk #8 FAILED at 1514.
Hunk #9 FAILED at 1547.
Hunk #10 FAILED at 1608.
Hunk #11 FAILED at 1699.
Hunk #12 FAILED at 1749.
Hunk #13 FAILED at 1763.
13 out of 13 hunks FAILED -- saving rejects to file encoder/encoder.c.rej
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 70.
Hunk #2 FAILED at 91.
Hunk #3 FAILED at 143.
Hunk #4 FAILED at 287.
Hunk #5 FAILED at 1088.
Hunk #6 FAILED at 1170.
Hunk #7 FAILED at 1292.
Hunk #8 FAILED at 1305.
8 out of 8 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej
patching file encoder/ratecontrol.h
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file encoder/ratecontrol.h.rej
patching file encoder/set.c
Hunk #1 FAILED at 208.
Hunk #2 FAILED at 391.
Hunk #3 FAILED at 580.
3 out of 3 hunks FAILED -- saving rejects to file encoder/set.c.rej
patching file encoder/set.h
Hunk #1 FAILED at 29.
1 out of 1 hunk FAILED -- saving rejects to file encoder/set.h.rej
patching file x264.c
Hunk #1 FAILED at 196.
Hunk #2 FAILED at 354.
Hunk #3 FAILED at 399.
Hunk #4 FAILED at 467.
Hunk #5 FAILED at 1107.
5 out of 5 hunks FAILED -- saving rejects to file x264.c.rej
patching file x264.h
Hunk #1 FAILED at 201.
Hunk #2 FAILED at 267.
Hunk #3 FAILED at 293.
3 out of 3 hunks FAILED -- saving rejects to file x264.h.rej

$ patch -p1 < /d/x264_hrd_pulldown.14_interlace.diff
patching file common/bs.h
Hunk #1 FAILED at 169.
1 out of 1 hunk FAILED -- saving rejects to file common/bs.h.rej
patching file common/common.c
Hunk #1 FAILED at 145.
Hunk #2 FAILED at 374.
Hunk #3 FAILED at 589.
3 out of 3 hunks FAILED -- saving rejects to file common/common.c.rej
patching file common/common.h
Hunk #1 FAILED at 288.
1 out of 1 hunk FAILED -- saving rejects to file common/common.h.rej
patching file common/frame.c
Hunk #1 FAILED at 109.
1 out of 1 hunk FAILED -- saving rejects to file common/frame.c.rej
patching file common/frame.h
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file common/frame.h.rej
patching file common/set.h
Hunk #1 FAILED at 125.
1 out of 1 hunk FAILED -- saving rejects to file common/set.h.rej
patching file encoder/encoder.c
Hunk #1 FAILED at 403.
Hunk #2 FAILED at 725.
Hunk #3 FAILED at 931.
Hunk #4 FAILED at 940.
Hunk #5 FAILED at 1386.
Hunk #6 FAILED at 1396.
Hunk #7 FAILED at 1418.
Hunk #8 FAILED at 1571.
Hunk #9 FAILED at 1633.
Hunk #10 FAILED at 1729.
Hunk #11 FAILED at 1779.
Hunk #12 FAILED at 1793.
12 out of 12 hunks FAILED -- saving rejects to file encoder/encoder.c.rej
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 89.
Hunk #3 FAILED at 140.
Hunk #4 FAILED at 286.
Hunk #5 FAILED at 1089.
Hunk #6 FAILED at 1171.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1305.
8 out of 8 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej
patching file encoder/ratecontrol.h
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file encoder/ratecontrol.h.rej
patching file encoder/set.c
Hunk #1 FAILED at 208.
Hunk #2 FAILED at 383.
Hunk #3 FAILED at 572.
3 out of 3 hunks FAILED -- saving rejects to file encoder/set.c.rej
patching file encoder/set.h
Hunk #1 FAILED at 29.
1 out of 1 hunk FAILED -- saving rejects to file encoder/set.h.rej
patching file x264.c
Hunk #1 FAILED at 196.
Hunk #2 FAILED at 354.
Hunk #3 FAILED at 399.
Hunk #4 FAILED at 467.
4 out of 4 hunks FAILED -- saving rejects to file x264.c.rej
patching file x264.h
Hunk #1 FAILED at 200.
Hunk #2 FAILED at 266.
Hunk #3 FAILED at 292.
3 out of 3 hunks FAILED -- saving rejects to file x264.h.rej

$ patch -p1 < /d/x264_hrd_pulldown.15_interlace.diff
patching file common/bs.h
Hunk #1 FAILED at 169.
1 out of 1 hunk FAILED -- saving rejects to file common/bs.h.rej
patching file common/common.c
Hunk #1 FAILED at 145.
Hunk #2 FAILED at 374.
Hunk #3 FAILED at 589.
3 out of 3 hunks FAILED -- saving rejects to file common/common.c.rej
patching file common/common.h
Hunk #1 FAILED at 288.
1 out of 1 hunk FAILED -- saving rejects to file common/common.h.rej
patching file common/frame.c
Hunk #1 FAILED at 109.
1 out of 1 hunk FAILED -- saving rejects to file common/frame.c.rej
patching file common/frame.h
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file common/frame.h.rej
patching file common/set.h
Hunk #1 FAILED at 125.
1 out of 1 hunk FAILED -- saving rejects to file common/set.h.rej
patching file encoder/encoder.c
Hunk #1 FAILED at 403.
Hunk #2 FAILED at 725.
Hunk #3 FAILED at 931.
Hunk #4 FAILED at 940.
Hunk #5 FAILED at 1386.
Hunk #6 FAILED at 1396.
Hunk #7 FAILED at 1418.
Hunk #8 FAILED at 1571.
Hunk #9 FAILED at 1633.
Hunk #10 FAILED at 1729.
Hunk #11 FAILED at 1779.
Hunk #12 FAILED at 1793.
12 out of 12 hunks FAILED -- saving rejects to file encoder/encoder.c.rej
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 89.
Hunk #3 FAILED at 140.
Hunk #4 FAILED at 286.
Hunk #5 FAILED at 1089.
Hunk #6 FAILED at 1171.
Hunk #7 FAILED at 1293.
Hunk #8 FAILED at 1305.
8 out of 8 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej
patching file encoder/ratecontrol.h
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file encoder/ratecontrol.h.rej
patching file encoder/set.c
Hunk #1 FAILED at 208.
Hunk #2 FAILED at 384.
Hunk #3 FAILED at 573.
3 out of 3 hunks FAILED -- saving rejects to file encoder/set.c.rej
patching file encoder/set.h
Hunk #1 FAILED at 29.
1 out of 1 hunk FAILED -- saving rejects to file encoder/set.h.rej
patching file x264.c
Hunk #1 FAILED at 196.
Hunk #2 FAILED at 354.
Hunk #3 FAILED at 399.
Hunk #4 FAILED at 467.
4 out of 4 hunks FAILED -- saving rejects to file x264.c.rej
patching file x264.h
Hunk #1 FAILED at 200.
Hunk #2 FAILED at 266.
Hunk #3 FAILED at 292.
3 out of 3 hunks FAILED -- saving rejects to file x264.h.rej

kemuri-_9 · 2nd August 2009, 14:49

Quote:

Originally Posted by juGGaKNot

i get one error
hrd also got errors, 13 modified, 14 and 15 :

i've usually gotten a patch to completely reject when the git repo settings have it in windows text mode (CR/LF) instead of linux (LF only)

check the settings for the git program you're using.

juGGaKNot · 2nd August 2009, 15:33

Using windows xp.

Quote:

$ git config --global core.autocrlf true

$ patch -p1 < /d/win.diff
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 638.
Hunk #2 FAILED at 649.
2 out of 2 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej

$ git config --global core.autocrlf input

$ patch -p1 < /d/win.diff
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 638.
Hunk #2 FAILED at 649.
2 out of 2 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej

$ git config --global core.autocrlf false

$ patch -p1 < /d/win.diff
patching file encoder/ratecontrol.c
Hunk #1 FAILED at 638.
Hunk #2 FAILED at 649.
2 out of 2 hunks FAILED -- saving rejects to file encoder/ratecontrol.c.rej

Trahald · 2nd August 2009, 15:55

When you installed git it asks what type of line endings you want, IIRC it defaults to windows (CR/LF) when installed on windows. You should select linux(LF) . When it happened to me, I just reinstalled GIT and changed the setting. I assume there is another quicker way to do it, but i didnt bother looking.

My own question... When i diff, the vcproj/sln files always end up in there. A few times Ive googled til i get tired of googling a way (well.. a simple way) to avoid that, but never can find one. i usually do git diff -ignore-space-at-eol > blah.diff . (the ignore arg ive found keeps the diff file from quoting the entire vcproj file but a header still shows up. ) you can see that at the beginning of my diffs

30th July 2009, 19:05	#2081 \| Link
moviefan Registered User Join Date: Jul 2005 Posts: 438	Ehm, basically... yes ;-). OK... I will redo the tracing. I closed the terminal this morning, but the information were as I mentioned. I started another encode with imk's build using DirectShowSource of the same source this morning and up to now there have not been any errors. Do you definitely expect more information than I posted, so that I missed something? In that case I do the tracing again. Edit: Actually, the DirectShowSource encode failed too, but for other, unknown reasons... I've just started the backtrace again. Edit: OK, an error occurred again. I now paste exactly what is shown in the terminal: Code: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. warning: Process detach: hModule = 0x10000000, gRefCnt = 2 Program exited with code 03. (gdb) bt No stack. This message is different to the one from this morning. However, there is an error and I hope this helps with debugging. Edit: The issue might have been caused by using SetMTMode(2) at the very beginning of the avs-script, especially before AVCSource/DirectShowSource. When I put it after source loading, the encodes seem to be stable. I have already encoded about 33000 frames and the crashes were always at a few 1000 frames. Last edited by moviefan; 1st August 2009 at 21:22.

1st August 2009, 23:41	#2083 \| Link
J_Darnley Registered User Join Date: May 2006 Posts: 957	You can discover the variable names by looking at common/common.c and the function x264_param_parse then add them to your preset. You don't have to add your preset name to the help if it is for your use. __________________ 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.

2nd August 2009, 11:55	#2089 \| Link
moviefan Registered User Join Date: Jul 2005 Posts: 438	Referring to jpsdr's post, is slicing actually needed to be BD compliant? And are there disadvantages using the multislice-patch? Last edited by moviefan; 2nd August 2009 at 12:09.

2nd August 2009, 13:17	#2095 \| Link
juGGaKNot Registered User Join Date: Feb 2008 Posts: 733	LOL, i tried it and it did not work, now it does. thnx anyway a download link for x264_win_zone_parse_fix_05.diff ? Last edited by juGGaKNot; 2nd August 2009 at 13:42.

2nd August 2009, 13:19	#2096 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,248	Let me google that for you: http://lmgtfy.com/?q=x264_win_zone_p...iletype%3Adiff __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 2nd August 2009 at 13:25.

2nd August 2009, 10:45	#2086 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,316	Hello. I'm totaly new in h264. I've try to encode videos in h264, and import them in scenarist. After faillure and research, it seems that standard x264 built lack some "4-slice" support in produced stream to be BD compliant, at least in scenarist (v4.3.0) aspect. I've found that maybe it exist some patched version wich add these "slice". I hope i'm in the right place to ask this. If these versions exist, where can i find them, and what specific command line option do i have to add in MeGUI ? Thanks.

2nd August 2009, 11:32	#2087 \| Link
nurbs Registered User Join Date: Dec 2005 Posts: 1,460	You can try to compile x264 with this patch and then add the appropriate custom command line options in megui.

2nd August 2009, 12:25	#2091 \| Link
moviefan Registered User Join Date: Jul 2005 Posts: 438	OK, if the patch is used, is x264 in its current development stage capable of 100% BD compliance (official requirements)? (speaking of encoding 1080p material, using Level 4.1 and the correct settings to be within BD specs)

2nd August 2009, 15:55	#2100 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	When you installed git it asks what type of line endings you want, IIRC it defaults to windows (CR/LF) when installed on windows. You should select linux(LF) . When it happened to me, I just reinstalled GIT and changed the setting. I assume there is another quicker way to do it, but i didnt bother looking. My own question... When i diff, the vcproj/sln files always end up in there. A few times Ive googled til i get tired of googling a way (well.. a simple way) to avoid that, but never can find one. i usually do git diff -ignore-space-at-eol > blah.diff . (the ignore arg ive found keeps the diff file from quoting the entire vcproj file but a header still shows up. ) you can see that at the beginning of my diffs __________________ ...yeah...but...why on earth would I compare apples with apples?

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