Page 1 of 1
FlowStone plugins compatibility
Posted: Tue May 21, 2024 5:34 am
by User108
There's a great piece of software called VstBoard:
https://www.kvraudio.com/product/vstboard-by-ctrlbrk
It even supports scripting.
But unfortunately, any plugin I create with FS does not work in it, saying "error while loading plugin". Why is this and how can it be fixed? May be I place input |output devices wrong way? I tried many combinations - no luck. All other plugins load just fine. And FS plugins in FL Studio load just fine.
Re: FlowStone plugins compatibility
Posted: Tue May 21, 2024 7:58 am
by tulamide
User108 wrote:There's a great piece of software called VstBoard:
https://www.kvraudio.com/product/vstboard-by-ctrlbrk
It even supports scripting.
But unfortunately, any plugin I create with FS does not work in it, saying "error while loading plugin". Why is this and how can it be fixed? May be I place input |output devices wrong way? I tried many combinations - no luck. All other plugins load just fine. And FS plugins in FL Studio load just fine.
Flowstone creates standard VST files. If the host can't read them, you have to contact the developer of the host, to correct the error in the software.
Re: FlowStone plugins compatibility
Posted: Tue May 21, 2024 8:20 am
by User108
But why that host reads other plugins just fine? I use Korg plugins as a reference plugins. That means something is missing in FS plugins, making them impossible to load. And as to "standart vst" - as far as I understand when FS exports VST, it actually exports FS runtime which then autoloads fsm schematics. Native VST plugins act differently.
Re: FlowStone plugins compatibility
Posted: Tue May 21, 2024 9:40 am
by tulamide
User108 wrote:But why that host reads other plugins just fine? I use Korg plugins as a reference plugins. That means something is missing in FS plugins, making them impossible to load. And as to "standart vst" - as far as I understand when FS exports VST, it actually exports FS runtime which then autoloads fsm schematics. Native VST plugins act differently.
I don't know, what else to say? You asked, I gave you the answer. You don't like the answer, but that's nothing I can change.
Maybe ask yourself this question: Why is it, that FS generated plugins run in every host out there, except this one?
When you have an answer to that question, the solution is close.