On Sun, Jul 08, 2007 at 02:14:49AM +0200, Julien Claassen wrote: > Hi Alexandre! > I've got a couple more questions: > 1. About the tempo-proc: what do you mean beats_per_measure? Shouldn't it > be: beats_per_minute? that's right, the tempo is in beats per minute. Are you talking about "beats_per_measure" in the source code? That stuff is the numerator of the current time signature during performance mode; AFAIK it's used only by the metronome. > 2. In an imported midi-song can I remap the device channel pair to another. > I tried using my mapdev-filter and similar means, but didn't hear anything > until I changed my device-settings. currently that can't work because the filter is applied when the track is recorded and not when it is played. In such situations I simply change the channel configuration to match the channel the track is using. But there should be a way to remap events in a track, that's on my todo list. > 3. Can I easily and human readably find out the length of a track or simply > blank a track to the end? trackinfo output contains the track length, but this isn't very readable. To bank a track to the end you can use 'trackcut' function and give ~0 (or any large number) as length argument. For instance: trackcut 0 ~0 0 > 4. As somewhat posed before - Ibelieve -, can I temporarily filter > sysex-data? sysex messages aren't pocessed as ordinary midi events; they're never passed from the input to the output. If there is a "current sysex bank" defined, in record mode sysex messages are appended to it. So, to stop processing sysex messages just define the current sysex bank to 'nil'. I plan to add filter rules for sysex messages. cheers, -- AlexandreReceived on Mon, 9 Jul 2007 11:57:03 +0200
This archive was generated by hypermail 2.1.8 : Wed Nov 08 2017 - 16:32:19 CET