SageTV v3.0.5 Beta

[ukmgranger]

Originally Posted by GbrNole

ps. when you get that decoder error you pretty much need to set it to overlay and then completely shut down the pc and restart before it will take.

ken c, still verify your quartz file because it will do this every time you try and use FSE if you're still using the 9.0b quartz.dll

I have had this same problem!

[Ken C]

Originally Posted by GbrNole

ken c, still verify your quartz file because it will do this every time you try and use FSE if you're still using the 9.0b quartz.dll

I am using the old version of quartz.dll, the one recommended in the SageTV Software forum. So, now I should be using the newest version ?

BTW, the problem does return ocassionally. What's got me scratching my head is all was working well for several days and nothing has changed.

Ken C

[koelec]

It might be a matter of taste, but in my opinion these new marker icons (especially the red ones: manual, 1st run, etc) shown in the epg and recording lists clog up the menu and show redundant information and should only be shown as part of the detailed info of a show. The border colors already subtlely provide most of this info.

Is there a way to disable the marker icons ? Ideally this should be configurable on each menu.

[stanger89]

Originally Posted by Ken C

I am using the old version of quartz.dll, the one recommended in the SageTV Software forum. So, now I should be using the newest version ?

FSE requires the 9c version.

[Ken C]

Originally Posted by stanger89

FSE requires the 9c version.

Ok, I'll make the change tomorrow. Thanks.

Ken C

[Wakecrash]

Originally Posted by Scott

Tried that - they said it was an "unsupported" set up and to buy a combined Tivo/Directv receiver. I think this is all about Directv controlling our hardware!

check out this link http://www.tivocommunity.com/tivo-vb...+local+channel

directv may follow through and fix the D10-100 recievers, someone in Houston has reported recieving a beta update that fixed the <100 channel changing problems and the screensaver issue. When talking to Directv, you usually have to get to 2nd level support for anyone who knows anything about this and it is usually better to say what you have is basically a standalone Tivo controlling your Directv box, since Tivo is by far more popular.

It would be nice if Sage had someway for reciever controll to be customized by a script, like myth TV can. Someone wrote a script for Myth TV that fixed the <100 channel change issue and allowed control of D10-200 recievers.

[snoopy]

You might head over to dealdatabase.com forums where all the tivo dtv hackers hang out. I seem to recall a serial program that gives you full control over channel changing via serial. This may not be what you are looking for but this stuff is pretty advanced hacking over their. Most of those guys are well versed with Linux which is what TiVo is built on.

[esubramanian]

I see a black band on the right side of the screen. In 2.x version, when I press the 'Full' button on the silver hauppauge remote (Is it toggle full screen?), this will go away, but now it does not. Anyone has the same problem?

[dadams]

esubramanian,

I had the same problem in 2.x and changed the aspect ratio settings in detailed setup>multimedia>aspect ratio. Try changing both the horizontal and vertical to the same value. I have mine set on 107% and the black bar disappeared on my standard definition TV.

Dennis

[esubramanian]

Originally Posted by dadams

esubramanian,

I had the same problem in 2.x and changed the aspect ratio settings in detailed setup>multimedia>aspect ratio. Try changing both the horizontal and vertical to the same value. I have mine set on 107% and the black bar disappeared on my standard definition TV.

Dennis

I was playing around with the horizontal value, but did not try anything above 100%. I will try it tonight. Thanks.

[blade]

esubramanian

Increasing the horizontal stretch is going to stretch the picture equally in both directions. So if you need to stretch 1" to fill out the right side of the screen you're going to lose 1" of video content on the left side because it will be stretch out of sight.

The first thing you need to do is get your current picture centered as best you can. Adjust the horizontal offset until there is an equal amount of black band on both sides of the screen, this should get your picture centered. Then raise the horizontal stretch 1% at a time until the black on both sides is completely gone.

I'd suggest doing the same thing with your verticle settings as well. Doing so will ensure that you're losing the minimum about of content possible.

[esubramanian]

Originally Posted by blade

esubramanian

Increasing the horizontal stretch is going to stretch the picture equally in both directions. So if you need to stretch 1" to fill out the right side of the screen you're going to lose 1" of video content on the left side because it will be stretch out of sight.

