More > JRiver Media Center 23 for Windows
Complaint Department
Awesome Donkey:
--- Quote from: tyler69 on June 26, 2017, 04:58:09 am ---I'd like to see some statistics on how many users have been helped "unofficially" by mc users and not by JRiver staff. So that's actually less workload for JRiver than having a "complaint department" ;)
--- End quote ---
It's rather nice to see a community of users helping other users with their issues. Not only that, it's rather nice to see the CEO and the JRiver developers themselves responding to support topics, so how many companies can you say do this? Many of them outsource their support to support firms and it's VERY rare to get responses from developers this way.
tyler69:
you're missing the point i guess. i never said that it is not nice to have a knowledgable community.
regarding the ceo responding: i know of a few companies that do this. there are sometimes matters, that i like to have official statements to. no biggie in my opinion.
Vocalpoint:
--- Quote from: tyler69 on June 26, 2017, 04:58:09 am ---My personal upgrade plan is now: wait until a new version comes out and then see what was added in the current one. If there's something I want in the current one (where development ends), I buy the new version.
Another point for me to stay away from new versions: since JRiver -like every company- has limited resources, it might take a while to optimize already implemented functionality when putting new things into the software is a priority.
--- End quote ---
I endorse the JRiver business plan - and I always support them immediately upon news of a new version license being available. But that's usually where the love ends (for a while).
My upgrade schedule is to enjoy the last build of the previous version until the "new" version moves up to at least Build 50. That is my benchmark to jump in and start a migration. I figure by Build 50 (within the "Latest" channel) - the app has settled to the point of daily use and most key enhancements are available and relatively solid.
VP
Sjettepet:
--- Quote from: Spike1000 on June 24, 2017, 01:03:46 am ---Have a read of this post, it explains JRiver's business model.
https://yabb.jriver.com/interact/index.php/topic,81987.0.html
Also, as stated at the top of this thread, MC 23 is currently in beta.
There is no obligation to upgrade MC. If you're happy with a particular version you can run that version for ever. If you want to upgrade and help fund the development of future versions of MC you can do that too.
Spike
--- End quote ---
As correctly pointed out in the last post in the thread referred to, this statement from JRiver is now 4 years old!
Also, I remember making my decision to move to MC 22 on the thread 'Plans for MC 22'. Can anyone point me to the thread 'Plans for MC 23'?
Don't get me wrong, I am supporting and will support JRiver with my paid master license and payments for upgrades even if I don't see an immediate use for them in my particular situation (audiophile, audio-only setup without networking). The reason for me to do this is that JRiver has long been the only piece of Windows software that offers the right combination (for me) of a nice GUI (then...) and audophile focus. However, there is a growing number of alternatives now and I guess I would like to see some confirmation that my loyalty pays off. For one, I would like to see at least some interest in updating the user interface ('experience').
MikeO:
Has anybody ever described Agile Development ?
It's about very small incremental changes, features, bug fixes etc. each "Release" is a small move from the last release.
Are you really whining about a paltry $ 20 a year "license" fee. Try some other software with 10 or more times this as an annual fee.
If you did a year on year comparison I am sure 22 and 23 will be very different as a result of the small released improvement
For me $20 is a steal and I am a pensioner ;D
Quality doesn't come free
Mike
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version