Change CV Sequence Formatting For The Default CinemaVision Path Directory

[MidnightWatcher 18]

Using a new SDHC I switched from OpenELEC to OSMC for my RPi2 and copied my entire CinemaVision directory that was on the OpenELEC SD card to the new OSMC SD card.  One thing I realized afterwards, however, was that the bumper and action file paths stored in each CV sequence contained the full directory/subdirectory path to the CinemaVision folder. On OpenELEC, for example, the path to my CinemaVision folder is "/storage/downloads/CinemaVision/" BUT now, after migrating over to OSMC, everything needs to point to "/home/osmc/CinemaVision/" instead.

Rather than utilizing a full directory/subdirectory path to the CinemaVision folder in each sequence, I'd recommend having a future update default directly to the "%/CinemaVision/" folder itself for the bumpers and action files in each new sequence created. That way anyone upgrading from, migrating to or adding a new system wouldn't need to manually update all of their custom sequences to ensure they point to CinemaVision's new directory path and could transfer over any existing CinemaVision directory and sequences with ease.

Edited March 6, 2016 by MidnightWatcher

[Ragnarok 198]

22 hours ago, MidnightWatcher said:

Using a new SDHC I switched from OpenELEC to OSMC for my RPi2 and copied my entire CinemaVision directory that was on the OpenELEC SD card to the new OSMC SD card.  One thing I realized afterwards, however, was that the bumper and action file paths stored in each CV sequence contained the full directory/subdirectory path to the CinemaVision folder. On OpenELEC, for example, the path to my CinemaVision folder is "/storage/downloads/CinemaVision/" BUT now, after migrating over to OSMC, everything needs to point to "/home/osmc/CinemaVision/" instead.

Rather than utilizing a full directory/subdirectory path to the CinemaVision folder in each sequence, I'd recommend having a future update default directly to the "%/CinemaVision/" folder itself for the bumpers and action files in each new sequence created. That way anyone upgrading from, migrating to or adding a new system wouldn't need to manually update all of their custom sequences to ensure they point to CinemaVision's new directory path and could transfer over any existing CinemaVision directory and sequences with ease.

Great suggestion! We've added this to our list of improvements.