search

stoermelder / vcvrack-packone

Modules for VCV Rack
GNU General Public License v3.0
179 stars 40 forks source link

MIDI-CAT total recall on opening the patch. #123

Closed nnbveh closed 4 years ago

nnbveh commented 4 years ago

I'm using MIDI-CAT with touchOSC controller app through touchOSC bridge. The combo works perfectly(so far at least), and i'm getting two-way communication. The problem is, when i start both Rack and touchOSC and open a patch, the values set for all the mapped parameters in vcv rack are not being send to the touchOSC. There's a simple workaround i've found: i just initialize MIDI-CAT from the context menu, and then undo it - voilà! all the knobs and faders in touchOSC now have the same values as my patch... Since it is technically possible, could it be implemented in the module itself? So when we open a patch which has MIDI-CAT in it mapped already to some parameters it would send all the values to the external midi device(in this case touchOSC).

stoermelder commented 4 years ago

I guess this is a problem on touchOSC-side as it works with hardware MIDI controllers exactly this way. @vcvrackideas you use touchOSC most of the time, does this work for you?

nnbveh commented 4 years ago

I see. i've tried it more and it works if i start touchOSC first, leave the config menu, and THEN open the patch. I guess there's nothing to do here but to remember to open both in the right order. Although it would be great to have an option to be able to send all the values manually...Thanks for the fast response! I'll contact the developer of the app and ask him if there's a way to improve this.

vcvrackideas commented 4 years ago

I'm using MIDI-CAT with touchOSC controller app through touchOSC bridge. The combo works perfectly(so far at least), and i'm getting two-way communication. The problem is, when i start both Rack and touchOSC and open a patch, the values set for all the mapped parameters in vcv rack are not being send to the touchOSC. There's a simple workaround i've found: i just initialize MIDI-CAT from the context menu, and then undo it - voilà! all the knobs and faders in touchOSC now have the same values as my patch... Since it is technically possible, could it be implemented in the module itself? So when we open a patch which has MIDI-CAT in it mapped already to some parameters it would send all the values to the external midi device(in this case touchOSC).

Just open touchosc layout first, all knobs down, run touchosc bridge if you use it and only then, at last run VCV Rack patch which was been already mapped to this layout. Profit!) This is because MIDI-CAT send midi feedback when it's opening

nnbveh commented 4 years ago

I'm using MIDI-CAT with touchOSC controller app through touchOSC bridge. The combo works perfectly(so far at least), and i'm getting two-way communication. The problem is, when i start both Rack and touchOSC and open a patch, the values set for all the mapped parameters in vcv rack are not being send to the touchOSC. There's a simple workaround i've found: i just initialize MIDI-CAT from the context menu, and then undo it - voilà! all the knobs and faders in touchOSC now have the same values as my patch... Since it is technically possible, could it be implemented in the module itself? So when we open a patch which has MIDI-CAT in it mapped already to some parameters it would send all the values to the external midi device(in this case touchOSC).

Just open touchosc layout first, all knobs down, run touchosc bridge if you use it and only then, at last run VCV Rack patch which was been already mapped to this layout. Profit!) This is because MIDI-CAT send midi feedback when it's opening

I've just replied with exactly this...Would be great to be able to send it manually any time though. OH, i saw an option to import a midi map preset, but i don't see a way to export it, how does one save them?

Thanks!

stoermelder commented 4 years ago

I just added a context menu option for that. I did not test it but it should work as expected.

OH, i saw an option to import a midi map preset, but i don't see a way to export it, how does one save them?

You can't. I don't see any use for exporting presets to MIDI-MAP. Why do you want that?

nnbveh commented 4 years ago

Cool. Thanks!

You can't. I don't see any use for exporting presets to MIDI-MAP. Why do you want that? Dunno, why is there import? I thought it was so we could load pre-mapped configs no? I was basically just wondering why there's this option at all, without having a real need for it yet, sorry)

stoermelder commented 4 years ago

Maybe you misread something. The import function is for VCV MIDI-MAP in case you have set up all your mappings in the stock module and you want replace it with my module.
Presets can be saved and opened in the "Preset" submenu but presets make not really sense for MIDI-CAT as mappings are specific for a set of modules which won't reappear in any other patch.

nnbveh commented 4 years ago

Now i get it, thanks. I thought it was some sort of mapping presets specific to this module...