![]() |
|
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
|
|||
|
|||
Problem with file attributes ? 320x240 ?
ok I record pretty much everything in vcd. works fine no problems. I sometimes want to put these on dvd. usually no problem. tmpgenc will allow this it just has to change the 44khz sound to 48khz. no big deal really fast.
this happened once before and went away now its back. I import the file into tmpgenc dvd author and it errors out saying the file is 320x240 (its not its 352x240 as it should be) BUT some goofed marker in the file header or something makes it THINK its 320x240 so it rejects it (has to be 352x240) just to make sure its not tmpgenc dvd author I gave it an older file made a week ago by sage and it took it JUST fine so there IS something different about this file (I only have last 2 days as mpg still and they all exhibit the same problem) so first question is why is it doing this and how do I stop it from doing it anymore ? (sage properties etc.. have proper information ie 352x240) and second is there anything I can do to REPAIR whatever is wrong with these file so tmpgenc dvd author will see there proper size as 352x240 I tried editing the file (cut some off the beginning and end) in tmpgenc and though it does this fine whatever is "wrong" with the file persists and dvd author still insists its 320x240 when its not ? Any Help would be greatly appreciated. even if I can not FIX this problem I really need to prevent it from happening in the future. Thanks ! Chris Taylor http://www.nerys.com/ |
#2
|
|||
|
|||
FYI Restarting Sage appears to have fixed this. I still need to know how to stop it from happening since the problem persists in files that were done when this was happening and since I can not tell when it "will" do it or "WHY" it will do this I can not predict it and I tend to leave this machine run unattended for days weeks or months :-( I dont want to have to baby it.
Chris Taylor http://www.nerys.com/ |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|