Sage 101: New install, Sage doesn' see my media library

[AWS]

Pictures and Music libraries work with \\<host name>\media\... path fine. Just imports of video files / recordings don't show up unless using the IP path.

AWS

[AWS]

I've been poking around the .properties files.

When I go into the SageTV and configure the media libraries (TV, Movie, Music and Pictures) to \\HTPC\Media\TV, \\HTPC\Media\Movie, etc then here are the values in the Sage.properties and SageClient.properties file. Do these appear correct?

Sage.properties:
seeker/archive_directory=\\\\HTPC\\Media\\TV,1;\\\\HTPC\\Media\\Movie,1;\\\\HTPC\\Media\\Music,2;\\\\HTPC\\Media\\Pictures,4;

SageClient.properties:
seeker/archive_directory=C\:\\Users\\htpc\\Videos,1;C\:\\Users\\htpc\\Pictures,4;C\:\\Users\\htpc\\Music,2;C\:\\Users\\Public\\Videos,1;C\:\\Users\\Public\\Pictures,4;C\:\\Users\\Public\\Music,2;

To me, the SageClient.properties file looks incorrect. I don't use anything in the Users directory.

I'll test later by pasting the sage.properties seeker/archive_directory string ontop of the SageClient.properties seeker/archive_directory unless someone says that's a bad idea.

Is the seeker/archive_directory variable the path to where the import libraries are saved?

Thanks.
AWS

[AWS]

Ok, that seemed to fix it. For whatever reason the sageclient.properties file was not updating correctly.

Manually made:
seeker/archive_directory=\\\\HTPC\\Media\\TV,1;\\\\HTPC\\Media\\Movie,1;\\\\HTPC\\Media\\Music,2;\\\\HTPC\\Media\\Pictures,4;

and so far it found all video files (doesn't explain why it was able to find music and pictures before but not videos). I'll watch for a few days to see if this keeps.

AWS

[panteragstk]

Were you changing the import directories on the client or the server? It explains it if you were changing them on the client, but if you were changing them on the server then I don't know what to tell you.

Glad you fixed it.

[AWS]

Sage runs as a service and I view via Sage... same physical box.

[Fuzzy]

the settings in the sageclient.properties are irrelevant. Import paths are a server side setting only. The only reason they existed at all in your client file is that they were probably copied there on first run (which is why they are showing the default sage library locations). I don't think changing this is what fixed your issue.

[AWS]

Originally Posted by Fuzzy

the settings in the sageclient.properties are irrelevant. Import paths are a server side setting only. The only reason they existed at all in your client file is that they were probably copied there on first run (which is why they are showing the default sage library locations). I don't think changing this is what fixed your issue.

Fuzzy is right. The issue resurfaced a day or so later.

I uninstalled all of Sage, re-installed and so far, crossing my fingers, it stays "resolved".

AWS

[AWS]

happened again, even on the fresh install.

One change I made, just now, was to use a different directory for Recordings and Imports, performed a refresh of the media libraries and a bunch of media files magically appeared.

So far so good on this separation of recordings and imports.

AWS

[Fuzzy]

That was quite possibly a problem. There is no reason to set up a recording and an import folder to the same location, so it probably is a situation that was never considered.

[AWS]

That could also explain why the music and picture import directories always worked and why the video and movie import directories worked sporatically.

[Fuzzy]

Just for your information, the import and recording folders are treated the same in sage. The only functional difference is that it will not record to a import folder.