Sage 2.1 and Custom STV's

[mightyt]

I have not been around before to the current v.2.0.20 Sage release and since then have grown quite happy :) with using some of the custom STV's provided here; such as MlbDude2 and Nielm 1.5.

Now that we are officially hearing about 2.1 release from Dan it made me wonder ...

If you are using Sage with a Custom STV today and a new version of Sage comes along (like 2.1) does that mean we have to ...

1 - Revert back to the original STV in order to get 2.1 functionality and can our Custom STV? ... or

2 - Can we easily upgrade to 2.1 and continue use existing Custom STV's on top of 2.1? ... or

3 - Do we have to wait for Custom STV upgrades that support 2.1?

Thanks, T.

[SHS]

It most likely be 3

[mlbdude]

Some or all :). There may come a time when an STV will not work with a new version of SageTV. Just like any other application that has addons those addons may have to be redone.

However, I can only guess, but I think for 2.1 you will be OK. Unless 2.1 default STV comes with new features that the other STV's don't have that you want. But that is another issue :).

[mightyt]

This is a little concerning to me .... Once one immerses him or herself in to a Custom STV and then tweaks it to their liking, they then become torn because the new Sage version may have desirable functions and yet still not have some of the features provided by the Custom STV already being used. So they end up at a loss either way they go. :confused:

Another concern is, what if the original Custom STV builder decides not to upgrade in support of the new Sage rev? Again, that leaves us having to choose and make unwanted trade-offs. :bang:

It appears to me, at best, if you are stuck on the goodness of your Custom STV, you would have to hope the developers who "will" support the upgrade, will do it in a timely manner, not months and months away. :cool:

This could potentially be circumvented if Frey ensures that STV builders who have been dedicated in supporting Sage in this forum get a long lead on pre-release upgrades (alpha and beta) so they can be ahead of the curve and have their STV's remediated prior to the next Sage release. This way the new Sage release comes out for us just about the same time an updated STV would. :jump:

Does Sage do this? Will STV developers supoprt this? Am I worrying about nothing? Or are others concerned as well? ;)

Thanks, T.

[ikarus79m]

I didn't even hear about 2.1 at all yet. Anybody knows what they will add and when it will be released?

[heffe2001]

I THINK this is what they are talking about:

http://forums.freytechnologies.com/forums/showthread.php?p=61142#post61142

So hopefully sometime next week we'll get the low-down on what all's changing :).

[Opus4]

So far, the mentioned changes for 2.1 are:

For favorites: "Keep at Most = N" + "AutoDelete = No" will cause SageTV to stop recording new episodes when N recordings are reached. You will have to delete one before another one will record.


Existing recordings that are not Manual Recordings or Favorites will no longer be auto-deleted when IR is turned off or Fav options are changed.


EDIT -- Almost forgot: Support for the Plextor ConvertX TV402U & 402U devices was announced here.
I don't remember whether anything else has been mentioned.

- Andy

[kny3twalker]

they said they would fix issue with nvDVD 2.55 crashes sageTV with VMR9 and DXVA disabled

Robert,

I showed the developer your error and he says it will be fixed in 2.1. I'm not sure of when the actual release date yet. We are still working some things out.

Thanks,

George

[mightyt]

This is a little concerning to me .... Once one immerses him or herself in to a Custom STV and then tweaks it to their liking, they then become torn because the new Sage version may have desirable functions and yet still not have some of the features provided by the Custom STV already being used. So they end up at a loss either way they go. :confused:

Another concern is, what if the original Custom STV builder decides not to upgrade in support of the new Sage rev? Again, that leaves us having to choose and make unwanted trade-offs. :bang:

It appears to me, at best, if you are stuck on the goodness of your Custom STV, you would have to hope the developers who "will" support the upgrade, will do it in a timely manner, not months and months away. :cool:

This could potentially be circumvented if Frey ensures that STV builders who have been dedicated in supporting Sage in this forum get a long lead on pre-release upgrades (alpha and beta) so they can be ahead of the curve and have their STV's remediated prior to the next Sage release. This way the new Sage release comes out for us just about the same time an updated STV would. :jump:

Does Sage do this? Will STV developers supoprt this? Am I worrying about nothing? Or are others concerned as well? ;)

Thanks, T.

Does Sage do this? Will STV developers supoprt this? Am I worrying about nothing? Or are others concerned as well? ;)

T.

[mlbdude]

What would the ramifications be if/when Studio is released? This is common in the industry. Heck, every time I get a new version of my browser new versions of the plugins have to be released. Just a sucky thing we may have to live with.

This is why it is important to try and get Frey to include as much as possible in the supported STV.

[mightyt]

What would the ramifications be if/when Studio is released? This is common in the industry. Heck, every time I get a new version of my browser new versions of the plugins have to be released. Just a sucky thing we may have to live with.

This is why it is important to try and get Frey to include as much as possible in the supported STV.

Agreed ... But, does that mean you STV developers get your hands on prerelease code so you can upgrade your STV's in a reasonable amount of time (if you chose to do so at all)? Or do you have to wait until it is released to the world to start, thus forcing us to wait that much longer??

I believe plug-in developers get new browser code prior to release so they can be prepared to get folks like you and me quick updates ...

Thanks, T.

[laurenglenn]

Agreed ... But, does that mean you STV developers get your hands on prerelease code so you can upgrade your STV's in a reasonable amount of time (if you chose to do so at all)? Or do you have to wait until it is released to the world to start, thus forcing us to wait that much longer??

I believe plug-in developers get new browser code prior to release so they can be prepared to get folks like you and me quick updates ...

Thanks, T.
That's covered by the NDA... :)

Basically, let's just say that I've used some of the 2.1 API's as some of them were implemented in the beta. And I imagine other STV users have been doing the same.


Lauren

[mightyt]

That's covered by the NDA... :)

Basically, let's just say that I've used some of the 2.1 API's as some of them were implemented in the beta. And I imagine other STV users have been doing the same.


Lauren

Thanks Lauren ... I was really interested in just knowing that developers had a head start so that when 2.1 arrives we (us custom STV users) don't have to choose between the old Sage version with cool custom STV functions vs. a new Sage version with no STV's available for some time. :cool:

Though it appeared hard to get a direct answer, I think it now appears that my concerns have been addressed. Looks like when 2.1 "really" hits the streets, "you all" (STV developers) will follow-up with STV updates shortly thereafter (rather than months away) ... Of course that's good news to me ... :D

Again, thanks for responding as best as possible. :thumb:

T.

[nielm]

I cound not really have developed my dynamic menu system without having access to 2.1

[mightyt]

I cound not really have developed my dynamic menu system without having access to 2.1

:thumb: :) :) :) :) :thumb: