×
What's new

Samplicity announces Berlin Studio plugin

when the update comes for m1 mac, how do I update? Just download again?
Do you have issues with the plugin on an M1?

I want to make a list of users who have issues on Silicon chips and if possible of users who have it running fine on an M1.

On the download page I will always mention a version number and its release date. If I find and fix something that explains Mac M1 issues, I will do mailing to notify all user.

The update from this week was better tested than the first release, and I had enough reasons to believe that all reported M1 / Silicon issues were fixed as well.

Given
 
Do you have issues with the plugin on an M1?

I want to make a list of the people who have issues on Silicon chips and if possible of user who have it running fine on an M1.

On the download page I will always mention a version number and its release date.

The update from this week was better tested than the first release, and I had enough reasons to believe that all reported M1 / Silicon issues were fixed as well.

If I find and fix something that explains Mac M1 issues, I will do mailing to notify all user.

Given
No, I'm switching from a PC to a mac soon so this is just me trying to be prepared haha
 
Do you have issues with the plugin on an M1?

I want to make a list of users who have issues on Silicon chips and if possible of users who have it running fine on an M1.

On the download page I will always mention a version number and its release date. If I find and fix something that explains Mac M1 issues, I will do mailing to notify all user.

The update from this week was better tested than the first release, and I had enough reasons to believe that all reported M1 / Silicon issues were fixed as well.

Given
Hi Peter,

I can confirm too, that the Logic validation is fine now and the EQ works. But the CPU usages is still pretty heavy, better though, but heavy. 50 instances seems absurd to me in the moment. Even 5 is too much (I‘m on BigSur with a 2015 iMac).
Maybe I don’t understand completely yet how Berlin Studio works too. In the beginning of this thread you mentioned, that the usage for positioning only, doesn‘t need much ram. But where’s the difference when I load a preset, lets say for 1st violins or front stage mics ? The CPU usage seems the same to me.
I can reduce CPU, when I set tails for mics I don=t need to 0 right ? Any other tricks to reduce CPU hunger ?
 
Hi all,

Samplicity (now a new company with an older owner) has been silently working on plugins in the last 1,5 year and is proud to announce it first product:

Berlin Studio

a reverb plugin with the acoustics of a large, famous German studio.

18 orchestral positions on the recording stage, captured with a Decca Tree, an AB-Pair and surround microphones.

Check out the new Samplicity website and the first demos.

Cheers,

Peter
hello,

is there a trial version?

Thanks
 
No, I'm switching from a PC to a mac soon so this is just me trying to be prepared haha

Hi Peter,

I can confirm too, that the Logic validation is fine now and the EQ works. But the CPU usages is still pretty heavy, better though, but heavy. 50 instances seems absurd to me in the moment. Even 5 is too much (I‘m on BigSur with a 2015 iMac).
Maybe I don’t understand completely yet how Berlin Studio works too. In the beginning of this thread you mentioned, that the usage for positioning only, doesn‘t need much ram. But where’s the difference when I load a preset, lets say for 1st violins or front stage mics ? The CPU usage seems the same to me.
I can reduce CPU, when I set tails for mics I don=t need to 0 right ? Any other tricks to reduce CPU hunger ?
I am baffled, you are using an Intel Mac. Not a recent Silicon one...

The software code for that is the exact same source code as for Windows. Ok, maybe 99.5% the same.

For Silicon there are more differences, also for computations. Not for Intel.

Can you share (maybe via email or PM?) what processor your Mac has (i5, i7?), how many cores and which speed?

On my Intel i5 dev laptop, 16 instances brings me to 50% CPU, with acceptable buffers sizes.

The next version has no processing when there is no input signal. This makes it easier to spot "CPU spikes" and to share their details. The 1.0.6 still has a constantly "running" engine.

Curious about your iMac's specs.

PS: I am playing a bit with Logic on my Intel Macbook Pro:
it makes a big difference if you set Processor Buffer Range to Large. At Small, the CPU usage is really high. And this is not your audio interface block size (!). I have that 128 samples, with a short roundtrip of 12 msec.
 
Last edited:
By the way Peter, did you disable the function to key in the value we want for this field? coz that's a very useful feature. Pardon me in case i've missed out anything on the update log.

1670057179544.png
 
By the way Peter, did you disable the function to key in the value we want for this field? coz that's a very useful feature. Pardon me in case i've missed out anything on the update log.

1670057179544.png
That is correct, it was not designed to be available and it was not "styled" as such. I now remember you mentioned it.

Not going to be difficult with this, I will send you a personal fix this weekend, and integrate a better looking approach, in the next version. Cheers!
 
I am baffled, you are using an Intel Mac. Not a recent Silicon one...

The software code for that is the exact same source code as for Windows. Ok, maybe 99.5% the same.

For Silicon there are more differences, also for computations. Not for Intel.

Can you share (maybe via email or PM?) what processor your Mac has (i5, i7?), how many cores and which speed?

On my Intel i5 dev laptop, 16 instances brings me to 50% CPU, with acceptable buffers sizes.

The next version has no processing when there is no input signal. This makes it easier to spot "CPU spikes" and to share their details. The 1.0.6 still has a constantly "running" engine.

Curious about your iMac's specs.

PS: I am playing a bit with Logic on my Intel Macbook Pro:
it makes a big difference if you set Processor Buffer Range to Large. At Small, the CPU usage is really high. And this is not your audio interface block size (!). I have that 128 samples, with a short roundtrip of 12 msec.
Thanks Peter, sent you a mail to your support address
 
Not that anyone cares but I won’t be getting this because I have altiverb and bought cinematic rooms pro yesterday and have run out of money, BUT I have read this thread and really appreciate your communication and support answering everyone’s queries and also quickly updating the plugin each time. Hopefully I could support at a later stage but thankyou for your passion and such a great IR verb.
 
I'm VERY much looking forward to getting this one, just waiting to see what the EDU discount situation is gonna look like. Might get it as a Christmas present to myself...
 
@Peter Emanuel Roos I stumbled onto what I think is an interesting development. @dcoscina mentioned that Berlin Studio wasn't recognized in Musescore 4, but on my system it is. I am able to load and use the plugin in Musescore 4, and it does not seem to affect the CPU adversely as it does in Logic. So far as I can tell, this is purely a Logic problem.
 
Back
Top Bottom