How the "Batch" works?

[jamewoong]

We all know that the default size of the output is 4.32 GB (is there a way to change this?).

I'm compressing a DVD-9 to DVD-5 and each time that I want to make this project, I always have to prepare it (wait 8-10 mins), then increase its size to 4.36 GB in the "Viewer/Editor". And yes, 40 MB can be used to insert a trailer an I need that space!

I want to know if I save this project with the "Viewer/Editor" (a oversize warning) setting saved and add this project to the "Batch", will it save all my settings (increase the size from 4.32 to 4.36 GB) by checking the option "Skip the prepare... in batch"? I'm asking this because I think it doesn't save that setting. I remember I leave it the last night and the output size was 4.32 GB!

What's wrong?

Can anyone tell me what the batch file will keep as setting?

Thank you.

[steptoe]

As mentioned in another post by jdobbs, basically the entire contents of the DVD-RB INI file, so that would include all INI alterations made by you to tweal the output sizes, any matrices, any filters that you are using, etc, etc

Very useful to know, as I just used it to create a batch list not realising I could also use it to create a more advanced type of profile for projects


If you want to change the output size, you have to be very careful as that extra 'space' is there to virtually guarantee it will never be oversized and to allow for projects to be bigger than expected, its not really exactly that size all the time it does vary slightly on each project, so making it slightly undersized will hopefully prevent an oversize error

[jdobbs]

40MB spread across 3 hours of content comes out to about 14Kbs. Do you really think you can tell the difference between something that was encoded at 4320Kbs and 4334Kbs??? Let's be serious. This obsession with pushing discs to the edge has to be put into its true context.

There are lots of very good reasons why the size is set as it is. I have explained in much detail on numerous occasions and a "search" will prove that. I also warn against pushing the size to the edge because virtually all blank discs (even the high-end ones) are prone to error there.

But if you decide to take the chance of pixelation in the last couple minutes of the disc... more power to you. The output size can be adjusted with this parameter:

TargetSectors=nnn

It is explained in more detail in the "Frequently Asked Questions" section of this forum and also in the HELP file that comes with DVD-RB. Look under "Hidden Settings". I just ask that you not later post a bug report explaining that you are getting pixelation in last part of your discs -- which has happened more times than I can count -- because it is the disc, not the program, and you are making the choice to experience that problem by increasing the target size.

Me? I leave it at the default.

{Down off the soapbox}

[jamewoong]

There are lots of very good reasons why the size is set as it is. I have explained in much detail on numerous occasions and a "search" will prove that. I also warn against pushing the size to the edge because virtually all blank discs (even the high-end ones) are prone to error there.
I remember to read that long time ago... But I always use nero to burn my media and at that size, I'll never have a problem. The 40 MB can be added to the trailer (in VTS 2), so no need to reencode that clip. At that size, there's still 10-20 MB left at the edge.

About the pixelation... It's not about the disc because the original DVD-9 is 100% perfect (no pixelation problem). As I mentionned in my other post, the problem was probably due to my video card or codec. After encoding it to DVD-5, the effect is totally different from 2 PC.

Anyway, thanks the answer, really appreciated.

[stereo]

I think jdobbs refers to the fact that a lot of discs are damaged at the edges due to normal handling, i.e. when you pick them up and touch them with your hands.

40MB of data/space won't make a difference. Though, I understand your desire to use the disc space. I normally reach 4.34GB at CCETargetSectors=2240000, leaving room for normal disc handling.

[jdobbs]

About the pixelation... It's not about the disc because the original DVD-9 is 100% perfect :confused: It is not a problem on the source disc. It is a problem on the destination disc. Blank discs are much more likely to have problem on the outer tracks (which are written last). There are lots of theories as to why. But to those who have burning DVDs for a while there is little disagreement that it is a truism.

That's one of the (many) reasons DVD-RB writes a 4.32GB image.