You shouldn't be using the asio duplex driver, just the regular native driver from Edirol. If your copy of Cubase is legit, the way to get tech support is through your MySteinberg account and complete a tech support form. From Dec 15th you'll have to log into MySteinberg to access the forums too. Check your inputs and outputs by pressing F4, read the manual or getting started quick manual for setting up your audio device. Set up the edirol driver in your VSTaudio settings in devices. If you're trying to record at 96 Khz, the Edirol isn't bi directional and has some kind of switch you have to select, so try recording at 44.1 or 48 Khz and or, adjusting that switch. One last thing - you could try downloading ASIO4ALL, a generic asio driver which sometimes works better than native drivers and see if your problem exists with this driver.

The interface I have is an Roland Edirol UA-25. I installed the drivers etc with no problem. I have even installed the latest fully 64bit compatible drivers. However, In cubase when I want to record in via the UA-25 I have to switch the ASIO driver in the VST Audio System. This is annoying to constantly have to.

If asio4all cures your problems, it's likely that the 64 bit Edirol driver is causing the issue in which case, contact them. Check your inputs and outputs by pressing F4, read the manual or getting started quick manual for setting up your audio device. Set up the edirol driver in your VSTaudio settings in devices. One last thing - you could try downloading ASIO4ALL, a generic asio driver which sometimes works better than native drivers and see if your problem exists with this driver. If asio4all cures your problems, it's likely that the 64 bit Edirol driver is causing the issue in which case, contact them.Yeah I have the ASIO4ALL driver already but the problem is the same with that. The reason I use the asio duplex driver as my defult device is because it has no input latency where as the ASIO4ALL has 12 ms.

As for my inputs, when I select ASIO4ALL the inputs are labelled as: Stereo In: LEFT: HD Audio Mic Input 1 RIGHT: HD Audio Mic Input 1 Is this not correct for recording in? I do notice that when I select this driver I no longer get the error message about recording audio not being available which must be a good sign. As for my inputs, when I select ASIO4ALL the inputs are labelled as: Stereo In: LEFT: HD Audio Mic Input 1 RIGHT: HD Audio Mic Input 1 This means it is using the inputs of your onboard audio interface, not the UA. We recently tested the UA 25X on a workstation, and while its performance is not the best, it was stable and functional. We only tested the ASIO 64 bit driver from the unit itself, not the generic ASIO or ASIO4ALL drivers. Also, the ASIO duplex driver (you mean the generic ASIO driver?) will create more latency. The 0.00 ms input latency is a miscommunication of the driver.

I don't know why you are getting issues with the driver called 'UA-25EX'. This is the one we used without trouble. Did you set the 'advanced driver' setting correct, at the back of the unit? This means it is using the inputs of your onboard audio interface, not the UA.

We recently tested the UA 25X on a workstation, and while its performance is not the best, it was stable and functional. We only tested the ASIO 64 bit driver from the unit itself, not the generic ASIO or ASIO4ALL drivers. Also, the ASIO duplex driver (you mean the generic ASIO driver?) will create more latency. The 0.00 ms input latency is a miscommunication of the driver. I don't know why you are getting issues with the driver called 'UA-25EX'. This is the one we used without trouble.

Did you set the 'advanced driver' setting correct, at the back of the unit?Yeah the advance driver is on. The sample rate is 44.1.

The driver I have installed is the most up-to-date 64bit driver for windows 7. I'm not a pC guy anymore. Been on mac for a while.

But I do remember that you should select your audio device in the control panel to use it with other programs itunes/web/youtube etc. As for your cubase woes. Do you know how to monitor with the ua25? Have you read up on the direct monitoring function built into your interface? Do you know how to monitor in cubase? Contact the vendor who sold you the interface, or get some help on the cubase forums.As you may have realised I am not a pro when it comes to hardware so i dont think I do know how to monitor the interface or cubase.what does that mean?? I think I will try adjusting the control panel to see if I can assign both drivers to work side by side.

