SageTV Community  

Go Back   SageTV Community > SageTV Products > SageTV Software

Notices

SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.)

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 06-10-2020, 05:25 PM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
Sage Video Directory Optimization

Hello - so I got a 16TB hard drive and I was wondering what would be the best way to optimize it for Sage. I was first thinking about partitioning the drive with 3 or 4TB for permanent imported videos, photos and music and allowing the other 12TB for temporary videos. We keep a lot of temporary videos and I was thinking that thousands of videos all in one folder might not be the best way to optimize things but I'm not sure. If it's not then I'm trying to decide if I should partition the drive and map various letters to the partitions or if I just maybe just create a few sub-folders for the temp videos all in the same partition. Has anyone had any experience with this?
Reply With Quote
  #2  
Old 06-11-2020, 09:32 AM
MattHelm MattHelm is offline
Sage Icon
 
Join Date: Jun 2005
Location: Chicago, IL
Posts: 1,207
I have my "main" imports all set up this way. Then I use folder view to find the show I wish to watch. Root of my import looks like this:

Anime
AnimeNew
Movie
TV_Shows

Then each directory is split as needed. The Anime and Movie directories have "A" through "Z" directories, and then the movies are place by name in those.

The AnimeNew and TV_Shows are split by series name, as both have fewer listings.

Makes it very fast to find anything!
__________________
Server #1= AMD A10-5800, 8G RAM, F2A85-M PRO, 12TB, HDHomerun Prime, HDHR, Colossus (Playback - HD-200)
Server #2= AMD X2 3800+, 2G RAM, M2NPV-VM, 2TB, 3x HDHR OTA (Playback - HD-200)
Reply With Quote
  #3  
Old 06-11-2020, 09:56 AM
JustFred JustFred is offline
Sage Expert
 
Join Date: May 2015
Location: Sunnyvale, Ca
Posts: 562
I've found that creating folders, rather than drive letters, works best.

Disadvantages of creating drive letters:
1. Unnecessarily imposes size restrictions.. a pain when one category grows larger than initially expected.
2. Harder to search using Windows search tools. Have to search each drive letter independently.
3. Moving files between drive letters is slower (has to actually copy the data between logical drives, instead of a near-instantaneous move between folders).
__________________
System #1: Win7-64, I7-920, 8 GB mem, 4TB HD. Java-64 1.8.0_141. Sage-64 v9.2.1 ATSC: 2x HDHR-US (1st gen white) tuners. HD-200.
System #2: Win7-64, I7-920, 8 GB mem, 4TB HD. Java 1.8.0_131. Sage v9.1.6.747. ClearQAM: 2x HDHR3-US tuners. HD-200.
System #3: Win7-64, I7-920, 12 GB mem, 4TB HD. Java-64 1.8.0_141. Sage-64 v9.2.1 ATSC: 2x HVR2250; Spectrum Cable via HDPVR & USB-UIRT. 3x HD-200.

Last edited by JustFred; 06-11-2020 at 11:49 AM.
Reply With Quote
  #4  
Old 06-11-2020, 11:18 AM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
When formatting the disk do you just set the cluster size to the default or 64K or some other size? Thanks,
Reply With Quote
  #5  
Old 06-11-2020, 11:48 AM
JustFred JustFred is offline
Sage Expert
 
Join Date: May 2015
Location: Sunnyvale, Ca
Posts: 562
Sage **used** to always recommend setting the cluster size to 64KB to reduce/eliminate pauses/stuttering, but that recommendation seems to have gone away years ago. As a practical matter, for a drive that contains mostly large files (such as video files), 64K still makes most sense (more efficient use of the directory structure). On the other hand, for an OS drive, let Windows pick the optimum default cluster size.
__________________
System #1: Win7-64, I7-920, 8 GB mem, 4TB HD. Java-64 1.8.0_141. Sage-64 v9.2.1 ATSC: 2x HDHR-US (1st gen white) tuners. HD-200.
System #2: Win7-64, I7-920, 8 GB mem, 4TB HD. Java 1.8.0_131. Sage v9.1.6.747. ClearQAM: 2x HDHR3-US tuners. HD-200.
System #3: Win7-64, I7-920, 12 GB mem, 4TB HD. Java-64 1.8.0_141. Sage-64 v9.2.1 ATSC: 2x HVR2250; Spectrum Cable via HDPVR & USB-UIRT. 3x HD-200.
Reply With Quote
  #6  
