Psst: Wanna see something mind blowing? With these fixes now, if your ALSA timer gave you a high enough frequency:
Go to: MusE Settings -> Global Settings: Midi Tab: "RTC Resolution" Change it from 1024 to an insanely high number like 32768. Observe in the terminal output that the timer duly complied! It is at this juncture we *must* point out a difference between ALSA Midi and Jack Midi: If you use Jack Midi with a high period size like say 1024, you do get high resolution (frames) but there will be high latency between you hitting a keyboard note and it being sent to some other output port or sounding through a MusE synth plugin for example. However, if you use ALSA Midi with these high-res fixes, but still a High Jack period size, in theory the low latency of the ALSA Midi will /far/ surpass the Jack Midi. But in practice, when Jack is running we /collect/ our ALSA events to be sent out at the next Jack cycle, so there is still a delay. Currently IIRC you would need to NOT run Jack to get the input-to-output low latency benefits of this HR timer. Which is ironic, because if Jack is not running there will be no audio and thus no need for hungry audio plugins and thus Jack could have been set to a lower period size - unless you are strictly visually editing/arranging some waves... Still, when recording or passing through ALSA midi, this high resolution timer is always good, the higher the better, the incoming note times can be resolved very precisely. Tim. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
