Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Compatibility

Reply
 
Thread Tools Display Modes
Old 11-17-2016, 05:51 PM   #1
voidWentFlash
Human being with feelings
 
Join Date: Nov 2016
Location: oakland, ca
Posts: 5
Default UAD Apollo ASIO drivers incompatible with Reaper (FIXED)

Hello all. Long time Reaper user, long time Reaper forum lurker, first time poster.

I have been using Reaper with a 1st generation UAD2 Apollo 8 interface for a couple years now. In the latest update to UAD software, my Apollo can now run properly with Thunderbolt in my Windows 10 environment with the new Consol 2.0, which is fantastic and all except for one pretty big issue: The ASIO drivers are not recognized by Reaper.

UA lists this as a known issue in the latest software release notes so I contacted their tech support about the issue and got the following (excerpted) reply:

Quote:
The issue with the Apollo Thunderbolt ASIO driver and Reaper is that Reaper places a character limit on the names of the ASIO drivers that can be used within the application. Reaper only accepts ASIO drivers that are 32 characters or less, and the name of our Apollo Thunderbolt ASIO driver just barely exceeds that limit.

We do plan on shortening the driver name in a future software release to comply with the character limits in these DAWs, however for the time being there is no known workaround. Note that this issue does not exist in any of our tested DAWs such as Pro Tools, Ableton Live, and Cubase. You may want to check with Cockos to see if they know of any way to bypass Reaper's character limit on driver names.
Is anyone else having this issue? And does anyone have any suggestions on how Reaper can either accomodate a longer ASIO driver name or how one could modify an ASIO driver to be less than 32 characters? UA is great but I imagine this issue isn't super high priority. In the mean time, I can only use Reaper with WDM which is not ideal.

I'd appreciate any insight into fixing this issue. Thanks!
(also, I apologize if this is in the wrong section on the forum. I used my best judgement)
voidWentFlash is offline   Reply With Quote
Old 11-18-2016, 07:43 AM   #2
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,363
Default

Thanks for the report. We should be able to correct this for the next REAPER release.
schwa is offline   Reply With Quote
Old 11-18-2016, 11:01 AM   #3
voidWentFlash
Human being with feelings
 
Join Date: Nov 2016
Location: oakland, ca
Posts: 5
Default

excellent! thanks Schwa. looking forward to it.
voidWentFlash is offline   Reply With Quote
Old 11-19-2016, 05:39 AM   #4
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,363
Default

The prerelease build is available with this fix. It would be great if you could test it!

5.29pre7 with the fix is here. If you do test and have any positive or negative feedback, please post in that thread, not this one.

General information about prerelease builds is here.
schwa is offline   Reply With Quote
Old 11-19-2016, 08:54 PM   #5
voidWentFlash
Human being with feelings
 
Join Date: Nov 2016
Location: oakland, ca
Posts: 5
Default

i finally got a moment to give this a try. It works - I can use the new Apollo ASIO drivers with Reaper! Thanks for getting this into a pre-release build so quickly.
voidWentFlash is offline   Reply With Quote
Old 11-20-2016, 08:30 AM   #6
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,363
Default

Great! Would you mind responding to whoever you have been communicating with at UAD to let them know the issue will be fixed in REAPER 5.29, which will probably be officially released in about a week?
schwa is offline   Reply With Quote
Old 11-20-2016, 03:14 PM   #7
voidWentFlash
Human being with feelings
 
Join Date: Nov 2016
Location: oakland, ca
Posts: 5
Default

of course. i just updated my ticket with that information. now back to making rainy day music. thank you again!
voidWentFlash is offline   Reply With Quote
Old 06-29-2017, 07:35 AM   #8
joe2
Human being with feelings
 
Join Date: Sep 2008
Location: UK
Posts: 355
Default

(I fear it might be time to re-open this thread!)

REAPER is crashing "pretty consistently" for me with the following setup:

- Universal Audio Apollo 8 Thunderbolt (latest firmware & software).

- StarTech[0] (or Apple) Thunderbolt 3 to Thunderbolt (2) adapter.

- USB-C Thunderbolt 3 port on Dell XPS 9560 laptop running Win10 (fully up-to-date).

By "pretty consistently", I mean this:

- My usual REAPER setup will crash as soon as it opens, when the Apollo TB ASIO driver is selected.

- A fresh, portable install of REAPER will open and play back some audio, but opening most projects results in a crash (*after* all/most? plugins have finished loading).

I've had a bit of a test with things like removing plugins, scripts, extensions, etc., but haven't been able to pinpoint anything specific yet. More testing is probably required.

If it helps, Windows Event Log includes this:

Code:
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: c:\program files (x86)\universal audio\powered plugins\drivers\audio\pcie\x64\uadasio.dll
FWIW, I haven't had any problems with my usual setup (RME Fireface UCX or Fireface 802 via USB).

It might be worth pointing out that these DAWs seem to run fine: Ableton Live 9, BitWig Studio 2.1 (demo), FL Studio 12, PreSonus Studio One 3 x64 (demo), and Reason 9.5 (demo). (My simple, first-pass test was to load a heavy-looking demo project in to each and just play it. I admit this isn't a good enough test, because of all the other things that might be involved, e.g. plugins.)

Any help would be much appreciated. (schwa, Justin?) Let me know if I can provide any more info that would be useful. Many thanks!


-----

[0] UA recommend the StarTech over the Apple, but I seem to have the same results with both. And the Apple one feels slightly better made, though I probably shouldn't be surprised about that.
joe2 is offline   Reply With Quote
Old 06-30-2017, 08:21 AM   #9
joe2
Human being with feelings
 
Join Date: Sep 2008
Location: UK
Posts: 355
Default

Ah, to be clear (re my post above):

I have no problem seeing and selecting the appropriate Apollo ASIO driver in REAPER (at least so far as the Preferences -> Audio -> Device bit goes).

(It's called "Universal Audio Apollo TB". There are also options for "...Apollo FireWire" and "...Apollo Twin USB". I'm assuming this is just because UA's installer supplies all the drivers in one go regardless of the specific hardware, but I'm not sure, and this probably doesn't matter.)

After I click "OK" to save and dismiss the Prefs dialog, REAPER crashes. (And when I close it/restart, it'll crash immediately upon opening with my "usual" setup.)

So I know I might be confusing this thread a bit by heading off into an issue that's not exactly what was discussed and resolved above, but the thread title was too tempting to ignore. If necessary, I'll repost this in a new thread/different forum (or just link to this thread).

Cheers!
joe2 is offline   Reply With Quote
Old 10-26-2017, 10:25 AM   #10
gloom
Human being with feelings
 
Join Date: May 2011
Location: Oslo
Posts: 35
Default

I have the exact same issue with the same setup (and UAD recommended adapter). Everything works in regular Windows operation, and Reaper works (though with some lag and just a plain stereo output) in other modes than ASIO, but once I switch to ASIO, it crashes. Cleaning out the reaper.ini for the audio setup allows me to enter Reaper again, but once again: once I select the Apollo TB interface under ASIO settings, it crashes.

Happens on Reaper 5.60 (64 bit).
gloom is offline   Reply With Quote
Old 10-27-2017, 10:34 AM   #11
gloom
Human being with feelings
 
Join Date: May 2011
Location: Oslo
Posts: 35
Default

Okay, I fixed it. In case anyone else finds this thread and have the exact same problem as me and joe2, here’s what I did:

- Deleted the entire Reaper folder from AppData roaming profile
- Uninstalled Reaper using the official uninstaller
- Rebooted
- Installed a fresh version of Reaper

I could now set up the ASIO (Universal audio apollo TB) as expected, with no crashes and no lag.
gloom is offline   Reply With Quote
Old 11-09-2017, 09:47 AM   #12
Dhekke
Human being with feelings
 
Join Date: Mar 2015
Posts: 1
Default

I'm also having crashed with the UA ASIO drivers, but they usually happen after I alt-tab back into Reaper. Problems started after 5.61.

Following the steps suggested by gloom above did not fix the problem. I'm going to try installing a previous version of Reaper later today, likely 5.60, and see if I can make it stop.
Dhekke is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:18 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2017, vBulletin Solutions Inc.