|
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.) |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
My Sage records in portions?
My Sage has started to do something odd. Instead of ercording a 1 hour show as one 2.9GB file, it is recording it as three files. One may be 1.4GM, one .5GB and another 1GB file to total the show.
I don't like this approach, and I don't know why Sage is doing it this way - any suggestions? Thanks! |
#2
|
|||
|
|||
What is your setup? Machines, memory, Tuners, network, etc...
|
#3
|
|||
|
|||
Intel Celeron ~400MHZ
318 MB Ram MS XP Professional SageTV v.2.0.19 Hauppauge 250MCE (shows up as Hauppauge WinTV-PVR PCI II in Sage) Linksys LNE100TX |
#4
|
|||
|
|||
What is the format of your hard drive? NTFS in 64K clusters will give you the best results. I believe someone had similar problems when the hard drive was formatted to use FAT32, which has limitations on file sizes.
I think someone also fixed this problem by physically moving the Hauppauge card to another slot on the PC and reinstalling. I am assuming that you are talking about SageTV and not Sage Recorder. Also, you might check to see what encoder you are using. If your machine is not set up to use the hardware encoding of the 250, your processor could be a factor. Just throwing out some guesses/suggestions. Good luck! |
#5
|
|||
|
|||
FWIW I get the same behaviour -- but I cause it myself by restarting either my machine, the service etc. Essentially for me its simply caused by sage being interrupted. I wouldn't be surprised if thats somehow the issue for you, but as the person above notes there could definitely be other factors.
Maybe someone else can chime in and tell us if that behaviour might happen if your system became overloaded for a certain length of time, forcing sage to "catch up" and essentially have to start a new file to be synchronized properly. I don't know. Cory |
#6
|
||||
|
||||
There is a setting for file size limit, but I'm not at home right now so I don't remember where it is. Not sure if this is exactly what you are describing though.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|