Carl, do you know what causes this? Is there a way to solve this, also for future versions?
- Carsten
2.10.5 - 2.11.x Config file incompatibility
-
Carsten
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
2.10.5 - 2.11.x Config file incompatibility
You do not have the required permissions to view the files attached to this post.
-
carl
- Site Admin
- Posts: 2548
- Joined: Thu Nov 14, 2013 2:53 pm
Re: 2.10.5 - 2.11.x Config file incompatibility
I'm struggling to reproduce this: is there a simple recipe?
-
Carsten
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: 2.10.5 - 2.11.x Config file incompatibility
It happens for me in both windows and OS X versions when downgrading from the 2.11.x test versions back to 2.10.5 stable. Which made 2.11.x testing and return to 2.10.5 for production a bit cumbersome, as config, certificates and cinema database are lost if you do not have a backup. Going from 2.10.5 to any 2.11.x was no problem.
- Carsten
- Carsten
-
carl
- Site Admin
- Posts: 2548
- Joined: Thu Nov 14, 2013 2:53 pm
Re: 2.10.5 - 2.11.x Config file incompatibility
I've never really tried to maintain backwards compatibility for config files... maybe I should...
-
Carsten
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: 2.10.5 - 2.11.x Config file incompatibility
I think I never experienced that before. I understand it may be difficult to cater for future changes in current versions. The trouble here certainly was that many people were interested in testing export and preview audio, but risked a loss of their config/certs/cinema database when reverting to stable.
Maybe it's okay to trash config, but make the dialog a little bit more explicit, or offer to back-up the existing config files before they are trashed?
Yes, of course, program config itself is not so important, and whoever is actually dealing with certs and cinema database really should have backups. Still...
The Mac is a bit special, as I can have many different versions in folders and switching quickly, but all using the same config files. In Windows and Linux, you need to uninstall/reinstall, which might keep people from version hopping. I remember DVD-o-matic, DCP-o-matic, and DCP-omatic2 having separate config files, so they could/can be operated in parallel. However, for DOM2 release and test versions, there is no such way to work.
- Carsten
Maybe it's okay to trash config, but make the dialog a little bit more explicit, or offer to back-up the existing config files before they are trashed?
Yes, of course, program config itself is not so important, and whoever is actually dealing with certs and cinema database really should have backups. Still...
The Mac is a bit special, as I can have many different versions in folders and switching quickly, but all using the same config files. In Windows and Linux, you need to uninstall/reinstall, which might keep people from version hopping. I remember DVD-o-matic, DCP-o-matic, and DCP-omatic2 having separate config files, so they could/can be operated in parallel. However, for DOM2 release and test versions, there is no such way to work.
- Carsten