Hi all. I'm still having occasional audio glitch problems, and I frequently get 1 or
more errors in a log file like this:
[31mERROR: [0ma2j_process_incoming: threw away MIDI event - not reserved at time
157016825
Is this a A2JMIDIBridge error? If so, should this cause a complete audio drop-out at that
point? It seems I only have difficulties when recording audio with Nama from a softsynth
playing from MIDI data. I have no problems either with playback of MIDI sequences,
playback of audio, or recording audio directly from a live sound-source. There was some
posts a while back about A2JMIDI not providing proper MIDI time stamps. Could this be
part of the issue? Is there any reason to be concerned with Nama/Ecasound creating MIDI
ports even when they're not being used? I'm just throwing out thoughts here,
because I'm not sure where to look for answers or how to test further. It even occurs
when recording a softsynth live, but of course I'm still using MIDI data to drive it.
Any suggestions would be appreciated. Thanks much.
Kevin
Show replies by date
IIUC you're playing a soft synth by a keyboard, connected via a hardware
MIDI interface, when you get audible "drop outs"?
If so, does the MIDI interface and or the audio device share the
interrupt with something else? If so, did you unbound or remount
hardware to get rid of shared IRQs?
Did you increase Frames/Period?
What's the output of /path/to/rtirq status?
Ralph said:
– IIUC you're playing a soft synth by a keyboard, connected via a hardware
MIDI interface, when you get audible "drop outs"?
It happens either when using my USB MIDI interface, or when sending MIDI data from
MIDISH sequencer through jack to the softsynth. Audio is via built-in audio card. I
don't absolutely know that there are no IRQ conflicts, but I can check. I haven't
changed period size yet. Is this a MIDI related error, Jack error, Alsa error, ... or can
we tell?
Thanks much.
Kevin