I'm not going to renew my subscription for Sonar Platinum until I see some Windows 10 drivers for my V-studio 20. Heck, this is a hardware device I bought specifically from Cakewalk, for Sonar, just a few years back, and Cakewalk isn't keeping the product drivers current? I am currently not even able to use the V-studio now because I have Windows 10. Inexcusable, Cakewalk!!  You guys oughta be ashamed!!! 

The V-studio series was created by Roland when they owned Cakewalk.  Even if Cakewalk could create Win10 drivers for it, they probably wouldn't be allowed to.
Check the Roland site (or other similar threads here) for current drivers/workarounds.

There are workarounds to get your product working with Windows 10.
I am using the VS 700 system myself on Windows 10.

Not renewing your subscription will make the company go bankrupt (excuse the sarcasm)  :-)

frimpitsky
I'm not going to renew my subscription for Sonar Platinum until I see some Windows 10 drivers for my V-studio 20. Heck, this is a hardware device I bought specifically from Cakewalk, for Sonar, just a few years back, and Cakewalk isn't keeping the product drivers current? I am currently not even able to use the V-studio now because I have Windows 10. Inexcusable, Cakewalk!!  You guys oughta be ashamed!!! 

Follow the instructions in this thread http://forum.cakewalk.com/FindPost/3267234 and you will get it working.  I know because I got my friends V20-Studio working under win 10 by following the information provided in that thread.

In answer to your unnecessary rant.

Roland made the hardware not Cakewalk, Cakewalk have nothing to be ashamed about.
 
Roland provided the Driver Not Cakewalk, again Cakewalk have nothing to be ashamed about.  
 
On the other hand I  do believe that Roland's actions are questionable and perhaps they should be very very very ashamed.

But how many hardware companies are there that just drop support for a product that is only a few years old but works perfectly if only for a driver.

Wookiee
But how many hardware companies are there that just drop support for a product that is only a few years old but works perfectly if only for a driver.

Is that rhetorical or do you want the full list?

Just because this "dropping the ball" on drivers phenomenon is quite common doesn't make my rant "unnecessary". And the whole "blame game" on Roland is bologna, because when my actual piece of hardware says CAKEWALK on it (yes, "Cakewalk by Roland") that means that Cakewalk was making an additional statement of their support of that hardware by having their name stamped on it. I don't think it'd start WW3 for Cakewalk to call up Roland and ask for a driver to be written, even if it's going to cost Cakewalk money. Hell, with all the thousands of dollars I've paid to Cakewalk for software over the years (and I'm sure I'm not the only one), you'd think it'd be important to Cakewalk to invest in long term customers by going the extra mile and pulling a few strings to keep the hardware they sell viable for at least a few years. Companies who partner need to see potential ties being severed at some point and, at the very least, make working contracts which ensure customer support for hardware for a reasonable amount of years. That's simply good business. The V-Studio 20 was released in March of 2010. Six years is not an unthinkable period to expect driver support for a product, especially when the product was available for sale for several years after that. Remember, I myself, and I'm sure quite a few others, did not buy the v-studio 20 and then look for software to run it with. We were long term Cakewalk Customers who bought a new device to use with SONAR, and a device that was advertised and sold by Cakewalk itself.  Now, does Roland suck too for doing this? Absolutely. And as far as the bankruptcy comment, well, my guess is I'm not the only person who purchased the v-studio 20 who feels this way. The software business is getting harder and harder and it never pays to piss off customers.

Karyn

Wookiee
But how many hardware companies are there that just drop support for a product that is only a few years old but works perfectly if only for a driver.

Is that rhetorical or do you want the full list?

I think you know Karyn, but list away if you want I will start the list for you if you like

1. Focusrite Saffire Pro 26i/o the original model.

frimpitsky
 

Just because this "dropping the ball" on drivers phenomenon is quite common doesn't make my rant "unnecessary". And the whole "blame game" on Roland is bologna, because when my actual piece of hardware says CAKEWALK on it (yes, "Cakewalk by Roland") that means that Cakewalk was making an additional statement of their support of that hardware by having their name stamped on it. I don't think it'd start WW3 for Cakewalk to call up Roland and ask for a driver to be written, even if it's going to cost Cakewalk money. Hell, with all the thousands of dollars I've paid to Cakewalk for software over the years (and I'm sure I'm not the only one), you'd think it'd be important to Cakewalk to invest in long term customers by going the extra mile and pulling a few strings to keep the hardware they sell viable for at least a few years. Companies who partner need to see potential ties being severed at some point and, at the very least, make working contracts which ensure customer support for hardware for a reasonable amount of years. That's simply good business. The V-Studio 20 was released in March of 2010. Six years is not an unthinkable period to expect driver support for a product, especially when the product was available for sale for several years after that. Remember, I myself, and I'm sure quite a few others, did not buy the v-studio 20 and then look for software to run it with. We were long term Cakewalk Customers who bought a new device to use with SONAR, and a device that was advertised and sold by Cakewalk itself.  Now, does Roland suck too for doing this? Absolutely. And as far as the bankruptcy comment, well, my guess is I'm not the only person who purchased the v-studio 20 who feels this way. The software business is getting harder and harder and it never pays to piss off customers.
 

 
I hear you and feel your frustration as I note above I have a perfectly good Saffire Pro I can not use under windows 10, for two reason, Focusrite does not supply a driver for Win 10 and Microsoft have not included Legacy Firewire support.

