Okay, I'll try it out. Thanks for you help, Boulder. BTW, should I use 24 for sample lenght also - on all source material (NTSCFilm, PAL & NTSC)?
|
Yes, it would make sense..until someone comes up with a sample length that gives a better prediction.
|
Thank you again, Boulder! You've been a great helper indeed...
:wink: |
okay, with all the latest talk on motion adaptive scripts and detecting scene changes, blah blah blah... got me thinking, should we be making any more changes to our tmpgenc settings than those in the old kvcdx3 template? I've read to change the motion search precision to fast (motion estimate search). But what about Detect Scene change (in the GOP tab) and the Special Settings (Quantize Matrix tab)? I just noticd there is an unchecked box for "No motion search for still picture part by half pixel"... Thanks guys!
|
Quote:
Quote:
-kwag |
Quote:
for the first time from days this is the first time that i got high CQ using the Boulder recomendations :!: maybe somebody remember a weeks ago when i post about low CQ. i did the test twice and ToK give me CQFinal CQ: 70,349 :D :D :D and before was CQ: 56,467 :arrow: huge difference,don't? i only uncheck the "Auto GOP" and wrote: 1,24,2,1,24! uncheck the "new faster prediction" and 2nd group of passes than i wrote this values: precision% 1,00 and speed up by 10 ! new video.en1 (thanks Kwag) only changing this line to: Job.MPEG.Video.VideoEncodeMode=MPEGVideoEncoder_Vi deoEncodeMode_interlace cos my source is 29,970,ntsc. the CQ: 70,349 is perfect for my desired size now! :D i'm happy and encoding now! thank you all friends, in special Kwag and Boulder for this result! :D :D :D |
should NTSC film users be unchecking auto GOP too? and manually entering a value?
|
Quote:
|
Quote:
Quote:
You wouldn`t use that GOP (24) with Anime/Cartoon...would you??? ******************************* The Devil`s always.....in the Details! |
Quote:
I had to reinstall my Windows (even manual repair failed) so i've only done 2 more tests, but i had an idea: Why not taking a longer sample size to make a better prediction with the adaptive script :?: I had good results with a Sampler length of 50, maybe 48 would be better. I thought that a bigger sample size than GOP would screw up Prediction or Sampler() but it didn't. Kwag, do you know why TMPGEnc encodes with a GOP of 24 instead of 25 with PAL-Sources :?: EDIT: Here is a comparison on a short movie (PAL): Code:
Sampler Length=48: |
I just finished encoding "Enough" (PAL) with GOP and sample size set to 24. And this is what I got:
Wanted size: 726 XXX XXX Encoded size: 721 XXX XXX (Don't have the exact numbers. I'm at work now) AMAZING! A difference less than ~0.7% :D !!! Final muxed movie was 795MB. I changed ToK's setting to what kwag recommended in an earlier post and used kwag's modified video.en1 file. Try it out all you PAL encoders out there. Thank you very much guys! Maybe I'll be able to sleep at night again now :wink: ! |
Hi, all
My way for PAL prediction is not fully tested (only two movies so far - an AVI and a DVD) but gave me for first time correct file sizes. Sample=1% of movie with the line in the script SelectRangeEvery(2500,25) run a sample at CQ100 without black borders. Mark the file size. Run the sample at CQ100 borders added. Mark the file size. Find the difference of the file sizes in %. Calculation of desired sample size samplesize=((fullvidoesize/totalframes)*sampleframes) + (% of the difference you found before). Hmm, sorry for the bad english. An example: A movie has 137145 frames. Final video size is 740912KB. Sample has 1375 frames. Sample size = (740912/137145)*1375 = 7428. CQ100 without borders = 15275 KB CQ100 with borders = 14569 KB Difference = 4.6% 4.6% from 7428 = 341 7428+341=7769 -> this is your real size of the sample. The results. AVI - required 730xxx KB, final encode 723xxxKB. DVD (the example above) encoded with CQ57 with sample size 7785 (a bit higher than the desired 7769). Required size 740912, final encode 742xxx (a bit higher). Well, it need to be more carefully tested. |
Quote:
|
Quote:
But I'll take a look :!: Maybe it's a bug in TMPEG :?: BTW, have you tried encoding with ToK with the screenshot I posted earlier :?: Here it is again: http://www.digitalfaq.com/archives/i.../2003/06/7.jpg -kwag |
Well I just have to post this one :mrgreen:
Here's my encode of K19, which just finished 5 minutes ago. Look at the log, and see for yourself :D Code:
============================================================= Thanks again to Jellygoose for suggesting to change asharp to unfilter on the adaptive part of the script. I'm updating the current script now. BTW, the settings I used for this movie are exactly as the screenshot above this post :!: I'm uptating the |
Thats great Kwag :D ,just a quick question with the new change in the script do you think we will be able to go back to the faster prediction in tok or still use the longer one.
Thanx |
Hey Bigg, I just tried Kwags settings vs tenras Fast prediction
Quote:
|
Quote:
I'll post the resulting CQ here in a while... -kwag |
Yes ovg64,i think we all could live with that :lol:
Looks like it might be a good night :D |
Quote:
Code:
============================================================= -kwag |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.