Script Transfers to Another Server/Host Computer

[VonMagnum 13]

I noticed yesterday when I was attempting to set up Cinemavision at a friend's house copying my Cinemavision directory/setup to their server/host computer and then setting it up on a FireTV Stick that the scripts wouldn't transfer.  I kept getting "parsing errors" when I attempted to bring up my scripts.  As near as I can tell based on some other behaviors (although I suppose it could be something else), the problem is that some of the data appears to be internally set to use my computer's hard drive name (e.g. "MegaMovies") and since my friend's drive is called something else (let's say "StarDrive") the scripts fail.  This did not happen setting CinemaVision up on a second FireTV at my own house (server name obviously is the same).  Somehow, this seems to have consequences even beyond the script itself when moving things over to a new computer host because when I select a video bumper and set it to "directory" (e.g. to select random Disney/Loony Tunes cartoons; I'm suing "shorts" for something else entirely).  I see my drive names appear on my friend's computers despite new scripts and I'm not sure how that's happening.  Even on my own FireTV, it doesn't show the master list of drives or devices, but just my Media drive that I have CinemaVision stored on.  I've noticed even on my setup that I cannot select any "directory" outside the one that the Cinemavision directory is setup on.  I don't know if this is due to some kind of setup config in Kodi itself or the CinemaVision plugin.

[Ragnarok 198]

On 5/10/2017 at 0:44 AM, VonMagnum said:

I noticed yesterday when I was attempting to set up Cinemavision at a friend's house copying my Cinemavision directory/setup to their server/host computer and then setting it up on a FireTV Stick that the scripts wouldn't transfer.  I kept getting "parsing errors" when I attempted to bring up my scripts.  As near as I can tell based on some other behaviors (although I suppose it could be something else), the problem is that some of the data appears to be internally set to use my computer's hard drive name (e.g. "MegaMovies") and since my friend's drive is called something else (let's say "StarDrive") the scripts fail.  This did not happen setting CinemaVision up on a second FireTV at my own house (server name obviously is the same).  Somehow, this seems to have consequences even beyond the script itself when moving things over to a new computer host because when I select a video bumper and set it to "directory" (e.g. to select random Disney/Loony Tunes cartoons; I'm suing "shorts" for something else entirely).  I see my drive names appear on my friend's computers despite new scripts and I'm not sure how that's happening.  Even on my own FireTV, it doesn't show the master list of drives or devices, but just my Media drive that I have CinemaVision stored on.  I've noticed even on my setup that I cannot select any "directory" outside the one that the Cinemavision directory is setup on.  I don't know if this is due to some kind of setup config in Kodi itself or the CinemaVision plugin.

I could've sworn we were using a universal variable for the %CVROOT% directory, but what you're describing tells me I'm wrong. That is one thing that we can do, which should make some of this easier to switch between computers. Since you can browse outside of the %CVROOT% directory in Modules, the problem you're having won't be solved 100% of the time, but it should be less of a headache for all of the content and Actions that you keep in the %CVROOT% directory. The name of the disk shouldn't matter at all, but the logical path does. I'll make sure that this is on our list for this development round. Good catch!