Posts: 57
Threads: 8
Joined: Jun 2015
Reputation:
1
05-18-2016, 02:53 AM
(This post was last modified: 05-18-2016, 12:39 PM by rutsch.)
Hi there,
I'm using Mixbus on Linux and I have problems to get a tight/usable Midi clock. The generated MIDI clock is a lot behind the time of Mixbus. I tried various Jack/Alsa settings (Jack Midi, Alsa RAW devices, etc) without success. Other programs like Renoise or Bitwig are generating a really tight clock signal, they use Alsa Midi devices as I know.
Any tips to create a tighter clock signal with Mixbus?
Is there some kind of latency setting for the clock signal?
Thanks in advance!
Posts: 263
Threads: 39
Joined: Feb 2014
Reputation:
6
05-20-2016, 02:13 AM
(This post was last modified: 05-20-2016, 02:15 AM by allank.)
ALSA sequencer set to use HPET device for timing.
Definitely use an RT-kernel .. I found this critical for tight MIDI timing.. (not as necessary for audio, don't ask me why, but that's what I found)
YMMV.. I also use external clock and still found weird timing issues until I used an RT kernel.. (also using a low period setting of 64 or 128)
Posts: 57
Threads: 8
Joined: Jun 2015
Reputation:
1
I'm already using a PREEMPT kernel and a system-timer frequency of 1000 Hz in my kernel configuration. Will try a RT and HPET. Thanks!
Posts: 57
Threads: 8
Joined: Jun 2015
Reputation:
1
Ok, compiled a realtime kernel for my Debian 8 machine. HPET is also enabled in the kernel configuration. The Midi clock is more in time now when using a buffer of 64 or 128. Still not as good as the clock of Bitwig Studio or Renoise but usable. Thanks again for the hint.
@allank
What distro do you use? Are you using Alsa Midi devices or Jack Midi with a2jmidi?
Posts: 57
Threads: 8
Joined: Jun 2015
Reputation:
1
Thanks, Patrick. Will check the script.
Posts: 1,283
Threads: 5
Joined: Apr 2015
Reputation:
44
05-25-2016, 04:21 AM
(This post was last modified: 05-25-2016, 02:40 PM by x42.)
Sorry, late to the party. For Midi Clock and Midi Timecode generators, Mixbus does not yet take any port latency into account. The generated Timecode is at least one cycle behind.
Best you can do at this point in time (Mixbus 3.3) is to run with smaller buffer-sizes.
EDIT: I was wrong above. That would explain if the generated timecode was too early (not too late). This is because (1) the timecode needs to be sent early to for the midi-port-latency itself, but (2) delayed by the worst-case latency to audio, so that things align.
Anyway for MTC this is fixed now, midi-clock (position) not yet.