UAD and REAPER issues

Jperkinski

Active Member
I've reported similar issues before but I still see problems with REAPER and UAD.

I have a REAPER project going and the DSP usage is at 29%. I paste an item FX plugin chain to the next item I want to work on, and then I get an error message from REAPER about DSP usage. The FX chain should only add a few percentage points to the usage as I have both an Octo and Quad processor. The last UAD plugin in the recently pasted FX chain becomes disabled.

Could somebody at UA please take a closer look at REAPER and UAD compatibly? I'm using the AU versions of UA plugins.

Here is the error message:
 

Attachments

Last edited:

Jperkinski

Active Member
FWIW. The power/enable button for my Octo card was turned off in the UAD Control Panel so maybe I was seeing this issue because my Apollo Quad MKII was trying to do all the processing. I am not using the Apollo Quad as the main interface, just as an add on to my Octo card which is supported as far as I know.

I'm not sure what would cause this button to disengage. I would also expect that if the Octo was disengaged, that the DSP percentage would shift to show that actual available DSP. Instead, it was reading 29% yet telling me there was no more DSP.

I'll have to keep an eye on it and see if it's REAPER that somehow caused the Octo card to be disengaged or something else.
 
FWIW. The power/enable button for my Octo card was turned off in the UAD Control Panel so maybe I was seeing this issue because my Apollo Quad MKII was trying to do all the processing. I am not using the Apollo Quad as the main interface, just as an add on to my Octo card which is supported as far as I know.

I'm not sure what would cause this button to disengage. I would also expect that if the Octo was disengaged, that the DSP percentage would shift to show that actual available DSP. Instead, it was reading 29% yet telling me there was no more DSP.

I'll have to keep an eye on it and see if it's REAPER that somehow caused the Octo card to be disengaged or something else.
Hi,
This is actually not a Reaper /UAD exclusive issue. It can happen with just about any DAW, and does often. I notice this behaviour when or if I have used FAST RESTART when firing up the computer. Some Fast Restarts scripts are written to be a little faster than the Octo Twin combo cares for. While you may have many instances of Fast Restart go off without a hitch, it can does happen where the Octo card will not re initiate after a fast restart.
Because I work in several different DAW's, I have gotten into the habit of checking my UAD System Configuration app before I crack open any project, in any DAW. If I notice that the UAD app is only showing the Twin, I shut down the computer , let it come to a full rest and then turn it back on and nine times out of ten, all UAD appliances will be recognised and functional.
I don't even think this is really a problem or an issue, many computers have many different FAST RESTART scripts, some are just too fast at for the Apollo/PcIe combo.
The Apollo Twin is unlike the ordinary interface, and as such, modifying our start up procedure can possibly [most likely] enable us to have the experience we are looking to have with the UAD software and hardware.
 

Jperkinski

Active Member
Hi,
This is actually not a Reaper /UAD exclusive issue. It can happen with just about any DAW, and does often. I notice this behaviour when or if I have used FAST RESTART when firing up the computer. Some Fast Restarts scripts are written to be a little faster than the Octo Twin combo cares for. While you may have many instances of Fast Restart go off without a hitch, it can does happen where the Octo card will not re initiate after a fast restart.
Because I work in several different DAW's, I have gotten into the habit of checking my UAD System Configuration app before I crack open any project, in any DAW. If I notice that the UAD app is only showing the Twin, I shut down the computer , let it come to a full rest and then turn it back on and nine times out of ten, all UAD appliances will be recognised and functional.
I don't even think this is really a problem or an issue, many computers have many different FAST RESTART scripts, some are just too fast at for the Apollo/PcIe combo.
The Apollo Twin is unlike the ordinary interface, and as such, modifying our start up procedure can possibly [most likely] enable us to have the experience we are looking to have with the UAD software and hardware.
Thanks for the info. Since this incident, I now keep the larger UAD Control Panel open on a separate monitor just so I can see that both UAD hardware units are on and working as I am working. So far I haven't seen the Octo go offline again yet.
 
UAD Bundle Month
Top