@SansGrip,
SansGrip wrote: Quote:
I tried to figure out how you determined the resize and crop values, but was at a loss. Still, adding Tmpgenc's resize decrease file size even more, so I went for it. 8) I gained ~1.5MB per 90 seconds of encode time and that allowed for a significant increase for CQ_VBR. :) -black prince |
Quote:
I got tired of this "Unpredictable" file size, depending on the resolutions. I did a test at 352x480, and the file size was WAY off 8O. So here's my latest findings and analysis. Just like the sampling theory, where you sample "at least" twice your highest frequency, a higher sampling rate with smaller windows should give a higher resolution than less samples of a larger window. The principle is that you have a finer grain resoution, the higher you go in sampling, and more "visibility" of the real material analyzed So I'm now testing 256 snapshots of 6 frames each 8O. It seems to give me almost the same sample file size, no matter what resolution I use :wink: So theoretically, this should be more than enough for ANY film of just about any size. You might as well set prediction factor to 1.0, because what I see is that the final size is now almost 100% accurate with the formula. Here are my three tests at different resolutions: Code:
352x240, Sample size=7,010KB, CQ_VBR=29.88 My own feedback. This doesn't work!. 256/6. Back to the drawing board. Now trying 128/24 ... -kwag |
Quote:
Quote:
Quote:
|
Quote:
Quote:
Quote:
|
@SansGrip,
SansGrip wrote: Quote:
mask settings. The numbers would not take and defaulted to 0. :( For DVD 3/4 small a output (528x480) and TV-overscan 2 the resize is BilinearResize(496,352,22,0,676,480) and AddBorders(16,64,16,64). :? Not sure how to get this setting in FitCD. :? I tested Tmpgenc's resize vs avs script resize with no filters and there is a decrease. I will test another movie and see if the results are them same. :) @Kwag, Kwag wrote: Quote:
IL = Framecount / 50 SL = round(Framerate) * 2 SelectRangeEvery(IL, SL) Are the CQ_VBR values a starting point :?: -black prince |
Quote:
Code:
IL=Framecount / 256 -kwag |
Quote:
Quote:
-kwag |
Hi SansGrip,
SansGrip wrote: Quote:
Test #1 Using avs resize LanczosResize(496,352) and AddBorder(16,16,16,16) with Clip Frame only in Tmpgenc. File Size = 18,547,704 Test #2 Using Tmpgenc's resize of 496x352 and Clip Frame. LanczosResize and AddBorders are commented and not being used. File Size = 17,252,889 The savings are 18,547,704 - 17,252,889 = 1,294,815 or 1.3MB 8O Picture quality and resolution are the same and of course excellent :mrgreen: I'm using LanczosResize and maybe that's why it decreases :?: -black prince |
Hey Kwag,
Kwag wrote: Quote:
Old = ((movie length / 100) * (test file size * .95)) = Total Video file Size New = ((movie lenght / 256) * (test file size * .98 )) = Total Video File Size :?: -black prince |
Quote:
LancosResize gives more sharpness, and that increase the file size. |
Quote:
You can calculate the Total Video File Size like this: (sample size / sample lenght ) * movie lenght * .98 note: movie lenght and sample lenght in seconds |
I just finished my first squeeze of a 120+ minute film onto one disc.
KVCD Predictor predicted 796 mb (CQ_VBR10.5), actual size 820mb (d'oh!). Used TMPGEnc's resizing, clipping, encoded at 480x352 (widescreen), new GOP. Quality is decent -- blocks are apparent on my 27" HDTV -- but for a 133 minute high-action film squished onto ONE 80-minute CD-R, I'm pleased =) It looks alright if you sit at a normal distance from the TV (6-8+ feet). I'll probably do two discs to improve the quality. EDIT: WOW! I was finally able to post on the board! =) |
Welcome grivad :D
-kwag |
Quote:
|
Quote:
|
Quote:
|
Quote:
Make sure you crop ALL borders from the source in Avisynth before running any filters on it (to reduce the work they have to do and thus speed things up significantly) and then resize within Avisynth using FitCD's suggestions. I'm certain that if you do this you'll find only a very slight difference in the two methods (and the difference will be due to the different resizing algorithms being used: TMPGEnc's is apparently slightly less "soft" than bilinear, at least according to my tests). |
Testing.... Testing ..... Encoding..... 8)
-kwag |
Just watched Resident Evil (352x480, CQ_VBR 15.55) and it looks very good -- not DVD quality due to the relative softness, but still very watchable and of course a lot sharper than standard VCD. Also the bitrate was high enough that there was hardly any noticible Gibbs...
Again, though, I had that freezing at the beginning of the disc. However this time there was very bad corruption at the end, video and audio, but only in the last 5 minutes or so. Is this another symptom of too-low minimum bitrate? |
Hi SansGrip,
SansGrip wrote: Quote:
same as yours. I used LanczosResize which add sharpening, so when I commented it and used Tmpgenc's resize the file size decrease was due to no sharpening. I'll switch to BilinearResize in the future. :? Thanks for being patient in answering my questions :) -black prince |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.