Your V700R is badged "Cakewalk" because when Roland owned Cakewalk Roland decided to badge all their interfaces as "Cakewalk". I have a UA-101, an interface which was originally made by Edirol. Roland took over Edirol and rebadged the UA-101 and other interfaces as "Cakewalk".

Cakewalk didn't write or maintain the drivers for the "Cakewalk" badged interfaces. Roland wrote the drivers and they were (and are) downloadable from Roland's website, not Cakewalk's.

Roland then sold Cakewalk to Gibson, but the interfaces and associated software licenses weren't part of the deal. The drivers for the various Roland-made interfaces are downloadable from Roland's website, and which interfaces get driver updates is decided entirely by Roland.

I seriously doubt there's anything Cakewalk can do to force Roland to write drivers for products Roland have decided not to support any more. I also strongly suspect that were Cakewalk to attempt to write and distribute a driver without Roland's consent and authorisation then Roland's lawyers would get very upset indeed amd the courts would be on Roland's side.

if they aren't going to do anything with it, they should open it and let someone else write a third party driver for it.
 
Granted, mine is working but there are some things that aren't working properly on my transport control such as my rewind to start button.

As far as I'm concerned, recent and expensive hardware should get manufacturer driver support for a long time. Especially if they want me to buy any more of their products that require drivers.

Failing that, as you say, make the code open source under a suitable licence to allow others to develop and maintain it.

tlw
Failing that, as you say, make the code open source under a suitable licence to allow others to develop and maintain it.

I guess third party libraries and hardware components (these days no device/drivers are produced by one company) have NDA. Even your own code when published can violate such agreements since it can have some information coming from not own by you proprietary part. What is not a problem for "pure software" (like Control Surface SDK), is problematic for hardware/software combination.
 
And even then. Roland could see no profit from selling these devices (they could just continue to sell them "as is" otherwise, may be with periodic "face lifting", like that is done with MCU). So whoever take future development will have no profit for sure. Drivers development is not an easy task. So have a look at really simple (relative to the drivers) thing, Control Surface plug-in. It IS open source, all not audio hardware related problems can be solved by tiny modifications in it, so the time investment is minimal. Have you ever seen any "community edition" of VS-700 CS plug-in? I do not...

I own the the full set of the Vs-Studio hardware and bought I believe one of the last available units in Scandinavia.
Now I could really cry about them not manufacturing them anymore...  but times change and so does hardware and software.  Infact I had a ZX81 with a 16mb ram pack...  I wish I could use it today  ;-)
My suggestion is always keep a back up of your old software which you know your product functioned.
You can always then use your equipment.
 
I do have the focusrite liquid channel which cost a fortune and is now dead on the Windows platform...  but I can operate with my mac or windows 98.