Old 06-11-2020, 11:51 AM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
So you think the NTFS default is okay to use or best to still use 64K for video drives?

Last edited by mike1961; 06-11-2020 at 12:23 PM.
Reply With Quote
  #7  
Old 06-11-2020, 12:33 PM
JustFred JustFred is offline
Sage Expert
 
Join Date: May 2015
Location: Sunnyvale, Ca
Posts: 562
For video drives, I prefer and continue to use 64K cluster size.
__________________
System #1: Win7-64, I7-920, 8 GB mem, 4TB HD. Java-64 1.8.0_141. Sage-64 v9.2.1 ATSC: 2x HDHR-US (1st gen white) tuners. HD-200.
System #2: Win7-64, I7-920, 8 GB mem, 4TB HD. Java 1.8.0_131. Sage v9.1.6.747. ClearQAM: 2x HDHR3-US tuners. HD-200.
System #3: Win7-64, I7-920, 12 GB mem, 4TB HD. Java-64 1.8.0_141. Sage-64 v9.2.1 ATSC: 2x HVR2250; Spectrum Cable via HDPVR & USB-UIRT. 3x HD-200.
Reply With Quote
  #8  
Old 06-11-2020, 12:39 PM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
That makes sense. I was thinking even though sage.properties files for the videos are only 1K or 2K even with 5000 files in a directory that would still only be around 320 megs with 64K clusters and then one will have great savings with fragmentation for the really large video files. Thanks
Reply With Quote
  #9  
Old 06-11-2020, 02:49 PM
NetworkGuy NetworkGuy is offline
Sage Fanatic
 
Join Date: Dec 2009
Location: Central NJ
Posts: 869
Quote:
Originally Posted by JustFred View Post
I've found that creating folders, rather than drive letters, works best.
Absolutely agree. I have multiple import directories and different sub-directories:
  • Movies - by genre
  • TV - by show name
  • Music - by recording artist
  • Photos - by event
__________________
Hardware: Intel Core i5-3330 CPU; 8GB (2 x 4GB); 2-4TB WD Blue SATA 6.0Gb/s HDD; Windows 7
Servers: ChannelsDVR, Plex, AnyStream, PlayOn,
Tuner: HDHomeRun Connect Quatro
Tuner: HDHomeRun Connect Duo
Sources: OTA, Sling Blue, Prime, Disney+,
Clients: ShieldTV (2), Fire TV Stick 4K (4)
Reply With Quote
  #10  
Old 06-11-2020, 02:53 PM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
I was thinking though that it might be a good idea to at least partition the imported stuff (videos, music and photos) from the temporary video directories. My thought being that the imported stuff is not likely to ever be deleted and only added to so fragmentation would be minor compared to the temporary video folder(s) which always have stuff added and deleted and could need a defrag every so often. Otheriwse, the imported stuff could just be on a completely separate drive if not a separate partition.
Reply With Quote
  #11  
Old 06-11-2020, 11:11 PM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
You know I just realized that everyone replying was referring to creating folders for imported files. But, what about the temporary video directories? I'm not sure how Sage decides which one to use but I think if there are several drive letters then it always uses the one with the most space for temporary recordings (recordings from the program guide). So, I'm not sure what would happen if I created separate folders on the same drive if it then looks at how many recordings there are in each folder or space available. Does anyone know the answer to this? Thanks,

Edit: from reading the manual it seems that sage looks at which drive has the most space and might spread two recordings at the same time over two drives. The thing I'm trying to avoid is having tens of thousands of files in one folder so I'm not sure if partitions might be better for a really large drive like 16tb for the temp recordings. Maybe I should partition it for 4tb for imported and the other 12TB maybe have two 6TB partitions for the temp recordings.