But try as suggested here I know it will work

Follow the instructions in this thread http://forum.cakewalk.com/FindPost/3267234 and you will get it working. 
If you do not understand how then PM me and I will see what I can do to help.

frimpitskyJust because this "dropping the ball" on drivers phenomenon is quite common doesn't make my rant "unnecessary". And the whole "blame game" on Roland is bologna, because when my actual piece of hardware says CAKEWALK on it (yes, "Cakewalk by Roland") that means that Cakewalk was making an additional statement of their support of that hardware by having their name stamped on it. I don't think it'd start WW3 for Cakewalk to call up Roland and ask for a driver to be written, even if it's going to cost Cakewalk money. Hell, with all the thousands of dollars I've paid to Cakewalk for software over the years (and I'm sure I'm not the only one), you'd think it'd be important to Cakewalk to invest in long term customers by going the extra mile and pulling a few strings to keep the hardware they sell viable for at least a few years. Companies who partner need to see potential ties being severed at some point and, at the very least, make working contracts which ensure customer support for hardware for a reasonable amount of years. That's simply good business. The V-Studio 20 was released in March of 2010. Six years is not an unthinkable period to expect driver support for a product, especially when the product was available for sale for several years after that. Remember, I myself, and I'm sure quite a few others, did not buy the v-studio 20 and then look for software to run it with. We were long term Cakewalk Customers who bought a new device to use with SONAR, and a device that was advertised and sold by Cakewalk itself.  Now, does Roland suck too for doing this? Absolutely. And as far as the bankruptcy comment, well, my guess is I'm not the only person who purchased the v-studio 20 who feels this way. The software business is getting harder and harder and it never pays to piss off customers.

Really? You're blaming the wrong person here. Cakewalk doesn't do hardware. They are a software company who happened to be owned by Roland at the time and they thought it was a good idea to release hardware that worked specifically with the product they at the time owned. Cakewalk had very little to do with the hardware. If you want to post the blame somewhere, it needs to be on Roland. Many of us have been pushing for new drivers since Windows 10 came out. Hell, we had to push for Windows 8 drivers as well because Roland was uninterested in doing anything but sitting on their own thumbs which is still the case now as the only drivers they have released for the V-Studio for Win10 was for the VS-100.
 
If you want to complain to someone about it, complain to Roland. Send them emails, contact their executives, make yourself be heard to the people who can actually do something about it because something tells me Roland and Cakewalk left on not-so-good terms and they could care less about each other.
 
Frankly, you bought the cheapest interface out of all of them. If anyone has a right to be pissed off it's those of us who dumped THOUSANDS into the VS-700 which they now refuse to support. None of us are blaming Cakewalk for this as it's not their fault; you shouldn't be either.

frimpitsky
Just because this "dropping the ball" on drivers phenomenon is quite common doesn't make my rant "unnecessary". And the whole "blame game" on Roland is bologna, because when my actual piece of hardware says CAKEWALK on it (yes, "Cakewalk by Roland") that means that Cakewalk was making an additional statement of their support of that hardware by having their name stamped on it. I don't think it'd start WW3 for Cakewalk to call up Roland and ask for a driver to be written, even if it's going to cost Cakewalk money. Hell, with all the thousands of dollars I've paid to Cakewalk for software over the years (and I'm sure I'm not the only one), you'd think it'd be important to Cakewalk to invest in long term customers by going the extra mile and pulling a few strings to keep the hardware they sell viable for at least a few years. Companies who partner need to see potential ties being severed at some point and, at the very least, make working contracts which ensure customer support for hardware for a reasonable amount of years. That's simply good business. The V-Studio 20 was released in March of 2010. Six years is not an unthinkable period to expect driver support for a product, especially when the product was available for sale for several years after that. Remember, I myself, and I'm sure quite a few others, did not buy the v-studio 20 and then look for software to run it with. We were long term Cakewalk Customers who bought a new device to use with SONAR, and a device that was advertised and sold by Cakewalk itself.  Now, does Roland suck too for doing this? Absolutely. And as far as the bankruptcy comment, well, my guess is I'm not the only person who purchased the v-studio 20 who feels this way. The software business is getting harder and harder and it never pays to piss off customers.

