More > JRiver Media Center 31 for Windows

Server Permissions

<< < (3/10) > >>

new2hifi:

--- Quote from: JimH on May 09, 2023, 03:57:49 pm ---...It will just not have access to JRiver servers any longer.
--- End quote ---

Does it affect JRemote connections or MC27 login authentication?

rhb:
Very unhappy with this. I've purchased the software numerous times in the past when I didn't need to (I wanted to support ongoing development) but cannot afford to do so again. This unfortunately means that I'll be losing part of the functionality that I paid for. Hopefully you can find some way to restore these services in the future.

nonsub:

--- Quote from: JimH on May 10, 2023, 12:53:49 am ---Several years. 

--- End quote ---

Several = a minimum of 3 years. Seems reasonable to me.

Not a fan of how this was handled though. IMHO it would have been better to absorb the cost for existing version owners and raise the price for new licenses to compensate. But it's not my company and JRiver has been on the market long enough that I guess they know what they are doing. i'm myself grateful that JRiver has not (yet anyway) moved entirely to a subscription model like everything else out there. I for one would not remain a customer were that to happen. I only use JRiver for Audio, 2-chan at that, WDM, and no advanced features really. So upgrades don't offer me anything really...

Awesome Donkey:
I think it's perfectly reasonable, considering bandwidth costs for the services in the older versions likely isn't insignificant. I'd be willing to bet JRiver's services in older versions consume more data than newer versions do, so having an end-of-life for the services in old versions of MC is reasonable in my mind.

Yes, it sucks if you use features like cover art and CD lookup in older versions and you won't be able to use them anymore without upgrading, but it's not unreasonable because a) it's probably not sustainable into the future with how everything has been increasing in price as of late thanks to inflation and b) having access to services in old versions for a few years (e.g. back to maybe MC29 or MC28, not sure) is at least 3 years. Though if you're on MC28 or MC29 (or whatever JRiver decides to support in regards to old versions) do keep in mind that with those the support may be only a year or two left, not sure how that'd work. I'd assume the older versions supported today don't have as much time left in regards to services support compared to the newly released MC31, for example.


--- Quote from: nonsub on May 10, 2023, 12:52:34 pm ---IMHO it would have been better to absorb the cost for existing version owners and raise the price for new licenses to compensate.
--- End quote ---

I disagree, even if you increase prices on new licenses the costs maintaining those services on old versions isn't insignificant and will increase over time as newer MC versions become "old" because remember it's an ongoing cost for servers and bandwidth. Even if they kept increasing prices it still likely wouldn't be enough to help maintain those services in older versions (plus it may drive away new customers if prices increase too much), if I had to guess. At some point a line in the sand has to be drawn, and it has.

nonsub:

--- Quote from: Awesome Donkey on May 10, 2023, 01:26:43 pm ---I disagree, even if you increase prices on new licenses the costs maintaining those services on old versions isn't insignificant and will increase over time as newer MC versions become "old" because remember it's an ongoing cost for servers and bandwidth. Even if they kept increasing prices it still likely wouldn't be enough to help maintain those services in older versions (plus it may drive away new customers if prices increase too much), if I had to guess. At some point a line in the sand has to be drawn, and it has.

--- End quote ---

Fair argument. That being said the 1-day notice to end users I believe would either be ignorance (ie. intentionally disrespectful to customers,) or incompetence (ie. switching cloud providers and suddenly finding a cost problem.)

 

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version