4.35 4.36 4.35...

[GooglyBear]

weirdest thing happened.. last night, i rebuilt my pc
reinstalled IC7, patched it once to the 2nd update
did 2 registry hacks.. dvdsavequality and analyzemaxrel

encoded 8mile = 4.35
encoded saving private ryan = 4.36
encoded seven = 4.35

the funny thing is.. all i do is set the bar to "4.35" and it encodes it to that size.. i know it for a fact because the first time i did 8mile after the rebuild, i set the bar to 4.38 and got a 4.39 pdi so i lowered it to 4.35 and got 4.35

hmmm this is some streak.. all i do is deselect the audio streams i don't want to keep, deselect the xtra's i don't want.. set the bar, hit f5 and let er rip..

right now i'm encoding red dragon.. the bar was set to 4.35 again, same steps.. i'll post another update on final size

but this is interesting.. perfect sizes all the time??? sup with that.. (and no this ain't no april fools, it's april 2nd after all)

[GooglyBear]

red dragon just finished, final size of pdi's 4.36
:confused:
in a way im glad but im wondering how's this happening.. is it the steps (i always do it the same way.. hell im superstitous now)
deselect audio
deselect xtras
set bar
f5 --> go

hmmm.. i'm going to do another movie
good will hunting
let's see how this turns out

btw, fyi..
maxrel = 16
savequality = 0

those were the changes i did

[GooglyBear]

got greedy.. i got greedy! :devil:
i set the bar to 4.38
final pdi size
4.40

bah re-encoding with bar set to 4.35, heh

:scared:

[mrbass]

