Padding of Favorites not working

[bigblue]

I'm still running SageTV 1.4. When I try to pad the end of my favorites, it dosen't seem to take effect. I have to go to each individual episode and pad the end time there if I want it to actually work. Is this a known bug in the version I'm running? Any way to fix it?

Thanks.

Athlon 2500+, Win2000 Pro, SageTV 1.4, Sage Recorder 1.4, 2x Haup 250s.

[stanger89]

Is the padding actually not there? I ask because Sage only displays the scheduled runtime in the progress bar, not the padding (even though it's there).

[sudipto]

Do you have other programs recording on the same channel right after the favorite episodes ? If so, Sage by default will remove padding on back to back recordings on the same channel. This is to reduce unnecessary conflicts.

However, if you would like to change this behavior, tweak the value of the property "remove_padding_on_back_to_back_favorites" in the Sage.properties file. Make sure Sage is completely closed (not just in sleep mode) when editing the Sage.properties file, or your changes will be overwritten by Sage.

[sudipto]

Originally Posted by stanger89

Is the padding actually not there? I ask because Sage only displays the scheduled runtime in the progress bar, not the padding (even though it's there).

Sage will, however, show the padding in the "View Upcoming Program Schedule"

[nielm]

"remove_padding_on_back_to_back_favorites"
I thought this was a 2.0 feature? bigblue is using 1.4

[bigblue]

The pad is definitely not there, when I watch the shows they just cut off at the end.

Yes there is another show which records on the same channel right after, but I have two tuners and the second one is not occupied. I had hoped the second tuner would just start the next recording while the first one recorded the extra pad at the end of the first show. Is there any way to make 1.4 behave this way?

Thanks.

[sudipto]

Oh, I didn't notice that you are still on 1.4

Well, why not upgrade to 2.0 ?

[bigblue]

I will upgrade if there's no other fix, but it took me quite a while to get everything working properly with the two tuners, so I'm really reluctant to rock the boat if it's not absolutely necessary. Figured I'd try for a 1.4 fix first.

[stanger89]

Originally Posted by bigblue

I will upgrade if there's no other fix, but it took me quite a while to get everything working properly with the two tuners, so I'm really reluctant to rock the boat if it's not absolutely necessary. Figured I'd try for a 1.4 fix first.

Just save your Frey directory and install 2.1 right over the top. If it doesn't work, uninstall, delete the dir, reinstall 1.4 and then copy the dir back.

[sudipto]

Originally Posted by bigblue

I will upgrade if there's no other fix, but it took me quite a while to get everything working properly with the two tuners, so I'm really reluctant to rock the boat if it's not absolutely necessary. Figured I'd try for a 1.4 fix first.

I have four tuners in my system and I regularly upgraded to the latest and greatest version of Sage using the method Stanger suggested and never had a problem ... that is until I upgraded to 2.1.

Myself and a couple others seem to be having some problems with version 2.1 ... but the release version of 2.0 (v2.0.20) worked perfectly for me. So if you are worried about stability, I would recommend giving 2.1 some time to mature and stay with 2.0.20 for the time being.

If you upgrade following Stangers advice, all your settings will be retained. Just make sure you have a copy of the Wiz.bin, Wiz.bak and Sage.properties so you can revert back if necessary.

[bigblue]

Anybody know how I can get a copy of version 2.0? The site only seems to be supplying 2.1 for download now.

[ToxMox]

Why not just use Stanger's method of upgrading and try 2.1 it may work fine for you. If you run it with the service disabled it acts very much like 2.0.

[sudipto]

Originally Posted by bigblue

Anybody know how I can get a copy of version 2.0? The site only seems to be supplying 2.1 for download now.

The released version of Sage 2.0 (ver 2.0.20) still seem to be available at the old download location here