Hi. I found a bug, when i try to export multiple DCP packages from one project. I need this to create packages with different sound levels.
Problem: after creating second package from the same project without closing it (project), first exported DCP package gets corrupted
If I close and reopnen project between exports, all packages are exported correctly.
How to reproduce:
1. set up project, and export DCP package ("DCP_out_1")
2. make backup copy of exported DCP package ("DCP_out_1_copy")
3. go back to GUI, change at least DCP package name (so it gets exported to new folder), and change sound level, export as new package ("DCP_out_2")
4. compare "DCP_out_1" and "DCP_out_1_copy", and check that some files of DCP_out_1 have changed their content
BUG: exporting multiple DCP from same project
-
- Posts: 7
- Joined: Wed Aug 23, 2017 10:13 am
-
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: BUG: exporting multiple DCP from same project
Ooops, that's a nasty one indeed, wrecking an existing working DCP, that can happen quickly and stay unnoticed until the DCP is ingested on the server.
At first sight, this doesn't seem to happen here with 2.11.19 (Sierra), both DCP folders appear to be correct - however:
After I create the first DCP, it loads and plays nicely in DOM and DOM player. When I create the second DCP with JUST a different name, the creation goes very fast as expected - but the first DCP that worked before now demands an OV when I try to open it in DOM and DOM player, while the second is okay.
It seems there is something going on around creating OV/VFs, even when 'refer to existing DCP' is not ticked... Seems it only happens in the metadata.
Carl - I attached the the files so you can have a look. Happens both with IOP and SMPTE.
- Carsten
At first sight, this doesn't seem to happen here with 2.11.19 (Sierra), both DCP folders appear to be correct - however:
After I create the first DCP, it loads and plays nicely in DOM and DOM player. When I create the second DCP with JUST a different name, the creation goes very fast as expected - but the first DCP that worked before now demands an OV when I try to open it in DOM and DOM player, while the second is okay.
It seems there is something going on around creating OV/VFs, even when 'refer to existing DCP' is not ticked... Seems it only happens in the metadata.
Carl - I attached the the files so you can have a look. Happens both with IOP and SMPTE.
- Carsten
You do not have the required permissions to view the files attached to this post.
-
- Site Admin
- Posts: 2548
- Joined: Thu Nov 14, 2013 2:53 pm
Re: BUG: exporting multiple DCP from same project
Thanks both for investigating this. I think the bug has been there for years! It should be fixed in 2.11.22.
-
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: BUG: exporting multiple DCP from same project
Wow, how did that slip through? Was it a side effect of versioning/OV/VF? Because that is not so old...
- Carsten
- Carsten
-
- Site Admin
- Posts: 2548
- Joined: Thu Nov 14, 2013 2:53 pm
Re: BUG: exporting multiple DCP from same project
I'm not sure how nobody noticed before... DCP 1 is made, its video asset is hard-linked to a "copy" in the video/ folder. When you create DCP 2 it sees that it already has a video file which could be right so it uses the data from it but re-writes its ID. Hence the hard-linked copy in DCP 1 is corrupted.
-
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: BUG: exporting multiple DCP from same project
Hmm, okay. I remember I did sound level variations often, but that was some time ago. Very often now I recreate DCPs, but then I usually do not use the first DCP anymore but only the following.
- Carsten
- Carsten