It's time for a reality check. I understand your frustration, but you paint a picture that implies the solution is simple - just have Cakewalk call up Roland, or spend a few bucks. This is naive.
 
The VS-series products were designed, engineered, and manufactured by Roland. They are based around Roland's proprietary intellectual property, including custom hardware which was also designed, engineered, and manufactured by Roland. Although Gibson and Roland are on good terms, one never knows when winds will shift, and it's not prudent to give your proprietary technology to a company that may someday be a competitor.
 
If you read the EULA for virtually any software, there are constraints against reverse engineering. There are also non-disclosure agreements in place at companies. Unless the relationship between Cakewalk and Roland was extremely unusual, Cakewalk cannot reverse-engine Roland's software (not that Cakewalk's software expertise is drivers; that's a whole other type of code), nor solicit the IP behind those drivers. Those drivers no doubt touch on elements that Roland considers proprietary. So if Roland isn't going to write drivers, and Cakewalk doesn't have the expertise to write drivers, then Cakewalk would have to hire some third party and it would be even less likely that Roland would want to expose their IP.
 
As to the idea that it's Cakewalk's responsibility to cover the expenses of Roland developing drivers, that too is unrealisitic. Resources Cakewalk devotes to fixing another company's product diverts resources from supporting customers of products that are actually made by Cakewalk. Sure, Cakewalk could probably fire a bunch of people in support, and pay Roland to develop drivers for a product from six years ago not made by Cakewalk, and when Cakewalk was under different ownership. That does not benefit the people who want Cakewalk support for Cakewalk products that they are using right now.
 

frimpitskyCompanies who partner need to see potential ties being severed at some point and, at the very least, make working contracts which ensure customer support for hardware for a reasonable amount of years. That's simply good business.

 
Roland purchased Cakewalk, not the other way around. Therefore it was up to Roland to dictate the terms of what happens with their intellectual property; Cakewalk was in no position to demand that Roland support complementary software, or operating systems made by neither Roland nor Cakewalk, for "x" number of years.
 
Finally you're overlooking another reality, which is you can get the V-series hardware working under Windows 10. In fact it was people at Roland who described a workaround for getting the V-Studio to work with Windows 10.

TerraSin, quit being silly. What I am suggesting would actually help CAKEWALK in the long term, unless they are ABSOLUTELY CERTAIN they will NEVER AGAIN sell hardware. It would benefit CAKEWALK to BEG Roland for those driver rewrites, or hire someone themselves to rewrite the drivers and pay them to do it. Roland is a mega millions corporation and, as huge pricks as they apparently are, they stand almost nothing to lose by not rewriting a driver for an updated operating system. Cakewalk, on the other hand, is a far smaller company who obviously needs some sort of parent company to even stay afloat. Now they are owned by Gibson, and if Gibson sells some sort of hardware through the Cakewalk website, are you going to buy it? Something tells me your answer would be a resounding "NO". I know that would be my answer. And don't think I am not in the process of ruffling whatever feathers I can on the Roland websites, but that doesn't mean I am not going to voice my opinion here. I will not stay silent simply because I didn't get quite as "ripped-off" as you did with my purchase. That's your problem if you value protecting a company's reputation over your true experience with that company. And I just don't think a driver rewrite would be as terribly complicated a solution as everyone is making it out to be. Perhaps I am wrong. Regardless, companies need honest feedback from customers, even if that means hearing an angry voice once in a while. Your denial to face reality means you will likely get ripped off on something like the VS-700 again in the future. I have tremendous respect for Cakewalk and have been a loyal purchaser since 1998. I would have to do a tally, but my guess is I have spent upwards of 3 or 4 thousand dollars on Cakewalk products in nearly a 20 year period, and I feel that is a conservative estimate. I am no expert in how separate companies join together for business in the fashion which Roland and Cakewalk did for whatever period of time they did business, but I DO know that, if they were indeed partners, BOTH partners had responsibility in this current predicament. If I marry a pregnant woman and decide to adopt her child as my own, a few years later, if things don't work out and I leave, I don't get to say "well, someone else knocked her up." Nor does the mother get to say "I'm gonna leave our child also, because YOU left!" They are BOTH responsible for that child's well-being and will BOTH BE HELD responsible if the child is neglected. Now, admittedly, it's a stretch in terms of the direness of the related situations, but I hope you can at least make the connection. The "blame game", solely on Roland, which you continue to play may shut most people up, but it still doesn't help the fact that anyone who got screwed with the driver situation is NOT going to ever buy any hardware from Cakewalk, or through Cakewalk, ever again. Case closed.