|
|
Don't reset meter when input changes. edit: fixed now |
|
|
I'd like to see a feature to automatically switch to a specified meter type on metering a track's input/a track being record enabled. |
|
|
I have just noticed a issue with the meterbridge and toolbar meter colours after they peak. I have posted about it here and included a screenshot - http://tracker.ardour.org/view.php?id=5601 edit: fixed in 3.3-62-g069fd15 |
|
|
allow to resize meterbridge label height (small, med, large | fit) edit: implemented in 3.3-87-g741bb8e |
|
|
Two things I've noticed that I thought I'd add note of - If the meterbridge window is open before adding any tracks, it won't expand, width wise, to accommodate them. However, if the tracks are added before opening the window, it will accommodate them when the window is opened. Any tracks added after that do not expand the window and you have to slide over to get to them. This has caught me out a few times when i didn't see the level of a track I expected to see. Once you open the meterbridge, it will no longer expand upon adding any new tracks, even if you close it and reopen it. Also, I've noticed that the meterbridge only allows for audio and midi tracks but not buses. Is this something that is deliberately left out or are there plans for something like this in the future? |
|
|
re: 0015197 (2nd part) Busses (and master bus and midi-tracks) display can be toggled in Session > Properties > Meterbridge |
|
|
re: 0015197 (1st part - window size) Automatic window-resize is a tricky issue with gtk/gdk. In particular here where the meter-width is not fixed (but depends on the type, number of metric-areas and channels). The current model gets it mostly right most of the time, which is arguably worse than not trying to resize the window at all. The idea so far is: resize the window to fit all visible meter IF the scrollbar was not previously visible AND the resulting window-size is smaller than screen. |
|
|
Thanks x42 for answering those questions. I seem to have missed those options in the meterbridge tab and I can understand what you're saying about window resizing. Another thought while I was using the meterbridge was in regards to groups and track types. There's no indication as to which meters belong to active groups. Same goes for tracks, there's no distinction between audio, midi and bus tracks. Could additional coloured boxes/lines work to indicate these so that it's easier/quicker to distinguish which tracks are which? I've attached a mock up of what I’m trying to explain. |
|
2013-07-30 19:09
|
meterbridgeidea.png (197,582 bytes) |
|
|
I've just noticed a little something else with the meterbridge. Sometimes after removing a track that is beside other tracks that are using different meter types, the meter markers from the removed track remain. I've attached an image of how this looks. Here's how I replicated it - Add 3 audio tracks Open meterbridge Change track 2 and 3 to the same meter type Delete track 1 See result in screenshot attached I am not sure if it happens in other scenarios but it seems to consistently happen when it's the first track that is removed and if it is beside tracks using a different meter type. Another observation is that it seem to only happen when there are multiple tracks to the right that share the same meter type, hence why I say to add 3 tracks to replicate the issue. Adding 2 tracks will not replicate this. Closing and reopening the meterbridge doesn't resolve the issue however, adding more tracks to the session removes the markers left by the deleted track. |
|
2013-07-31 20:15
|
metermarkers.png (29,030 bytes) |
|
|
re: 0015204 (invalid metric after track deletion) fixed in 3.3-119-gad8ffab |
|
|
Regarding the meterbridge window, would it make sense to lock the position of the master meter on the right hand side, similar to how the master track is locked in place in the mixer window? Or the have the option to view it this way? Just a thought. |
|
|
Just noticed an issue with the metering that happens sometimes, but not always. If you add an audio track, after a midi track, and you monitor the input of the newly added audio track using the editor mixer, it sometimes doesn't use the meter colours for an audio track. Instead it uses the colours from the midi input read out. I'll attach a screenshot of the issue. |
|
2013-09-09 14:12
|
wrong meter colours.png (29,265 bytes) |
|
|
Ardour 3.5 release concludes initial meterbridge development. Further feature-requests and bug-reports should get their own report. |
- Anonymous
