OP
OP
Peter Roos
Senior Member
Yes, iLok 2/3 dongle and cloud, not machine identification
Samplicity announces Berlin Studio plugin
- Thread starter Peter Roos
- Start date
- Watchers 129
wunderflo
Senior Member
Looking forward to that! Hopefully there will be a nice upgrade path.
Trash Panda
Clueless nitwit
@Peter Emanuel Roos how should we be preparing the input signal going into the reverb?
For example, let’s say we have three trumpets intended to be trumpets a3 through Berlin Studio.
Should trumpet 1 be mostly left, trumpet 2 centered and trumpet 3 mostly right before it gets fed into the trumpets section of Berlin Studio?
For example, let’s say we have three trumpets intended to be trumpets a3 through Berlin Studio.
Should trumpet 1 be mostly left, trumpet 2 centered and trumpet 3 mostly right before it gets fed into the trumpets section of Berlin Studio?
Obi-Wan Spaghetti
Senior Member
I hope we get at least 2 license per 1 purchase? i like to have a 2 keys.
Hi @Peter Emanuel Roos
Dumb question. I don’t notice a wet/dry knob in the screen shots? Or have I simply missed this? I trust this plugin is not only for use as an insert?
Thanks
Dumb question. I don’t notice a wet/dry knob in the screen shots? Or have I simply missed this? I trust this plugin is not only for use as an insert?
Thanks
portego
Member
Interesting concept.
Basically, the principle of IK's Fame Studio Reverb (with the different positions) but turned up to 11 for a whole orchestra... Love it
. Especially since you apparently can remove the tail reverb -> Instant positioning and depth?
But what i don't really get is, how you would add an ensemble patch into this concept? Sections (divisi) seems straight forward -> Each Section = 1 Position. But let's say, you did that, but you want to layer the strings with a library that only has an ensemble patch. What would be the approach for that? Put it on the Woodwinds section and adjust the delay?
Basically, the principle of IK's Fame Studio Reverb (with the different positions) but turned up to 11 for a whole orchestra... Love it
. Especially since you apparently can remove the tail reverb -> Instant positioning and depth?But what i don't really get is, how you would add an ensemble patch into this concept? Sections (divisi) seems straight forward -> Each Section = 1 Position. But let's say, you did that, but you want to layer the strings with a library that only has an ensemble patch. What would be the approach for that? Put it on the Woodwinds section and adjust the delay?
rudi
Senior Member
You just turn the "Dry Signal" down to 0 or mute it, and leave any of the wet signals on.
rudi
Senior Member
Yes, you can use the Woodwind location (or even the percussion positions) or alternatively the front or mid surround positions and choose the one you like best. Then adjust the dry signal delay to bring the ensemble forward to taste as needed.
Henrik B. Jensen
Senior Member
Can I use Berlin Studio as a tail reverb on the master bus without selecting any position?
i.e. as a “normal” tail reverb on master bus
i.e. as a “normal” tail reverb on master bus
rudi
Senior Member
As far as I know you have to select a position. Depending on the position you select the nature of the reverb tail will change. I've tried the front surround, mid-surround, woodwinds, percussions and choir position and each one has its own character, including width, since they are real locations. Some of the results are quite pleasant!
Henrik B. Jensen
Senior Member
I didn’t consider that the tail would be different pr. position, good point!
I’ll experiment with it
tabulius
Senior Member
I would like to know this as well!
rudi
Senior Member
You can pan the individual trumpets (or other instruments) as required. Since the impulses are true stereo, they will reflect the instruments pan positions.
A few things to bear in mind however:
A dry source signal panned in the middle is ideal as you can pan it as required either in the VSTi itself, or by adjusting BST's (Berlin Studio) input channel L and R levels as a pan control.
As well as changing the source position you can also control the width of the signal, e.g if you pan both L and R fully to the right you'll effectively end-up with single point fully panned to the right. By increasing the level between L + R, you can increase the perceived width of the signal, but as a rule solo instruments tend to be single point sources.
If the dry source signal is already pre-panned that works too, and you can still re-position it using the method above.
If the dry source signal is stereo that works the same as above, but avoid decreasing the width to a single point.
If using an ensemble source e.g Trumpet A3, you can also adjust the pan and width as above but be aware that there is likely some spatial information already in the signal and you can't be as extreme as with a mono signal. Of course you can use more extreme pan positions and width if you don't want to stick to a more realistic layout.
You can also play with the ER and Tail balance to create a more precise or more diffuse sense of position.
In practice I have found only a subtle audible difference between 3 individual trumpets panned L, C and R across the trumpet location, and all three being panned to the same position, as the width of the trumpet location is quite narrow, corresponding to a distance of only few feet between the individual instruments.
Your mileage may vary!
A few things to bear in mind however:
A dry source signal panned in the middle is ideal as you can pan it as required either in the VSTi itself, or by adjusting BST's (Berlin Studio) input channel L and R levels as a pan control.
As well as changing the source position you can also control the width of the signal, e.g if you pan both L and R fully to the right you'll effectively end-up with single point fully panned to the right. By increasing the level between L + R, you can increase the perceived width of the signal, but as a rule solo instruments tend to be single point sources.
If the dry source signal is already pre-panned that works too, and you can still re-position it using the method above.
If the dry source signal is stereo that works the same as above, but avoid decreasing the width to a single point.
If using an ensemble source e.g Trumpet A3, you can also adjust the pan and width as above but be aware that there is likely some spatial information already in the signal and you can't be as extreme as with a mono signal. Of course you can use more extreme pan positions and width if you don't want to stick to a more realistic layout.
You can also play with the ER and Tail balance to create a more precise or more diffuse sense of position.
In practice I have found only a subtle audible difference between 3 individual trumpets panned L, C and R across the trumpet location, and all three being panned to the same position, as the width of the trumpet location is quite narrow, corresponding to a distance of only few feet between the individual instruments.
Your mileage may vary!
Last edited:
Thanks! Bought it yesterday. The one instance per track and mute the others is what I've figured outIf you use two instances, you can set it up.
Quantum Leap also uses that approach and claim Surround support
Hehe, no I will not say Berlin Studio supports multi-channel this way.
But (!): if you set the tail level of any reverb channel to zero, after 2 seconds there will be no more CPU use for that channel. So if you do this with the surround mics channel, you can it in a second instance (without Decca and AB) with hardly any additional CPU load.
I am aware that "Surround mics" is confusing in this context. Maybe I should call them Very Wide And High...
Of course a surround version is in the planning, with proper panner controls and routing, but this will not be available before spring.
. Mixing my next film in 5.1 so I'll test this out. I've recorded flutes, guitars, clarinets and percussion this week so I'll def post some examples when I'm finished with it. Also in comparison to MIR.Hope machine based activation can be included sometime in the future. No go for me personally till then.
constaneum
Senior Member
One question. I'm aware that it works best with close dry recorded instrument. However, does it work best with centrally recorded or fine with recorded in SITU?
portego
Member
Can confirm that it works on a AMD CPU and in FL-Studio.
One instance of "Berlin Studio" uses on a AMD 5950x around 1% of the FL-Studio CPU-Meter. Would say, a little less than 1%, because the 1% Rule applies to about 80-90% or so. It is obvious that multithreading is not implemented yet, but "Peter Emanuel Roos" confirmed this in the "Berlin Studio - The Ultimate Reverb Test" thread and is working on it. So yeah, even if it is not optimised for AMD i don't see any problems but looking forward to the next update. Multithreading for the win
Btw. Played around only a little bit. So far I can say, it sounds amazing with VHorns and:
- Install Process was not a problem on Windows 10
- Also no virus alarm (which was mentioned on the homepage, it could happen)
- But install process is probably not finished, couldn't choose the drive (-> went to windows drive)
- A link parameter for the delays would be awesome (link all the knobs together)
- The delay knob didn't pushed it far enough in my first little test. My idea was, to push a string ensemble patch (front stage) to/behind the individual strings (with delay), but it didn't worked as planned -> ensemble on middle stage was fine. But this could also be problem of the string library (only tested it with 8Dio Majestica).
- Some kind of auto panning would be nice. In my test, the dry signal was just where it was (Example: Horn reverb left, but dry signal of the Horn in the middle). There are knobs in the plugin to pan it, directly in the plugin. But in my head I was thinking: "Why doesn't the plugin just pre-pan for an individual positon? Or why aren't there 2 settings for each stage (one pre-panned, one free). I'm a lazy bastard and it would just make sense in my head -> Every instrument center and remove the reverb -> Choose place and the option of pre-panning and voilà
. I mean, than you would have the exact angle of the panning for each position... But i get it, there would have to be 2 options, because some libraries are allready panned...
Yeah, this is my first impression of this neat reverb. Like it so far.
One instance of "Berlin Studio" uses on a AMD 5950x around 1% of the FL-Studio CPU-Meter. Would say, a little less than 1%, because the 1% Rule applies to about 80-90% or so. It is obvious that multithreading is not implemented yet, but "Peter Emanuel Roos" confirmed this in the "Berlin Studio - The Ultimate Reverb Test" thread and is working on it. So yeah, even if it is not optimised for AMD i don't see any problems but looking forward to the next update. Multithreading for the win
Btw. Played around only a little bit. So far I can say, it sounds amazing with VHorns and:
- Install Process was not a problem on Windows 10
- Also no virus alarm (which was mentioned on the homepage, it could happen)
- But install process is probably not finished, couldn't choose the drive (-> went to windows drive)
- A link parameter for the delays would be awesome (link all the knobs together)
- The delay knob didn't pushed it far enough in my first little test. My idea was, to push a string ensemble patch (front stage) to/behind the individual strings (with delay), but it didn't worked as planned -> ensemble on middle stage was fine. But this could also be problem of the string library (only tested it with 8Dio Majestica).
- Some kind of auto panning would be nice. In my test, the dry signal was just where it was (Example: Horn reverb left, but dry signal of the Horn in the middle). There are knobs in the plugin to pan it, directly in the plugin. But in my head I was thinking: "Why doesn't the plugin just pre-pan for an individual positon? Or why aren't there 2 settings for each stage (one pre-panned, one free). I'm a lazy bastard and it would just make sense in my head -> Every instrument center and remove the reverb -> Choose place and the option of pre-panning and voilà
. I mean, than you would have the exact angle of the panning for each position... But i get it, there would have to be 2 options, because some libraries are allready panned...Yeah, this is my first impression of this neat reverb. Like it so far.
portego
Member
Correction: There is a bug with FL Studio
The stage location will not be saved with FL Studio. The faders are fine, but the stage location will be the default "violin 1" when you save and open a project with FL Studio.
@developer team: is this fixable? Asking shyly as it kind of messes up my whole plan...
The stage location will not be saved with FL Studio. The faders are fine, but the stage location will be the default "violin 1" when you save and open a project with FL Studio.
@developer team: is this fixable? Asking shyly as it kind of messes up my whole plan...
aileero
Member
Agreed, just ran into this issue as well
A similar thing happens when you use the click and drag on the "save preset as..." on the mixer to drag the plugin with the same settings onto a different mixer track.
Strangely, saving the preset (in fl studio) and then loading it still works, so it probably has to do something with how the plugin is initialized.
constaneum
Senior Member
For FL Studio users who have unsaved stage location issue, you may opt for the "Make bridged" option which works while waiting for Peter to resolve this.
