APOLLO DSP Reset

I think I just found a bug and a solution to that bug with the Apollo's DSP. Today I tried to load a session that was perfectly fine yesterday and it was disabling plugins and giving me the DSP overload message. When I opened up the DSP meter after quitting the session, it was showing that I was using DSP even though I had no plugins loaded in the Apollo's Console app and no session open. The Control Panel Meter that shows how much each DSP chip is using was showing 3 of the 4 DSP chips were at about 18% DSP usage and 8% usage overall one the main meter which is a lot without having any plugins loaded. I tried uninstalling the UAD software and deleting the preferences without deleting my sessions preferences and installing it again and nothing. Turning the Apollo on and off wasn't resetting the DSP either. Resetting my computer did nothing as well. Finally I opened up the Apollo's Console app and the UAD Meters Control Panel and turned off the little blue DSP power switch next to the Apollo icon and pressed the Insert Effects (MON/REC) switch on the Apollo's Console app and it reset all of the DSP meters back to Zero %... When I hit the Insert Effects switch again it made the meters go back to showing DSP being used with no plugins loaded. Only when I turn off the blue DSP switch in the Control Panel and hit the Insert Effects switch in the Console app does it reset back to Zero. So basically hitting the Insert Effects switch in the Apollo's Console app while the Apollo's Blue DSP switch in the Control Panel is ON makes the DSP act up showing usage with no plugins loaded and causes DSP overloads if you try to use a certain amount of plugins. So if your DSP meter isn't at 0% without any sessions or plugins in the Console app loaded, you may need reset your DSP meters using the method I just explained.

Cool, please call ua and let them know !

Already sent a support ticket.... Of course after I sent them an email asking for a solution. SMH! LoL

Crisis, what crisis: yr on the job !!

This how my meter looks when the DSP doesn't reset and no plugins are loaded in the Console app or sessions are loaded up.

This is how it looks after I reset it by turning off the Blue DSP Power switch next to the Apollo icon in the Control Panel and pressing the Insert Effect (REC/MON) switch in the Console app.

hmm, there is a little signal on your 7/8 input ? but that is interesting do you have your fwb set hi or to max ?

AHHH sweet! This is great. Thanks a lot for sharing this as I have been scratching my head with this issue for a while now. Since 7.5 I'm at 9% idle DSP usage with only the console open on my Apollo Quad! It's always been around usually at 6~7%. I could not bring it back down, or reset it to zero. One of my chips was at 20% in idle!

This quirky workaround really did it for me to, emptied the DSP to 0%. Thanks a lot. I'll send a support ticket to UA as well.

Cheers, Dan

I've always wondered why it stayed at 8% when I first turn on my Apollo. I thought it was by design. Thanks for the workaround. Hopefully UA will fix this. I need all the DSP I can get. LOL

Very cool. It's interesting when I first tried this it didn't seem to work. I misunderstood which window you were talking about until I looked at your screen shots.
I first tried it from the little window that opens up when you choose "UAD Meter and Control Panel" from the top UA menu in the MAC toolbar and turned off the blue "UAD2" button and did the REC/ MON toggle thing. That didn't clear the meters.
I then opened the "System Info" menu as you show in your screen shots and tuned off the blue power button next to the Apollo in the Hardware list and toggled the REC/MONITOR switch and it worked like a charm.

Have you found a verifiable difference in instances from doing this or could it be it a system misreporting thing?

Either way very cool. Good job!

Joe

Same here
but have to do the procedure every time I start Apollo or change the setup!?

This is definitely a bug, or an oversight. We here have always simply thought that the 6 to 9% DSP load on an Apollo QUAD was simply the console app requiring some DSP, but this is really not the case. CRISIS has nailed it. His quirky workaround dumps all DSP load to 0% and it's not just a false reading, it's real DSP... and for me it's 10% more power.

I could never understand why one day a working session runs fine, then the next day you cannot open the same project without getting a DSP over-limit message. Why does the session work one day, then not the next?

Well, now before every session, I "dump" my DSP like CRISIS has outlined and I never run into that issue and actually get a much welcomed 8 to 10% boost!

Thanks again CRISIS for finding this out.. which leads me to the next question on everyone's mind; how did you come about to find the precise sequence anyway? Well done sir!

Thank you Crisis for the info.


Sent from my iPhone using Tapatalk

I think he was just:

clicking around

ua sent him a top secret email from an undisclosed location with no isp address and begged him to drop the fix

he was playing ouiji and the spirit of bill whispered in his ear " if u click here the dsp will come" !

either way props Crisis !

CRISIS said:

I think I just found a bug and a solution to that bug with the Apollo's DSP....

Click to expand...

Dude... I just popped in to say THANKS again for finding this bug and posting it. It has changed my life.

I get almost 10% more out of my QUAD now and no longer have the issue of a session working one day and not loading all plugins the next!!! See my before and after reset pic. Cheers mate!

My planned solution was to buy a few Octos. Now I only need two!

Thanks for this from me also. Is this sticked already?

Good job CRISIS !

tsutek said:

"...Is this sticked already?..."

Click to expand...

Yep - I added it to the "Apollo Tips and Tricks" sticky thread.

you are a gentleman and a scholar, crisis. thanks for figuring this out and sharing!

kills apollo inputs tho