So - I like to live on the edge...
 
I installed the Tech Preview on my main computer (against all advice :)).  Everything seemed to go fine.  I went from Win8.1 to the Win10 TechPreview.  All my exisiting drivers and applications worked except one - a very important one, unfortunately: My Edirol PCR-800.
 
It had Win 8.1 drivers, but under 10, it just fails.  I tried every way I know to get this to work, but no matter what, it shows up as an unknown device (named PCR) in the device manager.
 
This particular device was picky in the 8.0 to 8.1 change, where the 8.0 driver didn't work in 8.1, so I have no doubt that they will have to update it for 10 before it will work.  It's interesting what fails about this:
 
When you install the driver, it asks that you have the USB unplugged, then it does part of its installation, then asks you to plug it in.  There is an interim open window that waits for you to do this, which never gets a highlighted "next" button because as far as it's concerned, you never plugged it in, even though the device manager shows its presence.  Also, during this exchange, when you plug the KB in, the lights com on, then dim at about 7 seconds, then turn off and it doesn't do anything until you either power on/off or remove and re-plug the USB.  When I built the new 8.1 installation, it worked completely normally.
 
Seems like some simple setting in a file somewhere rather than some actual new driver code based on the fact that every other device on the system.
 
If anyone has any ideas on how to fix this, I'd like to know them.  In the meantime, I've rebuilt on a different drive (SSD) which was in need of being done anyway (which is why I wasn't shy to give 10 a shot "live"), but if I could get this working under 10 before Eiderol/Roland gets around to fixing this, it would be great.
 
Thoughts?

Jarsve
The swipe down to close apps is universal now in Windows 10, swiping inn from the left enters "app switch?" mode. You get all programs and apps up like alt tab. So desktop programs act as apps now.

That's great news, it should get rid of some of the disjointed feeling that 8 had when it first came out.  8.1 made some big improvements, but this is even better.  I'm hoping that 10 will be as well received as Windows 7 and XP were.

Yes I was also talking about the WinRT API (for all hardware), not Windows RT (Windows build for ARM only) which is a dead horse. The WinRT API is supposed to be the feature for both desktop and "modern" apps. However I'm pointing out that it has a very music-unfriendly foundation as MS ripped out things that are required for low latency audio. We no longer have the ability to change thread priorities. All low-latency audio APIs have been removed, leaving only WASAPI shared mode.
 
Also, the async/await pattern permeates the WinRT API. It doesn't work with traditional thread locking primitives (due to that it now results in a compiler error if you mix the two). Async/await also causes thread priority inversion, which is most likely why they removed all ability to change thread priorities, and hence had to remove WASAPI exclusive mode also [read: It isn't going to be easy to fix it after the fact].
 
I while ago I did an extensive set of micro benchmarking showing how async/await kills performance. I first realized there was a problem when I tried to port a real audio application to a "modern"/metro/toy app. Yet if you read Windows dev blogs etc people are going gaga over async/await.
 
It is somewhat concerning to me.

RT always seemed a bit of a blind alley to me. I bet it's not going to have much of a life-span, even in API form.

Thanks for clarifying the desktop vs Metro question.
Essentially the most important part, the multi-touch is the same for both.
Great. Or not so great if I missed something important.
 
So there are no obstacles for iPad apps to be ported to Windows and run as VST's and VSTi's or standalone. 
 
I would have a vertical monitor and a multi-touch nearly flat monitor on the desk and use it to play with the  multi-touch DAW, VST, VSTi and standalone applications. And yes the mouse will be ready to use whenever it is more efficient to do so. The day this will happen is not that far away.
 
 

Blades
Seems like some simple setting in a file somewhere rather than some actual new driver code based on the fact that every other device on the system.
 
If anyone has any ideas on how to fix this, I'd like to know them.  In the meantime, I've rebuilt on a different drive (SSD) which was in need of being done anyway (which is why I wasn't shy to give 10 a shot "live"), but if I could get this working under 10 before Eiderol/Roland gets around to fixing this, it would be great.
 
Thoughts?

If I were to guess, the edirol drivers have a hardcoded windows version check and fail to install properly on a higher version. Most of the Roland drivers have this flawed pattern which requires them to be rebuilt before they work on a new OS, so I wouldn't be surprised if this is the reason why it fails to install. There might be a way to hack the version compatibility check but I don't know how. Maybe there is some way to install a driver in Win10 and make it think the OS is Win 8 rather than Win10 to work around this check...

Edit the line where you see Windows driver singing. This is what we did to get the Asus thunderbolt landed on server 2012 !

Edit the line where you see Windows driver singing

Where would I find such a line?  Are we talking about in an inf file or something like a dll?
These are the files that are in the 64bit folder:
rdcl1027.dll
rdcp1027.cpl
rddp1027.exe
rddrvinf.dat
rdid1027.cat
rdif1027.inf
rduninst.dat
rdwm1027.sys
setup.dat
 
I've looked at each of these files (just in notepad++) and I don't see anything obviously about "driver signing" and some of them are obviously not just text files, so I wouldn't know what to even look for or how to edit them, short of using a hex editor to get into their details.
 
Thoughts?

Blades : I will talk to the tech that did the driver edit, I'm lead build/support on Thunderbolt , so I specked the system and devices. In turm you can try this :
 
Do the following:

1. start > search > cmd.exe (right click run as admin)

2. type the following

bcdedit.exe –set loadoptions DDISABLE_INTEGRITY_CHECKS

and then type

bcdedit.exe –set TESTSIGNING ON

You should get completion prompts after typing each. Once complete, restart.

Blades: talked to tech he suggested you try  : compatibility mode first? That always worked for my .exes... he gave me this link to.... :   http://blogs.technet.com/b/bernhard_frank/archive/2010/03/15/how-to-install-orca-exe-from-the-windows-installer-development-tools.aspx
 
hope you sort it out !