doing Gladiator right now with update2
dvdmaxanalyzerel set to 100% and dvdsavequality set to 0%.
6.20GB came out to 5.21GB
5.2GB at 81.85% 4.9GB (I think..crap can't remember)
set 4.66GB 72.35% (just started so I'll see)

If it doesn't come out below 4.37GB I guess I'll try your new trick and set it to 4.37GB.

[GooglyBear]

Originally posted by mrbass
doing Gladiator right now with update2
dvdmaxanalyzerel set to 100% and dvdsavequality set to 0%.
6.20GB came out to 5.21GB
5.2GB at 81.85% 4.9GB (I think..crap can't remember)
set 4.66GB 72.35% (just started so I'll see)

If it doesn't come out below 4.37GB I guess I'll try your new trick and set it to 4.37GB.

it's weird ain't it.. i noticed that too, it would be off by a few MB
like when i set it to 4.38, it did 4.40
i think for me the sweet spot is 4.35
it consistently produced the sizes above
right now i got about 48 minutes remaining on this session i figure after i watch ANGEL it'll be done :D

i'll post screenshots afterwards as i still haven't deleted the pdi's of red dragon, private ryan and this one is seven

[MackemX]

are you doing complete DVD's or movie only?

what format are the DVD's?

I created my own DVD to try an create the vobtrans.ax error and discovered a few more things

I had a titleset of 270MB with 5 titles each with a separate VOB ID

if I set title 3 to 50%, it copied titles 1 & 2 over at the processing speed and it also reduced titles 1 & 2, even though they were set to 100%, titles 4 & 5 were transferred across at high speed and were left alone

IC is all messed up and ain't gotta clue when it's reading IFO's and cannot seem to seperate titles within a title set

this will explain and confirm why some people have experienced times when it seems to process a title yet they set it to 100% as something else in the titleset is being processed

I'm trying to create a miniDVD for Pinnacle that crashes so they can use it as they state they cannot help with other problems as posted here on their forum

Pinnacle say they can't help (http://webboard.pinnaclesys.com/read_messages.asp?WebboardID=1&ForumID=877&SectionID=170&ThreadID=136109&ThreadStart=0&Pos=3&cntThread=121&lng=1)

[monomer]

Well I used to get final sizes that were very close to my settings way back when I was still using the DVDmagic trick and de-selecting all except the movie and the soundtrack I wanted but the problem was it wouldn't play in my Sony stand-alone. So now I strip out the movie and soundtrack with IFOedit and then run IC and my final sizes are always way too small! (...but the good news is that these backups will now play perfectly in my Sony:)

Recently I 'discovered' something while trying to run IC on two relatively "small" movies (Serendipity @ 4.44Gb and The Family Man @ 4.52Gb). I first ran them in IC at ~97% and ~95% respectively and they came out small 4.01Gb and 3.89Gb. When I used 100% they came out at the original 4.44Gb and 4.52Gb... no surprise there. But then I tried just 'one tick' down at 99.66% and got the same 4.01Gb and 3.89Gb file sizes again. What does this mean?

[GooglyBear]

setting it down to 4.35 again produced an almost-exact filesize.. final pdi was 4.34

various pdi's all encoded today
http://neotericdreams.net/images/misc/reddragonpdi.jpg
http://neotericdreams.net/images/misc/saveryanpdi.jpg
http://neotericdreams.net/images/misc/sevenpdi.jpg

i already deleted my 8mile pdi and right now i'm firing up good will hunting.. but the 8mile was 4.36 if i remember correctly

MisterX: i pretty much select all the xtras.. the only thing i really deselect are the unwanted audio streams..

this is freaky.. but in a good way
i got greedy though and set it once to 4.38 to see what happens.. final pdi was 4.40 (seven dvd)
i brought it down to 4.35 and final pdi came to be 4.34 :D which is fine by me

[mrbass]

Originally posted by GooglyBear
weirdest thing happened.. last night, i rebuilt my pc
reinstalled IC7, patched it once to the 2nd update
did 2 registry hacks.. dvdsavequality and analyzemaxrel


you never said what you set those two registry entries to.
I had dvdsavequality set to 6 and dvdAnalyzeMaxRel 7 (both default)
set Gladiator to 4.37 and it came out to 4.01GB. Then I changed dvdsavequality to 0 and dvdanalyzeMaxRel to 100 and set slider to 4.37GB and it came out to 4.23GB. So it seems to have an effect now with update2 as before it would still result in the same thing.

I'm gonna try 4.5GB and see if I can't get 4.36GB.

[MackemX]

Originally posted by mrbass
you never said what you set those two registry entries to.
I had dvdsavequality set to 6 and dvdAnalyzeMaxRel 7 (both default)
set Gladiator to 4.37 and it came out to 4.01GB. Then I changed dvdsavequality to 0 and dvdanalyzeMaxRel to 100 and set slider to 4.37GB and it came out to 4.23GB. So it seems to have an effect now with update2 as before it would still result in the same thing.

I'm gonna try 4.5GB and see if I can't get 4.36GB.

he did say in his 2nd post what he set them to

it cos you changed the savequality from 6% to 0%

that's simply why you got the increase from 4.01 to 4.23 :)

I suggest you always set it to 0 as it will give 100% of the allocated 4.37 to the DVD, whereas set to 6% it will reserve 6% of 4.37Gb which is 0.26Gb :)

so now are you with me?. If you ran it again with the savequality at 0 and samedvdAnalyzeMaxRel 7, you would probably get 3.97Gb (4.37Gb minus 0.13Gb lost due to inaccuracy of analysis and 0.26Gb reserved)

0.26Gb has been the reserve, then add to that the slight margin of predicted size error due to only analyzing 30% of movie will result in files around the 4Gb mark if correctly sized at the beginning getting rid of missed MB

I do hope you now follow :D

the 0.14Gb you lost is probably down to the black content or any small black lines cos 4:3 DVD's come out just about spot on with 98.5+% accuracy with a savequality of 0

the latest update produces better sized results but still not perfect, but you don't have to oversize as much now

I would only oversize by 4% of widescreen video content now instead of 7-8% for movies and 2% for fullscreen content

[GooglyBear]

-sigh- all good things as they say..

woke up today to check on good will which i left encoding overnight..

bar set to 4.35
final pdi
4.11 :angry: grr, damn

[red321]

Just ran Saving private ryan, region 2. Set the size to 4.35, by tweeking the main movie.

Version 7.02
maxrel = 16
savequality = 0

resulting image size 4.43 GB. No Cigar :(

[MediaMage]

ds9 season 1 dvd 2

size set to 4.35 gb= final size 4.8 gb

size set to 3.95 gb= final size 4.77 gb

size set to 2.5 gb= final size 4.5 gb

i´m giving up

[GooglyBear]

Originally posted by red321
Just ran Saving private ryan, region 2. Set the size to 4.35, by tweeking the main movie.

Version 7.02
maxrel = 16
savequality = 0

resulting image size 4.43 GB. No Cigar :(

:( here's something interesting..
what if we ran the same movie, same settings.. but on different pc's... i wonder if the pdi's would be the same :D wouldn't that be freaky if IC had different resulting pdi's based on same settings!!! LOL

anyhows i had a good streak..
4 movies with almost-perfect final sizes..
only the recent one, goodwill messed me up
but i'm not daunted.. i'm firing up Gasaraki #2
and maybe later tonight, Color of Night
and see what i end up with

heh, one of these days, IC will produce the size you specify.. hopefully

[MackemX]

Originally posted by red321
Just ran Saving private ryan, region 2. Set the size to 4.35, by tweeking the main movie.

Version 7.02
maxrel = 16
savequality = 0

resulting image size 4.43 GB. No Cigar :(

I cannot understand how some of you are oversizing, I never oversize :confused:

there are 2 things that it could be when you oversize and this is what to check for

firstly check out for missing MB's that IC does not show in final predicted filesize by autoresizing as these will increase the final size as they are not accounted for in the predicted size and this has been as much as 0.6Gb for me when I discovered it

http://www.deano.dsl.pipex.com/temp/sims3.htm

also still images affect the oversizing as IC cannot compress them. It's a bit complicated to explain but believe me it does struggle and on occasions oversizes on such things

that's why it's best to use the Title size recorder in my guide or you will just be searching for a needle in a haystack if you run it again and again guessing teh size as you will not know what title is oversizing your final result

http://www.deano.dsl.pipex.com/backup/filesize.htm

the movie itself will be ok, it's the menu's and extras that cause the oversiing problems

Guys it's upto you if you wanna follow this method but I can tell you now most of my DVD's end up around the 4.37Gb mark, with the last one actually being 4.38Gb with 0.7MB to spare!

what you oversize by depends on the content and it's screen format as 4:3 only seem to be out by 1% and most 1.85:1 movies by 4-5% since the last update with the above reg settings

I cannot express how succesful it is for me with 5 mins preparation and maybe 5-10 mins tidying up if I oversize by a little

you will come up with your own methods and no doubt others will post them to, but believe me this has worked since I first started using it and I've only fine tuned it to suit the updates and changes in reg settings etc

NJOY :D

[mrbass]

ok missed that..second post..anyways I follow and I knew that but didn't know that..lol

anyway gladiator set to 4.5GB came out to 4.34GB so that's good enough for me.

[GooglyBear]

Originally posted by mrbass
ok missed that..second post..anyways I follow and I knew that but didn't know that..lol

anyway gladiator set to 4.5GB came out to 4.34GB so that's good enough for me.

maybe for your current setup 4.5 is the sweet spot? try another dvd at that setting and see what you get

for me it seems 4.35GB is the sweet spot (err, ignoring the good will hunting 4.11 fiasco) lol

[mrbass]

ok now I'm doing monsoon wedding which (I strip streamed them so main movie only with subs and ac3 5.1 sound only) that is 5.89GB and I set slider to 4.53GB and see if I don't hit the gspot. Will post in a couple hours.

[red321]

MisterX

I cannot understand how some of you are oversizing, I never oversize

I have only seen this since I moved to 119, and started playing with the registry settings. I ran private Ryan Region 2 again, completely default, Auto sizing, no titles or audio tracks removed but with these reg settings and got an oversized result.

Version 7.02
maxrel = 16
savequality = 0

resulting image size 4.43 GB.

So its easy to get oversized :D ;)

[MackemX]

that's why I asked this
firstly check out for missing MB's that IC does not show in final predicted filesize by autoresizing as these will increase the final size as they are not accounted for in the predicted size and this has been as much as 0.6Gb for me when I discovered it

http://www.deano.dsl.pipex.com/temp/sims3.htm

also still images affect the oversizing as IC cannot compress them. It's a bit complicated to explain but believe me it does struggle and on occasions oversizes on such things

that's why it's best to use the Title size recorder in my guide or you will just be searching for a needle in a haystack if you run it again and again guessing teh size as you will not know what title is oversizing your final result

http://www.deano.dsl.pipex.com/backup/filesize.htm

If it's oversizing then something is wrong, so try to isolate it. Default you say, so it ain't being processed by a third party when you say ran it complete default so that ain't it. I assume you ripped it correctly so that won't be it

Is the total size displayed by IC when everything is included and set to 100% the same as the actual DVD folder?

If it was did you record the original/predicted and after title sizes?. I bet the movie title aint oversized and if everything else was ok before processing then one or more of your titles will be to blame cos it ain't reducing to what it said it would

simple checks taking only a few moments but saving hours in the end :)

I must have a different version then :), cos agreed I've had problems with sizes but normally find the root of the problem either before processing cos of missing MB's or cos IC cannot compress the extras like it says it will so I adjust it accordingly during the quicker 2nd run

I suggest you check the before and afters and for the sake of 5 mins recording the sizes you won't have to play the guessing game like some of you chaps are

3 runs just guessing like xxxxxxxxx just did just wastes time and effort if you get nothing at the end of it and you still ain't no further forward after the 3 runs

if everything is fine and you;ve checked IC's displayed sizes are valid then try recording the sizes and you will spot the title at fault straight away after the 1st run, believe me when I say this

the tools are there, use them and get the same success I do

it ain't quantum physics guys, its writing down a few numbers and comparing them so please try it and you will eventually see why I'm ranting on

sadly, I will have to do this until Pinnacle sort it out but I'm happy to do that if I wanna use this program for my processing cos I want results and I want them fast and I get them

links are in quote above and I hope you take my advice :)

p.s. savequality set to 0, just means nothing is being reserved from the 4.37GB which is what I now use

maxrel just depends on how long you wanna wait for analyzing cos it's still a shot in the dark even at 100, so that's why mine set to 10% cos it's normally enough and gives results within the target specified

cheers

[mrbass]

ok well monsoon came out to 4.42GB(slider set to 4.53GB)
monsoon is - 1.85:1 Non-Anamorphic Widescreen
while Gladiator is Widescreen anamorphic - 2.35:1

now gonna set slider to 4.45GB

[MackemX]

mrbass you are playing a guessing game :)

using low savequality settings with latest version of IC a 1.85:1 movie undersizes by 4% of the predicted video size

are you doing movie only? no menus

if so how big is the original video file and how big are audio/subs?

did you strip it with DVDToolbox first?

[mrbass]

yes stripped with DVDToolbox main movie only
movie + audio is 5.88GB
without auido movie only is 5.53GB

I'm setting 2% of 5.88GB = .12 + 4.37 = 4.49
ok so I set it to 4.48GB (I said 4.45 but just recalculated) and will see

now Gladiator was 6.22GB total after dvdtoolbox stripped it.
6.22 x 2% = .13 + 4.37 = 4.50GB
I set it to 4.49GB and it came out to 4.34GB

[MackemX]

please take time to read :)

ignore audio/subs that is a constant :)

