×
What's new
By:

Samplicity announces Berlin Studio plugin

AllenConstantine said:
Did the loud noise happen while using 256 buffer size, right? Or 512? Peter will definitely look into it and fix it. I’m constantly helping him out alleviate this but it takes time. You guys must be careful with this bug as you don’t want to break your speakers or worse, your ears.
Click to expand...
I will try to add non-obtrusive hard limiting: allowing overflowing with say 12 dB, but clip rogue signals.
 
For those who are interested. I measured a couple of delays, not all of them yet.

percussion forward dry > tree = 24 ms
woodwinds dry > tree = 15 ms
violins 1 dry > tree = 7 ms
violas dry > tree = 10 ms

Different mics don't seem to add extra delays.
 
JeffvR said:
For those who are interested. I measured a couple of delays, not all of them yet.

percussion forward dry > tree = 24 ms
woodwinds dry > tree = 15 ms
violins 1 dry > tree = 7 ms
violas dry > tree = 10 ms

Different mics don't seem to add extra delays.
Click to expand...
Nice!
When the dust has settled ;-) I will document/publish all those measurements, I have them somewhere, sample accurrate
 
I just got a huge "spike" of random noise during playback with BS on Master Bus and as insert on 1 instrument (thank goodness I have a limiter with "protection setting" on Master Bus)

Edit: Windows 11, Cubase 12
 
Peter Emanuel Roos said:
I have created a new test setup and with that, I can confirm that I am replicating reported issues with Silicon, Logic and AU validation at the moment. Not yet tried, but this may also include other setup combinations.

For now I recommend not to update. Contact me via email (or PM here) if you no longer have the installer of the first release and want to revert.
Click to expand...
Repeating my advice to not use the update;
and also adding the advice to not use the plugin in Logic (which has no protection against rogue signals; some other Daws do).

I am working on this, and seeing anomalies that need fixing, in a Logic environment (at least)
 
I purchased this plugin but when I click the link to download the Mac installer, either in my emails or from the samplicity website, it says invalid download link?
 
Peter Emanuel Roos said:
Repeating my advice to not use the update;
and also adding the advice to not use the plugin in Logic (which has no protection against rogue signals; some other Daws do).

I am working on this, and seeing anomalies that need fixing, in a Logic environment (at least)
Click to expand...
Dear Peter,

You are absolutely a fine gentleman who strives for a better performance of your fabulous reverb plugin!

Great things come to those who thrive! Keep up the good work.

Best,
A.
 
Jett Hitt said:
It would be very helpful if you could post a bit of instruction about how to remove Berlin Studio from Logic so that we can reinstall the first edition. My remove option is grayed out, and I haven't found where Logic stores this.
Click to expand...
If you re-run the previous installer, it should put the first, 1.0.1 version back.

You do not have to remove it from Logic, as it is not installed in a folder related to or managed by Logic, but by MacOS.

Send me a PM if you want to know where the files are stored.
 
Peter Emanuel Roos said:
If you re-run the previous installer, it should put the first, 1.0.1 version back.

You do not have to remove it from Logic, as it is not installed in a folder related to or managed by Logic, but by MacOS.

Send me a PM if you want to know where the files are stored.
Click to expand...
I will send you a PM, but for the record, rerunning the previous installer does not remove 1.0.2 from my system. I think someone else above had the same problem.
 
Trash Panda said:
@Peter Emanuel Roos is it possible to have the balance controls only impact the dry signal or have a separate set of controls only for the dry signal?
Click to expand...
I can understand the request and put it on "the" list.

In my setup I would not use that, because the input should be panned to the position from where the IRs were created. But that is being too strict and theoretical ;-)
 
Jett Hitt said:
I will send you a PM, but for the record, rerunning the previous installer does not remove 1.0.2 from my system. I think someone else above had the same problem.
Click to expand...
Hosts like Logic can cache information on plugins that can make this stuff really, really confusing.

The only way to know the version of a plugin file, is to verify it with Command-I in the Finder.

The files are located in
/Library/Audio/Plug-Ins/Components/
/Library/Audio/Plug-Ins/VST/
/Library/Audio/Plug-Ins/VST3/

You need to press Shift-Command-. (dot) to reveal the /Library folder

If you remove the Berlin Studio files from here, you are sure they are gone.
 
Peter Emanuel Roos said:
You mean audio channels?

No, but there are plans for a surround version, with surround panners in the input/reverb channels.
Click to expand...
Ooh that sounds neat.

I've got a question then:

If I were to put several instances of Berlin Studio on the same instrument but only use one mic each and mute the rest (so I could theoretically route the individual mic outputs out) would the CPU usage be the same as if I were to use one instance, or would there be a significant increase in CPU usage?

Thanks, and the demos sound great!
 
AlbertSmithers said:
Ooh that sounds neat.

I've got a question then:

If I were to put several instances of Berlin Studio on the same instrument but only use one mic each and mute the rest (so I could theoretically route the individual mic outputs out) would the CPU usage be the same as if I were to use one instance, or would there be a significant increase in CPU usage?

Thanks, and the demos sound great!
Click to expand...
Thanks!

You can stop most of a channel's processing by setting its tail level to zero, after two seconds its processing will stop. The way you describe it indeed has very little overhead.

Mute cannot do that, as you want reverb to keep going for being able to toggle the mute and solo buttons (otherwise you'd get weird missing reverb dips in your output using them).
 
Last edited:
Peter Emanuel Roos said:
Thanks!

You can stop most of a channel's processing by setting its tail level to zero, after two seconds its processing will stop. The way you describe it indeed has very little overhead.

Mute cannot do that, as you want reverb to keep going for being able to toggle the mute and solo buttons (otherwise you'd get weird missing reverb dips in your output using them).
Click to expand...
Perf. Thanks for the quick reply!
 
Peter Emanuel Roos said:
I can understand the request and put it on "the" list.

In my setup I would not use that, because the input should be panned to the position from where the IRs were created. But that is being too strict and theoretical ;-)
Click to expand...
So if I’m understanding you, we should be feeding pre-panned signals into Berlin Studio if the placement is not centered in the IR?

For example, trumpets with a centered source signal should be panned to the right a bit?
 
You must log in or register to reply here.
Back
Top Bottom