that's interesting.
Neil can you tell what drives up the cost - use of MLP or complexity of DVDA authoring?
b.t.w. what is DVDSP?
It's the complexity of the authoring, and the time taken to QC it.
You're putting 2 forms onto a single disc and then setting hooks from one into the other.
DVD-V is far simpler, as you do not have the restrictions with the Video_TS that you do when it goes into DVD-A.
DVDSP = Apple's DVD Studio Pro. It used to be Spruce Maestro, until Apple swallowed it up and was better in the old days.
Now it is an abstraction layer nightmare with many spec fudges and cannot produce DVD-A compliant title sets.
Another issue is that there seem to be a lot of people who think DVD-Audio is a DVD with Audio on it as opposed to a film.
Very bad that there is not even an LPCM stereo stream!!!
EDIT.
Another huge issue that gets terribly awkward sometimes is setting the layer break.
We're currently doing 2 concert titles that will also have the surround mix in Audio_TS as well as LPCM stereo & DTS with the film.
The problem here is that the Video_TS is the larger of the 2, so layer break needs to be set in Sonic DAC.
However, because there is no way to preview anything the only way to do this is as follows:
1 - Compile the Audio_TS
2 - Compile the Video_TS
3 - Determine the size of each _TS, and work out the bitrate in Mbps.
4 - Work out where this would tip me over the edge of the 4.2Gb limit for Layer 0, and pick the chapter point in the footage before this.
5 - Compile again after setting cutting point (as Sonic call it) to this chapter, and cross your fingers.
Given each full compile can take up to 45 minutes, and the only time you get to find out if Layer 0 or Layer 1 is too big is right at the end of the process when you get the dreaded yellow box with it's "Layer 0 exceeds 4.2Gb" message, and you can imagine how the hours mount up!
An ideal situation is the ATS larger than the VTS, and both smaller than 4.2Gb. This rarely happens though (sob)
