Blackmagic Forum

Looks like Resolve 15 will be able to create unencrypted DCPs and can also play unencrypted DCPs without any external help from easyDCP. If this happens, that will be a great boon for Indie filmmakers.

In the Media support fine print it says:
• Support for native Kakadu based JPEG2000 decoding and encoding
• Support for encoding unencrypted DCP packages using the Kakadu codec

In the Pre-installation Notes section it says:
• Support for decoding and encoding of EasyDCP formats is not currently available

Couldn't find much about the Kakadu codec in the Internet.

I hope my guess is right?

I am sorry, somehow the original post I created was posted thrice.
Can find a way to delete this thread.

The New DR15 Feature Guide says that this is for test playback. Below is the quote:

"DaVinci Resolve 15 also has new native DCP Encoding and Decoding support built‐in, for unencoded DCP files only. That means that you can output and import (for test playback) unencoded DCP files without needing to purchase a license of EasyDCP. If you have a license, a preference enables you to choose whether to use EasyDCP (for creating encrypted
DCP output), or the native Resolve encoding.

Willian Aleman wrote:The New DR15 Feature Guide says that this is for test playback. Below is the quote:

"DaVinci Resolve 15 also has new native DCP Encoding and Decoding support built‐in, for unencoded DCP files only. That means that you can output and import (for test playback) unencoded DCP files without needing to purchase a license of EasyDCP. If you have a license, a preference enables you to choose whether to use EasyDCP (for creating encrypted
DCP output), or the native Resolve encoding.

In my understanding, the "test playback" is for the import function as its the main, if not the only, reason you would import a DCP, not meaning its a limited function or you cant creat DCPs out of Resolve now. It's just encrypted DCPs that you need to have a license, but for unencrypted you can use Resolve just fine.
At least its my understanding of the text. The words "unenconded" and "encrypted" might be causing a confusion.

If somebody could clarify... I have not tested this function yet to be sure but I'm running v15 and so far so good. Using it in actual projects since yesterday.

Ulysses, thanks for your response.
Then, I never wish to be that wrong. I hope your interpretation is the right one.

Krishna Pada wrote:Couldn't find much about the Kakadu codec in the Internet.

http://kakadusoftware.com

they provide ready, optimised libraries for Jpeg2000 decoding/encoding. It's quite decent.

Just attempted to play an "unencrypted" DCP with no success. I do have the studio version. I was able to create a DCP here and reload it and play it just fine but when I attempted to playback a known good DCP that I know is "unencrypted" it only plays the 1st 10 seconds. So, my best guess is that they won't playback final DCP's that have been "encoded."

It is nice to create DCPs with Resolve now. Normally I will do this with DCPoMatic, which is a really fine toll to do so.
One thing I miss in Resolve is to create automatically a name for the file that is conform o the ISDCF.
As a projectionist I prefer to this because it will provide me with all features of the DCP which I need for correct screening.
I know that I could do this manually, but it would made it more comfortable.

I use the Beta Version 15.0.0b.030

DCP export/import is a great addition to Resolve, but still a bit buggy.

I'm getting artifacts on simple color bars and less than perfect levels when exporting and reimporting.

Also, import from known good dcp's made with DCP-O-Matic crashes resolve. Anyone else seen this?

Michael Reckert wrote:It is nice to create DCPs with Resolve now. Normally I will do this with DCPoMatic, which is a really fine toll to do so.
One thing I miss in Resolve is to create automatically a name for the file that is conform o the ISDCF.
As a projectionist I prefer to this because it will provide me with all features of the DCP which I need for correct screening.
I know that I could do this manually, but it would made it more comfortable.

I use the Beta Version 15.0.0b.030

Plus 1 on create names confirmed to the specification.

waltervolpatto wrote:

Michael Reckert wrote:It is nice to create DCPs with Resolve now. Normally I will do this with DCPoMatic, which is a really fine toll to do so.
One thing I miss in Resolve is to create automatically a name for the file that is conform o the ISDCF.
As a projectionist I prefer to this because it will provide me with all features of the DCP which I need for correct screening.
I know that I could do this manually, but it would made it more comfortable.

I use the Beta Version 15.0.0b.030

Plus 1 on create names confirmed to the specification.

Add my vote

I just tried creating a DCP in beta 6 (macOS Sierra) and although a lot has improved, I'm kind of surprised that the folder the DCP files are written into ends with .dcp. Although technically it doesn't matter and it does pass dcp_inspect, I'm used to having the foldername be named exactly like the composition name. Is this something that could be changed in a later version? Also there seems to be no place to fill in the Annotation and Issuer.