Midi Controller deactivates while load (solved)

[clemens]

Hello Forum,

I´m very new to Flowstone but could figure out a lot so far. I really enjoy workin with this Tool.
Also i´m Enjoying this Community a lot... People here are very Respectfull with each other and dont seem to be afraid to share their knowlege. Only reading a lot of your Posts/Threads and Comments helped me a lot to understand very quickly how everything works.
I´m experimenting with Flowstone scince 3 Month now and created a little VST Plugin.
I have following Problem now.

The issue i have happens in FL STUDIO. In Cubase everything works nice.
When i switch the Instrument with the Preset Manager while playing Notes with the Midi Controler in 60% the Midi-Input Information gets lost. Means: The Midi Controler gets deactivated. I have to go to the Settings of FL-STUDIO and re-activate (disable/enable) the Midi Controler to be able to input the Midi Notes to the VST. The Plugin doesnt crashes or whatever... as soon as i have re-enabled the Midi Input Controler i am able to continue playing the Instrument inside the VST. It´s just the Midi information that get´s lost.

I had the idea to cut the Midi Chain with a selector when the Load Button gets hit and send the Load Signal Delayed to the SAVE/LOAD Module. But this doesn´t seem to be a Solution that works.

Has anyone an idea how to work around that or had experienced the same Problem ?

kind regards

[MyCo]

Have you tried triggering the "clear audio" primitive on preset load? This should kill any active voices.

I haven't heard of that particular problem, though.

[RJHollins]

Are you, by chance, bridging your plugin to a 64-bit system ??

[Perfect Human Interface]

In FL Studio you need to make sure you have the correct channel highlighted in order to send MIDI from your controller (keyboard?) to the plugin. Check that first.

If you have the channel selected but the MIDI input seems to stop working, check if the plugin still responds to MIDI from the piano roll. If it responds from the piano roll but not from your controller, it may be your controller or its driver that's at fault, or for some reason not working well with FL.

[clemens]

Hey Guys,
thanks for the quick replys so far. Some more Facts:

@MyCo:
Triggering the "clear audio" primitive with load signal makes the whole daw crash !

@RJHollins:
No... its running in 32Bit Mode in Fl Studio. Whats crazy......... when i run the VST in Bridged Mode the issue is gone
But i want to make it work without Bridged Mode because i dont want users to force to run it in Bridged Mode.

@PerfectHumanInterface:
Midi Setup and everything is okay. I´m making Music scince 10 Years now. My Midi Keyboard is from akai and i had never a Problem like this before in any other Software(VST).
When the Midi stops workin i can still send notes with the Piano Roll to the VST.. this Works. It´s really the Midi Connection between the DAW and the Midi Driver that crashes. If it crashed and i go to settings i can deactivate and immediately enable the midi controler again and then i can continue sending notes to the VST.

[clemens]

i´ve really trd everything. I was deleting several Elements from the Shematic. Even if i dont connect the Midi Input to anything and Load a Preset from the Presetmanager i have this Problem.

What i could figure out so far.
When i deactivate the Midi Keyboard inside the FL-Studio Midi settings and add a "MIDI in Sel" primitive to the shematic it works. I can play the Keyboard via Channel 0 and never experienced a crash while holding keys+changing instruments.
It seems like its a Communication Problem Between the "MIDI IN" primitive and "FL STUDIO MIDI SEND"

It´s not an Option for me to force People to deactivate the Midi Controler inside Fruity to make the VST work with a Midi Keyboard.

i´m frustrated guys

[RJHollins]

......... when i run the VST in Bridged Mode the issue is gone

Not that I have any answer ... but there may be a clue from this.

As I understand, running in 'bridge' mode is like a 'separate/dedicated process' ... this 'might' be interpreted as an external MIDI source [i don't really know]

As I continue to guess and grab for straws I've have experience, what's called, losing focus of a plugin. It can stop all communication [audio and midi] to the host.

Hopefully someone knows the cause/solution. Sorry I can't help more

[clemens]

No Problem, thanks for your help so far.

The Presets i´m loading are big. It takes 1-2 Seconds to load the next preset. I think when Fl Studio Sends the Notes to the VST and get´s no Feedback because the VST is moving data to the Memory it deactivates the Midi Source.

Like i said, when i use the "Midi in sel" primitive and send the midi notes directly in the VST and not to the DAW the Problem is gone. Weird Stuff !

[RJHollins]

I understand ... I have a VST controller that talks to a collection on 'samplers' ... libraries can definitely take time to load.

Also, the possibility of conflict when re-loading a project ... my 'MIDI Controller' is a FS - VST that stores presets. Each sampler setting is also being stored and loaded by the DAW. For my project, I use a special TIMER that switches the controller-MIDI OFFLINE for a user defined time period. Otherwise, the loaded samplers can get 2 sets of reloading info. This is just my way ... can't say its the proper way, or absolutely necessary, but it has worked.

As for the MIDI standard protocol, I'm not sure if there is a confirmation or a 'ready to receive data' message that handshakes. Maybe one of the resident experts can enlighten us

[clemens]

how you switch the midi controler to offline ?