Hi all,
I've so far found no way to map 2 or more touch controls to same target directly in Daslight5.
Example:
A fader control will modify the scene speed. This works...
A button control should set the scene speed to a certain value (e.g. 50% which is 1,00x). This also works as I can set in Touch Mappings the mode to "value" and select any value.
But its not possible to have two controls at the same time via Daslight 5 directly.
Thats one example where I need multiple touch controls being mapped to same target.
Another example would be to have on multiple pages a fader which handles the same target, so I do not need to switch between pages.... In Daslight4 this was no problem at all.
BUT: I've found a kind of dirty workaround via xml....
First I create the mappings for the fader and export the preset.
Next I change the mappings from fader to button and export the preset to another file.
Comparing both files using an text editor shows me the differences .
Copy/Paste the difference from <SHORTCUT TYPE="2"><EVENT DATA up to the next occurance of </SHORTCUT> from one file into the other (adding, not replacing), save and import this preset (which now have two controls being mapped to same target). This works without error message.
Now I've got what I need, the fader adjusts the speed, the button resets speed to 0,5 which is 1,00x.
But: Interface is kind of broken at least once I open "Map Touch". The overlay on the controls which have mappings are broken, multiple entries are shown even for controls which have not modified in xml.
Any chance to get such a 1-to-n mapping into Daslight5 as it seems to be nearly done already... Just remove the function which replaces existing mappings and make the overlay show a hint that more than one control is mapped....
Regards,
Frank
Map Touch - not possible to map 2+ touch controls to same target - but possible via xml edit
Re: Map Touch - not possible to map 2+ touch controls to same target - but possible via xml edit
I've played today a bit more with import/export of presets.
It seems to me that Daslight5 will ADD ALL presets during import ON TOP of the already existing presets. This seems the reason for the messed up overlays...
This becomes handy as I can now
1. export with first mapping to file
2. select all mappings and delete them all
3. create the second mapping
4. import the exported file from (1)
Its a suitable workaround for me now but if there is no bug in Daslight5 related to multiple mappings, why not change the behaviour of Map Touch (and Map Midi and Map Keyboard) from current "replace" to "add" ? Or popup which asks "Such a mapping already exists, do you want to replace existing mapping or add as additional mapping ? Replace / Add / Cancel"
It seems to me that Daslight5 will ADD ALL presets during import ON TOP of the already existing presets. This seems the reason for the messed up overlays...
This becomes handy as I can now
1. export with first mapping to file
2. select all mappings and delete them all
3. create the second mapping
4. import the exported file from (1)
Its a suitable workaround for me now but if there is no bug in Daslight5 related to multiple mappings, why not change the behaviour of Map Touch (and Map Midi and Map Keyboard) from current "replace" to "add" ? Or popup which asks "Such a mapping already exists, do you want to replace existing mapping or add as additional mapping ? Replace / Add / Cancel"