SuperFlyTV
Stored data corrupted when working with multiple versions
Bug: When switching between release and development versions on the same desktop in windows 10 the stored data doesn't get properly translated from version to version resulting in corruption where differences in storage type occurs. This causes communication errors with casparCG and corrupted rundowns.
Run the release version, then compile develop version and try to go back and forth. Various data for casparcg, scanner, and superconductor have to be manually deleted.
Could you elaborate on the corruption? What does the corrupted data look like?
Things not working until the either the element or data is cleared and remade. This mainly has to do with the definition of the connection with CasparCG or any other thing that changed between versions. Parts made with the previous version have to have the layer reselected in the new one for instance. The casparcg server and layer definitions have to be deleted and redone to not be red. I don't have comprehensive list but at one point I was getting some weird casparcg connection errors until I nuked the application data folder in documents along with the casparcg media database after which the casparcg connection started working again with the exception of duration that is mentioned in issue 237
This is caused by incompatible storage schema between release and development builds writing to the same userData directory without versioning or migration logic.
There is migration logic for when movig to a newer version (here, here and here), but there is not any migration logic for when moving back to older versions as I don't see how that could be implemented in a reasonable way (I am open to suggestions though).
I'm closing this thread for now, since I don't have enough info about the bug to make a potential fix. Feel free to reopen if anyone can provide specific bug info, like what versions and attach the project file (can be exported from the Project page)