you need to look at the video only

you have 5.53Gb of video and 0.35Gb of audio

you have 4.02Gb for the video available for the video so that means normally you would use a setting of around 72.69% to fit it into 4.37GB predicting 4.02Gb of video and 0.35Gb of audio making 4.37GB (these are estimates and not exactly correct to the MB)

now this 4.02Gb predicted will undersize so that's why you add the extra % based on this figure and not the audio

with a savequality of 0 add 3% of this 4.02Gb (which is 0.12Gb), so that means an overall predicted size of 4.49Gb (4.37+0.12)

I used 4% before but that was when I had a setting of 1% on the savequality as the instantcopy settings program version I used didn't allow 0 so I've set it to zero manually

the % you use is upto you but 3% should be fine for most 1.85:1 DVD's

p.s. I'm still unsure about using DVDToolbox and then IC as I showed with the Road To Perdition where there was 0.12GB of difference between the DVDToolbox stripped film and the original directly fed to IC. IC seems to be at fault

IC checks audio sizes before showing the sizes, so personally I think it's down to IC not seeing the correct sizes of all the audio tracks for the movie title as in RTP it has 2Gb of audio/subs

If it estimates it's 2Gb then it would take that off the title size and therefore estimate the video size being the remainder

whereas with only one soundtrack from the stripped version using DVDtoolbox the audio size will be more accurate so therefore more accurate in estimating the video size

