Megui time delay

[Jayzy]

Hi guys,
I have some doubts I hope you guys can solve them. okay let me come to the point.

cabac=1 / ref=5 / deblock=1:-2:-1 / analyse=0x1:0x131 / me=umh / subme=5 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=3 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=16 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=1800 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 /

Okay. Check the details given above. Can you tell me which settings make time delay in theses settings? When I try to encode DVDs It showed me around 11 hrs remaining, which is really huge amount of time. So tell me a suggestion to reduce the time and get the work done.

And another question: deblock=1:-2:-1 really this setting makes any different in the video.

(Note : I encoded a DVD with these presets, which had given a great output)

[S_Prince]

It is maybe MeGUI x264 (HQ-Slow) Profile

Usually Encoding time delay does not depends on those profiles specially.. but in depends on those avisynth plugin u use in ur script

& deblock function is a H.264 specialty & it hardly makes any changes on the speed..

so kindly post your scripts here to examine the reason behind slow encode


Regards,

[Jayzy]

It is maybe MeGUI x264 (HQ-Slow) Profile

Usually Encoding time delay does not depends on those profiles specially.. but in depends on those avisynth plugin u use in ur script

& deblock function is a H.264 specialty & it hardly makes any changes on the speed..

so kindly post your scripts here to examine the reason behind slow encode


Regards,

Thank you very much for your quick reply mate :thanks:. So What do you mean by scripts? I guess, maybe you mentioned these settings

program --profile main --level 2.1 --pass 2 --bitrate 1800 --stats ".stats" --deblock -2:-1 --bframes 16 --b-pyramid none --ref 5 --qpmin 10 --qpmax 51 --aq-mode 2 --me umh --direct auto --subme 5 --partitions p8x8,b8x8,i4x4,p4x4 --output "output" "input"

I use medium speed preset not hq slow

I hope this helps.

[S_Prince]

I Am talking about the avisynth script u use as the input..

that can be the reason of slow encode..

[Jayzy]

I Am talking about the avisynth script u use as the input..

that can be the reason of slow encode..

I'm using 2.5 avisynth. And will this be the problem?

[sneaker_ger]

The old presets of MeGUI are deprecated. Use the newest builds and choose the speed within the x264 scratchpad:
http://www.abload.de/img/megui_speedaor2o.png

[sneaker_ger]

I'm using 2.5 avisynth. And will this be the problem?

Only if you use slow filters within the script. (Deinterlacing, Denoising etc.)

[Jayzy]

The old presets of MeGUI are deprecated. Use the newest builds and choose the speed within the x264 scratchpad:
http://www.abload.de/img/megui_speedaor2o.png

And I think I'm using the latest presets. I use automated two pass for encoding.

Only if you use slow filters within the script. (Deinterlacing, Denoising etc.)

I usually use (Deinterlacing, Denoising etc.) these kinds of scripts. I don't think this will affect encoding time.

[sneaker_ger]

I usually use (Deinterlacing, Denoising etc.) these kinds of scripts. I don't think this will affect encoding time.

How much they will affect the encoding time highly depends on the specific filters and settings. Some filters are very fast, some are extremely slow.

That's why S_Prince asked you to post your script.

[Jayzy]

How much they will affect the encoding time highly depends on the specific filters and settings. Some filters are very fast, some are extremely slow.

That's why S_Prince asked you to post your script.

okay bro. I hope this information will help you too.

cabac=1 / ref=5 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=16 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=593 / ratetol=1.0 / qcomp=0.60 / qpmin=3 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00

These settings take around 3 hrs.

cabac=1 / ref=5 / deblock=1:-2:-1 / analyse=0x1:0x131 / me=umh / subme=5 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=3 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=16 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=1800 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=2:1.00

These settings take around 11 hrs. So Can you identify which is really making time delay.

[sneaker_ger]

okay bro. I hope this information will help you too.

Those are the x264 settings, not the AviSynth script S_Prince asked for.