Last edited by mike1961; 06-11-2020 at 11:37 PM.
Reply With Quote
  #12  
Old 06-12-2020, 06:17 AM
graywolf's Avatar
graywolf graywolf is offline
Sage Icon
 
Join Date: Oct 2009
Location: NC
Posts: 1,366
Not really sure that is buying you anything. it is still 1 physical disk so although you have 2 logical partitions/drive letters, when it actually comes to writing, going to be using the same heads, so the arm would have to traverse between the disk locations.

What I have is record to a local drive, then daily I have a SJQ task run a groovy script that moves the files in the "temp location" to my NAS and uses ShowName for the folder and Season # as subfolder to it.

find_tv_to_move
Code:
import com.google.code.sagetvaddons.sjq.network.ServerClient;
import com.google.code.sagetvaddons.metadata.Factory;
import com.google.code.sagetvaddons.groovy.api.MediaFileHelpers ;

// What directory are we moving archives to?
File dest = new File("\\\\tower\\");

// Queued tasks are marked with this metadata value
String SJQ4_QUEUED = "SJQ4_ARCHIVED";

// Are we running on Windows?  File names are not case sensitive on Windows so we need to handle that
boolean isWindows = System.getProperty("os.name").contains("Windows");

ServerClient clnt = new ServerClient();
int i = 0;
for(Object mediaFile : MediaFileAPI.GetMediaFiles("T")) {
    String filePath = MediaFileAPI.GetFileForSegment(mediaFile, 0).getAbsolutePath();
    String ShowName = SJQ4_METADATA.get("SJQ4_SEGMENT_0");

    if(isWindows)  
        filePath = filePath.toLowerCase();
    
    
    // If the media file is already stored on the NAS, it's already been queued or it's actively recording then just skip it
    if(filePath.startsWith(isWindows ? dest.toString().toLowerCase() : dest.toString()) ||
//        MediaFileAPI.GetMediaFileMetadata(mediaFile, SJQ4_QUEUED).equals("1") ||
        MediaFileAPI.IsFileCurrentlyRecording(mediaFile) ||
        MediaFileHelpers.isBeingViewed(mediaFile)) 
        continue;
    
//    if ( ShowTitle ^= "The" ) {
//       println  "${ShowName} to be moved ... "
       println  (filePath + " to be moved ... ") ;
	   clnt.addTask("MVMEDIALR", Factory.getMap(mediaFile));
       MediaFileAPI.SetMediaFileMetadata(mediaFile, SJQ4_QUEUED, "1");
//    }
}
clnt.close();
return 0;
Code:
/******************************************************************************
     Move a SageTV Media File

     Last Modified: 16 Feb 2011
            Author: Derek Battams <derek AT battams DOT ca>

    Use this groovy script to move a SageTV media file object from one location
    to another.
    
    The media file to be moved is defined by the SJQ4_ID environment variable;
    the SJQ4_TYPE variable must also be "MediaFile".  The destination is given
    as the first command line argument to this script.  The destination is a 
    directory.

    This script will trigger a rescan of your media after a successful move; the
    rescan is necessary in order for SageTV to recognize the media file in its
    new location.
******************************************************************************/

boolean testMode = false; // Don't actually move any files, just print out what would be done
String flagsFile="\\\\PWM1\\Users\\PWM\\Documents\\SageTV\\Move_Recordings_Output\\HTPC-LR\\Move_Recordings_Output.txt" ;


/******************* DO NOT EDIT BELOW THIS LINE ************************/

// But if you do then send me your bug fix patches! ;)

import org.apache.commons.io.FileUtils;
import static groovy.io.FileType.*;
import com.google.code.sagetvaddons.sjq.network.ServerClient;
import java.io.*;
import java.util.*;
import java.text.SimpleDateFormat;
import java.text.DateFormat;

public WriteToFile(String outputFileName, String  content) {
    try {
         File outputFile = new File(outputFileName);
// if file doesnt exists, then create it
         if (!outputFile.exists()) {  
              outputFile.createNewFile();
         }
// true = append to file
         FileWriter fw = new FileWriter(outputFile.getAbsoluteFile(),true);
         BufferedWriter bw = new BufferedWriter(fw);
         bw.write(content);
// \n = new line feed         
         bw.write("\n");
         bw.close();
        } catch (IOException e) {
            e.printStackTrace();
        }
}

DateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd_HHmm") ;
Date runDate = new Date();
//string runDT = dateFormat.format(runDate)

String ShowName = SJQ4_METADATA.get("SJQ4_SEGMENT_0");
String type = SJQ4_METADATA.get("SJQ4_TYPE");
String id   = SJQ4_METADATA.get("SJQ4_ID");
File dest   = new File("${SJQ4_ARGS[0]}");
String NewShow = "${SJQ4_ARGS[0]}/${ShowName}";
String SJQ4_QUEUED = "SJQ4_ARCHIVED";

String flagSettings ;

println ("Parm passed = " + SJQ4_ARGS[0] );
println ("New File = ${NewShow}");
boolean RC ;


if(!dest.isDirectory() && !dest.mkdirs()) {
    println("Destination directory is invalid! [" + dest.getAbsolutePath() + "]");
    return 1;
}

if(!"MediaFile".equals(type) || id == null || !id.matches("\\d+")) {
    println("No media file attributes provided!");
    return 1;
}

Object mediaFile = MediaFileAPI.GetMediaFileForID(id.toInteger());
if(mediaFile == null) {
    println("No media file for id " + id);
    return 1;
}

if(MediaFileAPI.GetNumberOfSegments(mediaFile) == 0) {
    println("Zero file segments for media file; nothing to move!");
    return 1;
}

boolean WatchedFlag = AiringAPI.IsWatched(mediaFile) ;
boolean ArchivedFlag = MediaFileAPI.IsLibraryFile(mediaFile) ;
boolean LikeFlag = AiringAPI.IsDontLike(mediaFile)
int origAiringID = AiringAPI.GetAiringID(mediaFile);
String showExternalID = ShowAPI.GetShowExternalID(mediaFile);

println("Moving " + Arrays.toString(MediaFileAPI.GetSegmentFiles(mediaFile)) + " to destination: " + dest.getAbsolutePath());
// Copy all segments then delete the originals if more than one segment otherwise just do a filesystem move op
if(MediaFileAPI.GetNumberOfSegments(mediaFile) == 1) {
    try {
        if(!testMode)
            FileUtils.moveFileToDirectory(MediaFileAPI.GetFileForSegment(mediaFile, 0), dest, false);
        else
            println("Would move: " + MediaFileAPI.GetFileForSegment(mediaFile, 0));
    } catch(IOException e) {
        println("Failed to move file to destination!");
        e.printStackTrace();
        return 1;
    }
} else {
    def copied = [];
    // Copy the files to their new home
    for(File segment : MediaFileAPI.GetSegmentFiles(MediaFileAPI.GetMediaFileForID(id.toInteger()))) {
        try {
            if(!testMode) {
                FileUtils.copyFileToDirectory(segment, dest, true);
                copied.add(new File(dest, segment.getName()));
                println("\tCopy of '" + segment.getAbsolutePath() + "' completed...");
            } else {
                println("\tWould move: " + segment.getAbsolutePath());
            }
        } catch(IOException e) {
            println("Error copying segment '" + segment.getAbsolutePath() + "' to destination!");
            e.printStackTrace();
            copied.each {
                if(!it.delete())
                    println("Failed to delete '" + it.getAbsolutePath() + "'");
            }
            return 1;
        }
    }
}
 
println("Moving artifacts...");
mvArtifacts(id.toInteger(), dest, testMode);

