From: Tim E. R. <ter...@ro...> - 2013-07-24 00:40:58
|
On July 24, 2013 12:05:53 AM linux wrote: > In the midi track header, there is an option to set a delay. How is this > incremented? > > seconds? > > milliseconds? > > Does it work? > > Alex. > Howdy, Alex! To user list as well... Good question, as some of those boxes are not well documented, if at all. I have never ever used the 'delay' box, but I sure do use the 'transpose' box, I've said before the 'transpose' is a major reason I chose MusE a long time ago, because it transposes input notes. Sometimes I use the 'compress' box. According to the code, Delay is added to the start tick of each part. As if you had physically moved all the track parts to the left or right. Delay is in units of ticks, as in the upper readout of BigTime, Transport time readouts, Pianoroll midi note time readouts etc. so it should be affected by tempo, I think. It affects part playback notes only, not live events. Delay can also be controlled by the Python interface. Interestingly, Delay can be *negative* Nice for midi latency compensation! And for moving a midi part "beyond" the left border! About the 'Length' box: Similar, but it adjusts the percent length of each *note* in each part. Length is also used on exporting midi, where it is applied to notes along with Transpose, Velocity, and Compression values, but ironically not Delay - hm, is exporting Delay desirable? Make it selectable? Length is not currently supported by the Python interface. Notes to dev list: (Just noticed: TrackInfo Transpose, Delay labels vertical misalignment.) Still no Arranger position boxes or mechanism for numerical placement of parts. I was out of time last batch, we must get around to that soon, eh? I think Flo was asking for info about these boxes inside our tex docs. If someone could kindly update them... Remember my build script is there. Tim. |