Just to add, you have the right idea here. 48k may work and not sound bad in most cases, but since we do not have the 48k samples, the plugin just creates an approximation by stretching either the 44.1k or the 96k samples, not exactly sure. This could work for the EQs but not for the Pre, that must be used in the supported sample rates or it will sound completely wrong.

So if you want the purest experience, you must do 2x OS at 48k for the best possible sound, and it sounds great, at the price of CPU, or just settle for 44.1k if you can. It more efficient. but 96k sounds like more depth and definition.

Could you pm me what you've typed up so far for the installation instructions? Maybe I can help you, I found the installation process pretty easy besides the set path part.

 

Deleting this plugin instantly lmaooo

 

-

 

Last edited: Jun 4, 2024

With EQs it should not be a problem, you might get some slight artifacts but maybe not even perceptible in some cases. For Preamps or reverb you will have the wrong sound if you don't use the same SR.

 

-

 

Last edited: Jun 4, 2024

Yeah this is exactly why I said it is best to stick to supported sample rates or 48k 2x OS / 96k native.

 

For Camel it is way off... If you look at Stevie's curves for Pink, it is still the same frequency but there is some artifacts. So for some plugins I guess 48k can be ok, but it is buggy I agree with you. Better to be safe than sorry.

 

-

 

Last edited: Jun 4, 2024

Subtle difference, AA.

Fun fact, even though this is mentioned in the manual 'Please keep in mind that for each plug-in in the Desert suite we recommend that you calibrate your input levels to: -18dBFS = 0dBu. We suggest that you do not overload the input.' all of the graphs in that very same manual have been made with an input of 0dBFS (yes, those of the preamps too). There's nothing like conscientious consistency. Johnny de Sado just gives a f***.

 

Personally, seeing the way it operates with stereo material being fed to it, and reading the manual blurb about the GUI "C-LINK" control in question, I conclude that UltraMarine4 with "C-LINK" engaged is simply giving you the ability to have both channels controls track each other by operating a single knob from each so as to better facilitate easier settings matching between channels. I do not believe there ever was an intention from the dev to have the stereo compression channels "electronically linked" by engaging the "C-LINK" control. It also states in the manual that the Ultramarine4 plugin was supplied with only two sets of sampled files 44Khz and 96Khz...

 

-

 

Last edited: Jun 4, 2024

Hoooleeee crap, just decided to poke my head in, didn't expect 8 pages.

 

Yep. Completely agree. As the dev we are talking about here is acustica virtually nothing would surprise me anymore given their lack of attention to detail.

 

same thing stated by me a couple of pages ago, then?

well as Boreios wrote we only need a legit user of Ultramrine, I asked a friend of mine answer: "I dont remember if I have it, if I have I dont use since ages, will tell you"

not a plugin to remember

 

Their newer compressors have a stereo-link knob, but not the ULTRAMARINE.

C-Link = Control Link so your settings are same on both channels.

 

One wacky thing thing of note; even when the "C-LINK" button is engaged the meter switches (IN, GR, OUT) do not follow each other like the rest of the controls.

 

Found a problem with SAND 3, when trying to load the twenty first instance of the plugin, crashes DAW. Tested in S1 and REAPER

 

I can confirm this. Regardless of whether you load 21 instances of the SAND 3 on one track or on separate 21, the <Reaper> crashes

 

oh ok

AAHH...ok

--------------------------------------------------------------------------

got confused anyone?

 

Snow - Only 44 and 96 sample rates.
All 4 modules seem to be working properly. All indicators also works.