sounds confusing but look at the pics below to see what I mean in simpler terms. Same movie, same length displayed yet the original video size has a difference of 0.12GB!!!!!!!!!!!!

So again would this not affect IC's prediction of resulting filesize cos it cannot see the true size of the video?

size of DVDtoolbox stripped, movie only (http://www.deano.dsl.pipex.com/temp/rtp/rtp1.png)

size in IC using full original version (http://www.deano.dsl.pipex.com/temp/rtp/rtp3.png)

I guess one way to find out is use and strip all the audio and keep video at 100% then reload the IFO as the video should be the same size but I bet it's not

then strip the audio out using DVDToolbox and I bet the video is the same as IC's stripped version

this maybe why some people have reported oddities in video size when copying at 100% and only stripping audio

think it's another bug :D

[mrbass]

son of a gun it came out to 4.38GB....ok maybe I'll do the ol 2% but add it to 4.35GB to leave some headroom.
This time I'm gonna do it at 4.45GB cuz the slider won't let me choose 4.46GB.

[red321]

MisterX,

I think you missunderstood the point of my first post. I appreciate the help you have given, but I was merely replying to GooglyBear's post that he was getting 4.32 by setting 4.35 with Private Ryan. I assume that he is processing another version. I was working on the Region2 PAL widscreen version. If we are getting diffrent results with the same settings and the same source, that would indeed be odd. I should point out that I have had odd results with 100% copying, that I have mentioned in other posts, that seem to agree with Mrbass, but disagree with others.

My second post was just to point out that IC WILL oversize, even though the normal experience is undersizing.
Just to make sure I wasnt missing somthing, I checked your guides, and found:

1) No missing MB, so IC7 thinks the whole movie is the right size.

2) then used your neat spreadsheet, before and after.

