Sorry, but we do not do release notes for native plugins at this time.

How would/could I revert back to my current version should I need to ?

Alright ....

I carefully updated a few of my 'rare' need/use Natives [those not used in Mastering] ...

and all went well !

Major Fix ... all the GUI's are Re-Opening at their correct Size !!! YEAH !!

Don't know what else was changed with this update ... but GUI fix was major.

After initial testing, proceeded to update all important Natives.

Thank-you

Why? Developers from tiny one-man operations to huge companies generally do release notes, is there a reason UAD has decided they don't need to do that? I'd certainly appreciate knowing what was changing when I update my software, you know, it doesn't have to go into some kind of trade-secret compromising detail, either, just some notes like "bug fixes" "improved GUI consistency" etc. would be great to have. It's nice to have a rough expectation of what the patch changes and it can be very helpful to know that a version you've been relying on has some undesired behavior, I don't really understand not offering this but that's why I'm asking.

Just as a UAD user for many many years (on Mac), I don’t ever recall plugins breaking following an update. There may be some users with other experiences though.

There currently is no way to revert to older versions of the native plugins.

We do it for LUNA and for UAD, but just haven't started for UADx. This may change in the future, but there is no news to share.

You can for sure consider every update to be bug fixes and enhancements as we build out UAC.

Thank you for the reply, I appreciate it.

I will keep an eye out for the 2 plugin bundle to hopefully return. Fingers crossed...

So, I have a theoretical question: until now, if we bought the DSP version plugins, which is all I really want as an owner of 2 octos, we are given the Native versions, as well. This has been really cool. However, now we are looking at releases being only Native, as with the Sound City plugin. What happens if there is a later DSP release? Do we also get that as Satellite DSP owners?...

Thank you.

Yes.

Thanks for the updates, Drew

Any news on developing resizable GUI's for the DSP plugins?

Happy Holidays!

That is truly good and reassuring news. Thank you.

Can you speak to the comments about UAD DSP not being able to host a plugin if it takes more than 1 core to load it? Is it possible for a satellite to do this, but perhaps not an Apollo? Asking to learn. Especially since it puts an interesting spin on things: we have bought the DSP to offload CPU loads from our computers. This is most useful for plugins that have heavy demands, obviously. However, if you are going to build more complex and larger plugins that can't fit on a single core, then we actually cannot use our DSP for the specific job we bought it for...;-) Does the question make sense in this light?

Nothing to share at this time, but we know how much users want this.

Sats allow for chip spans.

If there's sonic changes - they'll almost certainly be noted. Not that I've ever seen that with UA - it's usually bug fixes.

Of course, if a fixed bug results in a sonic change...!

To be clear ...

I usually download and keep an Archive of all my Software and versions should I ever need to revert.

Lately, have been 'forced' to use the Company's Plugin Managers. Sure, it can be convenient ... but it also takes out some 'safety'.

Really, it has not been often of an issue ... but it has happened.

Not that anyones' OWN music is not as important ... but when you have outside Clients, I try to maintain some level of 'upgrade' caution.

Example: I use Reaper to do a lot of the basic Mastering work. They have recently released v7 ... but I have several custom Scripts that
do not work yet .... so I stay at v6.83.

To further belabor the point ... I'd like to know what the Change Log contains. I feel, an informed Customer is an engaged Customer that
would like to know what goes on with the tools purchased. We are Engineers after all, and I don't care much for 'guess work'.

anyway ... back to work.

Yes! Then please, please release the Sound City plugin as a DSP compatible version. I am sure I am speaking for every satellite owner when I say that we will always be looking for this option for any new releases, even if Native is also available. It is a bit of a deal-breaker for a lot of us, TBH.

Thank you for the information. I appreciate it.

I doubt if they'd muddy the waters even futher by having yet another sub catagory of plugins that work only for a select number of users. I suspect most if the installed UAD DSP power out there is Apollo anyway.

Well, with respect, I hope that they do make it available for satellite users. I am sure I am not alone in this thinking, either...;-)

As an owner of an Apollo 8 2xSatelites and 2xOcto cards so do I. I don't think they will though.

Let's hope you are wrong! Happy Holidays...;-)

Thanks for replying to my ticket here!
Been quite busy since christmas but I finally got the chance to check out the dbx160 compressor again and see if what you said applies to what I was observing.

At first I was trying it on drum overheads and it still seems to apply more compression with the the sc-filter on than without it. I still don't completely understand why its doing this but I figured this might be due to the compressor reacting more to the cymbals than to the drums at this point. This to me implies that there should be a shift in threshold when the sc-filter is enganged.

The attached audio sample of the compressed overhead track (dbx160 OH.wav) shows this behaviour. The snare drum initially has about 10db of gain reduction. After two bars the sidechain filter is engaged. The track now clearly has more compression than before. Both on kick and snare drum, at least thats what I hear.

When applying compression only to the kick and snare tracks however (dbx160 kick snare.wav) I can see more of the behaviour you were describing. The kick gets less compressed, but then again the snare drum also goes from 10 to 12 db of gain reduction when engaging the sc-filter.

So I'm not sure what to make of it. Like I said, my guess would be that there is a threshold change when the sc-filter is engaged, which makes an A/B comparison questionable. Maybe I am missing something.

Can you confirm this?

I’m waiting for iVOG to go native. Come on UA, convince LL it’s the only way!

Are you sure you just cannot simply drop in older versions manually of native plug-ins? Will these not be loaded as usual then?

I am referring to inside of UAC.

aha, OK. I must have misunderstood what RJHollins inquired about. Thanks.

yeah, it's about the lowend in the sound. In your cases, it's likely the high freq content that it's grabbing.

Do this:
Take a 100hz sine and run it through the plug. Then engage the filter on/off. You'll get less compression with the filter engaged.