View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0009530||ardour||bugs||public||2023-11-10 09:26||2023-11-21 10:43|
|Platform||Debian GNU||OS||Linux||OS Version||(any)|
|Summary||0009530: Launching clips with Launchpad Pro Mk3 stops working after a couple of triggers|
|Description||I can only use the Launchpad Pro Mk3 for a small number of clip trigger actions. Mostly 2-3, maybe sometimes 4-5. Any further attempt to trigger a clip will be ignored by Ardour. When I stop the transport triggering clips will work again for a small number of times.|
When Ardour won't respond to button pushes on the Launchpad it isn't possible anymore to launch a clip per mouse click either.
|Steps To Reproduce||1. Create a track in the cue window|
2. Fill up some slots with clips (I only used Ardour supplied drum Midi clips so far).
At this time I can trigger all the clips in the track by clicking their respective trigger icon (triangle)
With the Launchpad in Session Mode:
3. Push a button on the Launchpad to trigger a clip.
4. Push another button to trigger another clip.
5. Push yet another button to trigger another clip
After a couple of trigger button pushes on the Launchpad Ardour won't respond anymore to the trigger pushes. Moreover, as stated above, I won't be able to trigger any cue even per mouse click.
|Tags||No tags attached.|
||I am not able to reproduce this behavior.|
thanks for looking into this issue!
After reading your note I tried to eliminate everything else that might interfere with Ardour and the Launchpad. In the end I found that it is QJackCtl that somehow gets in the way: The behaviour I detailed above does only occur on my system when an instance of QJackCtl is also running.
That makes this issue itself solved, I guess. But there still is an issue with the interplay of QJackCtl and Ardour.
(My gut feeling is that it is QJackCtl doing wrong here since I have a couple of weird mostly minor issues with it since I transitioned my systems to pipewire.)
Again, thanks for caring!
my last comment sadly seems to have been a bit premature. I had a couple of good runs without QJackCtl but now the issue is back again, even without QJackCtl running. So the only thing that has changed for me is that the issue is not always reproducible but only "almost always".
What can I do to dig deeper?