02-03-2020, 01:45 PM
(This post was last modified: 02-03-2020, 02:13 PM by Scotty_123.)
First off thanks for the thoughtful feedback. I'll try to give a set of repeatable steps to replicate the reset Volume issue of Motif 1 when a clock stop message is received. I do know it is not dependent on the TouchOSC as it happens with or without the app running. I'll come back with some better information for you.
The only issue that you haven't mentioned is the menu corruption issue that I documented and others have experienced as well. That occurs when you are editing menu values using CCs but happen to be looking a different menu page than you are editing remotely via CC.
For example changing the humanize values via CC will temporally show erroneous values in the Pad menu box on menu page 1/3 if you are on physically on that menu page whilst editing the humanize CC. In fact most if not all menu items that are being edited via CCs will show erroneous information on menu items if you happen to editing remotely a menu related CC whilst viewing a different/unrelated menu page.
This doesn't seem to cause operational errors (it is disconcerting) and moving back and forth between the menu pages using the ndlr controls clears the erroneous information as a screen refresh takes place.
I have just setup a camera here to shoot some video and I'll post a link to highlight that issue and the Motif 1 Volume reset issue as well. Hopefully I can show the TouchOSC templates that I have completed as well.. I have now finished one that is working for android. Thanks again for the feedback.
Steve’s gone through the MIDI CC issues reported by Scotty_123 and here’s a rundown of his findings:
1. Midi CC numbers for PORT and CHANNEL appear to be switched for all four channels in relation to the manual. We’ll get on updating the manual to correct that. (Ex: For Pad - MIDI Channel is 19 (not 18), MIDI Pad is 18 (not 19))
2. The values for choosing port numbers match those listed in the manual and for any value out of range they repeat (VALUE is modulo by 7, so for instance 8=1, 9=2...)
3. Channel selection CC’s Value Range does not currently match the manual. They are spread across a range of 128 values evenly, (so channel 1 = 0-7, channel 2 = 8-15...) since no other CCs are handled this way, in a future update we are likely going to revert this back to a 1:1 range, with repeating for out of range values in the same format as the PORT selection above.
4. Clock-in CC 68: We have been unable to replicate the issue where editing this value makes changes to Motif-1 menu 1/3. Possible external software issue?
5. CCs to start individual parts exist (85-88) but it seems like we should be able to add an additional CC for Start All in a future release. Stay tuned
Other notes:
* CC17 is not a recognized CC number by the NDLR, PAD uses 18/19.
* The 0-6 vs 1-7 numbering may be the result of a bug common in “midi control software” ecosystem, or a possibly the result of a global setting to start count at 0 or 1. More testing with TouchOSC will be needed.
[/quote]
The only issue that you haven't mentioned is the menu corruption issue that I documented and others have experienced as well. That occurs when you are editing menu values using CCs but happen to be looking a different menu page than you are editing remotely via CC.
For example changing the humanize values via CC will temporally show erroneous values in the Pad menu box on menu page 1/3 if you are on physically on that menu page whilst editing the humanize CC. In fact most if not all menu items that are being edited via CCs will show erroneous information on menu items if you happen to editing remotely a menu related CC whilst viewing a different/unrelated menu page.
This doesn't seem to cause operational errors (it is disconcerting) and moving back and forth between the menu pages using the ndlr controls clears the erroneous information as a screen refresh takes place.
I have just setup a camera here to shoot some video and I'll post a link to highlight that issue and the Motif 1 Volume reset issue as well. Hopefully I can show the TouchOSC templates that I have completed as well.. I have now finished one that is working for android. Thanks again for the feedback.
Steve’s gone through the MIDI CC issues reported by Scotty_123 and here’s a rundown of his findings:
1. Midi CC numbers for PORT and CHANNEL appear to be switched for all four channels in relation to the manual. We’ll get on updating the manual to correct that. (Ex: For Pad - MIDI Channel is 19 (not 18), MIDI Pad is 18 (not 19))
2. The values for choosing port numbers match those listed in the manual and for any value out of range they repeat (VALUE is modulo by 7, so for instance 8=1, 9=2...)
3. Channel selection CC’s Value Range does not currently match the manual. They are spread across a range of 128 values evenly, (so channel 1 = 0-7, channel 2 = 8-15...) since no other CCs are handled this way, in a future update we are likely going to revert this back to a 1:1 range, with repeating for out of range values in the same format as the PORT selection above.
4. Clock-in CC 68: We have been unable to replicate the issue where editing this value makes changes to Motif-1 menu 1/3. Possible external software issue?
5. CCs to start individual parts exist (85-88) but it seems like we should be able to add an additional CC for Start All in a future release. Stay tuned
Other notes:
* CC17 is not a recognized CC number by the NDLR, PAD uses 18/19.
* The 0-6 vs 1-7 numbering may be the result of a bug common in “midi control software” ecosystem, or a possibly the result of a global setting to start count at 0 or 1. More testing with TouchOSC will be needed.
[/quote]