Project

General

Profile

Bug #1957

Quirky MIDI Configuration Issue

Added by Anonymous about 2 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
High
Category:
DSP
Target version:
Start date:
09/01/2020
Due date:
% Done:

0%

Estimated time:

Description

I am not sure if this is an issue with Zrythm or an issue with my setup. My MIDI setup is pretty basic. I have an M-Audio Midisport 2x2 connected to Jack via Alsa bridge. I have one keyboard connected to input 1 on the midisport. When I first tried Zrythm, I configured it to use Jack for audio and MIDI. Then I selected my midisport in the MIDI controllers in Zrythm preferences.

When I first went to record MIDI - I created a midi track in Zrythm, then I chose my Midisport Input for the track. Then I noticed that Jack was constantly spamming xruns at a regular interval. Every note I would hit resulted in xrun skipping and was completely unusable.

The jack flood of messages looked like this:

JackEngine::XRun: client = Zrythm was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error

These messages just repeat in this order constantly regardless of what Frames/Period I set in jack.

Eventually after a lot of trial and error - I was able to get the xruns to stop. I had to deselect the MidiSport under Midi controllers in Zrythm setup and then I had to make sure that my MIDI track input is set to only receive on channel 1. Then, everything works just fine.

I am unsure if this is a Zrythm bug or just some quirk with my Midisport interface. However, I have never had anything like this happen in either Ardour or LMMS.

Zrythm log file attached.

zrythm_log.txt (373 KB) zrythm_log.txt Anonymous, 09/01/2020 10:05 PM

History

#1 Updated by Alexandros Theodotou about 2 months ago

  • Category set to DSP
  • Priority changed from Normal to High
  • Target version set to 0.9 beta

#2 Updated by Alexandros Theodotou about 1 month ago

  • Status changed from New to Closed
  • Assignee set to Alexandros Theodotou

i think it's the warning message that it tries to show. I changed the log level to debug so it won't try to show it by default.
should be fixed now

Also available in: Atom PDF