Desperate Help on this project!!!!

[aefa]

Hi Everyone,

I've lost it completely!!!
I need desperate help with this before I go totally nuts!

Keyboard v2.1.fsm

Keyboard 2.1

(27 KiB) Downloaded 873 times

The keys on the keyboard are modified toggle switch buttons and the code is pretty much unchanged (only added couple of lines on the mouseLDown to set click region but the rest is unaltered)
The idea is to create an array of the toggled notes but be able to save them for next session. I added a Preset manager and it saves the key state but when it reloads again (I'm trying with fl studio) the array is gone.
The funny thing is that yesterday it worked but today it doesn't!!!!

Any way to solve this please?

Thank you in advance,

[Spogg]

Hi!

I tested this in FS stand-alone 3.08.1 and it worked nicely. I've made 2 presets, all the Cs and all the Fs.

I can only ask did you use the Save button on the preset manager's Properties view for each preset? Also did you save the whole schematic afterwards? This process is the only way to keep the stuff "inside" the preset manager for when you reload the schematic.
Many apologies if this is insulting your knowledge but it's all I could think of.
I have found that when I start getting weird stuff happening I close FS and re-open and sometimes it's fixed. If not then I know it's me!

Cheers

Spogg

BTW is this going to be an arpeggiator?

[aefa]

Hi Spogg,

Thank you for the help!
Strangely, when I use it in flowstone inside FL it works fine but when I save it to a VST that's when the crazy stuff happens. I can save presets and reload them, no problem. What I mean is, for example, you're using your VST in FL. You tweak it until you get what you want. Then you save the project in FL and close it. Next day you reload you FL project and all settings in your VST are exactly as you left them.
In my case, when I reload, the project the state of the keys are restored but somehow it doesn't pass the note number to the note array. As I said it only happens when using it as an external VST not FL plugin.

You don't insult my knowledge in this matter for I have none whatsoever!!

No, it's going to be a random pattern trigger.

[Spogg]

Hi again aefa

I spent a long time messing around with the VST export in Reaper.

I'll cut to the chase:

The stock Preset Manager doesn't function in Reaper unless the track into which the VST is loaded is set to Record armed mode. I tested this with one of my synths and the behaviour is the same. However, in play mode I can select the presets but the rest of the Preset manager's buttons are recognised by the mouse-over, but they don't operate.

In play mode Reaper doesn't respond to parameter changes on your plugin. If you switch to the basic UI in Reaper there's no change to the VST parameters if you have a key pressed on your UI. This is why the state isn't retained after saving; Reaper is not being told about the change of plugin state.

When I tested your plugin with Record armed everything worked as you would hope. Save the song file, close Reaper, reload and all the changes made before are retained. But only if you save after using Record armed mode to make your changes to keys pressed.
Note that this is with the option to save the whole plugin state enabled in Reaper. I believe this option is under the VST wrapper options in FL but I don't have that DAW to test it out.

I should add that the exported exe works just fine; the Preset Manager works as you'd expect.

I hope this helps...

Cheers

Spogg

[aefa]

Hi Spogg,

I've been working on this on my FL flowstone and then my friend would render the VST for me. Then, in my frustration, I downloaded the flowstone 3.0.8 Trial and the exported vst saves the presets as it's supposed to. So I bought the Full flowstone I tested it in FL and Cubase Elements and it's been working so far. Now I have to put all pieces together but I'm forseeing further problems adjusting the output midi port for the vst.

Thank you very much for your help. I'll post the project when I'm done and hopefully someone can make it better .

BTW the vst that didn't work was rendered with the 3.0.4 version of flowstone. It seem it was more of a compatibility problem because the version in FL is 3.0.8 I believe.

[Spogg]

I do very much appreciate your feedback and good luck with your project

Cheers

Spogg