glowingfish wrote: ↑Thu Jan 24, 2019 6:15 am
Thanks for all the info and it is correct that when you save into the 'midi controller' map in the preset dir of that device/module, you save the CC assignment. Now when I load a device and go to the preset map and go into the midi controller map and click on the saved preset then all midi cc's are assigned again. Then I can load every preset I want and the midiCC's are still assigned. Works great for me and don't have to save a whole project to save the midiCC assignment.
I dunno why, but that saving method never worked for me and the next day when I launched SCOPE and loaded devices, the MIDI assignments were gone except those which are permanent for a given device because they were set in stone w/ SDK already when the device was developed.
glowingfish wrote: ↑Thu Jan 24, 2019 6:15 am
The only thing is that when you start a new project, load a device/module, you have to click on the midiCC preset first in the midi controller map... but that is a piece of cake I think
see above ... what I´m doing wrong ?
What do you mean w/ "save into the MIDI controller
map" ?
Do you mean the MIDI CC preset-file inside the presets folder ?
I tried for several times saving my MIDI CC assignments for a given device into that file, but it never worked as expected, at least for me.
glowingfish wrote: ↑Thu Jan 24, 2019 6:15 am
Indeed I also noticed some bugs when reloading the midiCC midicontroller preset. Some knobs are not assigned anymore. For instance in the Inferno synth, the Tune and the lfo/manual (knob) paramters are not active anymore after loading the midiCC preset. Re-assigned them, stored over the excisting preset and no luck.... I guess a bug.
Well, that´s almost identical behaviour I experienced myself.
glowingfish wrote: ↑Thu Jan 24, 2019 6:15 am
Hopefully it will be solved in the future.
The behaviour should have been changed:
1.)
When MIDI assignments for a device are global,- like they actually are and were:
Once you bring in a device into a project, it should load the latest MIDI CC assignments file automatic,- and when you remove the device from project and made some changes to the MIDI CC assignment for that device before you remove it,- the MIDI CC file should be automaticly overwritten/ auto-saved.
or:
2.)
Make MIDI assignments storable w/ every device´s single presets,- means: Save ´em automatic w/ every preset you save for a given device,- so you can use different MIDI CC assignments w/ every preset (synth´s-, fx-device´s patch).
(Probably doesn´t make much sense for mixers though)
And when you save the project, every MIDI assignment for every device still existing in that project should be autosaved w/ that project in addition,- so once you load that project again, the project loading all the devices, all the MIDI CCassigments should be autoloaded too.
glowingfish wrote: ↑Thu Jan 24, 2019 6:15 am
Maybe is is no issue anymore with the new Scope 7 ? Iam still using 6 and works great for me so far (so good)
Are you sure you´re using SCOPE v6 ?
I use(d) SCOPE v5.1 (32Bit) w/ XITE-1 on a Windows XP 32Bit machine
Bud