The first thing you need to do is get your current picture centered as best you can. Adjust the horizontal offset until there is an equal amount of black band on both sides of the screen, this should get your picture centered. Then raise the horizontal stretch 1% at a time until the black on both sides is completely gone.

I'd suggest doing the same thing with your verticle settings as well. Doing so will ensure that you're losing the minimum about of content possible.

I did not change the stretch values. I was trying the offset values. Whenever I specify any horizontal offset above zero, the black band on the left increases in size, but it does not change the right band. I am pretty sure I tried that, but I will check again tonight. Thanks

[blade]

Originally Posted by esubramanian

Whenever I specify any horizontal offset above zero, the black band on the left increases in size, but it does not change the right band. I am pretty sure I tried that, but I will check again tonight. Thanks

I had this same problem a few months back. If stretching the picture doesn't fix it then you might try increasing the desktop resolution by a few pixels or try adjusting the desktop offset in windows.

[esubramanian]

Originally Posted by blade

I had this same problem a few months back. If stretching the picture doesn't fix it then you might try increasing the desktop resolution by a few pixels or try adjusting the desktop offset in windows.

I have the desktop resolution set to 1920x1080! Not sure if that is a problem.

[srothwell]

Originally Posted by srothwell

Sent this to the bug site twice..... maybe someone here has had the same problems:

1. .m2t files still do not show up as imported files.
2. If you remane a .m2t file to .mpg, Sage 2.2 would play it just fine, but Sage 3.0.5 gives a render playback error.
3. On my system (using overlay, 3D accel) if you go to full-screen mode (not exclusive) while something is playing the text overlay will tear up on the screen. If you go to full-screen mode THEN selecting something to play, you will get a render error then Sage will lock up and you have to kill it and start over. This same thing happens whether I'm using VMR9 or overlay. FSE or non-FSE mode. Doesn't matter. Sage 2.2 didn't do any of this. Incidnetally, full screen on my PC is 1920x1200. Don't know if that matters or not.

However, to put a kink in things, Sage doesn't always misbehave in the same way with these circumstances.

For instance, sometimes I can playback a file then go to FullScreen mode and it will bring the playback fullscreen, the OSD won't break up and it will appear to work fine---until you tell it to back to non-fullscreen mode. When you tell it that, Sage screen goes black but the audio continues. I have not ever been able to get the video (or OSD) back after going back to non-full screen mode.

Throughout all the intermittent problems, if I go TO full-screen and back again, the screen is black and Sage will always keep it's window on top of other windows and will eventually lock up. This doesn't matter if you have video playing back or not. Even when a menu is is up toggling between FS and non-FS will cause the problem.

I have made sure that I had DirectX 9c and the latest quartz.dll file but this was to no avail.

Here are screenshots of what happens with the text tearing up when you go full screen:



The "gunk" you see on the first picture is the OSD that's been screwed up. The gunk on the second picture is the main menu.

Once this mess-up happens, you have to CTL-ALT-DEL kill sage and re-start to ever get it to work again.

Is anyone else having this problem?

[stanger89]

You're not using the 350 TV out are you?

I assume not, what video card are you using? What drivers?

[srothwell]

Originally Posted by stanger89

You're not using the 350 TV out are you?

I assume not, what video card are you using? What drivers?

Nope. ATI 8500 with whatever are the latest Catalyst drivers.

[stanger89]

That could be a problem, FSE VMR9 is definitely DX9 functionality, you've got a DX8 card. No idea what happens if you try and mix the two.

[Ken C]

Speaking of FSE ...

Replaced the quartz.dll with the DirectX 9c version. No longer getting the playback error but now Sage locks up when going from full screen to window. Anyone else having this problem ?

Ken C

[srothwell]

Originally Posted by Ken C

Speaking of FSE ...

Replaced the quartz.dll with the DirectX 9c version. No longer getting the playback error but now Sage locks up when going from full screen to window. Anyone else having this problem ?

Ken C

Voila! Turning off FSE mode solved everything. I would swear I turned that off before. ARRGGHH!!!

So, I'm still haveing trouble playing .m2t (transport stream) files. Even after I added .m2t to the sage properties file, I still get the "Trouble rendering video for playback" error.

I've tried different decoders etc. These files (off my HDV camcorder) play just fine outside of Sage.

Any ideas?