BPM not changing via Carla
-
- F4 - Digitalis
- Posts: 3
- Joined: Fri Apr 10, 2020 6:10 pm
BPM not changing via Carla
I'm using Giada 0.16.2-x86_64.AppImage on Ubuntu 19.10 with jack. I change the tempo using Carla but the tempo number in Giada doesn't change and the beat counter keeps going at the same speed. Is there somethign else I need to do to get it to sync?
- FFT
- F14 - Syrian Rue
- Posts: 549
- Joined: Thu Mar 08, 2012 6:51 pm
Re: BPM not changing via Carla
Hey hellocatfood, did you try the other way around, i.e. to change the tempo in Giada? Does it work that way?
-
- F4 - Digitalis
- Posts: 3
- Joined: Fri Apr 10, 2020 6:10 pm
Re: BPM not changing via Carla
I'm using Giada with Jack and so the BPM field is greyed out and it won't let me change it. I can change bpm if I use Alsa as the backend but I need to use Jack.
- FFT
- F14 - Syrian Rue
- Posts: 549
- Joined: Thu Mar 08, 2012 6:51 pm
Re: BPM not changing via Carla
Oh yes, I forgot that Giada works in Jack "slave" tempo mode, my bad. So I have another question: does the BPM value change when using a different Jack-based software (e.g. Ardour)? Sometimes the jack bpm information is not sent correctly across jack clients.
-
- F4 - Digitalis
- Posts: 3
- Joined: Fri Apr 10, 2020 6:10 pm
Re: BPM not changing via Carla
I've tried using Ardour to change the BPM as well (it's using Jack) and it still doesn't update in Giada.
To be sure, opened Giada, Carla, Ardour, and Qjackctl. Changing the BPM in Ardour affected Qjackctl and Carla but not Giada.
To be sure, opened Giada, Carla, Ardour, and Qjackctl. Changing the BPM in Ardour affected Qjackctl and Carla but not Giada.
- FFT
- F14 - Syrian Rue
- Posts: 549
- Joined: Thu Mar 08, 2012 6:51 pm
Re: BPM not changing via Carla
Alright, I was able to reproduce the problem by using Ardour + Giada through Jack. The bpm change signal is received correctly but interpreted the wrong way.
So thanks for the bug report, this will be fixed in the next (and upcoming) version 0.16.3.
So thanks for the bug report, this will be fixed in the next (and upcoming) version 0.16.3.