These settings take around 11 hrs. So Can you identify which is really making time delay.

I will not tell which setting exactly affects time, because just changing a few settings here and there is a bad idea. Use the new preset setting as shown in my screenshot, because those presets "were picked to be roughly optimal positions on the speed-compession curve based on testing". Just changing a few parameters here and there may increase your speed, but you will be off that curve.

[Jayzy]

Those are the x264 settings, not the AviSynth script S_Prince asked for.


Than tell me what is avisynth script. I already installed version 2.5 or you mentioning these stuffs (LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("F:\Video Songs\Songs (1).FLV", cachefile="E:\MEGUI PATH\Songs (1).FLV.ffindex", threads=1)
#deinterlace
#crop
#resize
#denoise)

I'll try what you mentioned above.

[sneaker_ger]

In AviSynth the "#" character marks the start of a comment. So that script only does decoding. Even though it is set to only use a single thread for decoding, the script should be very fast and is probably not the source of any slowdown. (You can see in the task manager whether your CPU is used to the fullest, i.e. 90%-100%.)

[Jayzy]

In AviSynth the "#" character marks the start of a comment. So that script only does decoding. Even though it is set to only use a single thread for decoding, the script should be very fast and is probably not the source of any slowdown. (You can see in the task manager whether your CPU is used to the fullest, i.e. 90%-100%.)

It takes maximum usage100%. Targeting quality and automated 2 pass are almost giving same output qualities.

[sneaker_ger]

2pass is generally only recommended if you want to hit a specific filesize. (Like a DVD for example) Otherwise use constant quality which offers the same quality for the same bitrate, as you have already found out.

[Jayzy]

2pass is generally only recommended if you want to hit a specific filesize. (Like a DVD for example) Otherwise use constant quality which offers the same quality for the same bitrate, as you have already found out.
Okay. but still I didn't understand the time delay. Should I update avisynth script?

[sneaker_ger]

No, your AviSynth script is fine as is.

[Jayzy]

No, your AviSynth script is fine as is.

Thanks for your replies brother. But I've got to find out the issue. What makes the delay?. What should I do to reduce the speed to get the work done?

[Guest]

You speed things up by choosing a faster encoding preset and/or by getting faster hardware. What is so hard for you to understand?

[Jayzy]

You speed things up by choosing a faster encoding preset and/or by getting faster hardware. What is so hard for you to understand?


Okay bro, I'll tell you the problem.I used same DVD to get the details
cabac=1 / ref=5 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=16 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=593 / ratetol=1.0 / qcomp=0.60 / qpmin=3 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00


This took 3hrs too encode


cabac=1 / ref=5 / deblock=1:-2:-1 / analyse=0x1:0x131 / me=umh / subme=5 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=3 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=16 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=1800 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=2:1.00

This took 11 hrs to encode. S_Prince replied these presets don't influenced on time delay. what makes the delay?

[Guest]

You have slower settings for the second one. What presets did you select to generate these command lines?

Regarding S_Prince's comment: Of course presets affect encoding time.

[Jayzy]

You have slower settings for the second one. What presets did you select to generate these command lines?

Regarding S_Prince's comment: Of course presets affect encoding time.

Thanks brother finally I got the right answer. Are you asking these details which is given below or something else?

program --profile main --level 2.1 --pass 2 --bitrate 1800 --stats ".stats" --deblock -2:-1 --bframes 16 --b-pyramid none --ref 5 --qpmin 10 --qpmax 51 --aq-mode 2 --me umh --direct auto --subme 5 --partitions p8x8,b8x8,i4x4,p4x4 --output "output" "input"

[Guest]

I am asking what presets you used in MEGUI. See post #6.

[nhakobian]

Also, what CPU do you have? In the settings it appears that you have threads=3, which implies that you have a dual core non-hyperthreading cpu (x264 by default sets threads = 1.5 number of logical cores you have). Also you are performing 2-pass encoding. Are the encoding times you are quoting including both the times for the 1st and 2nd pass together?

If you have a slower dual-core CPU with something like preset=veryslow, I could see it possibly taking ~11 hours for both passes together (even though that does seem a little slow even to me). It all depends on which presets you chose, and what CPU you have. If you have something that's like a Pentium D, it might take that long.

[Jayzy]

I am asking what presets you used in MEGUI. See post #6.

Preset : medium
Tuning : Default
AVC profile : main profile
AVC level ; 2.1
Target play back : DXVA

[x265]

Jayzy >> set you preset to very fast, this will decrease the encoding time but will result in lower quality encodes.

[Guest]

Preset : medium
Tuning : Default
AVC profile : main profile
AVC level ; 2.1
Target play back : DXVA That's one. Does it correspond to the 3 hour encode or the 11 hour one? And what was the other one?

[Jayzy]

That's one. Does it correspond to the 3 hour encode or the 11 hour one? And what was the other one?

Preset : medium
Tuning : Default
AVC profile : main profile
AVC level ; 2.1
Target play back : DXVA
This took 11 hrs


Preset : medium
Tuning : Default
AVC profile : main profile
AVC level ; 2.1
Target play back : default
This took 3 hrs

[Guest]

What about your Encoding mode, quality, and tuning fields (also seen in post #6)?

I doubt simply specifying target as DXVA would make such a large difference.

[Jayzy]

What about your Encoding mode, quality, and tuning fields (also seen in post #6)?

I doubt simply specifying target as DXVA would make such a large difference.

Encoding mode is automated 2 pass. Both quality and tuning whole things are same right. I'll try DXVA to AVCHD or Default. Let me check and I'll post the details tomorrow.

[Jayzy]

Hi guys.
subq and ref. Can these two settings be the reason for encoding delay in meGUI.

And how to sharpen the video a bit. :o.

[x265]

Try sharpening with lsfmod(), I am a newbie myself so i don't know much about this filter. I have used this for some of my encodes.

http://forum.doom9.org/showthread.php?t=142706 --- copy the code into notepad and save it as .avsi instead of .txt and then copy that avsi file to your avisynth plugins folder.

[LoRd_MuldeR]

Hi guys.
subq and ref. Can these two settings be the reason for encoding delay in meGUI.

Please specify what exactly you mean with "encoding delay"!

[Jayzy]

Try sharpening with lsfmod(), I am a newbie myself so i don't know much about this filter. I have used this for some of my encodes.

http://forum.doom9.org/showthread.php?t=142706 --- copy the code into notepad and save it as .avsi instead of .txt and then copy that avsi file to your avisynth plugins folder.

Great. Thanks for ur reply. I'll try :o. Will this work with megui?

[Jayzy]

Please specify what exactly you mean with "encoding delay"!

It's take around 4 hrs. If I increase these settings (subq and ref) Will it take too long to encode?

[x265]

Please specify what exactly you mean with "encoding delay"!
I think what he means is the time it takes to encode that particular source.

[Guest]

@Jayzy

Do not open new threads for the same issue. I have merged the new thread back into this one. Thank you.

[Jayzy]

@Jayzy

Do not open new threads for the same issue. I have merged the new thread back into this one. Thank you.

Sorry for the inconvenience brother. I'll never repeat this.

[Asmodian]

Raising subme (subq = subme) and ref can have a very large impact on speed, we would need to know what values were used in both encodes to be able to say if that large of a change in encoding speed was expected.

Sorry I haven't used MeGUI in years and don't know what values it uses for the presets.

[Jayzy]

Raising subme (subq = subme) and ref can have a very large impact on speed, we would need to know what values were used in both encodes to be able to say if that large of a change in encoding speed was expected.

Sorry I haven't used MeGUI in years and don't know what values it uses for the presets.

Okay bro. What about handbrake?

[x265]

Jayzy >> It's not good since you can't use aviscripts.