DANDERMAN123@DSLEXTREME.COM This all begs the question as to whether there are any 'improvements' in the Roland/Edirol Windows 10 drivers that are absent for the driver hacks discussed above. Yes, I know that there can't be any such improvements for 'missing' drivers, but what I am getting at is whether there are features in Windows 10 for which older instruments cannot take advantage because their hacked drivers are really Windows 8x. Not Windows 10. Or are the Windows 10 drivers basically just Windows 8x drivers with minimal mods to recognize the new build? Is there are readme or change log with the drivers?

Otherwise email Roland (who will probably ignore the request). SOLVED Maddeningly, I simply cannot find a.INF file in my extracted Files/64bit folder when extracted. I have upgraded to Win 10, based on the reports as to how this hack for PCR controllers was working for everybody. Can anyone please tell me what the actual name of the. Akka Protobuf Serialization. INF file is, and any reason why I cannot find one in the exracted Roland site Ver 1.0.1 Drivers for Windows 8/8.1? I found it in the end, my problem was it had a different name from the one in the video. I found Method 1 to work for my PCR-500, but I DID have to reboot after disabling the driver signature verification. I did try first time without doing that as suggested it may not be necessary, but it failed.

A quick reboot, run the install with the amended.inf file again, and it worked a treat. DANDERMAN123@DSLEXTREME.COM This all begs the question as to whether there are any 'improvements' in the Roland/Edirol Windows 10 drivers that are absent for the driver hacks discussed above. Yes, I know that there can't be any such improvements for 'missing' drivers, but what I am getting at is whether there are features in Windows 10 for which older instruments cannot take advantage because their hacked drivers are really Windows 8x. Instacode Crack 2008 Democratic Primary here. Not Windows 10. Or are the Windows 10 drivers basically just Windows 8x drivers with minimal mods to recognize the new build?

The driver only differs between different versions such as 1.0, 1.01, 1.2 and so on. From what i understand, that has nothing to do with what OS it is made for. So if the driver version of the win 8.1 and 10 driver is not the same it is most likely another driver. As an example my UA25 did not support multi channel audio routing or whatever you call it in version 1.0 but did in 1.01.

I have an Edirol FA-101 firewire audio interface and a 64 bit machine. The FA-101 used to work fine under Windows 7 but today I upgraded to Windows 10 and the device is no longer being recognised. I have downloaded the 64 bit Windows 8/8.1 driver from Roland and unzipped it, and would like to use your method to get the FA-101 working again. But whenever I double click on the setup.exe file in the driver download, it says it cannot find the driver files and lists them. The unzipped download has a top level folder called fa101_864d_v100, which contains Setup.exe, Uninstall.exe, and Readme.htm.

It also has two subfolders, Readme and Files. The Files subfolder contains 16 files (including two.inf files); the files in this subfolder are the ones Setup says it cannot find. I have tried copying the Setup.exe into the same folder as the driver files and double clicking it again but I still get the same problem.

Does anyone know what is going on please? I finally got Method 1 to work.

Thanks very much for the tip. I'm not sure why it didn't work first time around, maybe a reboot IS needed after disabling Windows driver verification.

In the interim I had sent a support request to Roland who told me my product was not compatible with Win 10. When I told them it was and they should update their Win 8 driver setup files in accordance with this thread, I got the usual corporate legalistic nonsense about them not supporting Win 10 with my product & not supporting modifications to their drivers. Naturally I will now think long & hard before I buy another Roland product, but for now my Edirol FA-101 is working in Windows 10 very nicely thank you! Nothing like reviving an old thread.

I finally upgraded to Wiin 10 on my DAW. I have a UA 25-EX and tried both methods. I had no luck. Device manager shows the UA 25-EX with the dreaded yellow triangle.

I have 2 questions: My upgrade was from Win 7 Pro (64 bit) to Win 10 Pro (64 bit). Do I need to use/mod different drivers? This seems to be for Win 8 to Win 10 upgrades. I'm not sure that makes a diference.

What should the settings on the UA 25-EX be for success? As an aside I tried the Win 10 update drivers to find the proper driver and it ran all night. Very frustrating to say the least.