Notifications
Clear all
Topic starter
I noticed that in M2-117-UM `AllCtrlList` property does not have `defaultCCMap` field, unlike `ChCtrlList`, while other fields are equivalent (unless I'm missing anything other than I posted here). Is it an intended design, or just an overlook? I don't see any particular reason to skip it only on AllCtrlList.
Posted : 10/07/2025 8:08 pm
The historical reason was that because the Default Control Change Mapping Profile is a single channel profile then the ChCtrlList Resource can make reference because it can only describe a single channel at a time. The AllCtrlList can describe more than one channel and therefore has a slightly different use-case.
Did you have a ause-case where you would see this need?
Posted : 10/07/2025 11:38 pm
Topic starter
I don't think there should not be a question on whether I have a use case or not, but it should rather be a specification design consistency.
If I were to return the control list properties for a traditional GM synthesizer, I should be able to simply return one single `AllCtrlList` with all the controls with all those properties including `defaultCCMap`, instead of having one `AllCtrlList` with all those property *except for* `defaultCCMap`AND 16 `ChCtrlList` that *only* contains `defaultCCMap`. One tiny errata correction in the specification fixes this nonsense.
Posted : 11/07/2025 3:54 am
