I just tweaked it a little more!
Now you can specify in the function calling the title of the movie, the number of CDs you are targeting and the correction factor. Code:
Prediction("Matrix", 2, .99) Here is the function: Code:
#---------------------# |
Quote:
If you put it right after the Mpeg2Source(), then it will be resized with the frame and should display correctly with any resolution. Try this way with the last script. It's working perfectly for me. edit: oops! Sorry kwag... I didn't hit the refresh and didn't see you post. :oops: :wink: |
Stupid me again :imstupid:
IT GOES AFTER THE MPEG2SOURCE LINE Quoting my original post: So put the Prediction() statement AFTER the line where you open the .d2v" That's the way it gets properly resized. I'm taking a break to clear my mind :twisted: -kwag |
Wonderful modifications muaddib :mrgreen:
Works like a charm 8) -kwag |
Work, but I can't see the title anywhere 8O
I'm checking the screen coordinates now :!: |
Quote:
I think that we both need a break... because we are both wrong! 8O :twisted: I was testing it with a 4:3 source, and it really works like a charm in this kind of source, but if we use a 16:9 source and use gripfit, it will cut the black borders and cut the displayed information too, than add the borders back again. So , at the end, I think we will have to use it after the filters. :? I have to go to work now, but I'm thinking in a solution... :wink: cya |
Here it is... (I hope it works correctly now :D )
The way you call it still the same. Use it at the end of your script, just before sampler(). Code:
#---------------------# |
Muaddib,
:ole: :mrgreen: Edit: It would be great if we could get the file name part from the mpeg2source line :!: Then the title could be automatically assigned to the variable :D Can't wait until AviSynth gets ported to Python code. Then I'm going to have MUCH more fun :mrgreen: -kwag |
Here's a slight but very usefull mod.
Change your Prediction("Matrix", 2, .99) line to Prediction("Matrix", 2, .99).Sampler(length=24) Now you only have to comment out this line after you read you values and encode away :D -kwag |
Quote:
|
Would it be possible to include as another frame the calculations for the new CQ?
SO, no need for a calculator or an Excel spreadsheet. Just edit the .avs, and include in the Prediction filter the obtained file size and the used CQ value. That would be very nice. Gaudi |
That can't be done Gaudi. The CQ must be found by running a full sampler on the movie.
-kwag |
Quote:
This would be great, but unfortunately while the script is processing we don't have the sample done yet, so can’t know what size it will be. edit: Wow... I'm 8 min late! That's what happens when you answer the forum while working... :D |
Mon Dieu! I have just walked away from my computer for a few days and when I come back you have all gone crazy with avisynth scripting!! :lol:
I have just used my old trick to keep up the pace = doing a search on "kwag" name to get an idea of the last plugins and scripts to use :wink: As I see it Kwag, you keep on posting your scripts over and over again. You should be praised for that, however here is an idea for you to spare your (golden) fingers. Before indulging in video encoding, I was playing with lame MP3 encoder and used to hang around a site called r3mix. It was all about finding the best settings to gest the best encoded sound quality (remind you of something? :roll: ). In between many changes and tweaking, the guy "in charge" used to post his last command line parameters somewhere on the site, so that anybody could use it for encodes. Each time a better tuning was found, after days of testing and postings (sic), he updated this "recommended settings". Well. I know that we can adjust our scripts according to source quality (ranking from excellent to crappy, even for $$$ DVDs), but a sticky post with a generic script still could do a lot good for the growing number of newcommers. Mmmm... Maybe simply updating black prince wonderfull "how-to" would do the trick too... Just an idea. Cheers. |
Hi Graal_CPM,
Yes, I know I have to put a sticky somewhere, but haven't got around to it yet :D I'll see what I can do, because it's easier to reply with a link, than write and write ( or copy+paste ) over and over again :lol: -kwag |
Probably what gaudi means is, after sampler encoding edit the avs script and put the sample mpeg size.
I don't know a lot about avs scrip but i guess it could be possible this way. bye |
Quote:
Well, that was exactly what I meant. Using the avs script as a calculator. I wouldn´t mind editing the script if that makes the use of a calculator innecessary. Thanks |
I don't know if this could be useful, but i changed the prediction script to choose the size of cd ( i often use CD-RW of 74 Min. ) like follow
Quote:
prediction("Matrix",2,.99,74) or prediction(cdtime=74) bye |
I changed the desired sample size to mb and truncated to four digits. Also rounded off the audio mb's.
Code:
#---------------------# |
This is getting better every day :mrgreen:
|
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.