On Thursday 05 June 2003 10.46, Richard Bown wrote: > On Thursday 05 June 2003 9:24 am, 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. > > No, not necessarily. Sysex messages (bulk data dumps, song dumps > etc) can be huge - megabytes in some cases. It's not always > desireable to import them into a document directly but referencing > them (and being able to spool them out onto the MIDI pipes) is > probably something we could do.
Besides, you generally don't want the sequencer to just start sending tons of SysEx, reprogramming your whole rack, just like that. Some applications seem to make a difference between "light" SysEx events, used to tweak the occasional parameter, and SysEx dumps containing patches and stuff. The latter normally result in a confirmation dialog, and they're not sent every time you hit play. //David Olofson - Programmer, Composer, Open Source Advocate .- The Return of Audiality! --------------------------------. | Free/Open Source Audio Engine for use in Games or Studio. | | RT and off-line synth. Scripting. Sample accurate timing. | `-----------------------------------> http://audiality.org -' --- http://olofson.net --- http://www.reologica.se --- ------------------------------------------------------- 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
