What's 'Out of PGM/Mem' mean?

Does anyone else get this error and what does it mean? I get it when trying to load Ocean Way as a new effect or sometimes when loading a project with Ocean Way in it, but the UAD meter usually shows both PGM and MEM usage as low. It seems like power cycling the Apollo fixes the error, but it's a clumsy workaround. For me, this is the only plugin that errors like this. Any ideas?

Win 7 64bit, Cubase 7.06, Apollo Quad (latest drivers), using the recommended Sonnet Firewire card.

Same thing here, without an Apollo. The reason why is because the OWS takes 75% of a single SHARC chip's PGM per instance. The UAD system balances the load fairly well, but if you add an OWS and you don't have a SHARC with less than 24% of PGM currently in use, the system doesn't shuffle plugins that are currently running to make room. Hence the error message. If you reload the project, the load balancer will start with the heavy plugins first, load them, then put in the lighter ones where it can. That way it will usually load correctly without throwing an error.

The instance chart on UA's website is incorrect since it only takes into account DSP power. The number of OWS instances is half of what is advertised, basically one per SHARC.

Great info, that explained it perfectly. I couldn't quite understand if I had things setup improperly but at least I can rest easy knowing it's not something I screwed up. Thank you!

The only other plugs on the session I am running are stock PT 11 Avid plugs.



-------------------------
I think I'll have to treat myself to a new Black White Dot Bikini soon.

I have been having this problem quite a lot with the Ocean Way plugin. I've had projects that worked fine for some time and then would suddenly disable the OWS plugin with no ability to get it to work again. The last project this happened on was using only 44% of the PGM on the card. I had to do some creative shutting down of other UAD plugins and freezing to get my mix back. Has this issue been addressed in newer releases? It is a serious PITA.
Windows 7, Nunedo 6, 2 UAD quads

Dean

I have found a work-around solution to this problem. If I move the fx channel with Ocean Way, which is a PGM hog, to the first channel of the mixer, the UAD loads it first on which ever chip it is using. Then the lower PGM plugs can load up in the remaining space. Hopefully UA will figure out a more elegant solution but this is working for now.

Dean

DRickard said:

I have found a work-around solution to this problem. If I move the fx channel with Ocean Way, which is a PGM hog, to the first channel of the mixer, the UAD loads it first on which ever chip it is using. Then the lower PGM plugs can load up in the remaining space. Hopefully UA will figure out a more elegant solution but this is working for now.

Dean

Click to expand...

Check out my new thread regarding PGM usage. Although there I didn't come up with any new workarounds, the PGM issue is more complex than I previously wrote. One thing that might help is if UA modified the load balancer so that OWS instances were squeezed onto single SHARC chips first, thereby sharing their PGM; as it is, by default OWS instances will be loaded onto separate SHARCs and PGM will be needlessly wasted.

http://uadforum.com/general-discussion/15720-ocean-way-studios-load-balancing-pgm-usage.html

I just read your new thread about, and I see that the subject is really more complex.
But.. anyway, following your suggestions here, at least I succeeded to "bypass" the issue and load more instances of OWS.
(In pro-tools is good that we can just deactivate temporalily some uad plugs and not to unload )

Yes, in Nuendo you can deactivate any plugin within an individual project (in other words this problem doesn't stop a project from loading) or deactivate it globally for all projects. There is the freeze track option but that is near useless for effects on sends and who wants to print a track to turn off an effect. I only want to print actual mix downs!

Dean

cheerful hamster said:

Same thing here, without an Apollo. The reason why is because the OWS takes 75% of a single SHARC chip's PGM per instance. The UAD system balances the load fairly well, but if you add an OWS and you don't have a SHARC with less than 24% of PGM currently in use, the system doesn't shuffle plugins that are currently running to make room. Hence the error message. If you reload the project, the load balancer will start with the heavy plugins first, load them, then put in the lighter ones where it can. That way it will usually load correctly without throwing an error.

The instance chart on UA's website is incorrect since it only takes into account DSP power. The number of OWS instances is half of what is advertised, basically one per SHARC.

Click to expand...

Ya know what, that makes sense. I think the console / driver has a bug though. With my apollo quad, I had a clean project and on one channel (hi-z 1) with just a Vintage amp room and then tried to load an OWS and got this. I've loaded ows on top of vintage amp room before.

I had left the apollo on from last night. The UAD meter showed like 3% used with no plugins, then I loaded up vintage amp room and it went up a little, then OAS wouldn't load. I think whatever it uses to store how much resources are taken is not clearing out. I also think that it uses different processes to display how much dsp is left on the uad meter vs the process used to check whether or not it has enough dsp to instantiate a plugin. (Just my hallucination though)

I also noticed that I can't load a unison plug along with a vision on the same channel, it does the same thing. Even after re-starting the thing.

Yesterday I finally purchased the Ocean Way plugin. I had the same trouble as mentioned above using Ableton and the Ocean Way plugin as a return track (last one to load).
My UAD system is a mix of 1 Quad and 2 Solo cards. I recognised that the cards would load/be recognised in random order. Device 1 could be a Solo or sometimes the Quad card. The trouble with the missing PGM/MEM only appeared when a Solo card was the first device. Here is my workaround for OS X to load/recognise the Quad as the first device:

1. Open your OS X volume
2. Open "System"
3. Goto "Library"
4. Open "Extensions"
5. Search for "UADSystem.kext"
6. Right click, choose "Show Package Content"
7. Open "Contents"
8. Edit "info.plist" as shown in attached screenshot
9. Restart your System
10. Quad/biggest card will be recognised as first device
11. Make music!