V-ISAN Numbers

[Eric69]

Wondering if any professionals here have had issues lately in replication and the new requirement for V-ISAN numbers? I hear some replicators require it and some dont. The newer version of Scenarist require it before the build correct?

[digitalvideo]

Hi Eric,

Some time ago sonic put a message about that on the support site.
But i just check and they delete it.

May be can you contact them.

[Eric69]

I noticed that too.

Im looking for someone with some real world experience with replicating with the new requirements. Sonic's support is fairly useless. I get better and faster answers here. Clients on a quick turn around and doesn't have time to wait for the ISANs

[2themax]

I believe that if you output to BDCMF 1.02, you can get around using the ISAN. Versions 1.03 and 1.10 will require it.

[rik1138]

Yes, if you use the older BDCMF, it won't require it... I _think_ you can leave all zeros in the V-ISAN and just tell the replicator that it's fine (Scenarist only gives you warning I believe, not an actual fail), but some replicators are also requiring that the ISAN be present and valid... It is now, technically, a required part of the Blu-ray spec.

Every disc I've made since this went into effect we have required the client to provide an ISAN number, so I'm not certain exactly what will happen now if you try to get by without using it...

If the client is really in hurry and won't provide/wait for the ISAN, contact the replicator they are using (or you are using, however that works out), and see if they will allow an all-zero ISAN to be replicated. Nothing is _preventing_ them from doing it, just policy...

[rik1138]

Okay, I just got to experience this first hand... The client I just did a disc for said they didn't have a V-ISAN number, and that they have been made optional recently...

The company that is in charge of ISAN numbers for the US (SecurePath) is apparently not issuing them at this time. AACS LA has made including ISAN numbers on Blu-ray optional, it is _NOT_ required (but use them if you have them).

Scenarist 5.2 will not allow you to make a BDCMF image without a valid ISAN number, it actually does fail (I thought it was just a warning). As mentioned, to get around this, change the AACS spec version to 0.92 in the CPS editor, and CMF to Version 1.02 (the AACS spec might change automatically if you set CMF to 1.02). Then the ISAN fields will be removed and you can create your disc image. No replicator should have a problem accepting this image.

When Scenarist 5.2.1 is released, this won't be necessary (I assume they will allow all zeros in the ISAN field, which it currently will not allowed).

Anyway, might be a little late, but that's the current status of V-ISAN numbers... I suspect they will remain optional, at least until there's a reliable way to have them assigned...

[Eric69]

Yeah....I just had a job replicated as well without ISANs. Thanks for the heads up!:thanks: