Blu-ray + UHD/4K + Streaming

A community for authoring Blu-ray, 4K/UHD and more!

My client is switching to a new replicator plant for a project we're working on, and they asked us a setup question that threw me for a loop: are we delivering as Type A or Type C? According to them, Type A apparently has no AACS encryption, but Type C is apparently already encrypted, usually by another replication plant.

Which type is the BDCMF that DSA spits out? There's clearly a (very long) AACS encryption step when we export, but since we're not being asked for the AACS ID# at any point, or getting updated keys from AACS, so I honestly don't know what the answer here is. Anybody know?


Views: 688

Reply to This

Replies to This Discussion

This from Scenarist's Manual:

Type V (as Virtual Machine) Refers to Step 0 of BD+ process, and is transmitted
to an Eligible Content code Developer (Macrovision), which performs BD+
processing. Never transmitted to Replicator who does not perform BD+

Type A Flagged for encryption, not signed by AACS, no ROM-Mark applied. It is
the basic format of BDCMF transmitted to a replication facility. Also is step 1 of
BD+ process when it is transmitted to the replicator.

Type B Encrypted, not signed by AACS, no ROM-Mark applied. Done by
replicators, and used to request signature from AACS LA.

Type C Encrypted, Signed by AACS, no ROM-Mark applied. Used to transmit data
between replication facilities. There are two types, C1 and C2. C2 is not
applicable to Authoring houses.

Type D Encrypted, Signed by AACS, ROM-Mark applied. It is the internal format
of the replication facility.

Type P Refers to the ROM content (non-movie content) to be transmitted to a
replication facility. Sonic does not have a tool at this time that supports this type
of ROM-only BDCMF.

Encryption is handled by replication tools, such as Eclipse.

Ive always delivered Type A.   Basically, C is signed AACS and A is not

If you create a BDCMF master with DoStudio for replication you have created a type A master

Great, thanks!

Hi Justin,

 If you are really interested in how the replication process works, we have this wikipaper on it:



What I couldn't get from the wiki was:

Can any other authoring software out there (Bluprint etc.) do type C images? If yes, is it common to provide type C files for replication?

Thank you!


Hi Tobz,

   Type C requires you to be approved by the BDA.  Eclipse Data Technologies is one of three tools that can create the Type C. It is extremely uncommon for replicators accept a Type C from an authoring company/content owner.    We have been asked a few times this year about Type C, though.  Are you able to explain how you came about wondering about Type C?  If not publicly in private?   This way we can possibly add some clarification where needed.



Hi Denny,

thank you for your reply. The replicator in question is Sony Australia. They would have prefered a type C image because of a tight schedule of the project (would have saved them 2 days).

Cheers Tobz

Hi tobz,

    Thank you for the information.  We'll do some research on this to see if there is anything in that can be done within the rules of the BDA.



Reply to Discussion


Latest Activity

Marc Morris replied to Marc Morris's discussion DoStudio - importing Chapters XML from FCPX
"Thanks Rob. Sadly it doesn't open fcpxml files. I purchased XtoCC, but I found a bug in the…"
Jun 13
Rob Aubey replied to Marc Morris's discussion DoStudio - importing Chapters XML from FCPX
"Marc, You could try this tool to see if it will convert the TC of the XML to the correct format.…"
Jun 10
Marc Morris posted a discussion

DoStudio - importing Chapters XML from FCPX

I've recently upgraded from FCP 7 to FCPX, and I had no problem exporting XML chapters from the old…See More
Jun 7
Rob Aubey replied to Scott Rossi's discussion DoStudio
"Hello Scott, Unfortunately, DoStudio is not for sale any longer. I would be interested speaking…"
Feb 8

© 2019   Created by Denny and Rob.   Powered by

Badges  |  Report an Issue  |  Terms of Service