Automatic shutdown after error
-
- Posts: 40
- Joined: Fri Jun 08, 2018 8:12 am
Re: Automatic shutdown after error
Has been upgraded 2.13.26 But still the same wrong result, is there any other way to open this project I need to use it to decrypt DCP
-
- Site Admin
- Posts: 2550
- Joined: Thu Nov 14, 2013 2:53 pm
Re: Automatic shutdown after error
Maybe you could try 2.13.27 and see if that's any better.
-
- Posts: 40
- Joined: Fri Jun 08, 2018 8:12 am
Re: Automatic shutdown after error
Carl thank you very much I have obtained DKDM through other means
-
- Posts: 13
- Joined: Sat May 05, 2018 11:43 am
Re: Automatic shutdown after error
Hi Carl,
Every time when I load an existing dcp, appears the files as MISSING, is this the same error'?
Every time when I load an existing dcp, appears the files as MISSING, is this the same error'?
-
- Site Admin
- Posts: 2550
- Joined: Thu Nov 14, 2013 2:53 pm
Re: Automatic shutdown after error
Could be; MISSING is actually a bit of a catch-all for "there's a problem". Does the DCP import OK? Are you adding it with the "Add DCP" button?
-
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: Automatic shutdown after error
Mario - I don't have that in any of my recent DCP-o-matic versions. Now, please get this straight - normally, when you load a pre-existing project, DCP-o-matic expects the content/DCP to be at exactly the same position/path where it was when you saved the project. If you moved it, renamed the folder, changed drive letter order (if on an external drive/USB stick), the DCP is no longer where DCP-o-matic expects it. If DCP-o-matic shows 'Missing', right click onto the DCP in content list and choose 'Find missing', then point to the location where the original DCP is saved. The DCP folder name needs to be the exact same as when it was last referenced in DCP-o-matic.
Another reason could be that there were changes done to the DCP after you saved it from DCP-o-matic. Then DCP-o-matic doesn't recognize it anymore as the DCP you originally referenced in the project.
- Carsten
Another reason could be that there were changes done to the DCP after you saved it from DCP-o-matic. Then DCP-o-matic doesn't recognize it anymore as the DCP you originally referenced in the project.
- Carsten