(2017-06-04, 08:57)Charger Hellcat Wrote: Disappointing bug that needs to be fixed pretty quick. It's caused half of my Cinema Vision experience to now be useless.
Hey Charger, lets make sure that the disk(s) that you're use to store your CinemaVision content are added as a source in the
Kodi File Manager. Your CinemaVision content can be stored on local disk, or on network storage. CinemaVision doesn't care as long as it can read/write to the location. You don't need to add specific directories as sources, just the root of whatever disk or share that houses your content.
- Open the Kodi File Manager.
- Select Add Source.
- Select Browse.
- Browse to the root drive or share that you wish to use to store your CinemaVision content and press OK.
- Name the source and press OK.
For example, on a Windows machine if your content is on your local
D: drive, you'd add
D: as your source. Now that we have the source added in Kodi, lets test our ability to write to that source.
- Open the Kodi File Manager.
- Select the source that you just created, which points to the root drive or share that will be used to store your CinemaVision content.
- Browse to the location which will contain your CinemaVision content.
- Create a new folder called CinemaVision.
- Press C on the keyboard.
- Choose Make new folder.
- Name the folder CinemaVision.
If the CinemaVision folder isn't created, you should modify the permissions on the share to allow Kodi to write to the share, or set up authentication with the correct permissions.
Once all of that is verified and your root drives or shares are configured in the
Kodi File Manager, you should be able to properly browse from within CinemaVision. CinemaVision actually uses the Kodi File Manager to browse, so if you can browse properly to the files/folders from within the Kodi File Manager, the same is true for browsing from within CinemaVision. One thing to note, once you set your
Content path in CinemaVision settings, when you choose
Single File or
Directory when editing a Module it will default to the directory for that module. We did that to reduce configuration time so you didn't have to browse all the way up the tree to find the video you want. For example:
If you select Single File in the Video Bumper Module, when you go to choose your file, it will take you straight to the
%CVROOT%\Video Bumpers\ directory. If you want to choose a different directory, you have to go up in the tree from there.