DSP Robotics Support

i'm thinking and working about this now
i hope i can get a solution very soon.

Hey, this should work...

I did also a correction

Well the preset cc is now direct to GUI DAW BUT - if you change the preset the value of the CC will NOT change.
The value will change if you change it on learning the knob or start up your vsti and the VST parameters are loaded.

Regards

thanks for the responce again.

the one from Tektoog was able to save the Midi-in selector from the DAW, but now the Midi-Learn function
was not working anymore, don't know how to fix this.
because the midi-learn was not working, I can not tell if the midi CC was saved aswell.
could you fix the midi-learn again tektoog?

the one from Chackl did not save the Midi-in selector and CC from DAW, but it saved the midi-in selector from the Vst program manager, but it did not saved the CC.
the midi-learn fuction was working.

would be great that all settings (midi-in device and CC) are saved from the DAW preset.

jan

tomorrow i'm back on my Computer at home.
I'll take a look with a test on it and do a fix

Regards

hey, sorry about the previous non working version... 1 link too much...
This one works...


but recalls the same CC for each preset...
So as long as you have only 1 preset to recall you'll be fine...
As I haven't made the Midi learn system in the schematic I don't know where the bug is...
I might have a look later...

tektoog wrote:hey, sorry about the previous non working version... 1 link too much...
This one works...

rubyknob-v1.3.1 MIDI select - TekTooG.fsm

but recalls the same CC for each preset...
So as long as you have only 1 preset to recall you'll be fine...
As I haven't made the Midi learn system in the schematic I don't know where the bug is...
I might have a look later...

Look

If you Change the preset with presetmanager - No cc Change
If the Parameter is changed without clicking it on the presetmanager - CC will Change

I did this that the CC does not Change every presetmanagement but the Parameters are changed in the DAW to do an auto-load on VSTi

thanks again for your effort.
@Tektoog
the new version has the midi-learn again and the midi-device select is saved by my DAW as before, but the CC is not saved.
so I still have to learn it the CC again.
tried to make a version with just a midi -in, so I have to set the midi in from my DAW, it saved aswell the midi-in device, but still no CC. besides that now my DAW hangs everytime.
@C.hackl
the rubyknob1.4 has the midi-learn function and my DAW saved aswell the midi-in device, but still no CC was saved.
this is wat I maked sofar:

maybe I changed something?

jan

mr.jan wrote:thanks again for your effort.
@Tektoog
the new version has the midi-learn again and the midi-device select is saved by my DAW as before, but the CC is not saved.
so I still have to learn it the CC again.
tried to make a version with just a midi -in, so I have to set the midi in from my DAW, it saved aswell the midi-in device, but still no CC. besides that now my DAW hangs everytime.
@C.hackl
the rubyknob1.4 has the midi-learn function and my DAW saved aswell the midi-in device, but still no CC was saved.
this is wat I maked sofar:

rubyknob-v1.4 MIDI in Chackl.fsm

maybe I changed something?

jan

I you pressed MIDI learn, did you connect an externam MIDI interface module to it?
or did you directly export a VSTi?

hey chackl
this fsm file:
rubyknob-v1.4 MIDI in Chackl.fsm
I exported it directly as a vst, I'm using the free version, so there is the noise, but who cares, it's still a test.
I removed the midi selector and instead i use only a midi-in ( input module).so in my DAW I choose a midi device in.
this midi device in was saved by my DAW, but not the CC.
or should I export it as a Vsti, because the midi?
or do I have to use an external MIDI interface module? in this case, witch one, and has this to be in the vst module?

greetings
jan