if(!testMode) {
    RC=MediaFileAPI.DeleteFile(MediaFileAPI.GetMediaFileForID(id.toInteger()));
    if ( !RC ) {
       println ("DeleteFile failed");
    } else {
       println ("DeleteFile success");
	}
	//    ServerClient sc = new ServerClient();
    File NewFile   = new File(NewShow);
    println ("NewFile string = " + NewFile.toString() );
	RC=MediaFileAPI.AddMediaFile(NewFile, null);
    if ( !RC ) {
	   println ("AddMediaFile failed");
   } else {
	   println ("AddMediaFile success");
	}

    Object mfNew = MediaFileAPI.GetMediaFileForFilePath(NewFile);
	if (mfNew == null ) {
	   println ("mfNew is null") ;
	}

	Object origAiring = AiringAPI.GetAiringForID(origAiringID);
	RC=MediaFileAPI.SetMediaFileAiring(mfNew,origAiring ) ;
    if ( !RC ) {
	   println ("SetMediaFileShow failed");
    } else {
	   println ("SetMediaFileShow success");
	}
    if ( WatchedFlag ) {
        AiringAPI.SetWatched(mfNew);
        println("${NewShow} Should be Watched...");
        isWatched = "Watched" ;
    } else {
        AiringAPI.ClearWatched(mfNew);
        println("${NewShow} Should be Unwatched...");
        isWatched = "Unwatched" ;
    }

    if ( LikeFlag ) {
        AiringAPI.SetDontLike(mfNew);
        println("${NewShow} Should be Don't Like...");
        dontLike = "Don't Like" ;
    } else {
        AiringAPI.ClearDontLike(mfNew);
        println("${NewShow} Should be Like...");
        dontLike = "Like" ;
    }

    if ( ArchivedFlag ) {
        MediaFileAPI.MoveFileToLibrary(mfNew);
        println("${NewShow} Should be Archived...");
       isArchived = "Archived" ;
    } else {
        MediaFileAPI.MoveTVFileOutOfLibrary(mfNew);
        println("${NewShow} Should be UnArchived...");
       isArchived = "UnArchived" ;
    }
    AiringAPI.Record(MediaFileAPI.GetMediaFileAiring(mfNew));

    flagSettings= dateFormat.format(runDate) + "|" + NewFile.toString() + "|${origAiringID}|${isArchived}|${isWatched}|${dontLike}" ; 
	WriteToFile(flagsFile, flagSettings) ;
	
}

//MediaFileAPI.SetMediaFileMetadata(mediaFile, SJQ4_QUEUED, "1");

println ("Move completed") ;
 
return 0;

def mvArtifacts(int mfId, File dest, boolean testMode) {
    for(File segment : MediaFileAPI.GetSegmentFiles(MediaFileAPI.GetMediaFileForID(mfId))) {
        String prefix = segment.getName().substring(0, segment.getName().lastIndexOf('.'));
        File baseDir = new File(segment.getParent());
        baseDir.eachFileMatch FILES, {!new File(baseDir, it.toString()).equals(segment) &&  it.toString().startsWith(prefix)}, {
            File artifact = new File(baseDir, it.getName());
            if(!testMode) {
                FileUtils.moveFileToDirectory artifact, dest, false;
            } else
                println("Would move artifact: " + artifact.getAbsolutePath());
        }
    }
}
Reply With Quote
  #13  
Old 06-12-2020, 10:59 AM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
I was thinking the way it might help is rather than 20,000 files in a single folder (as an example) I would only have half that number and also fragmentation would be less of an issue. But, as you mentioned, I'm not sure how much that would help.
Reply With Quote
  #14  
Old 06-12-2020, 11:28 AM
Tiki's Avatar
Tiki Tiki is offline
Sage Icon
 
Join Date: Feb 2005
Location: Southwest Florida, USA
Posts: 1,992
I had no idea what you meant by ďtemp video filesĒ. It sounds like you are talking about the Sage Recording Directories.

I really donít think it matters whether you partition the drive or not as far as Sage is concerned. Itís simply a matter of personal preference. Years ago there were compelling reasons for partitioning a drive (such as the fact that older versions of Windows couldnít handle partitions larger than a particular size). But these days I think itís usually better to just leave one big partition.