Odd thing with this movie is that the main movie was oversize !

Dvdsavequality = 0
;)
TITLE ORIGINAL ACCURACY
1 103.00 101.64
2 97.28 99.92
3 250.00 99.84
4 5765.12 102.25
5 861.00 101.46

Please note I am not expecing you to fix my problems, or questioning your good advice to the forum.:D Just pointing out that I am not experiencing the same as others.

[MackemX]

Originally posted by mrbass
son of a gun it came out to 4.38GB....ok maybe I'll do the ol 2% but add it to 4.35GB to leave some headroom.
This time I'm gonna do it at 4.45GB cuz the slider won't let me choose 4.46GB.

mrbass, highlight the % slider bar for the title then use your arrow keys to add or reduce 0.1% :)

this allows fine tuning as using the mouse arrow cannot allow these adjstments

[MackemX]

Originally posted by red321

TITLE ORIGINAL % PREDICTS ACTUAL ACT % ACCURACY
1 103.00 49.68 51.17 52.01 50.50 101.64
2 97.28 49.68 48.33 48.29 49.64 99.92
3 250.00 49.68 124.20 124.00 49.60 99.84
4 5765.12 49.68 2864.11 2928.64 50.80 102.25
5 861.00 49.68 427.74 434.00 50.41 101.46

