Quote:
-kwag |
Video and audio at 112 kps.
|
Quote:
-kwag |
I used the 0.89 prediction factor.
|
Quote:
-kwag |
I'll encode "Patton" tomorrow (in Finnish time :wink: ) and see if the Predictor will handle this one, the movie's almost 3hrs long. I'll be using KVCDx2 PLUS at 352x576 and post the results along with the script as soon as it's done.
Edit: and to make it difficult for the Predictor, I'm putting permanent subtitles in the movie. It's going to be interesting to see what happens. |
Quote:
You really want to torture the encoder :lol: . Let us know your results :wink: -kwag |
Oh, forgot to mention that I plan to put the movie on 2 CDs. I can't use the LBR since my Pioneer doesn't like really low bitrates with VCD headers. If I use 352x288 and burn as SVCD (to allow using bitrates lower than 700), I get some annoying bob'ing in the picture, especially in the subs. If the resolution is n x 576, there's no problem.
|
Quote:
Then why don't just go 704x576 :?: Or x3 :?: If I put "Red Planet" on a single CD-R at 704x480, then you'll be coding only ~90 minutes per CD-R. So your 3 hour movie should look almost like the original in two CD's at 704x576 or 528x576 :idea: -kwag |
Quote:
If I really want to work on this, I'll test the Predictor with both options 8) I might just finish both tomorrow if I start early. |
Quote:
-kwag |
kwag, why did you change the mode from CQ to CQ_VBR anyway? what's the difference between these two?
Seriously they both look the same, to me, using your Q-Matrix and limit it to a certain file-size... |
Quote:
-kwag |
Quote:
The reason this occurs is because Blockbuster is adding random noise to the clip. Since it's random, it'll likely get encoded differently each time you run it. I just added a new parameter for the noise method allowing one to specify a value with which to seed the pseudo-random number generator. This should cause the same "random" noise to be generated each time you run the filter with the same settings. I'm testing it right now and will release later today if it's all working. |
kwag -
Just so I'm clear, if one increases the error margin in KVCDP from 5 to 11%, the target sample size should decrease, correct? |
Quote:
Edit: Or 200 samples of 12 frames each. This will increase the sampling resolution. Must try that too. -kwag |
Quote:
Quote:
Predicted size was 812mb with an error margin of 0%, final size is 808mb 8O. It does take longer to encode the sample strips, but it's surely worth it if it makes the prediction more accurate... |
Hi Kwag and those experienced users,
Correct me if I'm wrong. The NEW method is as follows: (1)---Commenting out the bilinear resize and add borders from the .avs script, and calculating the aspect to put it manually in TMPEG. Also, check that your masks are correct as in my second sample, because these will change once you remove the bilinear resize and add borders lines from your .avs script. This is what I did: My movie is 720x480, and my target is 704x480. So I use our friend FitCD, just to find out the values I need for my resize. When I open my .d2v, and I select XVCD (704x480) as destination with 2 blocks overscan, I see that the resize line is this: BilinearResize(672,352,16,0,688,480) so that means that I will use 672x352 in TMPEG under "Video arrange method: (Center custom size)" and use these values. (2)---Use new template with new GOP (1-12-2-1-24) (3)---Use predictor factor as 0.89 then we will be able to fit 90 mins into ONE CD-R???? |
Quote:
Personally I see a size increase when I switch from Avisynth's bilinear to TMPGEnc's internal resize. I have a feeling the big difference kwag saw was the result of adding borders after Blockbuster. But I could be wrong :). Quote:
Quote:
Quote:
|
Ok, here's the results of my tests wrt to bp's recent post about Blockbuster and unpredictable file sizes. I encoded a 2059-frame sample three times using exactly the same settings and script. Here's what I got:
1st encoding: 10,555,039 bytes 2nd encoding: 10,554,551 bytes 3rd encoding: 10,554,716 bytes So it seems Blockbuster does indeed cause some unpredictability. The amount of variation seen will depend on how much noise it's having to add to the source material. Now here's the same sample encoded with the same settings, the only difference being the use of the new seed parameter: 1st encoding: 10,554,519 bytes 2nd encoding: 10,554,519 bytes 3rd encoding: 10,554,519 bytes I can think of no reason why this would affect anything in an adverse way, so I'm going to package it up and make a release in a few minutes. |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.