BDCMF 1.02 vs 1>03?

[Eric69]

Ive heard news going around that some replicators are not accepting 1.02 BDCMF builds...only 1.03. Could anyone shed some light on why this is? More importantly how to remedy this situation should it arise? Scenarist wont allow a 1.03 without ISANS but that rule as been change to allow titles without ISANs.

Just this just have do with Eclipse and its settings throwing out needless errors?

[rik1138]

To my knowledge, no replicator should be refusing 1.02... They might be recommending 1.03, but they shouldn't refuse the older one. Especially if you can no longer get ISAN #s (not sure if that's been rectified...)

If it's really a problem, try contacting Sonic and telling them you need to be able to make a 1.03 build without ISANs. They are planning to allow that anyway, they may be able to give you a beta build of the software to get around it for now...

You might even be able to just put in a dummy ISAN (all 1's or something, I know it will reject all 0's). If the client isn't providing you with an ISAN, they obviously won't be attempting to use them, so it really shouldn't matter... (But check with Sonic first, tell them it's urgent and you _have_ to use 1.03...)

Rik

[mp3dom]

At least here in Europe, the replicators accepts BDCMF 1.02 without any problems (AACS ver. 0.92 and without V-ISAN). I have replicated 2 disks just now. It was mandatory some time ago, but due to some problems in obtaining V-ISAN in USA, it was reverted back to 'suggested' but not mandatory anymore.

[rik1138]

Yeah, I know some replicators here in the US aren't refusing 1.02 (Technicolor & Deluxe for sure). But I'm not sure about smaller ones. There could be one that thinks 1.03 is the only way to go and isn't really aware of the ISAN problems... But they should still be _able_ to accept 1.02. They may not _want_ to, but the ability should still be there...