Log in

View Full Version : 3 Backup Attempts...3 different problems


recoil47
24th February 2005, 23:55
It seems that my excitement about completing a successful backup the other day was a bit pre-mature. I tried 3 different backups the last day and a half, and all 3 have so far been unable to complete --- for 3 different reasons.

From what I can tell, I'm doing things exactly the same way.

1) The most annoying issue, is the one I have just finished trying to do. Everything went along just fine...but when it comes time to BURN the files, or the ISO to the DVD...it says there isn't enough room!

IMAGE SIZE: 2,303,091 Sectors
DISC SIZE: 2,297,888 Sectors

How the heck to I fix this? As I mentioned, it looks like everything went along just fine. I got ZERO errors in Scenarist. This DVD had only one VTS file and it was huge. I encoded that, and left what little else there was untouched.

Very confused....

The other two issues are more complex, and I will attempt some more digging and attempts before posting questions. The one above though, I just dont get...

jel
25th February 2005, 04:02
very occasionally there can be issues with an oversized disc.

this can be for many reasons:

DTS audio
method of encoding
specification of dvd-size in dif4u
etc etc

my suggestions:

reduce the DVD - sixe in the DVD calc selection of DIF4u to safe -10 megs, to reduce any further oversize issues

re-encode the menu using numenu4u (if you havent done so already) or reduce the average bitrate and re-encode the movie asset again, or use shrink to reduce the total size to fit onto a dvd-/+r

Trahald
25th February 2005, 04:32
yeah.. shrink is usually good for quick fix.. it will only have to apply 98% so generally wont notice.. usually you can pick assetts like menus.. or remove and additional audio. i set my dvd size in dif4u to safe-50.. i prefer slightly smaller size than having to redo anything (50 mb compared to the gb size of dvdr is very small amount to lose)

recoil47
25th February 2005, 07:13
I havent been using NUMenu because its been far too tricky (for me) to get to work right. But I will take a look at trying to specify DVD size in DIF4U.

OK, I am letting this run overnight, so I will see the results tomorrow (as it takes like 5+ hours to encode this sucker (3+ hour miniseries).

I did find the DVD CALC section in DIF4U 1.4.7. and I used it. It did calculate some data. What I dont know right now, is if that data is being USED. All that I can see is it calculated some sizing numbers. Does stuff from the DVD CALC automatically get incorporated into a script? Or is it something I need to know for manual work later?

I did set it to the -10Meg selection, but again, dont know if that was all that was needed. Can someone answer this? by the time I am able to look at this again, the Encoding will be done, and everything will be imported into Scenarist. Hopefully the CALC thing worked and the sizing is right.

If I needed to do something else...then it wont work. Did I miss a step? If so what?

Thanks!

muppets
25th February 2005, 09:35
DIF4U includes the bitrate calculation results in the CCEData.txt file. You don't need to do any manual calculations. Just set the DVD-R Size to Safe-10 and everything else is done automatically.

recoil47
25th February 2005, 23:23
Arrrg.

What sucks is I did use the Safe - 10 setting...and it still was too large (just barely). So now I assume I have to use the Safe -30 setting. Its kinda harsh that you find this sort of thing out AFTER you spend 5 hours encoding. :)

Another thing thats weird, is why is this DVD oversized when the one I did the other day is just fine?

jarthel
26th February 2005, 07:00
Originally posted by recoil47


1) The most annoying issue, is the one I have just finished trying to do. Everything went along just fine...but when it comes time to BURN the files, or the ISO to the DVD...it says there isn't enough room!

IMAGE SIZE: 2,303,091 Sectors
DISC SIZE: 2,297,888 Sectors

How the heck to I fix this? As I mentioned, it looks like everything went along just fine. I got ZERO errors in Scenarist. This DVD had only one VTS file and it was huge. I encoded that, and left what little else there was untouched.


I do not trust ccedata.txt produced by dif4u. I used reauthor to calculate the bitrates. The recommended dvd size in reauthor is not the max DVD size so you have some extra space.

influenza
26th February 2005, 13:36
Well actually the dif4u bitrate is a bit more conservative than reauthorist (if set to the same output size).

Jarthel: I'm sure you reported the problems?

jarthel
26th February 2005, 14:59
I did not report the problem cause there is an easy workaround :)

it's not like it's a "show-stopper" to warrant a report
-------
I do not know if dif4u is more conservative but I tried 1 dvd and I used ccedata for that. oversized dvd is the result. created cce bitrates using reauthorist, encoded the .m2vs and no oversize problem.

I haven't used ccedata.txt since cause using reauthorist to calculate bitrate is only a few simple clicks. I know some people can't be bothered with a few simple clicks but that's no problem with me.
--------

I looked at duf4u before and I never saw an option where I can specify DVD size.

recoil47
26th February 2005, 18:50
Jarthel,

What is the workaround for this? I dont even have reauthorist installed as it wasn't a part of the "Big 3" that I was using...but I dont want to run into future problems with oversized discs. They are a pain because you dont know you have one until after you spent 5 hours encoding, then have to go back and do that all over again...

Thanks

jarthel
26th February 2005, 23:30
reauthorist is part of the "old big 3". check doom9's software section. If not, you should be able to find it using google.

the5thdragon
27th February 2005, 00:38
Originally posted by jarthel
reauthorist is part of the "old big 3". check doom9's software section. If not, you should be able to find it using google.
erm...reauthorist only works with pcg demux though. ;)

influenza
27th February 2005, 10:21
@Jarthel:

Even if it might not be a show stopper, since you found a workaround, we would like to receive error reports of course. Thats the only way to maintain and improve the current applications.

And like the5thdragon noted reauthorist doesn't work with vobid demuxes.

So please report if anything doesn't seem to be right. (including all resources necessary of course)