- Allow more (48?) definitions
…so all individual MIDI channels on each MIDI-out can be defined.
I know this might be overkill, but any compromise will always leave some sad users.
Maybe a nice compromise would be to select from ‘many’ definitions while maximum usage is 16 per project?
Add optional range and value definitons for CC
Really, really helpful!
Example for Roland JX-03.
cc#13 = 0 - 5… for… DCO-1 Range = 64’, 32’, 16’, 8’, 4’, 2’
cc#14 = 0 - 5… for… DCO-1 Wave = Sine, Triangle, Saw, Pulse, Square, Pink noise
cc#15 = 0 / 1… for… DCO-1 LFO modulation switch
My current definitions are:
…and I still have to look at the device panel to see what settings I can select.
…and I can’t remember if a OFF/ON setting on some device should be 0/1 or (0-63)/(64-127)…?
- proposal for optional extended CC-value definitions:
My new definitions would be like:
13:O1 RANGE, 0-5, (64’, 32’, 16’, 8’, 4’, 2’)
14:O1 WAVE, 0-5, (SIN, TRI, SAW, PUL, SQR, PNS)
15:O1 LFO , 0-1, (OFF, ON)
With CC definitions like these, Pyramid could limit values for a certain CC (like 0/1 or 63/64) and optionaly show 3 characters of text for each individual value in the range.
I think that the number of optional value descriptions can be limited to 8 or 10 values for each CC. The numeric value will show when there is no description.
Optional request for Program Change definitions
Would be super nice.
P1:PIANO-01, MSB, LSB
This could be used for factory presets and organized user banks.
The 8-character program name could be shown next to the track name on top of the display.
MSB and LSB for Bank Selection are optional.
The number of Bank Selects for each device could be limited to 16, although 8 might be more than enough for most devices (but not all).
Unreal request for Note-definitions per Program change
I would be in heaven and might send flowers and chocolat to Squarp
Like the current note-definitions, but a seperate list for each Program Change…
Usage: Select drumsets with different percussion instruments from modules with various setups.
I know that some of these requests could be a lot of data (like Bank/Program Changes and extra Note per Program definitions).
I think it’s fine if this data is not continuously in memory, but stays on the memory card and is not loaded until the system has a few milliseconds time to make the info visible … even if it takes 2 seconds … better late than not
When you have arrived at this sentence while reading, thank you very much for all the attention!