On Wednesday 30 July 2003 8:48 am, Chris Cannam wrote: > For the sequencer's purposes it really just describes which MIDI > channel of a particular device a track is playing on. At the GUI > side we associate all sorts of information with an instrument > (volume, pan, program changes etc), but the sequencer doesn't know > that -- it just gets asynchronous events when they change, which it > pushes out to the MIDI device on the right channel for the event's > instrument.
Yeah, but the thing is it probably should know about all this stuff now. In other words we probably do want Instrument/Track information at the Sequencer now so that we can firstly solve this issue but also provide information for the Studio as we improve its facilities. > The sequencer doesn't know which track > a segment or MappedEvent is on anyway... does it? No, the sequencer currently has no notion of tracks. But I think we now need to introduce that layer - the current MappedInstrument layer was put in just for simplicity to begin with and to get something working for the slice-based approach (where the MappedEvents would be updated regularly with new Instrument information on each fetch). We now need more description of this mapping at the sequencer. R ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
