-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PKL annotation? #313
Comments
Haven't had a problem with this before. Can you confirm that the title and annotation feilds were filled out on the form, and that the PKL was included in the DCP package generated? Would be helpful if screenshots were included |
Usually the annotation is just the title of the clip, with potentially some version info. Can you provide some more info about your requirements? Do you need the package to be encrypted? I can provide a simple guide in a little bit. Replying on mobile right now |
The annotation has to match the title?
…On Fri, Sep 15, 2023 at 4:24 PM geekwilliams ***@***.***> wrote:
Usually the annotation is just the title of the clip, with potentially
some version info. Can you provide some more info about your requirements?
Do you need the package to be encrypted?
I can provide a simple guide in a little bit. Replying on mobile right now
—
Reply to this email directly, view it on GitHub
<#313 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK3YUKCFFDUFISFUZDDD4YDX2TPRNANCNFSM6AAAAAA42GRHM4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It doesn't have to match, just that it generally does |
Hello. Just got this feedback from SimpleDCP about a couple DCP files I made using OpenDCP. Anybody got any guidance?
Neither of the DCPs, even when unzipped, are registering as DCPs because there is no PKL annotation. This is a required field and may cause the DCP to not register on a digital cinema server as a DCP. Please repackage the DCPs with the appropriate PKL annotation (usually just the CPL name) and resubmit
The text was updated successfully, but these errors were encountered: