Apologies... looked over what I sent and found so many typos that my text might be bordering on incoherence in places. So decided it was worth sending an errata. I highlighted the correcting words in bold, red and all caps. (I guess on text-only clients you'd only see the all-caps).
(wrote a draft last night, practically falling asleep on the couch, didn't comb through it enough before sending)
On 09/07/2022 8:30 AM EDT Andrew S <foss...@flight.us> wrote:Found a downloadable PDF for Korg Kronos -- which has its SysEx specs, too. Found some Roland SysEx listings, as well as Alesis (didn't search exhaustively). Indications are - no, this info is not at all secret and not undocumented. Major brands provide it in their product's user manuals(It *is*, most definitely, "proprietary" - ... For example: some Roland synth mode there might not even have a control parameter that might exist in a Korg)
(It *is*, most definitely, "proprietary" - ... For example: FOR some Roland synth modeL THERE might not even BE a control parameter that exists in SOME Korg MODEL)
So... if the developers were to add SysEx banks, similar to the instrument banks, and they got usage traction, it would be like porting in and concentrating SysEx data scattered about various User manuals, into one uniform library that cuts across makes and models... (But! at the same time creates uniformity and top-level observation point for system exclusive data... yada yada, etc, etc). Might even be an original, and unprecedented (?)... and snowball... with a creative feedback loop... As in... a Rosegarden would be quickly oriented about SysEx possibilities, with the availability of such a bank... Might even, no doubt, impact further hardware purchase decisions : - ))). Might slightly shift production focus away from virtual synths and plugins to external hardware... guessing the trend these days is to move the other way... (away from external hardware to plugins
So... if the developers were to add SysEx banks, similar to the instrument banks, and THE FEATURE got usage traction, it would be like porting in and concentrating SysEx data scattered about various User manuals, into one UNIFYING library that cuts across makes and models... AS WELL AS creating uniformity and top-level observation point for system exclusive data... yada yada, etc, etc. Might even be an original, unprecedented THING and snowball (?)... BOOSTING THE APP-USER creative feedback loop... As in... a Rosegarden USER would be quickly oriented about SysEx possibilities, with the availability of such a bank... Might even, no doubt, impact further hardware purchase decisions : - ))). Might slightly shift production focus away from virtual synths and plugins to external hardware... guessing the trend these days is to move the other way... (away from external hardware to plugins)
_______________________________________________ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
