I do understand that all device may or may not support them, but if supported they do have the same function for all devices?
So one could implement a a GS? GM? virtual device editor that can set them all?
And they will mean same thing? on all devices.
I especially was wondering about the reverb, chorus CC are they always same "effect" or dependent upon the sysex settings for chosen effect?
And right out of the mind i can see that banks, is not a generic thing?
So i am probably wrong even hoping for some generic parameters.......
And i also have wonderings about when to use CC reverb depth VS SYSEX reverb depth are they the same......
Pan seem to be generic.....
Modulation seem to be generic.....
Sustain seem to be generic......
Channel volume seem to be generic....
Well i find the midi jungle very confusing.
What parameters would you include as generic for GS? GM, having the same function on all devices "if implemented"?
When one think of they could not agree on a bank standard, well that i just sad.
JT
So one could implement a a GS? GM? virtual device editor that can set them all?
And they will mean same thing? on all devices.
I especially was wondering about the reverb, chorus CC are they always same "effect" or dependent upon the sysex settings for chosen effect?
And right out of the mind i can see that banks, is not a generic thing?
So i am probably wrong even hoping for some generic parameters.......
And i also have wonderings about when to use CC reverb depth VS SYSEX reverb depth are they the same......
Pan seem to be generic.....
Modulation seem to be generic.....
Sustain seem to be generic......
Channel volume seem to be generic....
Well i find the midi jungle very confusing.
What parameters would you include as generic for GS? GM, having the same function on all devices "if implemented"?
When one think of they could not agree on a bank standard, well that i just sad.
JT
Pages 6 and 7 show all of the CC messages that are in the standard.
https://www.midi.org/forms/midi_chart-v2.pdf
I do not have any actual MIDI hardware, so I can not tell how each one will react on different devices, but I'm sure someone else will be able to help out.
Bank Selects you have already seen are different if it is GM, GS, or XG.
I believe CC reverb depth would work on "all" devices, while SYSEX reverb depth would be specific to a manufacturer or device.
CC messages are part of the MIDI standard. SYSEX format is, but the actual SYSEX messages are not. SYSEX = SYStem EXclusive, meaning they work on certain systems (devices) only, and not others.
Some good explanations of what each CC message does can be found here, and might help you decide what to implement:
https://www.presetpatch.com/midi-cc-list.aspx
https://www.midi.org/forms/midi_chart-v2.pdf
I do not have any actual MIDI hardware, so I can not tell how each one will react on different devices, but I'm sure someone else will be able to help out.
Bank Selects you have already seen are different if it is GM, GS, or XG.
I believe CC reverb depth would work on "all" devices, while SYSEX reverb depth would be specific to a manufacturer or device.
CC messages are part of the MIDI standard. SYSEX format is, but the actual SYSEX messages are not. SYSEX = SYStem EXclusive, meaning they work on certain systems (devices) only, and not others.
Some good explanations of what each CC message does can be found here, and might help you decide what to implement:
https://www.presetpatch.com/midi-cc-list.aspx
Jonas,
You seem very fond of over-complicating things?
Specifically, you keep trying to create software that hopes to treat all midi devices the same, when they are not.
Each midi device, keyboard, tone module, whatever, should come with a MIDI Implementation Chart, this is a standard format/layout as defined within the MIDI specs, and this Chart will indicate which MIDI features are supported by that device, and may includes notes as to partial support. All aspects of the support may include 'Receiving' and 'Transmitting' MIDI data, not all cases will support BOTH.
The information on this Chart will usually summarise details given in the device manual.
It is often possible to find the MIC via the web for devices that you do now have direct access to. Even if the MIC is within one of the standard manuals, it may be on the web as a separate document.
Geoff
You seem very fond of over-complicating things?
Specifically, you keep trying to create software that hopes to treat all midi devices the same, when they are not.
Each midi device, keyboard, tone module, whatever, should come with a MIDI Implementation Chart, this is a standard format/layout as defined within the MIDI specs, and this Chart will indicate which MIDI features are supported by that device, and may includes notes as to partial support. All aspects of the support may include 'Receiving' and 'Transmitting' MIDI data, not all cases will support BOTH.
The information on this Chart will usually summarise details given in the device manual.
It is often possible to find the MIC via the web for devices that you do now have direct access to. Even if the MIC is within one of the standard manuals, it may be on the web as a separate document.
Geoff
JohnG
changed the title from CC messages, are they all generic? to CC messages, are they all equivalent? — 2 years ago
0
Undo
Votes
This is something that MIDI 2.0 will address nicely once MIDI devices start to support Capability Inquiry.
Software will be able to ask the MIDI device what its capabilities are and the software can then behave accordingly.
Software will be able to ask the MIDI device what its capabilities are and the software can then behave accordingly.
- Eddie Lotter
- 2 years ago
- #22
Agreed, legacy devices will always have to be handled the old way.
The MIDI 2.0 spec does allow for "proxy" devices to handle MIDI-CI for legacy devices, but manufacturers have little incentive to create them.
The MIDI 2.0 spec does allow for "proxy" devices to handle MIDI-CI for legacy devices, but manufacturers have little incentive to create them.
There are no comments made for this post yet
Well Geoff i had the idea to have a few oldschool GM GS instrument editorsa implemented, and i can see some correspondence according to this and other pages.
I
But i was also thinking of having the minimal set of messages "that may" be supported by any device as an optional GM/GS synth with its possible settings.
Maybe create a framework for support oldschool moduls, by simply chose a NRPN set of messages by selecting synth, for old romplers and maybe some LA synthesis features.
I
But i was also thinking of having the minimal set of messages "that may" be supported by any device as an optional GM/GS synth with its possible settings.
Maybe create a framework for support oldschool moduls, by simply chose a NRPN set of messages by selecting synth, for old romplers and maybe some LA synthesis features.
- Page :
- 1
There are no replies made for this post yet.
