SageTV V4.1.13 Beta Is Available

[bcjenkins]

Is anyone else seeing button mapping issues on the MCE remote? The green button and the info button don't seem to be working. I'll test more when I have time then file bug.

B

[Opus4]

Did you select the MCE remote in Detailed Setup -> Commands -> Remote config? That's a new step you have to do.

- Andy

[lambda379]

Originally Posted by Narflex

6. Fixed bug where the STV selection wouldn't stick on an extender

After updating to 4.1.13, the STV won't stick for my MVP. The unusal thing is, I never had a problem in this area with previous versions. Anybody else having a problem with the STV not sticking in 4.1.13?

[oshapir]

Originally Posted by bcjenkins

Is anyone else seeing button mapping issues on the MCE remote? The green button and the info button don't seem to be working. I'll test more when I have time then file bug.

B

I have the same problem with key mapping on my MCE2005 remote. BTW I did select the MCE as the remote in the Setup - no change.

Oren.

[bcjenkins]

Originally Posted by oshapir

I have the same problem with key mapping on my MCE2005 remote. BTW I did select the MCE as the remote in the Setup - no change.

Oren.

ditto. Filed bug report.

B

[Shane Pitman]

4. Bug fix: Stuttering every 5 minutes when watching SageTV, fixed by optimization to how Seeker sorts media files

I was on .11 and experiencing stuttering routinely. I just upgraded to .13 and I have had zero stutter thusfar. Muchos gracias!

[Shane Pitman]

Originally Posted by Opus4

Did you select the MCE remote in Detailed Setup -> Commands -> Remote config? That's a new step you have to do.

- Andy

I'm having remote (green button no workie) issues since upgrading to .13 as well, and I have no MCE remote option in Remote Config, only No Remote or External Setup, Hauppauge 34, Hauppauge 45, StreamZap, USB-UIRT+Any, Evations IRMan+Any.

[Opus4]

Make sure you are using the SageTV3.xml file that installed with v4.1.13. Be sure to check for the .xml extension.

- Andy

[Shane Pitman]

Originally Posted by Opus4

Make sure you are using the SageTV3.xml file that installed with v4.1.13. Be sure to check for the .xml extension.

- Andy

Oddly enough, I can't select ANY .xml STV's as they aren't showing up in Sage (even though they are in the same dir they've been in). In Sage only the older .stv's are being listed.

Edit: I edited the Sage.properties file to use my xml (MCE) STV, but if I try to select an STV via the Sage menus I am still only able to see the older .stv's.

[AndyS]

Originally Posted by Shane Pitman

Oddly enough, I can't select ANY .xml STV's as they aren't showing up in Sage (even though they are in the same dir they've been in). In Sage only the older .stv's are being listed.

Edit: I edited the Sage.properties file to use my xml (MCE) STV, but if I try to select an STV via the Sage menus I am still only able to see the older .stv's.

Shut Sage down completely and edit the properties file manually. Once you are using an XML STV you will be able to see all of the other XML STVs.

Andy.

[Shane Pitman]

Originally Posted by AndyS

Shut Sage down completely and edit the properties file manually. Once you are using an XML STV you will be able to see all of the other XML STVs.

Andy.

^^Edit: I edited the Sage.properties file to use my xml (MCE) STV, but if I try to select an STV via the Sage menus I am still only able to see the older .stv's.

[Opus4]

Originally Posted by Shane Pitman

^^Edit: I edited the Sage.properties file to use my xml (MCE) STV, but if I try to select an STV via the Sage menus I am still only able to see the older .stv's.

Please read the post where I said what xml file to select. That is the _only_ STV that has all the latest changes, including the MCE remote selection:

Originally Posted by Opus4

Make sure you are using the SageTV3.xml file that installed with v4.1.13. Be sure to check for the .xml extension.

- Andy

[marneb17]

Shut Sage down completely and edit the properties file manually. Once you are using an XML STV you will be able to see all of the other XML STVs.

Edit: never mind ;-)

[Shane Pitman]

Originally Posted by Opus4

Please read the post where I said what xml file to select. That is the _only_ STV that has all the latest changes, including the MCE remote selection:

- Andy

My bad, editing the Sage.properties to use SageTV3.xml allowed me to select the MCE remote AND returned the ability to see .xml STVs. Unfortunately (and I know it's not Sage's problem) if I go back and select SageMC_169.xml even after setting MCE as my remote using SageTV3.xml, the media center remote once again has button issues and I can no longer see .xml STV's in the list. So... default STV is it for now.

[Narflex]

NOTE: Apparently the image loading support is broken in SageTVClient in 4.1.13. Sorry about that. We'll fix it for 4.1.14 of course.

NOTE: DVB-T support is still very beta. Complete support for DVB-T is not planned for the next major release (which we're very close to); but we are planning it for the one after that.

[Ian Norman]

For Australian owners of Conexant Stratford based DVB-T cards such as Leadtek DTV1000, Provideo PV913 etc, also Kworld VStream DVBT100, this is the first beta that will allow you to check out how DVB-T works in SageTV.

You will have to manually add your channel info to the FRQ file but all works well.

There are a couple of small issues but as Jeff said full support is not yet implemented.

Cheers

[mayamaniac]

Originally Posted by Narflex

NOTE: Apparently the image loading support is broken in SageTVClient in 4.1.13. Sorry about that. We'll fix it for 4.1.14 of course.

I think I'll skip this version then, will wait for 4.1.14. Glad I found out about it late and read other people's problems first. Thanks to the brave users here that tried it first and reported the problems.

[michelkenny]

Originally Posted by lambda379

After updating to 4.1.13, the STV won't stick for my MVP. The unusal thing is, I never had a problem in this area with previous versions. Anybody else having a problem with the STV not sticking in 4.1.13?

I'm pretty sure I had this problem also when I upgraded to .13. I noticed it when I was trying the new power cycle (green button on MVP), though I've noticed it during other upgrades too. Everytime I restart the service to enable the debug log, the problem goes away and I am unable to reproduce it. I just realised that it always happens on my first service startup after an upgrade, so it may be related to what I do during an upgrade. I have a theory... when I get back home tonight I will try to go through another upgrade process to see if I can reproduce it with debugging turned on from the start.

[trini0]

Originally Posted by Narflex

HDTV Update: If you're using HDTV you should go into Channel Setup again for your HDTV card in SageTV and rescan for channels. SageTV will now find all of the channels & subchannels available and add them to the channel list automatically.

Looking good so far.
I went from 11 digital channels in a default install to
31 digital channels with no sweat.
Now if we can just get epg data for some of those channels...
Hmmm...
Thats a discussion for another day

[rickgillyon]

Originally Posted by Narflex

[DVB-T support is still very beta. Complete support for DVB-T is not planned for the next major release (which we're very close to); but we are planning it for the one after that.

I have to add to this, that I have now been using DVB-T with SageTV in the UK for months. There have been occasional problems, but I always prefer my DVB-T tuners over my Cable PVR-350s, as the picture is loads better. So, it may be very beta, but it's working very well for me (4.1.12 anyway). Worth a try if you have DVB-T tuners.