Incredible and Zacks,
Thanks for the heads up :!: |
Quote:
PERO solamente usas/copias el códico del Asunto original aqui!!! Porque el Babelfish tambien modifica partes en el codico en la translación. http://babelfish.altavista.com/babel...p=en_es&tt=url Espero que te ajuda! Muchos saludos! Inc. |
Hi Inc...
One little question... How does the Slicer Routine determine the second Offset value? What's the criteria? :roll: |
Criteria??
Well the purpose of the pong offset is that the pong-slices will be in the position between the slices of the "ping" turn, so that effect. more movieinformation will be predicted in the same time than simply a normal prediction using more % of the movie. :wink: |
I understand the theory... :wink:
I just wanted to know why the value for the second offset differs from movie to movie. I for instance got 30 sec. as offset value. And I saw a post where it's 50 seconds... |
It mainly differs at diff. gop multipler settings as this results in larger slices with the same % of the whole movie = larger "holes" between the larger slices for example.
|
I really must thank you Incredible for making this "Slicer" routine :!: :wink: It has worked EVERY time for me so far. No more re-encoding movies that gets too big. :D
|
Also a nice advantage is that you can use it perfectly for mencoder or ffvfw prediction, .. cause its encoder independent ... just avisynth as frameserver is needed :)
MCE prediction "could" also be possible but the Q range of MCE is defenitely to small for acurate predictions. |
Quote:
What would you need with MCE, for accurate predictions. |
:)
Thanks but .... I do know MCE more than well and "one" of the bad things when doing Q VBR is that the range is def. too small (as I remember something approx. about 1-32). I tested MCE about for one week some month ago (actual release) and TmpgEnc does output better (and faster when doing a prediction in TmpgEnc compared to MCE at 2pass, if Q prediction in MCE is used to much failures accord. to filesize do occur cause of the reason expl. one line above). Best quantisation on the same endfilesize does deliver mencoder at specific settings (2 Movies on one DVD-R) even better as QuEnc which I tested this evening ("still" too less options to set for optimizing... but that will change in the next release I think). But ... thanx Inc. |
Here http://www.kvcd.net/forum/viewtopic.php?t=9832
there is a spanish traslation of this http://www.kvcd.net/forum/viewtopic.php?p=52657#52657 post. |
Quote:
http://www.digitalfaq.com/archives/error.gif |
Quote:
|
Hi:
@ Incredible I was just playing maths with your function, and found out that Code:
Round(((Frames/Framer)/60)/(round(((Frames)/100)/(gop*gl))*sa)*60)/2 Code:
Round((gop*gl*100)/(framer*sa*2)) Said this, I think your function can be improved in the following way: Code:
############################################################### Debug = 1 is only for that, you can set at 0 and you won't see any subtitle. (default = 0 this means inactive, 1 = Debug subtitle active) Maybe you will need to adjust your factor 1.009 (test it please) Code:
c = sampler(c,samples=(round((Frames)/(gop*gl)/100*sa*1.009)), Length=(gop*gl)) The other instructions just as in http://www.kvcd.net/forum/viewtopic.php?p=52657#52657 See you. Prodater64 |
NICE! :)
Thanks for taking the time to integrate that conditional auto off Method. I didn't integrate it cause many users do make Offs like ping=5 and pong=calculated_pong+5 as predictions will come out more accurate if the first seconds of the beginning wont be sampled, means these Frames in 99% of cases are just black and this will stand in no good relation to the 2% prediction of the whole movie. Also I leved it that way as this can be very nice tweaked to get diff. slices of test-encodes I did when testing FFvfw or Mencoder.... = better way to catch fast moving scenes for example. But anyway, your auto off routine will seem less complicated to noobs! According to the factor you discribed 1,009, ... well everybody gots his "own" perfect factor (as known from TOK) so evreybody can tweak here on his own. BUT pleas do not change the order of the variables in the Command as many users now are "acostumbrado" in those settings Slicer(percent, GOP, Offset, GOPmulti, Debug)! So the variable for mutiply the GopFrameCount should be still right behind the Offset determination of the Command Syntax. Yours is def. more logic, but changing this and on the other hand refering to my explanation at the start of this therad will cause confusion of Users :wink: To me it seems you're more in mathematics and if the "shrinked" calculation for sampler() will work the same, ok. Test this by using my latest and your new one on the same movie and watch the resulted framecounts in Vdub so you can compare. According to "no just Slicer()", This command doesnt get its advantage of default usage, cause anyhow we have to alter that by changing offsets or in your case from "ping" to "pong". Just slicer() would cause big noob confusions :wink: Thanks for participating in developement! Inc. |
Quote:
I already edited previous post. Quote:
Quote:
Quote:
Slicer(percent, GOP, Offset, GOPmulti, Type, Debug)! Quote:
I only found small differences round functions related. See you. Prodater64 |
Hi:
My first Ping-Pong Prediction (Incredible's Function) with Mainconcept Encoder. Not very easy, but thinking that is first time... http://www.digitalfaq.com/archives/error.gif Code:
Target Sample------------------------------------> 14438 KB |
Hi:
Quote:
Change log - Script can shows movie title on info screen. - Script show more info on screen. - Info screen don't show sample. Activate/Deactivate with Debug control. - "Control Panel" in avs for: set movie name, CD number, CD time, Factor. - Slicer Settings more comprehensibles, same order like Incredible original, plus Ping/Pong, Debug and Encode controls. - Easy to understand for anybody. This method has 1 avsi file, plus code to wright in your avs encoding file. AVS Encoding Script The statements after "Here your script" until "Not to modify" are just an example. You must to put your script there. Copy this script and paste it in you AVS script. Trebuchet MS font, normal, 12, 1024*768 optimized. Code:
############################################################### AVSI file Copy this script and paste it in a text file with avsi extension. Put it in your avisynth 2.5x folder. It is self explanatory. Code:
#------------------------# |
Where do you got all these CDs /CDtime parameters, and subtitel routines and so on ... is that inspired from the manual prediction thread??? As they also delaed with cd size and so on there. As I remember :)
|
Quote:
|
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.