×
What's new
By:

Samplicity announces Berlin Studio plugin

Trash Panda said:
No, it has an effect on all the mics, but it's less pronounced once it's run through the IRs. Stick a flute on the Mid Stage Wide and set the L or R input knob to the extreme of one side or the other (e.g. set L all the way to R or set R all the way to L). You can hear a difference, but it's subtle.
Click to expand...
You're right! The effect is more audible on other source materials than on the one I tried, where it was extremely subtle. Thanks for pointing that out!
 
Just confirming that any use of the EQ creates an ear-shattering volume spike in Logic for me. I feel this should come with an official warning via an email from yourself @Peter Emanuel Roos so as to warn others as it was quite unpleasant and with headphones on like I had could do some damage. I will avoid the EQ until this is confirmed as fixed of course. All else working fine except validation.
 
Hey all,

Do not use the 1.0.2 version. It was rushed out too quickly - a start-up mistake, my bad.

An update that fixes this is being tested and will be distributed after more tests (not only by me).

This version also includes the needed stereo panner in the Dry channel, with an indication where the sound is panned.

I hope to give white smoke, green lights, fireworks and more apologies within a few days :blush:

This fix will also include hard clipping above (say) +12 dB.
Daws like Reaper do this out-of-the-box, sad that Logic does not do that.
 
Go To 11 said:
Chrome would not let me download the latest emailed update. I logged into my email on Safari and it worked fine. Try a different browser perhaps.
Click to expand...
Caused by the email list provider I selected this summer. Not usable this way...

I have to look into an alternative or a way to make them use the links as they are.

The samplicity domains are safe with SSL/Https - the emailer inserts something that seems not certified.
 
Kalli said:
I just wanted to +1 to the request for panning options. The value of this became apparent when I tried to place a harp on the left using the mid stage wide position. Panning the input to the left only affects the dry signal. The other signals sound as if the harp was center stage, so there is a perceivable mismatch. I don't know what is technically possible, but further panning functionality for applications like this would be a great addition!

@Peter Emanuel Roos, I understood from your previous post that you recorded the IRs separately L and R at each stage position. Does that mean it's technically possible to emulate the effect of sound coming only from the L position?
Click to expand...
I have of course been focusing on the noise / AU issues, but I found this missing feature also very important.

My current version now has stereo panning (also) in the Dry channel, with an indication of where the sound "goes".

When the update has been well tested it will be distributed.
 
Peter Emanuel Roos said:
I have of course been focusing on the noise / AU issues, but I found this missing feature also very important.

My current version now has stereo panning (also) in the Dry channel, with an indication of where the sound "goes".

When the update has been well tested it will be distributed.
Click to expand...
This sounds awesome, Peter! Let me know if you need help with beta testing.
 
Really looking forward to the update, but…..will there be any improvement concerning the heavy CPU load in Logic too ?I guess it might be related to the EQ noise, so I‘m slightly confident. :thumbsdown:
 
Probably not just logic...even in FL studio. I had about 12 instances and I noticed the CPU is around 50 to 60% and occasionally will spike. When disabling all the instances, it'll be around 30%
 
Hello I have a question:

So instead of inserting it on all my instruments, would it make sense to send all my instrument to group channels that have Berlin studio on them? Worried my cpu is taking hits with all the plugins loaded
 
I was about to purchase this especially at this price but the computer usage and noise issues has gotten me scared. I would use it for every section in the orchestra and that would be a lot of instances. I’m running a newer i7 with 64 gb of ram and I never have issues with my computer coming close to 100 % usually runs around 30-40 % with a full 50 track piece loaded with fxs. Peter is this something that will be fixed in the future and should I wait till the kinks are worked out? Will this intro price last a little longer? Forgot to mention I’m on windows 11 Cubase 12.50. Thank you so much !!!!
 
Last edited:
NeonMediaKJT said:
Hello I have a question:

So instead of inserting it on all my instruments, would it make sense to send all my instrument to group channels that have Berlin studio on them? Worried my cpu is taking hits with all the plugins loaded
Click to expand...
I create busses for some instruments (e.g. Horn1,2,3,4 or the woodwinds) and use direct inserts on instruments with an own position (like V1, V2, VA, VC etc.)
 
Living Fossil said:
I create busses for some instruments (e.g. Horn1,2,3,4 or the woodwinds) and use direct inserts on instruments with an own position (like V1, V2, VA, VC etc.)
Click to expand...
Same here. I've been doing some pre-panning going into the plugin for separating Horns 1-4 and the various woodwind/percussion sections as well.
 
Ike said:
I was about to purchase this especially at this price but the computer usage and noise issues has gotten me scared. I would use it for every section in the orchestra and that would be a lot of instances. I’m running a newer i7 with 64 gb of ram and I never have issues with my computer coming close to 100 % usually runs around 30-40 % with a full 50 track piece loaded with fxs. Peter is this something that will be fixed in the future and should I wait till the kinks are worked out? Will this intro price last a little longer? Forgot to mention I’m on windows 11 Cubase 12.50. Thank you so much !!!!
Click to expand...
The current intro price will run until the end of the year.

The fixes for the current issues are being tested (rather a few days more than the previous hurry).

The loud noise issue was very likely in the EQ department, which has been rewritten in the last days (the processing part), with 64 bit processing; faster and more accurate as a side-effect.

The validation issue was the plugin blowing up the AU validator when it was told to process at 22.5 kHz. An internal downsampler was switched on to up-sample - not anticipated buffer overruns, but easy to fix.

Emailing issues from the website will hopefully be fixed now I am switching to Mail Chimp, not in the first place for marketing emails, but for the so-called transactional emails (confirmation, download links).

Even with quite some convolutions being calculated, the processing should still be light. On a medium i5 laptop I have used 16 instances (all mics) for a demo, at 50% CPU in Reaper. I advise proper routing with groups and not to add so many full length reverb tails.

TIP: if you set a reverb channel's tail to zero, it will stop calculating the tail part after 2 seconds. The mute can't do that, as you would miss reverb when you toggle it back on. This was meant for positioning-only. I will be made a more understable setting in a next version (so, one toggle for positioning, making processing extremely light).

The late December update will have an option for enabling the multi-threading (which is off in the first releases), making calculations even lighter. Another option will be the first lossy computations option (there are more eggs in the basket, but not all will be added at once).
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom