ComSkip not working..
 

I am not sure what I am doing wrong here, but I can't seem to get ComSkip working on my clients.

My setup is 1 main server running latest default STV. I have DirMon2 and ComSkip working fine on my HD-PVR recordings. I loaded ComSkip STVi on the server and it seems to be working.

Now I have 2 clients running SageMC 6.3.9a. They are also running the iTV theme (not sure if that matters). I don't see any ComSkip information for any of my recordings..

Am I missing something obvious?

Make sure the paths are defined as UAC (\\server\share).

Gerry

Sory for the noob questions but:

Set paths on the server or the clients?

Which path do I set, the regular sage setting for the recordings folder?

Thanks!

Your comskipping your recordings so it would be the recordings path. Just use UNC paths everywhere. Server and clients need to see the recordings on the same path. I don't think mapped drives work but you can try the same drive letter for both of them also.

gerry

Thanks for your replies gplasky :thumb:

I have one more question if you dont mind. Since I now have to share the folders on the network, can I share them read-only?

I ask because I am curious if when I delete a recording, does it also delete the .edl and text files? If so, it is the server deleting the files or the client? I assume that when a client normally deletes a recording, it's a message from client -> server and then the server deletes it. I wasn't sure if this woudl hold true for the comskip data files.

You can set Dirmon2 to delete the files left over if the cooresponding .mpg or .ts files doesn't exist. If you share as read-only you won't be able to delete them. It's the client and the ID that is logged in that will delete the file.

Gerry

Thanks again Gerry,

I wasn't sure how to open the directories up read/write for the server, but still read only for the clients since you have to have the same path in bot.

So I did just decide to use a mapped drive. My recordings folders on the server is D:\SageTVShows. So I shared the entire drive read only, and then mapped the d share to d: on my clients (after re-ordering some drives in disk management). Voila, things work :) :goodjob: