Search found 23 matches

by abique
Fri Jan 11, 2019 10:01 am
Forum: VST 3 SDK
Topic: Vst::kDistributable - remote processing
Replies: 5
Views: 158

Re: Vst::kDistributable - remote processing

I think it can be interesting to load the UI in a different process, that would isolate some bugs and also smaller code size in the audio engine.
by abique
Thu Jan 10, 2019 8:01 pm
Forum: VST 3 SDK
Topic: Is it OK for a plugin to call IComponentHandler::restartComponent() from a random thread?
Replies: 3
Views: 61

Re: Is it OK for a plugin to call IComponentHandler::restartComponent() from a random thread?

Hi Arne,

Many thanks for your answer.

Did you mean "must" when you said "try"? ;-)

Regards,
Alex
by abique
Thu Jan 10, 2019 8:48 am
Forum: VST 3 SDK
Topic: Is it OK for a plugin to call IComponentHandler::restartComponent() from a random thread?
Replies: 3
Views: 61

Is it OK for a plugin to call IComponentHandler::restartComponent() from a random thread?

Hi,

I wonder if it is OK for a plugin to call IComponentHandler::restartComponent() from a random thread?
Or this method has to be called from the main thread?
What is the right way for plugin to figure out what is the main thread id?

Many thanks,
Alex
by abique
Tue Feb 13, 2018 1:27 pm
Forum: VST 3 SDK
Topic: Is IComponent::getState()/setState() thread-safe?
Replies: 15
Views: 1532

Re: Is IComponent::getState()/setState() thread-safe?

Thank you very much! :)
by abique
Mon Feb 12, 2018 11:49 am
Forum: VST 3 SDK
Topic: Is IComponent::getState()/setState() thread-safe?
Replies: 15
Views: 1532

Is IComponent::getState()/setState() thread-safe?

Hi, In Bitwig Studio we use IComponent::getState() from the GUI thread. But I cam across a crash where IComponent::getState() was concurrent to a program change executed on the Audio thread. So please, could you guys clarify if getState() and setState() are thread-safe? Also in general I think that ...
by abique
Thu Sep 21, 2017 9:03 am
Forum: VST 3 SDK
Topic: AddressSanitizer: odr-violation
Replies: 13
Views: 3015

Re: AddressSanitizer: odr-violation

Hi,
No I did not.
Alex.
by abique
Thu Sep 07, 2017 3:14 pm
Forum: VST 3 SDK
Topic: AddressSanitizer: odr-violation
Replies: 13
Views: 3015

Re: AddressSanitizer: odr-violation

So maybe there is a gcc/clang attribute we could add to those fields so they are private?
by abique
Thu Sep 07, 2017 1:08 pm
Forum: VST 3 SDK
Topic: AddressSanitizer: odr-violation
Replies: 13
Views: 3015

Re: AddressSanitizer: odr-violation

I mean if I build a single plugin which contains many different plugin interface in one .so: vst2, vst3, lv2, .... If I don't include ../../libs/vstsdk3/base/source/baseiids.cpp in the plugin then I'll rely on the host to provide the symbol. But if one host only implements lv2, then it will not prov...
by abique
Thu Sep 07, 2017 12:25 pm
Forum: VST 3 SDK
Topic: ASSERT macro redefined
Replies: 1
Views: 718

ASSERT macro redefined

Hi guys, it seems that you (re)define a few standards macros in vst3sdk, like ASSERT or DEBUG.

Is it possible to rename those to VST3_DEBUG, VST3_ASSERT, and so on to avoid naming collision?

Many thanks,
Alex.
by abique
Thu Sep 07, 2017 12:17 pm
Forum: VST 3 SDK
Topic: AddressSanitizer: odr-violation
Replies: 13
Views: 3015

Re: AddressSanitizer: odr-violation

But then if a plugin host which does not support vst3, but vst2 opens the plugin some symbols will be missing right?

Go to advanced search