You have to explicitly click in the scale widget in order for the scroll wheel to work. And I ensured that the number of characters in the numeric label at creation time remained the same as the number of characters that it could be set-to throughout the life of the application. In reply to this post by Tim-2 On August 10, I guess around – 90dB it becomes hard to differ between noise and signal. Unfortunately, scroll-wheel events are not passed on even though the scale widget has the focus. Oh well, but at least there’s the potential to actually use the space. I setup all the numeric labels to use monospace fonts, which by definition, are the same size for all characters.
|Date Added:||3 April 2013|
|File Size:||38.93 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Note a few screenshots musomik mixers with slider markings that stop at dB or less: I setup all the numeric labels to use monospace fonts, which by definition, are the same size for all characters. Metering post-fader is of no value at all to users who know what they are doing, and possibly just confusing to others.
Re: [LAU] mudita24 1.02 — improved envy24control mixer/router for ice1712-based sound-cards
It’ll look bad with short meters fixed at min dB. The issue here would simply be done by padding ” Could even say demands it, but the meters could end up longer than sliders! Monospace labels will handle the rest.
It’s also distracting to musonkk proportional spaced text for such dynamic numeric labels as they’d musnik up wobbling around, so even if it wasn’t for the sizing issue, i’d still want to use monospace fonts and labels that don’t change their width, for dynamic numeric labels.
IMHO, the dual slider per channel umsonik we have now is confusing and adds a lot of clutter. On Sat, Aug 21, at 1: And I ensured that the number of characters in the numeric label at creation time remained the same as the number of characters that it could be set-to throughout the life of the application.
We give the user AFM buttons and three runtime options: Make it simple, at least for the user, and then for you as well.
In reply to this post by Tim-2 On August 10, There’s no master level controls to add their attenuation to the meters. There’s also significant inefficiency if labels are resizing unnecessarily, as there ends up being potential resize requests being passed up and down the widget hierarchy. On August 10, The not-fully-supported-by-alsa Edirol DA http: You have to explicitly click in the scale widget in order for the scroll wheel to work. I believe cards with no analog controls will have no “Analog Volumes” page.
Post-fader metering buttons would be an answer there as well.
Oh well, but at least there’s the potential to actually use the space. Te88 all the Envy24 cards I’ve seen have the same controls on the ADC’s and DAC’s so it’s possible that my hardcoding would have worked in the majority of cases. How else can we solve it?
This is far more complicated than it needs to be. I’m not sure about the M-Audio Audiophile In reply to this post by Tim-2 On Sat, Aug 21, at 1: In reply to this post by Fons Adriaensen Since this app comes up with a fixed size, what about, if the user stretches the app vertically, then it’ll expose the longer sliders but leave the meters the same. Free forum by Nabble.
Maintenance – Wartung
For such cards, “Monitor Inputs” and “Monitor PCMs” would be useful with peak meters, and there’d be tx88 “Analog Volume” panel, nor any possibility of combining the mixer and dac or adc controls onto the same page. T8s8 we chop them off at the min slider value. I’m in holiday Crete, divingbut feel compelled to add this to the discussion: The issue of max width or min width isn’t important. That means ensuring all outputs are text-formatted to produce the same number of characters width, no matter what the input.