On Wednesday 30 July 2003 09:48, Chris Cannam wrote:
>
> The problem with changing the instrument from the dropdown is that each
> MappedEvent already has an instrument id fixed into it. So if you
> change the instrument for a track, you surely need to rewrite all the
> MappedEvents for all the segments on that track with the new instrument
> ids in them. As I notice Bownie has also just said, I'd be surprised
> if it worked without doing that.
Well currently the only thing that happens is the sending of a
MidiControllerEvent. The segments are not refreshed. The purpose of the
ControlBlock is (among other things) to avoid that large refresh. Next thing
I'd put it would be a track's muted status.
> The other thing is, if you store the track id -> instrument id table in
> a control block and make that available to the sequencer, what does
> that actually give you? The sequencer doesn't know which track a
> segment or MappedEvent is on anyway... does it?
Yes, it does, because I pass the TrackId instead of the InstrumentId to the
MappedEvent's ctor (that part is currently commented out).
--
Guillaume.
http://www.telegraph-road.org
-------------------------------------------------------
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
