This is intentional.
If you solo the track, the sidechain source also needs to be active, otherwise nothing is fed into the sidechain.
1 Like
That makes no difference.
Something similar happened to me yesterday, don’t know if it is the same case (Ardour 8.12.0).
To resolve this I go to Preferences - Monitoring - Solo-In-Place mute cut : slide the fader all the way to the left (-inf).
I have not figured out when exactly this happens so I have not done a bug report yet. It looks, so far, that this happens only when opening some sessions created with older ardour versions, but only if I select a scene. Every time I select a scene S-I-P mute cut goes back to 0db and have to put it back to -inf.
If I dont select a scene it doesnt happen.
It is kinda random so far, I cannot reproduce it with every session. I 'll try figure it out some more when I have the time
2 Likes
Once you open velocity editor and turn on two or more parameters (eg: velocity and pitch bender) you cannot turn these off anymore.
Actually there is a way to close these parameters… you have to click EXACTLY on the little green light on the button… But I assume this isn’t correct.
This little guy:
does nothing and has no tooltip.
It’s the toggle for autoscrolling to follow the playhead, it does the thing it should. The no tooltip issue is known and will be fixed closer to the release time. It’s a pesky issue that keeps returning.
1 Like
It’s more of a feature. Clicking the button brings the given controller to the foreground, which is nice:
Though yeah, it can be confusing too.
2 Likes
Why not just make this a left clickable + button, no text required?
Some glitchy behaviour with the CC editor - is this only CC1 by the way, or can I edit other CCs too? Is there a way to see multiple CC lanes at the same time?
1 Like
Because single left-click is used to select, and not trigger an action.
You can also hide those messages in Preferences > Appearance > “Render + hints on page background (requires restart)” if it annoys you.
1 Like
First of all I want to apologize for my kinda emotional complaints, I’ve managed to run ardour with clock.force-quantum 64 (and even lower values on ardour’s buffer (16 and 32, but with some xruns), fullscreen on 4k monitor(!!!)
The main cause of lagging was… cinnamon, I’ve switched to mate and things are MUCH better now (tested on 8.12 and 9-pre0)
I still have problems with looped MIDI regions, but it works better when using a2jmidid (with midi disabled in wireplumber)
Shouldn’t it indicate the on/off status somehow in that case?
1 Like
Sorry to sound blunt, but this is just ridiculous. You’re going to get a ton of bug reports for this.
1 Like