×
What's new

Samplicity announces Berlin Studio plugin

I don't have much time this morning to play with it, but when I read @Saxer 's post, I thought, "Hey it is worth a shot." So I opened Logic in Rosetta mode, and so far as I can tell with my limited fiddling, the plugin works fine. Perhaps others can verify. (And hell, maybe this is expected behavior--I wouldn't know that.)

Beautiful sound, BTW!
Thank you for trying this, it may help me with my investigations. This means I have to pay extra attention to the Silicon specific parts of the software.
 
I am zooming in on a point in the code where something is not OK anyway, in a Mac Silicon environment (at least). This is slow work, but I will not let go ;-)
This is for the mentioned issues with strange sounds and the input for the EQ.
I do my best not to bother you with too much technical terms, I know I often do that ;-)
The AU validation is probably something else that may be quicker to find and fix.
 
Great plugin, I am really enjoying it!!
Only one question: to be able to use it it seems I have to keep the PC connected to internet, otherwise it doesn't work. Am I doing anything wrong or is there a workaround?
Update: unfortunately this is in my code - but it will be changed to "semi-offline" in any future update, like a soon upcoming fix for the AU things.
 
Update: unfortunately this is in my code - but it will be changed to "semi-offline" in any future update, like a soon upcoming fix for the AU things.
Thanks Peter! It'll be interesting to know what "semi-offline" involves. It also might be a good idea for it to be made clear in the description/requirements of the plugin! :)
 
Thanks Peter! It'll be interesting to know what "semi-offline" involves. It also might be a good idea for it to be made clear in the description/requirements of the plugin! :)
I agree, but it's a bit busy at the moment ;-) noted
Several weeks of offline use without internet access, I would expect that myself as user
 
I agree, but it's a bit busy at the moment ;) noted
Several weeks of offline use without internet access, I would expect that myself as user
No problem! I understand how extremely busy things are for you at the moment :2thumbs:.
I'd also like to highlight the excellent customer support you provide, and how outstanding Berlin Studio is. :dancedance:
 
@Peter Emanuel Roos : Maybe you didn't see my last message (wouldn't surprise me... :-) ),
however, the problem with offline bouncing is serious at the moment (which is inside of Metaplugin inside of Logic).

Usually it starts bouncing for a short while and then finishes the process without leaving a bounced snippet. Afterwards, Logic shows me the spinning ball.

I hope, this will be no further issue once the AU version is working.

(Offline bouncing is mandatory for the way I work, with lots of CPU hogs on the Masterbus)
 
@Peter Emanuel Roos : Maybe you didn't see my last message (wouldn't surprise me... :) ),
however, the problem with offline bouncing is serious at the moment (which is inside of Metaplugin inside of Logic).

Usually it starts bouncing for a short while and then finishes the process without leaving a bounced snippet. Afterwards, Logic shows me the spinning ball.

I hope, this will be no further issue once the AU version is working.

(Offline bouncing is mandatory for the way I work, with lots of CPU hogs on the Masterbus)
I know in which specific part / lines the issue with Logic on Silicon is...
It results in huge internal values, that clip, distort or silence the host.
I guess it also causes your offline bounce problems, as that uses the same incorrect calculation(s).
It would be nice if I could send out a well tested update tomorrow.
I will also run offline bounce tests - noted ;-)
 
Lol, then there is a third "Logic" issue. I expected it to be explainable by what I found today.
Will test that as well thoroughly in a realistic session setup, with debuggers.
Sorry if I miss details, a bit busy ;)
Honestly, I think it could also be related to Metaplugin itself.
When there is an AU version, I can immediately report back if the issue still is there.
 
Peter, one question:

Close mics of instruments - they contain early reflections that tell our brain that the instrument in question is not very far away from us as listener, right?

When we add Berlin Studio to such an instrument, won’t the instrument’s “close mic ERs“ mean our brain is perceiving the resulting sound as “not quite right”?

Hope it’s understandable!
 
Peter, one question:

Close mics of instruments - they contain early reflections that tell our brain that the instrument in question is not very far away from us as listener, right?

When we add Berlin Studio to such an instrument, won’t the instrument’s “close mic ERs“ mean our brain is perceiving the resulting sound as “not quite right”?

Hope it’s understandable!
That is actually what the delay(s) in the plugin are/were meant for. Especially the one in the dry input channel.

There is an approach used by a number of classical recording engineers:
- Use overall microphone sets, like the Decca Tree, or what you often see in concert halls hanging from the ceiling: an AB-Pair
- But also use spot mics at low levels
- Delay the sound of these spot mics with a time equivalent to the instance to the center Decca microphone
- This merges the sounds from the spot mics and the global mics and in the case of samples also puts early reflections back in a correct range

What it also does is - I discovered more recently - is smoothen the transients contained in the dry signal (!), and making them more distant by the EQ effect this has.

For woodwinds, for instance, if I remember well, that delay of the dry signal should be around 18 msec.

My intention is to include an auto-align option in a future version that does this automatically. I have calculated all time delays and thus distances for the stage positions.

This will be done, not by delaying the direct sound, but by skipping all the IR samples until the first significant sound in the Decca center. Meaning that the dry sound will still play immediately, but the global mics start "earlier". I find this very effective and have used it in all my current demos on the Samplicity site.

When we work with samples, there will be no more subtle break between the dry sound, its early reflections and what the global mics pick up.

In this first release I personally find the delays confusing, maybe they should go out, because people may not understand their short range (which is already equivalent to more than the studio's depth). It is different from pre-delays in regular reverbs, this is for such subtle time alignments.

To come back to your question about our perception, if you would look at the IRs from the Decca for the woodwinds, you would see that the ERs start later, after a near silence. Using a sample where the ERs start right away is in theory (and in my view) indeed not the best option, but I am not sure if many people would notice... A nerdy person, like me :-D would experiment with this delay stuff...

A very good topic, that will certainly make it into a blog post, that I hope to be able to write...
Programming can nearly be put aside for a while, then the site and shop need a good update, support with ticketing, FAQ etc, advertizing and then good documentation. Because who reads manuals? ;)

Cheers
 
Last edited:
That is actually what the delay(s) in the plugin are/were meant for. Especially the one in the dry input channel.

There is an approach used by a number of classical recording engineers:
- Use overall microphone sets, like the Decca Tree, or what you often see in concert halls hanging from the ceiling: an AB-Pair
- But also use spot mics at low levels
- Delay the sound of these spot mics with a time equivalent to the instance to the center Decca microphone
- This merges the sounds from the spot mics and the global mics and in the case of samples also puts early reflections back in a correct range

What it also does is - I discovered more recently - is smoothen the transients contained in the dry signal (!), and making them more distant by the EQ effect this has.

For woodwinds, for instance, if I remember well, that delay of the dry signal should be around 18 msec.

My intention is to include an auto-align option in a future version that does this automatically. I have calculated all time delays and thus distances for the stage positions.

This will be done, not by delaying the direct sound, but by skipping all the IR samples until the first significant sound in the Decca center. Meaning that the dry sound will still play immediately, but the global mics start "earlier". I find this very effective and have used it in all my current demos on the Samplicity site.

When we work with samples, there will be no more subtle break between the dry sound, its early reflections and what the global mics pick up. I have used this often in my orchestral templates.

In this first release I personally find the delays confusing, maybe they should go out, because people may not understand their short range (which is already equivalent to more than the studio's depth). It is different from pre-delays in regular reverbs, this is for such subtle time alignments.
Auto-align sounds like a good idea. All this stuff is complex!
 
Back
Top Bottom