I seem to be getting a lot of No Align warnings in Ardour 8.11
In a session which has no midi, the log tells me:
2025-02-28T13:17:42 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
How does this relate to the warning? (it was repeated twice in the log)
And how can I fix it?
Many thanks
It does not relate at all.
This warning informs you that Ardour cannot use a given MIDI device.
This is strange.
It was the only error message/s in the log
Also I have successfully used the din midi on the x18 for recoding and playback
Heres the log at start of a new session:
2025-02-28T16:06:07 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T16:06:07 [WARNING]: AlsaMidiOut: failed to open midi device ‘142:0’.
2025-02-28T16:06:07 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T16:06:07 [WARNING]: AlsaMidiIn: failed to open midi device ‘142:0’.
2025-02-28T16:06:07 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T16:06:07 [WARNING]: AlsaMidiOut: failed to open midi device ‘143:0’.
2025-02-28T16:06:07 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T16:06:07 [WARNING]: AlsaMidiIn: failed to open midi device ‘143:0’.
2025-02-28T16:06:07 [INFO]: Scanning folders for bundled LV2s: /opt/Ardour-8.11.0/lib/LV2
2025-02-28T16:06:08 [INFO]: xjadeo version: 0.8.14
2025-02-28T16:06:09 [INFO]: harvid version: 901
2025-02-28T16:06:10 [INFO]: Loading menus from /opt/Ardour-8.11.0/etc/ardour.menus
2025-02-28T16:06:10 [INFO]: Cannot set I/O Priority for disk read/write thread
2025-02-28T16:06:10 [INFO]: Loading user ui scripts file /home/mel/.config/ardour8/ui_scripts
2025-02-28T16:06:10 [INFO]: Loading plugin order file /home/mel/.config/ardour8/plugin_metadata/plugin_order
2025-02-28T16:06:10 [INFO]: Loading history from /home/mel/Music/Untitled-2025-02-28-16-06-00/Untitled-2025-02-28-16-06-00.history
2025-02-28T16:06:10 [INFO]: Untitled-2025-02-28-16-06-00: no history file “/home/mel/Music/Untitled-2025-02-28-16-06-00/Untitled-2025-02-28-16-06-00.history” for this session.
I started the X18 and X-Air-Edit before starting Ardour
Heres a screenshot of the recording I have now made, from a korg synth, using the din ports on the X18 and which plays back correctly through general midi synth in this session
Do you have any ideas what I could/should do?
Many thanks
PS I posted this as I read in another topic to look in the session log for errors which might cause no Align.
No Align errors are caused by ambiguous routing which contains two different paths of different latencies, and so makes it impossible to have a single latency correction value.
Thank you Chris. How would i go about finding the conflicting paths?
I’ve just tried a no align session in safe mode and its not lighting the No Align lamp.
Im only using ACE, Harrison and X42 plugins.
In the master I put 32c buss pre fader then X42 crest factor post fader, no problem. As soon as I add X42 limiter pre fader, following 32Cbuss, the No Align lights up
I’ve used X42 limiter for years and I’m sure I never used to get this issue
Heres my dsp usage for that session
Is it the gaps preceding the last two plugins which shows the problem?
Now Ive tried it with another limiter (TL1313), as the only plugin in the master before the fader and the No Align light comes on
That plugin adds latency.
If no-align lights up, you have made multiple direct port connections: One path via the plugin and another connection around it.
Are any tracks connected directly to physical outputs?
Do you perhaps use Aux busses with direct connections (rather than sends)?
There should be hints in Window > Log about which ports causes this.
This is my session log for the no align session:
2025-02-28T18:17:50 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T18:17:50 [WARNING]: AlsaMidiOut: failed to open midi device ‘142:0’.
2025-02-28T18:17:50 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T18:17:50 [WARNING]: AlsaMidiIn: failed to open midi device ‘142:0’.
2025-02-28T18:17:50 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T18:17:50 [WARNING]: AlsaMidiOut: failed to open midi device ‘143:0’.
2025-02-28T18:17:50 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2025-02-28T18:17:50 [WARNING]: AlsaMidiIn: failed to open midi device ‘143:0’.
2025-02-28T18:17:50 [INFO]: Scanning folders for bundled LV2s: /opt/Ardour-8.11.0/lib/LV2
2025-02-28T18:17:50 [INFO]: xjadeo version: 0.8.14
2025-02-28T18:17:51 [INFO]: harvid version: 901
2025-02-28T18:17:52 [INFO]: Loading menus from /opt/Ardour-8.11.0/etc/ardour.menus
2025-02-28T18:17:52 [INFO]: Cannot set I/O Priority for disk read/write thread
2025-02-28T18:17:52 [WARNING]: Ambiguous latency for port ‘Click/audio_out 1’ (1040, 1088)
2025-02-28T18:17:52 [WARNING]: Ambiguous latency for port ‘Click/audio_out 2’ (1040, 1088)
2025-02-28T18:17:52 [WARNING]: Ambiguous latency for port ‘Click/audio_out 1’ (1040, 1104)
2025-02-28T18:17:52 [WARNING]: Ambiguous latency for port ‘Click/audio_out 2’ (1040, 1104)
2025-02-28T18:17:52 [INFO]: Loading user ui scripts file /home/mel/.config/ardour8/ui_scripts
2025-02-28T18:17:52 [INFO]: Loading plugin order file /home/mel/.config/ardour8/plugin_metadata/plugin_order
2025-02-28T18:17:53 [INFO]: Loading history from /home/mel/Music/letsGo/letsGo.history
2025-02-28T19:00:46 [INFO]: Cleared Explicit solo: solo
2025-02-28T19:00:46 [INFO]: Cleared upstream solo: solo up:1
2025-02-28T19:00:46 [INFO]: Cleared upstream solo: solo up:1
2025-02-28T19:00:46 [INFO]: Cleared upstream solo: solo up:1
2025-02-28T19:00:47 [INFO]: Cleared Explicit solo: solo
2025-02-28T19:23:42 [WARNING]: Ambiguous latency for port ‘Click/audio_out 1’ (1040, 1136)
2025-02-28T19:23:42 [WARNING]: Ambiguous latency for port ‘Click/audio_out 2’ (1040, 1136)
2025-02-28T19:25:09 [WARNING]: Ambiguous latency for port ‘Click/audio_out 1’ (1040, 1136)
2025-02-28T19:25:09 [WARNING]: Ambiguous latency for port ‘Click/audio_out 2’ (1040, 1136)
Does this mean that I have routed the clIck out wrong in audio connections?
Click is not on by default, not like it used to be
Aha. So the metronome is connected both to physical outputs (directly to hardware), and in addition routed though a Bus → master [latent plugin] → output.
Solution: break one of those connections and exclusively connect it.
2 Likes
Thank you so much, that’s got it, what a relief 