On Thursday 05 June 2003 10:24, Chris Cannam wrote: > Richard Bown wrote: > > Presumably we don't want to import them > > Or does one import a single .syx file into a single sysex event? > That sounds like the obvious thing.
Yes. this is the point. It is not a good idea to manage big sysex bank sets inside RG, because this can be done better by a sysex dump manager/librarian. BTW, Michael: i don't know a really good program of this kind for Linux. What i would like is a way to insert little sysex messages into a segment, like: - GM, GS, XG Reset standard sysex messages. - Universal sysex messages, like GM Enable/Disable and Master Volume. Another class of little messages i used to include in my songs are vendor specific messages. For instance, there are messages (for Roland JV-80 and GS synths) to change the scale temperament allowing to make experiments with microtonality. Such adjustement is worth enough to be inside the composition, and sent at the very beggining of it. I have a library of little .syx files on disk. With Cakewalk, it was very trivial to import them into the song. I would like to have something like this in RG, perhaps as a function of the new Simple/Full Event List editors. Nothing but than two buttons for load/save the data when editing a sysex event from the event list view. BTW: Anybody can close the bug 674731 ? Regards, Pedro -- ALSA Library Bindings for Pascal http://alsapas.alturl.com ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