Please note I am not expecing you to fix my problems, or questioning your good advice to the forum.:D Just pointing out that I am not experiencing the same as others.
;)

lol :D, when I click quote I can see your figures like this. If you use the # beside the PHP button on stuff like that it's great, I only learnt last week :confused:

TITLE ORIGINAL % PREDICTS ACTUAL ACT % ACCURACY
1 103.00 49.68 51.17 52.01 50.50 101.64
2 97.28 49.68 48.33 48.29 49.64 99.92
3 250.00 49.68 124.20 124.00 49.60 99.84
4 5765.12 49.68 2864.11 2928.64 50.80 102.25
5 861.00 49.68 427.74 434.00 50.41 101.46

I agree IC does oversize on some titles but this shows it is working correctly, movie title or extra title, but anyway I think I have an answer for some of that oversizing/undersizing :), but I didn't mean anything by my suggestions that you were struggling but more as a pointer to others

anyway I'll be back later cos I've noticed another bug about IC :(

cheers

[mrbass]

Originally posted by mrbass
son of a gun it came out to 4.38GB....ok maybe I'll do the ol 2% but add it to 4.35GB to leave some headroom.
This time I'm gonna do it at 4.45GB cuz the slider won't let me choose 4.46GB.

ok so I did what I said and it came out to 4.36GB so I'll try the 2% reduction then the old add 4.35GB to it.

[MackemX]

@red321

this is the issue I was talking about earlier but was busy writing it up :)

LINK (http://www.deano.dsl.pipex.com/backup/guesstimates1.htm)

It may or may explain why the movie oversized in your case but it is still an important issue with IC and it's resulting filesizes

along with the other identifying the true content of the DVD content issues I've shown in my guide, I'm surprised IC gets as close as it does sometimes :p

[mrbass]

that's why I don't trust IC....I am taking 2% off what dvdtoolbox says not what IC says.

[MackemX]

I thought was DVDtoolbox way to blame when I first noticed this but it turns out it's IC again!

I will also use DVDtoolbox for sizing and even better if you want the exact amount it only takes a few mins to analyse it using DVDToolbox

IC is a total mess and needs some work fixing this and other issues regarding title size amounts

until then I'll have to babysit it when I do use it :(, but I feel sorry for users unaware (or not) of these pitfalls and not doing a few simple checks until it is fixed, if it ever is

I've also posted on the Pinnacle forum about this issue just so they are aware of it but I doubt much will be done

why can DVDToolbox identify the estimated video size within seconds yet be correct and IC is can be as much as 0.17Gb out?

one word, UZZZZZZZZZZZZZZZZZLESS! :confused:

[mrbass]

yeah...dvdtoolbox for me has always been within 0.2GB of the real size. It takes about 5 mins or so for a for a 'real analysis'.

[MackemX]

just did another 4:3 series DVD and got it to 4.37GB adding 1% of the all video when I set it to predict to fit 4.37Gb

It had no hidden MB and IC saw it's true vide sizes cos I checked it was the same as DVDToolbox's size

DVDAnalyzeMaxRel=10% DVDSaveQuality=0 DVDAnalyzeMinAbs=40MB

predicted to fit 4.37Gb (video=4.07Gb, audio/subs=0.31Gb)

1% added predicted 4.42Gb (video=4.11Gb, audio/subs=0.31Gb)

resulting file 4.37Gb (video=4.07Gb, audio/subs=0.31Gb)
few mins work resulting in only 4Mb to spare :)

p.s. is it me or has anyone noticed that IC now runs a litle slower?

[jippiejajee]

Originally posted by MisterX
just did another 4:3 series DVD and got it to 4.37GB adding 1% of the all video when I set it to predict to fit 4.37Gb

It had no hidden MB and IC saw it's true vide sizes cos I checked it was the same as DVDToolbox's size

