×
What's new
By:

Samplicity announces Berlin Studio plugin

Peter Emanuel Roos said:
Are you sure you typed 10.3.6?

From 2004?

https://apple.fandom.com/wiki/Mac_OS_X_10.3.6
If so, this must be caused by the code not being supporting that OS and processor (?)
Settings were used for MacOS 10.14 and Intel processors that support the AVX instructions (available for some 10 years).

If you have a more recent MacOS version, I can make a special build for your configuration, to test if this might resolve the CPU load issue. I will take this offline with you via email (expect it later this weekend from my deltaworks.nl domain). I am curious and hope to learn from this.

The AVX flag was set in this 1.0.2 update - not in the first 1.0.1 release. Maybe a hint for me.

Be aware that validation in Logic is a process that can easily send false negatives, by caching etc. The next installer will include a cleaner tool for first removing previous plugin files. Does Logic show that you now have the 1.0.2 version? This is now also (barely) visible in the lower left corner of the plugin window.

The processing inside this plugin is rather light compared to other convolution-based plugins. It should not slow down regular computers.

Regards,
Peter
Click to expand...
10.13.6 of course, sorry. The machine is old (mid 2010) but not that old ;-) I saw the hint that it´s not tested, but it worked with 1.0.1 and passed validation.
Yes, the plug in shows 1.0.2 in Logic and I´ve seen other users reporting, that it´s pretty light on CPU. Maybe it´s related to BigSur ? Unfortunately I can´t update the OS on my slave, but if it solves the problem I would move to Monterey on my Logic host machine.
Would you prefer, if I send a mail to your support address instead of posting this here ?
 
AAX will expand the usability of the Plug-in. Hope every effort to get in to the daw works great!

I will wait till everything works on that platform
 
Chris Hurst said:
It is a really impressive sounding plugin, so if you need any help with the logic/Big Sur issue, then just let me know - happy to test.
Click to expand...
Well, to reassure everyone in this "support" thread - as it has turned into - not a single issue has been found related to the complex convolution technology inside.

These are edge cases, nasty ones, related to I/O and parameter handling.

Thanks for you offer Chris
 
Heinigoldstein said:
10.13.6 of course, sorry. The machine is old (mid 2010) but not that old ;) I saw the hint that it´s not tested, but it worked with 1.0.1 and passed validation.
Yes, the plug in shows 1.0.2 in Logic and I´ve seen other users reporting, that it´s pretty light on CPU. Maybe it´s related to BigSur ? Unfortunately I can´t update the OS on my slave, but if it solves the problem I would move to Monterey on my Logic host machine.
Would you prefer, if I send a mail to your support address instead of posting this here ?
Click to expand...
I will contact you later this weekend by email
 
Peter Emanuel Roos said:
The MacOS binaries contain an Intel layer and a Silicon layer, they should not be run via Rosetta at all - can you tell me how you are using that? I am not an Apple expert, maybe I miss something.

Is one of the hosts enforcing Intel code to be run via Rosetta on M1 and not using Silicon itself? If so, would separate Intel and Silicon versions of the plugin help, or am I still too confused at this moment?
Click to expand...
AFAIK, for Apple Silicon native mode:

* Cubase 12 only runs VST3 that are Apple silicon binaries
* Studio One runs AU as native AS, if it exists, or via Apple’s AUHostingCompatibilityService (Rosetta2); VST3s only run if they are AS native (no R2)

And when running the executables on Rosetta2 compatibility mode:

* Cubase 12 runs both VST2 and VST3 Intel x64
* Studio One runs VST2/VST3/AU for Intel x64
 
Last edited:
Olympum said:
AFAIK:

* Cubase 12 Apple Silicon only runs VST2/VST3 that are Apple silicon binaries
* Cubase 12 Rosetta2 runs VST2/VST3 Intel64 R2 wrapped (the difference here is that with a Universal binary, the Intel64 version gets picked up, not the AS one)
* Studio One Apple Silicon runs AUs with AS, if it exists, or it R2 wraps the Intel64 binary; VST3s only run as AS native (no R2)
* Studio One Rosetta2 runs VST2/VST3/AU Intel64 R2 wrapped
Click to expand...
I am happy that the compiling, bundling and signing of all binary files for MacOS runs automatically on my build computers. This is completely impossible to do manually.

When the website is updated I will start making downloads with CPU specific versions

Thanks again for these details!
 
Runs here in Logic 1.7.5 now. It really sounds impressive! MacStudio Ultra Monterey 12.6.1

Hi CPU usage though, but i think it's one of the Apple teething troubles: Logic shows the active core up to 100% and the CPU level is pulsing, even without input. Happens on other plugins too, Vienna Synchron (ok, it's Rosetta), SWAM instruments, Unify and depending on the loaded sound also Kontakt. If you compare Logics CPU meter and the activity monitor it shows very different CPU usage. But if Logics avtive CPU hits the ceiling there's crackling.


CPU.jpg
 
Saxer said:
Runs here in Logic 1.7.5 now. It really sounds impressive! MacStudio Ultra Monterey 12.6.1

Hi CPU usage though, but i think it's one of the Apple teething troubles: Logic shows the active core up to 100% and the CPU level is pulsing, even without input. Happens on other plugins too, Vienna Synchron (ok, it's Rosetta), SWAM instruments, Unify and depending on the loaded sound also Kontakt. If you compare Logics CPU meter and the activity monitor it shows very different CPU usage. But if Logics avtive CPU hits the ceiling there's crackling.


Samplicity announces Berlin Studio plugin
Click to expand...
Hi Torsten,

If I can provide extra dedicated, single CPU versions, this should be completely solvable, don't you think?

To make their purpose very "clear", they will need to have either Intel or Silicon in their name, else everything will become even more confusing ;)
 
Peter Emanuel Roos said:
Hi Torsten,

If I can provide extra dedicated, single CPU versions, this should be completely solvable, don't you think?

To make their purpose very "clear", they will need to have either Intel or Silicon in their name, else everything will become even more confusing ;)
Click to expand...
If I recall, Logic tends to have problems when plugins try to manage multi-core processing on their own. It works much better when the plugins allow Logic to do the core allocation. Thus plugins like u-he Diva have "multiprocessor" on/off toggles right on the front panel.
 
Trevor Meier said:
If I recall, Logic tends to have problems when plugins try to manage multi-core processing on their own. It works much better when the plugins allow Logic to do the core allocation. Thus plugins like u-he Diva have "multiprocessor" on/off toggles right on the front panel.
Click to expand...
Exactly for this reason I have switched off the multi-threading in my convolution engine. I did not want to take any risks with my first releases. So there is only processing in the "callback" from the host, nothing special.

Future updates of Samplicity plugins will run lighter / smoother when I do enable the multi-threading and/or make it optional.
 
Been testing the reverb throughout the morning. Ended up replacing all my current spacialization solutions. It sounds incredible and it's very versatile. I love the interface as well. Super convenient.

In case it helps somehow: In Reaper it is running like a charm. On Ve Pro not so much. On my end it seems to be the interface that is quite cpu heavy and slows ve pro to a crawl but only while I keep the interface open. I don't have a dedicated video card so that might be related.

My specs are i7 8700, 64 gb ram and windows 10.

Again, amazing work. Definitely ground breaking.
 
I want to add my request for iLok machine autorización to, is a must need, when everything was ready ported to their license scheme
 
Ivan Duch said:
Been testing the reverb throughout the morning. Ended up replacing all my current spacialization solutions. It sounds incredible and it's very versatile. I love the interface as well. Super convenient.

In case it helps somehow: In Reaper it is running like a charm. On Ve Pro not so much. On my end it seems to be the interface that is quite cpu heavy and slows ve pro to a crawl but only while I keep the interface open. I don't have a dedicated video card so that might be related.

My specs are i7 8700, 64 gb ram and windows 10.

Again, amazing work. Definitely ground breaking.
Click to expand...
Wow, thanks so much!

I have unfortunately no experience with VE Pro at all, did not have VSL products in my DAW in the last many years (I did in the last GigaStudio years, the content was really great, but I don't want vendor locking like that - ok, everyone does that now ;-) )

From a plugin's (or my ;-) perspective it is just a host - I have no idea yet about its architecture and if there could be reasons to have less "time" or CPU available for the plugins that run in it.

Does it run itself within some kind of wrapper (no time to check that, sorry)

The GUI indeed requires some processing power, if you close it, that usage is entirely gone and only the reverb processing remains. Weird that this makes a difference though! It is simple 2D graphics, a fair video card is already OK.
 
Flyo said:
I want to add my request for iLok machine autorización to, is a must need, when everything was ready ported to their license scheme
Click to expand...
Why will you not be able to use an iLok dongle or iLok cloud? Do you have a reason for machine-based?

I will receive the Pace / iLok development software next week and start integrating it. This will take at least two weeks of development, I have been told.
 
Peter Emanuel Roos said:
Why will you not be able to use an iLok dongle or iLok cloud? Do you have a reason for machine-based?

I will receive the Pace / iLok development software next week and start integrating it. This will take at least two weeks of development, I have been told.
Click to expand...
Exactly the reason is for mobile portability without hanging around with one USB stick for ilok, leave it free for usb instruments and so on… l also work without cloud based authorization is needed in venues without WIFI
 
Flyo said:
Exactly the reason is for mobile portability without hanging around with one USB stick for ilok, leave it free for usb instruments and so on… l also work without cloud based authorization is needed in venues without WIFI
Click to expand...
When I am more experienced with the Pace software I can make a well informed decision.
 
Hi Folks, I received an email with the link for the Berlin Studio 1.0.2 update on Windows (earlier this morning UK time).
I've tries both Edge and Chrome browsers and I'm getting this error. So, I can't get access to the update.

Cheers...

Anyone else having this problem?
Samplicity announces Berlin Studio plugin
 
You must log in or register to reply here.
Back
Top Bottom