INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Windows => Topic started by: Hendrik on July 01, 2015, 08:57:32 am
-
I brought up this discussion internally, but we can only do so much without knowing what you guys think about the topic at hand.
In short, we're trying to evaluate Windows XP support for future MC versions.
There has been a bit of movement in the FFmpeg/Libav camp and it looks like XP support may be dropped on that side eventually, which would mean I would also drop support in LAV and the FFmpeg libraries MC uses for video transcoding.
Additionally, there are a few new features we're thinking about, which would take serious effort to make compatible with Windows XP, mostly because the libraries enabling these features simply do not support XP anymore.
We see two options here:
1) No Video support in future MC versions on Windows XP (among a few small other things)
2) No future MC at all on Windows XP
Personally, I would favor (2), as that is more honest towards the users, while (1) will of course allow running audio-only MC still on XP machines, with a limited feature set, however, which we may need to document somewhere.
So what are the thoughts? Is someone still overly attached to Windows XP, and if so, why? The OS is essentially dead afterall, with no updates anymore, security related or otherwise.
PS:
For the sake of clarity, dropping XP support will also drop support for Server 2003, since that is basically the same OS.
-
Windows XP has 12-14% market share globally, and that's about half what it was a year ago. I would wager that the majority of those are enterprise clients who have been slow to upgrade (significant portions of the government and private sector are still paying for support on XP). You can probably realistically expect that to drop significantly more over the next year after the launch of Win 10 and as various enterprise clients get tired of paying for extended XP support.
That said, given that OS X's market share is about 4.5%, and Linux only 1.5%, XP still probably has enough of a consumer base to make it "worth JRiver's while" to provide limited support for another year until it dips into windows 2000/ME territory (fractions of a percent each), but that's a business calculation/decision for JRiver.
I think anyone running XP at this point should be prepared for things to stop working. I don't run it and haven't for several years, so I don't have any skin in the game, but your option 1) seems like a good compromise in the near term, with a transition to option 2) in a year or two. As an aside, I would bet even money (based entirely on anecdotal evidence from lurking around home audio/theater forums) that far more "audio only" and/or audiophile-type customers are continuing to use XP than are video/TV customers, so option 1) may even be perfectly satisfying to that crowd.
-
+ 2
-
What mwillems said.
-
I would go for option 2. I work for a software company that is global, and I pushed for us to drop XP support. It just makes it too hard to move forward with new technologies. There will always have to be the discussion that 'well, if we do that, will it work on XP'...for the small percentage of users that are using XP with MC, I just don't think it is worth it. If it will only support audio, it would be easy enough for someone to move to Linux on the same hardware they currently have if they don't want to upgrade their OS due to hardware limitations, or even budget.
While it was mentioned that the user base for XP is higher than that for OSX, I would suggest that the difference is that users of OSX are more likely to use a media center app than those that are still using XP.
just my two cents worth.
-
What glynor said.
-
With 4K and 8K video on the way, this basically needs to happen.
I've been testing 4K/8K playback recently, and I can only get smooth playback in 64-bit players.
With 32-bit players only having access to 3GB RAM, I can't buffer enough frames in advance to prevent it from stuttering, and decoding performance seems like it's faster in 64-bit too.
So I'm really hoping that MC21 makes the switch to 64-bit, prior to UHD Blu-rays launching later this year.
And I can think of a few good reasons for the audio engine to move to 64-bit as well.
I don't see much reason to continue supporting XP these days, especially with Windows 10 launching at the end of this month.
Perhaps MC20 could be updated so that MC21+ licenses will still activate it, or MC20 licenses are still available for purchase if anyone does wish to purchase a new copy of MC to run on XP?
That way you still have a "legacy" version that people can buy if they really need to stick with XP for some reason.
Though not exactly the same, we still have a couple of MacBooks in use today which are 32-bit CoreDuo/Core2Duo machines, and those only support up to OS 10.6
It is very frustrating when I'm trying to get software for them and the developer only offers their latest version which requires 10.7+ despite older versions of the program running just fine on 10.6
-
64-bit and XP are not necessarily related.
-
64-bit and XP are not necessarily related.
Well I still think that keeping around a legacy version of MC20 for XP (either continuing to sell MC20 licenses, or letting newer MC21/Master Licenses activate it) rather than hampering the development of MC21 is the way to go.
You say that the new audio features you're looking to develop won't work on XP anyway, so why hold it back?
MC20 is already a very mature and capable product on XP as it is.
-
I'd favor option 2 also. The OS is 13 years old, I think that's enough time.
-
I do use XP on a couple computers because I have work related software that is XP specific and these are niche programs that do not get updated. I do run MC on them but honestly I could care less if it stopped working.
So +1 mwillems and option 2
-
I do use XP on a couple computers because I have work related software that is XP specific and these are niche programs that do not get updated. I do run MC on them but honestly I could care less if it stopped working.
For XP specific stuff, I just run it in a virtual machine (or XP mode if using Windows 7). This is what I actually do right now in VMWare Player on Windows 10.
-
If you wanted to put a stake in the ground, is would not be unreasonable to tell the world that XP support in MC will freeze at the final incremental release of v20.
-
Option 2 - MC20 is the last version to "Officially" support XP. Later versions of MC may run XP but it an unsupported platform and some features may not work.
-
Option 2 also.
I do still have a twelve year old Dell laptop that runs XP, but it is sssllooowww, so if I want to run XP programs, they are run in a VM on Windows 7. Video on an XP PC couldn't work that well, since it would probably be an old machine like mine. Hence, any users are probably just running audio on it.
Option 1 still gives you much of the work, and has other downsides. If users still want to use the hardware XP runs on, they could use the UNIX version, and probably get a better result. Maybe offer then a UNIX licence on a case by case basis, on request.
-
Let me speak up for XP...
There is an inexhaustible supply of old Pc's in the world /family with XP loaded that make perfectly adequate music players and will handle most of the video that casual users would ask of it. They are not worth the time to upgrade to win 10 and likely won't have hardware support in win 10. They add functionality to any flatscreen in the house by accessing your MC server. Or I just run the music from my tablet.
I think of them as free substitutes for the Nuc based PCs that JRiver is selling.
The issue is that all versions of MC must match on the network...
I think the solution would be to tweak the MC server software so that a MC18 to 20 client machine could access what ever current MC server is on the home network. Add in something similar to the master license for the latest and greatest version hooked up to your main system running MC21 etc .... and everyone is happy.
When I try to play a video file that is too much for an old PC..... I shrug and move on. I get it that it is an old box and its purpose is to play music or youtubes in odd places.
It's better then putting it into the landfill!
This way... there is no downside in my staying up to date with the latest MC release.
FYI, loading netframe beyond version 2.0 will interfere with playing higher res video files.
-
You can run Windows 7 on practically any hardware which can run Windows XP, sometimes even more efficiently, FWIW - Windows 10 may be another beast entirely.
Unfortunately, we cannot guarantee infinite forward compatibility with media servers, as that would severely cripple our ability to enhance the functionality.
-
I say go for option 2, for a pure music player MC 20 has enough features, just let that be the final XP-supporting version.
-
You can run Windows 7 on practically any hardware which can run Windows XP, sometimes even more efficiently, FWIW - Windows 10 may be another beast entirely.
Unfortunately, we cannot guarantee infinite forward compatibility with media servers, as that would severely cripple our ability to enhance the functionality.
The official system requirements for Windows 10 are the same as Windows 7, though I don't know how it will run on older systems.
I think it should run faster on supported hardware, because they've focused a lot on getting Windows 8/10 running well on the low-end hardware that's going into tablet devices. (and potentially phones)
But those requirements are considerably higher than XP:- 1 GHz CPU rather than 233 MHz
- 1 GB RAM (32-bit) rather than 64 MB
- 16 GB HDD Space rather than 1.5 GB
So I don't know that Windows 7-10 will be replacing XP on older systems. (and that won't be a free upgrade)
Then again, if those systems have at least a 1GHz CPU, it should be very inexpensive to upgrade them to 2-4 GB RAM these days.
Having Media Server compatibility would be the only issue with keeping MC20 around I suppose, as I could see people running the latest version of MC on their server, but keep around old XP clients.
Are there specific reasons why it wouldn't work, or is it just immediately blacklisted due to the version numbers being different?
Is it possible to design a more forward-thinking Media Server for MC21 to perhaps make that the last version for XP?
-
Option 2. Make MC20 last that supports XP
-
Are there specific reasons why it wouldn't work, or is it just immediately blacklisted due to the version numbers being different?
Its not tied to the MC version directly. The database carries a version number, and media server and client have to be built for the same version.
However, its not a given that this database version is going to be increased. I don't think it actually was increased in MC20, so MC20 should still work with MC19, AFAIK.
We only increase it when breaking changes are introduced, a new datatype for fields, or some other changes which cannot be handled dynamically. The last time I remember it being changed was for the release of MC19.
I do not know if there are plans that may require increasing the version number for MC21. I'm not aware of any myself, but I do not know every single plan on every developers plate. :)
-
Option 2.
As Hendrik mentioned that there is no probable change to the database version in the foreseeable future, a XP machine could still run v20 and talk to a (v21?) MC server.
By the time such a change is needed to the database, XP will have dipped below the radar and it will be a non-issue for almost all users.
Maintaining compatibility with XP has its costs on a (small) development team...
-
You can run Windows 7 on practically any hardware which can run Windows XP, sometimes even more efficiently, FWIW - Windows 10 may be another beast entirely.
Unfortunately, we cannot guarantee infinite forward compatibility with media servers, as that would severely cripple our ability to enhance the functionality.
So I don't know that Windows 7-10 will be replacing XP on older systems. (and that won't be a free upgrade)
Then again, if those systems have at least a 1GHz CPU, it should be very inexpensive to upgrade them to 2-4 GB RAM these days.
Additionally, any computer that could run XP could easily run one of the more user-friendly linux distros in most cases even with the "heavy" desktop environments. Linux may not be everyone's cup of tea as a daily desktop (I don't typically recommend it to non-technical users for daily use), but for light around the house use like mschneid was describing, as a music streaming box/ ID replacer, or as a "screen smartener," Linux works great on old machines and the price is right (free).
I recently repurposed a 2007 Core 2 Duo macbook that was struggling with OSX as a linux box and it runs faster on a modern linux distro with one of the "nice" 3d-accelerated desktop environments than it ever ran on OSX (even when it was new).
So it's not like the options for old secondary boxes are "XP support, buy a new windows license, or landfill." You can also sit through Linux Mint's graphical installer and wind up with a surprisingly snappy windows-like desktop for free on which newer versions of MC will run. Linux isn't for everyone (especially for normal PC use), but for this kind of thing (reclaiming old boxes for special uses) it really shines.
-
Well you guys beat me to it. I was going to say have one last XP build and make it available for the next few years.
Regarding the server changes: Couldn't users of XP map the server's drives locally and have their own library? Sure that would loose some features but you could keep on running those XP machines if you're stubborn.
-
For the record: MC19 does still work fine with MC20's servers. I did it this morning.
Also, I said +1 to mwillems, but I really meant the general idea. I disagree somewhat on his market share analysis, but the central point holds. If supporting XP in audio-only mode is basically very-low or zero pain, do that. Otherwise, I'd say kick it to the curb.
By the way, if anyone reading this is using XP still on a machine connected to the Internet, you're asking for trouble. So, you shouldn't be updating to new versions of software anyway, at least not via the Interwebs.
-
For those that insist on keeping XP running AND Internet connected :
http://betanews.com/2014/05/26/how-to-continue-getting-free-security-updates-for-windows-xp-until-2019/
Lots of ATM bank machines are XP based : "The workaround makes use of updates for Windows Embedded Industry (formerly known as Windows Embedded POSReady)".
Personally, I have no use for this as Ì am Win8.1/Server2012R2/Linux based...
Edit : Obviously, such a workaround is not 100% legit, as your purchase of XP has never bought such an extended support !
-
Also, I said +1 to mwillems, but I really meant the general idea. I disagree somewhat on his market share analysis, but the central point holds. If supporting XP in audio-only mode is basically very-low or zero pain, do that. Otherwise, I'd say kick it to the curb.
Yeah any metric for market share will be imperfect. I was looking at a few different sources based on browser and search engine stats, which are a relatively good proxy for consumer use because they're (typically) not just machines running in a rack somewhere, they're (mostly) machines used by people. But I'll concede the numbers are at best approximate, although a few major sources of web analytics and Gartner seem to agree within a few percentage points. The most pessimistic XP estimate I've seen is 6.48% from statcounter, and that's still larger than the most optimistic OSX estimates I've seen.
Even conceding some static in the data, based on the available data the current installed base of machines browsing the web and running searches on Win XP is very likely to be larger than the same installed base for OSX and linux combined, and may be as much as twice as large. Whether those machines are mostly "work" machines unlikely to be running MC or not is a question I lack data to speculate about, but I thought these were useful data points for the discussion.
Like I said above, people running XP should expect things to break, and if support vanished tomorrow, I wouldn't shed a tear. There just may still be a significant number of XP users out there in the market. I can't readily calculate the juice/squeeze coefficient ;D
-
I didn't mean whether the market numbers were correct (I think those browser based stats are fundamentally flawed, but that's another story), I meant whether they're relevant at all.
All computer users are not equal. Apple may have an overall low percentage of total computers, but they have nearly 100% of expensive computers (at least in the US, and growing quickly elsewhere). They're also the only vendor still growing share, and not declining y/y.
Is a customer who is willing to spend $2k on a laptop the same as someone who buys the cheapest possible $150 laptop from Best Buy? Are both equally likely to spend $50 on a premium media management application? What about someone who still runs XP on a 7 year old machine?
But, that's all a sideshow. Like I said, the overall concept, I agree. Worth keeping around in audio-only format? Sure, if it isn't too hard and doesn't cause other issues. Worth spending a bunch of effort on and/or holding back progress for modern OSes? Heck no.
Also, for the record, I'd recommend dropping 10.6.8 with MC21 as well.
-
No mention here of the $$ aspect.
I don't upgrade my XP and Vista machines to Windows 7 simply because the upgrades would cost significant money.
I have XP and Vista machines, because - other than 1080p playback - there has not been any compelling new features that require any of the faster hardware.
So, instead of buying new $399 laptops that will break in months and are poorly designed, instead I use $3000 laptops that have reached the end of 3 or 4 year accounting depreciation cycles, all the while sitting unused in the office of someone who primarlly uses their phone.
When they wear out, I replace them with the latest 4 year old laptops.
Some of the old ones still work and perform tasks. I have a Thinkpad T41 that is new looking - but its audio playback chip died, so I now use it as a DVR running MC20 and a Hauppauge USB TV tuner.
It records to a 3TB drive on my router which can then be accessed by the Home Theater PC. It runs Windows XP.
So TV recording is another use besides audio and video. If I had to stay on MC20, I would miss any fix or feature that Yaobing implemented.
Asking a bunch of techies who have Windows 10 on all their machines, whether or not to drop support for Windows XP, is like going to the Wednesday night Chess Club and asking:
" So is there anyone here who cannot make it on Wednesday nights ? "
-
Keep in mind that XP is 14 years old next month, not 3 or 4, and extended support ended more than a year ago.
I am all for keeping older machines in service, but at some point things become obsolete.
-
Keep in mind that XP is 14 years old next month, not 3 or 4, and extended support ended more than a year ago.
I am all for keeping older machines in service, but at some point things become obsolete.
7 years:
Windows XP Service Pack 3 (SP3) was released to manufacturing on April 21, 2008.
The point was that it is only obsolete to techies.
A good 14 year old laptop - Thinkpad T22 - can do everything that an end consumer wants to do - browse the web, send 140 character text messages, listen to music, etc. - with the sole exception of HD video.
In fact, a top-of-the-line smartphone from 5 years ago has the same specs as the T22.
Web sites are continually simplifying in order to be more smartphone friendly, not becoming more complex.
-
An update to the OS doesn't update its age, really. The tech its based on is still 14 years old, which is the reason we're even thinking about removing support.
We and other developers don't just do it out of spite (although some might), but for actual technical reasons. Using some modern features of newer Windows versions becomes a serious problem when you have to consider XP support at every corner, while the number of people using XP is very small as it is, and shrinking every day. The feature difference between XP and Vista is huge.
Its just a matter of resources. If we had infinite resources, we could support XP infinitely. But at some point we just have to ask ourselves .. how much effort do we put into supporting this in the future? What if software libraries we use stop supporting XP, like FFmpeg/Libav for the video functionality, do we spent hours and hours on trying to restore XP functionality, or do we accept XP's fate and move on to actual new features? Or even worse, we want to support new fancy features, but making it so that it works on XP (or at least doesn't break anything) would be a huge undertaking?
If we don't do it for MC21, chances are much higher that we do it for MC22. The thing is that it might cost a lot of time to keep it supported, especially when thinking about a few new features, so I'm not sure what will happen yet.
Should we drag it out another year? We don't know yet, which is why we're asking peoples opinions here to make an informed decision. Personally, I would rather not, as it may impede additions of new features, which would be a shame.
-
Put a bullet in its brain. You sell a linux version, right? Ubuntu + MC for linux should cover the old hardware.
-
Time to move on.
Give XP the axe.
Go all the way with option 2.
-
XP is well old now, more than a couple of years, I don't think anyone would blame you for dropping support. I would suggest not working hard to make new fetures compatible, in other words as soon as you want to introduce something that is not global across all versions of Windows then that would be the time to say we no longer support XP as of MC v2x Build yy, no point in dropping it if there is no actual reason for it and there are no immediate plans to introduce a new feature that won't work on it. But you might want to make a clean break as it were so that everyone knows what the cut off point is going to be and cut it off at the beginning of a new MC release cycle. I have an XP machine which is still quite a capable machine and I have an installation of MC on it purely for dev and testing purposes, but I wouldn't shed a tear if I could no longer run MC on it. Due to a quirk of Shuttle's BIOS the Windows 7 and 8 installation programs won't run, well known problem with the Shuttle XPCs of mid 2000s, they are fully capable of running 7 but the installation media hangs due to something weird in the BIOS. What really hurt though was JRemote's dropping of iOS5.1 after only 2 years for no apparent reason other than a new flat look for the icons...
-
We wouldn't want to cut support in the middle of versions life-cycle, so we have to plan a bit ahead, or get stuck mid-way and have to either postpone changes or spent a lot of time working around the problems.
So here we are thinking ahead for MC21.
The issue with some of the problems we're facing is that it might disable the entire video functionality on XP, and working around this may be quite an undertaking, which spawned this inquiry in the first place. Not an arbitrary idea, but planning ahead.
-
We wouldn't want to cut support in the middle of versions life-cycle, so we have to plan a bit ahead, or get stuck mid-way and have to either postpone changes or spent a lot of time working around the problems.
So here we are thinking ahead for MC21.
The issue with some of the problems we're facing is that it might disable the entire video functionality on XP, and working around this may be quite an undertaking, which spawned this inquiry in the first place. Not an arbitrary idea, but planning ahead.
Just talking about my own particular situation:
As I mentioned, the one big technological improvement over the past 14 years has been video playback (and video screen hardware).
So, I myself am not using MC20 for video playback on any XP machine, and the one thing that I do regularly improve is graphic cards and video screens (and the Home Theater PC hardware as a whole).
I think it is safe to say that the sort of person who uses MediaCenter on old computers running XP, is likely doing Audio Only (cf "MediaJukebox") or perhaps TV recording.
So, if you say " we are going to stop supporting video functionality on Windows XP in MC21 " (your option 1), that would be fair, as it is unlikely to impact very many people.
And, BTW, I consider it very silly that you are asking people who have stopped using XP to give feedback on whether to support XP.
-
That's, by no means, the main technical benefit to Vista and newer. But, I think we get your vote.
-
And, BTW, I consider it very silly that you are asking people who have stopped using XP to give feedback on whether to support XP.
We were trying to ask everyone.
-
We were trying to ask everyone.
And in shocking news, Tesla owners think that petrol engines should no longer be supported:
http://teslaclubsweden.se/test-drive-of-a-petrol-car/
-
If you don't already collect the data, I'm sure you could determine which systems are using XP every time they use an Access Key, and hence the numbers and proportions.
Of course that would not identify all XP users, only those that are using an Access Key. Plus of course, privacy laws would probably prevent you from contacting those users to get their opinion . . .
-
And in shocking news, Tesla owners think that petrol engines should no longer be supported:
http://teslaclubsweden.se/test-drive-of-a-petrol-car/
This is the public MC forum, not the Windows 10 users club, so I really don't get where you are going with these comments.
No matter which Windows version you are using, you can visit this forum. :p
-
I'm sticking by my suggestion of:
"As of MC21, Windows XP is no longer officially supported and there may be features of MC that will not work on this version of Windows."
I'd not code MC21 to prevent it from running on XP... I'd just not test, fix, or respond to issues with with MC running MC on XP from MC21 onwards. If it happens to continue working great. If it fails so be it.
-
I don't think that's very fair towards new customers.
Sure, people that are updating from MC20 that follow the forums and have read this will be aware that it may be compromised on XP, but new customers probably won't. Just look at how many people bought into MC on the Mac without knowing that it (previously) lacked any kind of video playback, theater view etc. They just assumed it had parity with the Windows version.
Better to just say that MC20 is the last version which supports XP, and keep it available for anyone that wants it. (and that includes supporting files such as the versions of LAV Filters, madVR etc. that it will download)
Ideally buying a new license for MC21+ would still be able to activate MC20 for anyone that wants to buy a copy to run on XP.
-
I don't think that's very fair towards new customers.
Sure, people that are updating from MC20 that follow the forums and have read this will be aware that it may be compromised on XP, but new customers probably won't. Just look at how many people bought into MC on the Mac without knowing that it (previously) lacked any kind of video playback, theater view etc. They just assumed it had parity with the Windows version.
Better to just say that MC20 is the last version which supports XP, and keep it available for anyone that wants it. (and that includes supporting files such as the versions of LAV Filters, madVR etc. that it will download)
Ideally buying a new license for MC21+ would still be able to activate MC20 for anyone that wants to buy a copy to run on XP.
The first point is quickly answered with it's up to the buyer to inform themselves and JRiver offers a 30 day trial. If a new Mac for MC user couldn't work out video shortcomings in 30 days ... (Well, politeness stops me from filling that one in).
Regarding axing XP, agree with dropping it off the "on purpose" compatibility maintenance list from MC21. I think the crew at JRiver have enough to deal with. If the plan is to ensure audio compatibility - fine. However, I would expect that most new users wouldn't be stuck in the OS past.
How about keeping MC20 on offer for a version or two at a reduced price for the luddites?
-
I don't think that's very fair towards new customers. Sure, people that are updating from MC20 that follow the forums and have read this will be aware that it may be compromised on XP ...
We offer a 30 day trial of the full version. That seems fair to me.
Let's try to keep this on topic. Is full XP support important or not? I think it's clear from the comments above that it's of only very minor interest at this time, and it's going away steadily.
-
I'm sticking by my suggestion of:
"As of MC21, Windows XP is no longer officially supported and there may be features of MC that will not work on this version of Windows."
I'd not code MC21 to prevent it from running on XP... I'd just not test, fix, or respond to issues with with MC running MC on XP from MC21 onwards. If it happens to continue working great. If it fails so be it.
I agree.
-
Another thought is how many people will be buying MC for the first time to use on XP? Probably not many.
I would like better performance and and new features out of any future version of MC that I purchase. Keep MC20 available and keep moving forward.
-
Option 2. Bring on the new features.
-
We offer a 30 day trial of the full version. That seems fair to me.
Let's try to keep this on topic. Is full XP support important or not? I think it's clear from the comments above that it's of only very minor interest at this time, and it's going away steadily.
Jim, I think you should try to get a handle on how many XP users you have now. Most of the comments here have been from techie types who buried XP long ago. Since they aren't XP users now, they aren't the people whose opinions really matter.
Kstuart and mschneid are offering some ideas that fit the remaining users of XP. Here's some thoughts that I think might be in an XP users mind:
- old PC, not worth spending money on.
- It runs and I don't want to disturb anything.
- I own it, it's free and I'd like to get some use out of it.
- As long as this old PC does what I need, I don't want to spend money on a replacement.
- Got NO money to spend on computers.
I doubt that installing Linux is a reasonable step for most XP users. I doubt that spending money on a Windows upgrade is attractive either.
Find a way to get info from your XP users. I think they would be happy to keep using MC with the current feature set as long as they keep the XP PC going. These people aren't expecting wonderful new features; they just want to keep using MC as it is now.
For the record, we've been off XP for a couple of years in our home.
-
I think they would be happy to keep using MC with the current feature set as long as they keep the XP PC going. These people aren't expecting wonderful new features; they just want to keep using MC as it is now.
MC20 isn't going to break tomorrow, so you can always do that!
-
Personally, I believe that XP needs to be put to rest. It had its time, but I can see no reason to actively support it in the future, especially when it makes development suffer. By the same argument that keeps XP alive, we should also still support Windows 200, ME, NT, 98, ... because we should still have supported them a few years back, and some people use them.
I understand the argument that these (very) old machines some people use to play music can only run XP, but if people themselves cannot install a Linux distribution on them, then certainly they know someone who can help them (it's rather easy, though that may be biased). Also, it has been suggested that the Media Server may well continue working between 20 and 21, at least for a while...
-
- old PC, not worth spending money on.
- It runs and I don't want to disturb anything.
- I own it, it's free and I'd like to get some use out of it.
- As long as this old PC does what I need, I don't want to spend money on a replacement.
- Got NO money to spend on computers.
But yet, it is the end of the world that they can't buy the upgrade to MC21?
I'm confused. Do they have money to spend on software upgrades, or don't they?
-
But yet, it is the end of the world that they can't buy the upgrade to MC21?
I'm confused. Do they have money to spend on software upgrades, or don't they?
That's what I was wondering.
Are the people that are unable/unwilling to spend the money to upgrade from XP likely to upgrade MC?
With the people sticking to old software/hardware because it's what they know and "if it's not broken, don't touch it" rather than being in a position where they can't afford to upgrade the software/hardware, isn't that attitude likely to carry over to MC as well?
-
XP could be on 2nd, 3rd or even 4th computer... Primary PC is which they have invested and to which they have updated MC also. That said I agree that it isn't sensible any more to take XP into account when specifying new features.
-
But yet, it is the end of the world that they can't buy the upgrade to MC21?
I'm confused. Do they have money to spend on software upgrades, or don't they?
end of the world if they can't buy MC 21: I don't see that this relates to anything that I said. It is usually much cheaper to get business from existing customers than to acquire new customers. Checking with XP based customers before you cut them loose might be prudent. If few are expecting to upgrade MC further on an XP computer, JRiver is free to go ahead. (See the sample message beloew.) However, if a significant number are expecting to continue to be able to upgrade on XP computers, JRiver may want to modify its plans.
money for upgrades: Some have the money and some don't. Outside the world of computer techies, people don't look forward to spending money on computer hardware or software. However, when something breaks, their priorities change.
willingness to upgrade: Outside the techie world, people often use the same OS on a PC until they replace the hardware. However, during the life of a PC, an MC user might upgrade MC several times. It is (usually) straightforward to do so compared to an OS upgrade.
JimH would not have asked the question in the OP if he felt that JRiver no longer had customers using XP or might get new customers who used XP. The thread had lots of pronouncements by techies who didn't seem to have any empathy for XP users. I tried to get a different point of view into the thread. I listed some thoughts that might be in an XP users' mind. I don't expect that every XP user would have all of these thoughts.
At the beginning of my post, I said that JRiver should be getting feedback from XP users. JRiver should try to get information from and about real MC users on Windows XP before planning the end of support for MC on XP. That would be a prudent step.
JRiver may find that XP users are not likely to yield much upgrade business until their PC running XP gives up the ghost. However, that will probably happen in one to three years. At that point, those users will be buying a new PC with a recent version of Windows and installing software. They might be quite receptive to an MC upgrade then. (Or an ID.)
I could imagine that JRiver might announce the change in support with a positive email like this:
"As we develop MC 2x for Windows, we will be using features that are not available under Windows XP. MC2x will not work fully under XP. We recommend that you continue using MC2x-1 on computers running XP. When you are ready to move to a later version of Windows (7,8 or 10), consider upgrading to the current version of MC."
-
Checking with XP based customers before you cut them loose might be prudent.
I believe that is exactly the point of this thread.
I don't see a ton of people coming out of the woodwork saying "I run XP on my primary machine and I'd like to pay for the next version of MC on it." Those are the only answers that matter, really.
Are there more out there, just holding back for some reason?
Now, certainly Interact doesn't reach everyone. But there is no perfect way to reach everyone. A mass mailing might generate a few more responses, but (1) I think they were trying this first, (2) that comes with a huge set of problems, and (3) response rates for mass mailings like this are usually somewhat dismal.
They were trying to gauge the reaction. So far, I see a few people, but many of the responses have been somewhat ambiguous as well (not my primary machine, I'm guessing others feel like X, etc, etc). Certainly no groundswell of opposition to the idea.
-
I don't see a ton of people coming out of the woodwork saying "I run XP on my primary machine and I'd like to pay for the next version of MC on it." Those are the only answers that matter, really.
huh....
.... It's the 4th pc in house... Its not worth the time to upgrade it... even when the cost is only time. not to mention the cost of a unix mc license. ... So, when MC upgrades and the trial version of the latest version won't access my music library... that will freeze my MC upgrade path
untill a) I absolutely want a new feature or b)... the xp machine dies and I consider upgrading. The issue for me is strictly the library version compatibility.
I must admit... I really am a primary audio user... MC nailed that market a long time ago.... Upgrades are really to satisfy curiosity and support the effort... So... chances are old Pc's will die off before this becomes an issue. MC will just need to clearly label the compatibility pathways. As long as the tradeoffs are clear to me... I have no problems with MC moving onwards.
-
This is the public MC forum, not the Windows 10 users club, so I really don't get where you are going with these comments.
No matter which Windows version you are using, you can visit this forum. :p
But if you are visiting this Forum, you are less likely to be running XP.
Just as a frequent participant in "Supercar Enthusiast Forum" is unlikely to be driving an 1985 Honda Civic.
To get feedback from XP users, send an email (something that JRiver already does from time to time).
-
But if you are visiting this Forum, you are less likely to be running XP.
I don't think you can be sure of that. Remember that people visit the forum in order to learn about MC.
-
I'm sticking by my suggestion of:
"As of MC21, Windows XP is no longer officially supported and there may be features of MC that will not work on this version of Windows."
I'd not code MC21 to prevent it from running on XP... I'd just not test, fix, or respond to issues with with MC running MC on XP from MC21 onwards. If it happens to continue working great. If it fails so be it.
Something to keep in mind though: If someone who uses XP uses the MC21 trial version, buys the product, then finds bugs 6 months later only to be told "XP isn't supported". They are not going to be happy. At the very least there should be a warning when running on XP for the first time etc....
-
>:( What bugs me is that I have already paid for MC21 and now because I am only finding this thread today I am learning that it may not work on my computers. >:(
All this talk about XP being dead is bull. The market share figures are pure Microsoft propaganda. The UK government pays Microsoft a fortune to continue using XP, as does the US Navy, etc. etc. Why? Because they do not want to spend a fortune investing in new hardware, and because in many ways XP is more of a business-oriented OS, certainly more than Windows 8 or 10, and in some ways more than Windows 7.
If "upgrading my computer" were merely a matter of spending several thousand dollars on hardware and the current MS Office suite, then migrating my data, that would be painful but acceptable. However I am, among other things, a composer, and I have a great deal of customized software I use in that connection. Bringing a Windows 10 computer up to speed so that I can function would take weeks, and I know for a fact that much of my customized software will not work in Windows 10. Unless most people, probably, I spend less than 50% of my time working (and for me my computer is basically a work device) on software made by Microsoft. And again, I know that much (most) of the software I work with will not work on the new versions of NT (which, in case anyone loses sight of this, are all Vista, 7, 8 and 10 are -- repackaged versions of NT, the last "new" operating system Microsoft developed).
For the record I would like to see MC 21 (not MC 20) as a version of MC that is fully compatible with XP, and after that JRiver can do whatever it likes.
;D And hey, guys: I was going to clear time to do the MC21 upgrade within the next couple of days, so please let me know pretty soon so that I don't waste my time and find myself messing up my media libraries.
-
>:( What bugs me is that I have already paid for MC21 and now because I am only finding this thread today I am learning that it may not work on my computers. >:(
All this talk about XP being dead is bull. The market share figures are pure Microsoft propaganda. The UK government pays Microsoft a fortune to continue using XP, as does the US Navy, etc. etc. Why? Because they do not want to spend a fortune investing in new hardware, and because in many ways XP is more of a business-oriented OS, certainly more than Windows 8 or 10, and in some ways more than Windows 7.
If "upgrading my computer" were merely a matter of spending several thousand dollars on hardware and the current MS Office suite, then migrating my data, that would be painful but acceptable. However I am, among other things, a composer, and I have a great deal of customized software I use in that connection. Bringing a Windows 10 computer up to speed so that I can function would take weeks, and I know for a fact that much of my customized software will not work in Windows 10. Unless most people, probably, I spend less than 50% of my time working (and for me my computer is basically a work device) on software made by Microsoft. And again, I know that much (most) of the software I work with will not work on the new versions of NT (which, in case anyone loses sight of this, are all Vista, 7, 8 and 10 are -- repackaged versions of NT, the last "new" operating system Microsoft developed).
For the record I would like to see MC 21 (not MC 20) as a version of MC that is fully compatible with XP, and after that JRiver can do whatever it likes.
;D And hey, guys: I was going to clear time to do the MC21 upgrade within the next couple of days, so please let me know pretty soon so that I don't waste my time and find myself messing up my media libraries.
I would recommend installing Windows 7 and using XP mode for Windows Virtual PC. That way you can run software that is dropping support for XP alongside your tried and true XP music programs seamlessly.
-
All this talk about XP being dead is bull. The market share figures are pure Microsoft propaganda. The UK government pays Microsoft a fortune to continue using XP, as does the US Navy, etc. etc. Why? Because they do not want to spend a fortune investing in new hardware, and because in many ways XP is more of a business-oriented OS, certainly more than Windows 8 or 10, and in some ways more than Windows 7.
I don't think any argument that relies on the UK Govt approach to technology is one that is worth making :D
Unfortunately you'll have to accept that XP, as a consumer OS, is dead and that you will end up needing to migrate. It would be wise to work on that strategy now before it is forced upon you, always good to have options after all :)
-
For correctness, Windows XP is based on the NT kernel. Also, an operating system is a lot more than just the kernel.
As far as software companies go, Microsoft is one of the better ones in the area of backwards compatibility and support. They provided security patches to XP for many, many years. Windows has provided various compatibility modes to run old apps. The newest Office still opens ancient Office documents.
Unfortunately, for many, Microsoft is moving on. It's too costly and limits moving forward. I don't think you'll find anything from Google, Apple, or the UNIX/Linux community that is better for LTS. Can't blame JRiver for doing the same, although it should be clear to anyone upgrading before paying (if it isn't).
-tm
-
Beside using XP Mode as was suggested earlier, there is also a compatibility dropdown on the properties for each program. This often helps if there is an issue. You choose the OS you need to be compatible with - has worked well the rare time I've needed it. I only ever used XP mode for a hardware driver for an old large scanner I sometimes needed).
Your biggest issues in using Win10 (I skipped 8.x) will be ensuring you have drivers for audio, wireless, etc.
I imagine any software you are using as a composer is also going through or has gone through an upgrade cycle (or several) for the latest OS's.
That said I still use an old Win 95 laptop to control a MIDI rig I have. But I would never expect it to do anything new. It's an old spare and runs the old programs. But it is really ancilliary to making music.
(Plus all this upgrade business is why I bought LOTS of hardware/outboard gear in the late '90's when everyone else went computerized. I got great equipment at a good price and it doesn't get obsolete). ;)
-
I don't see how one can expect a 3rd party to support a platform that the first party no longer provides meaningful support for. In some ways it's asking JRiver to assume those support costs themselves- some governments are willing to pay a fortune (using your dollars, btw) to sit on an old platform- is that a cost you are willing to bear yourself should JRiver pass that expense on to you?
And as a side note- as someone who works in IT in a large enterprise Windows 10 has many features that make it much better for the enterprise over Windows XP. The management capabilities are greatly expanded.