SageDCT tips

[sflamm]

Correct - it has been removed in 2.7.2 (donator) in favor of the FFmpeg option (better all around for performance and simplicity).

For those that are having some issue with FFmpeg, I dont see any reason not to uninstall 2.7.2 and reinstall 2.6 which has the VLC support. There are no other improvements to SageDCT that would be missed by using 2.6 instead of 2.7.2 that I know of...

[HuMan321]

Originally Posted by sflamm

Correct - it has been removed in 2.7.2 (donator) in favor of the FFmpeg option (better all around for performance and simplicity).

For those that are having some issue with FFmpeg, I dont see any reason not to uninstall 2.7.2 and reinstall 2.6 which has the VLC support. There are no other improvements to SageDCT that would be missed by using 2.6 instead of 2.7.2 that I know of...

Could my FFmpeg problems be from using WHS2003 and not having Windows medai player or anything besides VLC media player 2.0.5 installed? I never watch video on the WHS machine so it was not important until maybe now to test???

[mores]

I have been running 2.18 (I think) since it came out - is there a compelling reason to upgrade? I don't have a lot of issues - very few halts and occasionally I have to reboot the Prime. Am I lucky that 2.18 still works that well? is that a geographical thing?

[sflamm]

Upgrade to 2.7.2.

Simply uninstall the old and install the new. All your settings will remain the same.

[Cazador]

Originally Posted by sflamm

Is the recording directory on the same machine as SageDCT or is it on a network share?


If it is a local storage location I would also use the "path replace" to change the write to use a local path - it will be faster (keep the UNC in SageTV config)

How do you do multiple path replace. For example unc paths are: //server/sage_d, //server//sage_e , etc

Direct paths d:\sage , e:\sage, etc

[nyplayer]

Originally Posted by Cazador

How do you do multiple path replace. For example unc paths are: //server/sage_d, //server//sage_e , etc

Direct paths d:\sage , e:\sage, etc

You don't it does not work. For multiple drives using Bandwidth it is useless. One of the reasons I went with local Paths and mapped the drives in my clients. I have 4 recording drives.

[MattHelm]

Originally Posted by Cazador

How do you do multiple path replace. For example unc paths are: //server/sage_d, //server//sage_e , etc

Direct paths d:\sage , e:\sage, etc

I just had to fix all my recording paths to local, because of this. Not really an issue, unless you have a lot of PC clients.

[sflamm]

Why? It is trivial to have a single location ... Drives are super cheap.
And you could have put a windows junction point as a second approach.

[nyplayer]

Originally Posted by MattHelm

I just had to fix all my recording paths to local, because of this. Not really an issue, unless you have a lot of PC clients.

Why is this a problem if you have multiple clients it is easy to Create a batch file to map drives and run them on the client once? Below is my setup 2 Drives for archiving 4 for recording. It is better to have Multiple recording drives if 1 fails the others continue recording.

net use M: \\SAGESERVER\M /PERSISTENT:YES
net use N: \\SAGESERVER\N /PERSISTENT:YES
net use O: \\SAGESERVER\O /PERSISTENT:YES
net use P: \\SAGESERVER\P /PERSISTENT:YES
net use Q: \\SAGESERVER\Q /PERSISTENT:YES
net use R: \\SAGESERVER\R /PERSISTENT:YES

[nyplayer]

sflamm,


First I ever heard of a windows junction.... Did a google search I am not sure how you would use it. In A sage Server?

[sflamm]

First I ever heard of a windows junction.... Did a google search I am not sure how you would use it. In A sage Server?

Been around forever - like a symlink in Linux/Unix but for directories in Windows - use the "mklink.exe" command.

In this case create a base UNC path (e.g. c:\sageTV\recordedTV which is shared as \\server\recordedTV) and then put a local junction point for each sub storage location

mklink /j "c:\sageTV\recordedTV\directory1" "d:\directory1\"

If the drive is on another machine use (e.g. \\server\drive1):

mklink /d "c:\sageTV\recordedTV\directory1" "\\server\directory1\"

http://comptb.cects.com/2268-overvie...nks-in-windows

if you have multiple clients it is easy to Create a batch file to map drives

That is a painful manual process that must be maintained on every machine (no updates can be made centrally).

[nyplayer]

I understand If you make a change of a drive letter on the server you have to map it on all the clients to get Comskip to work but you will still be able to play the files... server will stream it. ... But it is better than Using replace path and having that 1 drive go down and nothing gets recorded by the Prime... I guess that is my Disaster Recover experience never put all your eggs in 1 basket.

[sflamm]

But it is better than Using replace path and having that 1 drive go down and nothing gets recorded by the Prime...

The problem is that the replace path functionality will not replace only a leading prefix (I believe).... I bet babgvant would be happy to add a "replace leading prefix" switch that substitutes only the leading prefix and not the full prefix. (e.g. \\server\recordedtv only and not \\server\recordedtv\directory1. with a leading prefix only it would map to c:\recordedtv\directory1 instead of c:\recordedtv that it does today)

The other solution is to just use a raid 5 array in one location ... resilient to failure and much faster.

[Cazador]

Originally Posted by nyplayer

Why is this a problem if you have multiple clients it is easy to Create a batch file to map drives and run them on the client once? Below is my setup 2 Drives for archiving 4 for recording. It is better to have Multiple recording drives if 1 fails the others continue recording.

net use M: \\SAGESERVER\M /PERSISTENT:YES
net use N: \\SAGESERVER\N /PERSISTENT:YES
net use O: \\SAGESERVER\O /PERSISTENT:YES
net use P: \\SAGESERVER\P /PERSISTENT:YES
net use Q: \\SAGESERVER\Q /PERSISTENT:YES
net use R: \\SAGESERVER\R /PERSISTENT:YES

I like this idea. It never occured to me to do that. If I end up going that route, though I'll had to change drive letters on the server to match free drive letters on the clients.