I've recently read three articles where the maximum bitrate for DVDA was shown as 9.6Mbs. None of the articles cited a source for this erroneous maximum bitrate. Do you happen to know who concocted the 9.6Mbs maximum DVDA bitrate myth? I'd like to have a little chat with him/her.
Thanks in advance.
It is in the DVD-Audio Book Specifications.
These cost around $10,000 to purchase (done by those who create applications and/or players), similar charges apply to DVD-Video book specs too.
The spec limitation is not a myth. What needs to be understood is what the specification means, and it does not mean "no players will do this", it means that "all players must be capable of at least this".
Given the way specs are interpreted, that will mean in the real world that as a bare minimum, all players have to be capable of decoding - glitch free - a stream of 9.6Mb/sec. Given that the best you can do with LPCM is 24/96 in Quad without exceeding this bitrate, the specs further state that all above 9.6 require the mandatory use of MLP Lossless to get the rate below this figure. No disc can have a 24/96 5.1 LPCM stream and still be called DVD-Audio, because it ain't. It's out of spec.
Any applications that allow this are treading on very thin ice indeed, because these titles could simply never be used for replicated content carrying the logos. It will fail at glass mastering, and the disc should be rejected by the plant as out of spec.
The reason for this is simple - the specs are the absolute minimum tolerances for players, so for most cheap players, read "exactly what they generally do, and no more".
The disc would fail at factory simply because it could not be successfully played in all players, as there are plenty out there that cut off sharply at 9.6Mb/sec, and will simply not be capable of demuxing the streams. What happens is debatable, as different players error in different ways. The disc might skip, it might glitch, it might not load the overlays, it may play & stop or it may do any other thing except play properly.
it is an unknown quantity once you drift out of spec.
You can certainly do this on some applications, and BTW my copy of Chrome certainly will *not* accept a 5.1 LPCM set under any circumstances (I tried) and will try Sonic to see what that does.
My guess is that even if it does import, it won't compile without a spec violation warning. You can always compile through a spec violation if you choose to do so (or in Sonic's case, set this as a preference before attempting to compile) but what you end up with cannot get replicated, and playback cannot be guaranteed.