One thing you donít want to do is to create two Sage recording directories on the same partition. This will confuse Sageís logic for how much free space is available and how much free space it needs to keep.
__________________
Server: Ryzen 2400G with integrated graphics, ASRock X470 Taichi Motherboard, HDMI output to Vizio 1080p LCD, Win10-64Bit (Professional), 16GB RAM
Capture Devices (7 tuners): Colossus (x1), HDHR Prime (x2)
,USBUIRT (multi-zone)
Source:
Comcast/Xfinity X1 Cable
Primary Client: Server Other Clients: (1) HD200, (1) HD300
Retired Equipment: MediaMVP, PVR150 (x2), PVR150MCE,
HDHR, HVR-2250, HD-PVR
Reply With Quote
  #15  
Old 06-12-2020, 12:34 PM
mike1961 mike1961 is offline
Sage Icon
 
Join Date: Dec 2005
Location: California
Posts: 1,555
I thought it might matter but perhaps not. Figure 16TB with one folder for a Sage Recording Directory and figure an average of 2GB per video is 8,000 files then double that since each could have a sage properties file which is 16,000 files in one folder. Maybe that's not a problem but at some point I would think the number of files in a folder could be an issue but I'm not sure how many one would have to have.
Reply With Quote
  #16  
Old 06-13-2020, 02:07 AM
xjim1's Avatar
xjim1 xjim1 is offline
Sage Advanced User
 
Join Date: Sep 2010
Location: colorado
Posts: 219
I move stuff around quite a bit and prefer folders, a lot quicker than moving between partitions. You can still move your recorded files into different folders. Sage will still see them as long as they're under either a recording directory or imported videos folder. I do what others have mentioned and organize by series and seasons, or whatever. You also won't have to be concerned as much about defrag'g either.
Reply With Quote
  #17  
Old 06-13-2020, 09:15 AM
UgaData's Avatar
UgaData UgaData is offline
Sage Aficionado
 
Join Date: Sep 2005
Posts: 436
Windows has a limit to the number of files in the ROOT Directory of a Drive(:\, 250 files or so) but there is no limit within Folders/Directories.

I always format DATA drives with 64K blocks. And defrags can be scheduled with the OS to run in the background (for me once a week).

I also set the drive letter to be something unlikely to be a local drive letter (something greater than E: - usually R: thru U: ), this way there are no conflicts when accessing the Drive from other clients (i.e. both client and server will see U: as the share - for import directories it helps if the server and client see the same share. Of course if you only use extenders this may not matter)
__________________
"Unencumbered by the thought process"

The only constant in the Universe is change.

Last edited by UgaData; 06-13-2020 at 09:36 AM. Reason: Add drive letter suggestion
Reply With Quote
  #18  
Old 06-13-2020, 03:50 PM
nyplayer nyplayer is offline
SageTVaholic
 
Join Date: Sep 2005
Posts: 4,799
Quote:
Originally Posted by UgaData View Post
Windows has a limit to the number of files in the ROOT Directory of a Drive(:\, 250 files or so) but there is no limit within Folders/Directories.

I always format DATA drives with 64K blocks. And defrags can be scheduled with the OS to run in the background (for me once a week).

I also set the drive letter to be something unlikely to be a local drive letter (something greater than E: - usually R: thru U: ), this way there are no conflicts when accessing the Drive from other clients (i.e. both client and server will see U: as the share - for import directories it helps if the server and client see the same share. Of course if you only use extenders this may not matter)
I find that 64K blocks is no longer needed and uses more space when you store EDL files and other small files.
__________________
Windows 10 I3 Dual Core 3.0 Server, SageTV9... OpenDCT with 2 HDHRPrimes and 4 HDHRconnects for a total of 14 Tuners.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
recordings location optimization bbig119 SageTV Software 2 12-03-2008 07:44 AM
Hauppauge's TCP/IP Optimization Taddeusz SageTV Media Extender 2 06-14-2007 01:11 PM
Video directory showing up in Import Video Directory dvd_maniac SageTV Software 5 12-19-2004 09:38 AM
DScaler/Elecard or other optimization beneficial for DLP Samsung with DVI from ATI?? davedelite SageTV Software 25 02-05-2004 07:18 PM
BUG: Recursive Video/Library Directory set up crashes sage (sage.properties) wayne SageTV Software 0 07-11-2003 12:59 PM


All times are GMT -6. The time now is 02:53 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.