I’ve just updated to 7.2 (dl on ardour.org). The transparency of audio regions disappeared. I tried to set it up back, but I can’t find the right cursor (preferences → colors → transparency): dragging regions obviously changes the transparency when dragging, it doe’s work.
Any of covered region base, editable region or region alpha doe’s change anything, in grab or edit mode.
When I have overlaid regions for crossfade or punched-in records, I like to have an idea where does the lower region starts/stops and how is the waveform. When I drag the region it becomes more transparent and I can set it very accurately (this is working).
This change was made to better reflect the difference between audibly-opaque and audibly-transparent regions. Allowing opaque regions to ‘look’ transparent can be confusing.
The (visible) region transparency was originally devised as a way to allow the grid to be seen(*). In the last few weeks, Robin found an innovative way to render the regions so the grid remains visible (as if it were overlaid on the regions) with minimal cpu cost. So it’s no longer so necessary to allow the region transparency preference.
This has been the default operation on Mixbus for several years (opaque regions are fully opaque). So there is some precedent that it is workable once you get used to it.
That said, if enough people request it, we could re-introduce the preference and default it ‘fully opaque’ for Mixbus while leaving some transparency for Ardour.
In the interim, I suggest that you consider these ideas:
as you’ve noticed, the regions go transparent while you are dragging them. In many cases this accomplishes the desire for “an idea where the lower region starts/stops”
since 7.0, there’s now a keyboard shortcut to quickly switch between layered and stacked region modes, so you can quickly see a fuller picture of your region stacking, and then switch back.
(*) Regarding the grid, Mixbus’s approach was to leave a small gap between each track where the grid lines could be seen. But I like the new 7.2 way much better, and it’s also much better for MIDI regions. So now Ardour and Mixbus will behave exactly the same, by default.
thanks for your answer, which leaves me somewhat disappointed, because for me it felt more as a bug, so I switched back to 7.1 today hoping for a fix in 7.3.
It’s not only the disappeared Gridlines behind the waveforms which for me is definitely a step back, but also my waveforms which were pretty dark now they look more grey and I can’t get them back to dark anymore, which means a worsened visibility for me.
Reinstalling at least part of the previous status (why not completely?) would be really great
I cannot see regions at all on 7.2 (also downloaded from ardour.org). I’m running Manjaro.
I will downgrade to 7.1 to see if the problem disappears. Or, um, stops disappearing.
I have been using 6.9 for older projects but converted one to 7.2 and then opened a new empty project and imported audio into it. Both 7.2 projects show me nothing but grid in all of the regions, whether audio or midi. Starting the playhead produces the sounds that I am expecting to be there; I just cannot see them!
Posting in this thread because it seems related. I can start a new one if need be.
Hm, I can’t seem to find any setting that makes the regions completely opaque. Where in the preferences is that option available? I’ve tried to lower the “covered region base” setting to zero, but nothing seems to happen. I would love to have completely opaque regions which turn a bit transparent when moved. Any help much appreciated.
Just echoing @Blindekinder on this. I really miss having slightly transparent regions. Fine-tuning crossfades is impossible without being able to see the lower region. And no, I don’t want to continually switch between layered and stacked modes, or have to move the top region to see where the lower one ends.
interesting, if you have a session with like 16 or 30 tracks, and then set the view to all tracks then try zooming in and out of all the tracks and it should be slow. but maybe considering you may be using linux you don’t have this issue.