DVDAnalyzeMaxRel=10% DVDSaveQuality=0 DVDAnalyzeMinAbs=40MB

predicted to fit 4.37Gb (video=4.07Gb, audio/subs=0.31Gb)

1% added predicted 4.42Gb (video=4.11Gb, audio/subs=0.31Gb)

resulting file 4.37Gb (video=4.07Gb, audio/subs=0.31Gb)
few mins work resulting in only 4Mb to spare :)

p.s. is it me or has anyone noticed that IC now runs a litle slower?

Hi MisterX, your are making almost a science of analyzing and minimizing the re-size issue, incredibly, but I must say it pays off, the 'lost' space is considerably reduced.
Question what are the decimals values you would advice te enter in the registry for DVDAanalyzeMaxRel, DVDSaveQuality, DVDAanalyzeMinAbs

[MackemX]

the lost space is reduced because you are setting the DVDSaveQuality to 0. This is just a reserve % like DVD2One's reserve MB feature

set to 0 it reserves no space and uses the full 4.37Gb whereas before it would reserve 7% of the 4.31Gb which is 0.30Gb. That's why most people got around 4Gb, give or take a few 0.0xGb's apart from the 'oddities' because of the 'phantom' and 'original video size' bugs I have shown in my guides

If you give IC a DVD which it recognises the true size (checking for hidden MB's or inaccurate reported original video sizes) to begin with, it's between 98%-102% accurate with these reg settings

a 1.85:1 film is a little less more accurate and has a slightly larger margin of error but still within a specific margin, but again very predictable if you check the 'true' sizes first

I get between 4.35Gb and 4.39Gb now (50MB window). I'm not bothered about a PDI that's over 4.37Gb cos I just reduce one of the extra titles by a few MB's and stick it back in (10mins work). If I would not be able to correct a slight oversize due to lack of small extras or a movie only, I would use a slightly smaller oversize % in relation to video format in the 1st place

the settings when entered into registry should be
DVDAnalyzeMaxRel = 0a
DVDSaveQuality = 0
DVDAnalyzeMinAbs = 10

and it show up like this

DVDAnalyzeMaxRel = 0a(10)
DVDSaveQuality = 0 (0)
DVDAnalyzeMinAbs = 10(16)

I am bit deep into ain't I :D, but I like a challenge and this is a challenge and it's just about finished as I see no more unknown problems that I cannot overcome using IC

it ain't a science, it's basic mathematics really and all this info is there to help everyone and show that for 5-10 mins prep work you can actually get excellent results outta IC :D

sadly this 5-10 mins checking/working out needs to be done if you don't wanna keep guessing when it oversizes/undersizes and get nowhere after hours & hours like some people do

hope it helps at least one person :)

[red321]

p.s. is it me or has anyone noticed that IC now runs a litle slower?

Mister X,

Wondered when somebody was going to mention this. 119 seems quite a lot slower then 114 was. I am running win2K sp2, 1600+xp and 512 DDRAM, and movies seem to be taking closer to 3 hours to process rather than the previous just over 2.

[jippiejajee]

Thanks MisterX for clear reply much appreciate
You are right that it is worth to put in 5-10 minutes preparation but the tricky point is that first you need to know what you have to do. And we are lucky that that there is somebody like you who has put in probably many hours to come to the correct way of work. Thanks again for sharing your experience.

Jippie

[mrbass]

I did saving private ryan NTSC R1 stripped with dvdtoolbox
6.41 (dvdtoolbox reports) x 2% = .13 + 4.37GB = 4.50GB...
I set slider to 4.50GB then it came out to 4.36GB.

[monomer]

