Copy link to clipboard
Copied
Hello,
i have just created a Trailer with Premiere CC 17.1 for usage in a cinema. Therefore of course I used the wraptor DCP-export. The name of the file is according to the DCP-naming convention which means: "Name-of-movie_TLR_F_EN..........dcp"
I know that "TLR" stands for trailer, and the cinemas need this coding explicitly to create a properly working playlist for the commercials block.
But now I have the following problem: I got feedback from the cinema, that they are not able to create their playlist. The reason: The computer in the cinema checks all incoming DCP-files for errors and inconsistencys and says: Your DCP is described in the file name as TLR="Trailer" but I recognize your content kind as a "Feature". Sorry, this is a conflict, I cannot play your file.
So my first step was to verify the problem with the Software "Easy DCP-Player+", which is able to make hasum check of DCP´s and read metadata. And in fact, the file is recognized as content kind "Feature"
My first thougt was: There must be any checkbox in the export-Settings of Premiere to choose the content kind. But as far as I can see, there is no option. Can someone confirm this?
"Easy-DCP Player" and the cinema-computer tell me that the file is a "Feature", although I marked it in the file name as "Trailer". So the content kind (Feature, Trailer, Advertisement....) must not be only coded into the file name but also in the metadata of the DCP. My quick look at the other files in the DCP-folder showed me: At least in the CPL-file, ther is one relevant entry (which I have marked red)
 But I have no idea if the information is additionally coded into another metafile, any cryptic code or whatever.
So I though: Genious how I am, I will just edit the CPL-file with an texteditor. So I just changed the word "Feature" to "Trailer" and saved the file. But now comes the next problem:
Through manipulating the metadata, the hashsum check of the cinema´s computer will fail of course, which is even a worse error than before.
So my question: How can this be solved? Adobe Premiere obviously knows only one content type, which is "Feature" and writes that into the metadata. And my last option would be to name a Trailer in the file name as a feature. But I am sure the cinemas will dislike this also and it will lead also to an error. Because in a commercial block must not bea any "Feature".
So I would be very thankful if anyone can help!
@chrisb94858317
You would need Wratpor Pro instead of Wraptor Lite. It's been a while since I've used the pro version, but I remember the 30-day license for the Adobe version being $100. I've always gone with the 30-day option as I don't encode DCPs very often and it's a cost that's easily billed back to the client.
I own Resolve Studio and have considered licensing easyDCP for use with it, but I remember easyDCP Resolve being something like $1,100 (the price varies depending on the exchange ra
Copy link to clipboard
Copied
Update: My workaround (whereas I do not know if it really works) is as follows:
Change manually the word "Feature" to "Trailer" in the file CPL....xml . Then, calculate the new Sha1-Hashsum for this file. Write this new hashsum into the PKL...xml so that everything is correct again.
So I am excitet if the cinema-computer will accept such a modified DCP. But this topic here in the Adobe-forum is still important for me to solve. Because even if this would work, it would be a very bad, error sensitive and inconvenient solution.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Hello Rutta89, sadly the above described workaround does not work. I got feedback from the cinema that they get an error with the such modified DCP. Error message of the cinema´s server: "ingest errors detected" (whatever that means...). I guess that there are some more plausibility checks running and a the hashsum is certainly something they double and cross check...
The second workaround which actually worked is as follows:
The created DCP works perfect on cinema server. But: I know its bad practice, it´s just a stupid workaround. So I would also be interested in a good solution. I mean Adobe promotes the Wraptor DCP for cinema usage, but some basic functions seem not to be implementet.
Copy link to clipboard
Copied
Some more people asked on this Youtube-Video for the solution. But it seems that Premiere has no possibility to set the content type...
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
It's 2025 and I'm having the exact same issue - I can't change the content kind from Feature to Advertisement.
In November I started using Davinci Resolve for editing after years of Adobe frustrations. This cinema ad was and is my last project using Premiere Pro! Sick of the unresolved issues.
Copy link to clipboard
Copied
Hi @,
Thanks for the message and question. Welcome to our forum. At the same time, I'm sorry to see you go, but let us know if we can help you in the future.
As far as the Wraptor issue goes, you may have to use another DCP option for that option as the software agreement was for a light version of the software. I am not sure, but perhaps that version did not have the option. More information about the full version is here: https://adobe.ly/3BNSwfG from our expert @Warren Heaton. Perhaps @Eric Escobar might have a comment that could advise you on this further. Sorry for the frustration and good luck to you.
Thanks,
Kevin
Copy link to clipboard
Copied
@chrisb94858317
You would need Wratpor Pro instead of Wraptor Lite. It's been a while since I've used the pro version, but I remember the 30-day license for the Adobe version being $100. I've always gone with the 30-day option as I don't encode DCPs very often and it's a cost that's easily billed back to the client.
I own Resolve Studio and have considered licensing easyDCP for use with it, but I remember easyDCP Resolve being something like $1,100 (the price varies depending on the exchange rate). There's also easyDCP Plus for about $190 for one month, but that's a stand alone application.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now