Hi, On 12/29/05, Chris Cannam <[EMAIL PROTECTED]> wrote: > > If we were to permit the user to select multiple MIDI tracks and record > on all of them at once, how should they select which track records > which MIDI data?
Recording from multiple sources, we are storing two properties for most recorded events: recorded_channel and recorded_port. The recorded_channel property is meaningful only for channel events, because system events (as system exclusive) don't carry channel information. So, if you want to route recorded events into tracks on a channel basis, there should be a default route to hold at least system exclusive events. My proposal: implement a track-based recording filter. Something like the global recording filter, but allowing also to include only one input port and/or only one MIDI channel. By default, allow all events to pass for each track. These two attributes could be included also in the global recording/thru filter, to make Michael happy with his broken keyboard. The problem with those per-track recording filters is that you may want to have mutual exclusive sets of filtering conditions. This is what most sequencers have, and most musicians would expect, I guess. Regards, Pedro ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