You guys keep talking about final size predictions as if you understand what IC7 is doing... okay explain this...
last night I did a IFOedit 'strip the movie' of Sleepy Hollow and ended up with a VIDEO_TS of 5.19Gb. I then ran IC set to 88.79% (4.62Gb) and ended up with a finished file size of 4.02Gb. Because I felt this was too small and I should be able to do better I re-ran IC this time set to 94.22% (4.9Gb) and ended up with a final size of 3.91Gb!? Huh??? Sleepy Hollow is 2.35 and a very dark movie so I can understand the extreme compression but how the heck do you explain a SMALLER file size after selecting LESS compression of the same movie file??? Predicting final file size is such a 'crap-shoot' with IC7 anymore. I don't understand how everybody keeps talking about being able to predict the final file sizes... as far as I can tell it's all pure guessing.

[MackemX]

Originally posted by monomer
Sleepy Hollow is 2.35 and a very dark movie

2.35 is the keyword

the reason why is HERE (http://www.deano.dsl.pipex.com/backup/sizing.htm)

basically you cannot do 2.35:1 movie only and get 4.37Gb with IC unless it's either a huge one, or you do actually keep the extras :D

I guess I must be lucky then cos I've guessed mine all the time :D

hope this helps

p.s. what are your reg settings?

[monomer]

Mr. X
I pretty much have kept all the default settings except for the DVDsavequality I have set to Zero and I have True as my setting for DVDmagic (also I've turned off the preview to speed things up a little)... anything that's single layered I do an ISO (both read and write) in DVDecrypter... if its over 6.2Gb I'll do a 1:1 and split to 2 discs... If its an "in betweener" then I'll either do IC or DVD21... but lately IC's random final file sizes have been driving me crazy. It's turned what should be a simple ~1.5 hour compression routine into a 3-6+ hour guessing game filled with frustation. (BTW, I always 'strip' to movie only with IFOedit before compressing.)

[MackemX]

the only time IC is unpredictable is when you try an do a movie only with a 2.35:1 or letterbox movie

IC sizing is not a guessing game, it's simple mathematics unless it's a movie like the one you have

this is because IC cannot deal properly with these black bars that are contained within the actual image and not created by the player

until Pinnacle deal with it then it will still vary wildly whenever you try to reduce it, so that's why you got the results you did

If you set it to 70%, you would find it will probably come out ok, but any higher than a certain percentage then IC will just create random sizes

as for the speed issue, IC is now works slower with the latest update but I ain't complaining cos it's now even more predictable if you do a few important checks 1st

I have always found it predictable for the movie title.I have stressed that since day 1 using a simple method, it's the extras that caused greater problems due to varying content but even that is easily corrected

this is one 'bug' I couldn't find a simple solution to. Well actually there is a simple solution and that's to use DVD95Copy or DVD2One if you have them, cos it hardly affects the main image and gives very high quality due to the large saving from the black bars

p.s. do you keep menu's?, if not use DVDtoolbox as shown in mrbass's GUIDE (http://www.mrbass.org/dvdtoolbox/), great for movie only

[filmking]

I've been using the same procedures as Monimer. With a 2.35:1
movie (ABANDON... very dark too) I've tried in vain to get IC7 to work. Usually after IFOEDIT
creates the movie only I have a 5.8GB folder which IC7 then can't make any bigger than 3.02GB no matter what I put the slider at. With these 2.35:1 films I now no longer bother making a movie only version with IFOEDIT... I just have IC7 do the entire disc w all the extras and wind up with something like 3.8GB. Interestingly, the picture still looks damn good. IC7 would sure be great if they could remedy this black space bug.

[monomer]

Mr. X...
Thanks for the explanations and the links... though I'm not sure I really fully understand it all. As for keeping the menus... nope. I actually prefer to just put in a movie and have it start immediately with a DTS soundtrack (DD 5.1 if DTS was not an option). Menus I can have anytime I want... just slip in the original DVD.
My needs are simple... I just want the movie to look like the original on a ~114" projector screen when played through my computer (meaning progressive at 856X480 pixel matched to the projector). Both DVD21 and IC7 are capable of this as long as I don't compress too much. The compression limits for my situation seem to be approximately 80% for DVD21 and about 70% for IC7. Compressing beyond those points, and I risk seeing various compression artifacts.