|
|
Screenshot_20241226_073204-ardour-midi-bug.png (26,658 bytes) |
|
|
The project directory of this session to help reproduce (3.2MB extracted - No Audio/Midi files). |
|
|
More info I discovered: * You absolutely need my project (above) to reproduce. * If you create 2 NEW midi tracks in that project and connect them to each other the same way described earlier, they work... * The problem is with the tracks "piano" and "choir_eric". If the input of these tracks comes from ardour, nothing comes in. If it comes from the outside (e.g. midisport) then it works. * Trying to create a new MIDI track to reproduce the same scenario as "piano" or "choir_eric" (same connections, same instrument, etc) works. So now the question is: What is so special about MIDI tracks "piano" and "choir_eric" that makes them different from a newly created track? |
|
|
Confirmed using Ardour 8.10 and the session posted above, both using pipewire-jack and jack2. Before that, I had tested with a news ession of just 3 midi tracks without any plugins, and got the MIDI notes passing through just fine (this was created and run using a self-compiled Ardour 9 from current github, and again, both with pipewire-jack and jack2). In the latter case, I didn't even engage any of the "rec-enable" or "In" buttons. |
|
|
First you need to fix the feedback issue, otherwise Ardour will not pass any signals at all after reloading as session. I've disconnected "Insert" "WIDTH_M" and "WIDTH_S" After that I can use Ardour's Virtual Keyboard to connected to "MIDI_KBD" and the signal reaches both downstream tracks. Tested with Ardour/ALSA (to rule out any issues with JACK or pipewire) bug-9872.png (83,315 bytes) |
|
|
I followed your instructions: * Create 2 MIDI tracks (Track1, Track2). On track1 I used no instrument, Track2 I used Ardour's default General MIDI Synth, * Connect some MIDI keyboard to Track1's input. I used Ardour's Virtual keyboard * Connect Track1's output to Track2. * Make sure In/Disk/Rec and metering points all make sense. I left everything at default with default preferences both In/Disk are implicitly active. * Nothing from the MIDI keybaord makes it to Track2. Here the MIDI synth on track 2 plays notes just fine. |
|
|
x42: "I followed your instructions: ... Here the MIDI synth on track 2 plays notes just fine." > Yes because as I mentioned afterwards, "You absolutely need my project (above) to reproduce." and "If you create 2 NEW midi tracks ... they work" x42: "First you need to fix the feedback issue" > The Feedback indicator lights up but I cannot see any feedback at all. WIDTH_M and WIDTH_S mono tracks are only connected to "INS_MS" (the insert of the "WIDTH" stereo track) I don't see anything from the width* tracks connected to itself. I suspect that the feedback indicator is wrong. THEN, maybe based on that feedback detection being wrong the data isn't passed due to incorrect feedback detection? |
|
|
> The Feedback indicator lights up but I cannot see any feedback at all. As discussed on IRC, the issue is that three busses are 'inserted' into track's signal flow: "inserts" are used to send to an Ardour bus and return a result to the source track. This constitutes a feedback loop: the signal of a track depends on data from the same track. inserts are only to be used with external hardware (and are latency compensated); for a track with an insert the following happens: The track is processed in one go (atomically): send data to external device; receive data from external device from previous cycle. This works with external device; but not with Ardour internal busses. For that to work the track would have to stop processing halfway, send data to the bus, wait for the bus to finish processing, receive data from the bus, and then continue. |
- Anonymous
