hi,
Many apps got option for different midi drivers:
raw
alsa_seq
jack
In which situation is best to use which one? It's confusing because sometimes they create ports in 'Audio' tab, other times in 'MIDI' tab or 'ALSA' tab. Sometimes in all of them.
Performance wise and rule of thumb which driver should be use priorily? Perhaps the question is which MIDI driver is best suited for what?
thanks
MIDI drivers mad confusing!!!
Moderators: MattKingUSA, khz
- autostatic
- Established Member
- Posts: 1994
- Joined: Wed Dec 09, 2009 5:26 pm
- Location: Beverwijk, The Netherlands
- Has thanked: 32 times
- Been thanked: 104 times
- Contact:
Re: MIDI drivers mad confusing!!!
Afaik JACK MIDI still has jitter, especially with external gear. The only option that doesn't have jitter that I've heard of is the alsarawmidi driver in introduced in Jack2 1.9.8. Haven't tried it as I'm not a Jack2 userfalkTX wrote:alsa-midi allows custom non-standard messages (sysex etc) at cost of jitter, while jack-midi is more limited but has no jitter or latency whatsoever.
Re: MIDI drivers mad confusing!!!
Oh god no. That's the most low-level, stream-lined MIDI API. For all practical purposes, the alsa seq API goes through this. Always use the raw api if a program offers that option, especially if the program syncs MIDI to other, non-MIDI data (such as digital audio).falkTX wrote:ignore the raw option, it's old and basically unused now.
Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.