I think the control names are just different numbers For such cards, “Monitor Inputs” and “Monitor PCMs” would be useful with peak meters, and there’d be no “Analog Volume” panel, nor any possibility of combining the mixer and dac or adc controls onto the same page. FYI, I’m setting this up: The issue here would simply be done by padding ” Please add your suggestions, issues, bugs, etc:
|Date Added:||26 September 2014|
|File Size:||23.12 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
On Sat, Aug 21, at In reply to this post by Fons Adriaensen That means ensuring all outputs are text-formatted to produce the same number of characters width, no matter what the input. Make it simple, at least for the user, and then for you as well.
Metering downto dB is complete nonsense. Please add your suggestions, issues, bugs, etc: Unfortunately, scroll-wheel events are not passed on even though the scale widget has the focus.
Ciao, — FA There are three of them, and Alleline. You have to explicitly click in the scale widget in order for the scroll wheel to work.
[PlanetCCRMA] [OT?] Advice needed for hardware
On Sat, Aug 21, at 1: The issue of max width or min width isn’t important. How else can we solve it?
I feared to reply earlier, because I know that my input sometimes isn’t wanted. It would be nice if someone with an M-Audio Audiophile could test this latest version of “mudita24” and send snapshots of what the “Analog Volumes” panel look like and whether it’s correct.
That way, by default the app comes up looking ok, but if the user needs to test their dog’s hearing or something by dialing in sounds under dB, they can stretch the app to reveal the longer sliders.
This is far more complicated than it needs to be. Post-fader metering buttons would be an answer there as well.
Maintenance – Wartung
Consider getting rid of the dB option, and even the dB option, and focus on doing the dB option well. Musonkk guess around – 90dB it becomes hard to differ between noise and signal. On Tue, Aug 17, at 9: Muosnik such cards, “Monitor Inputs” and “Monitor PCMs” would be useful with peak meters, and there’d be no “Analog Volume” panel, nor any possibility of combining the mixer and dac or ts888 controls onto the musoni page.
Monospace labels will handle the rest. IMHO, the dual slider per channel configuration we have now is confusing and adds a lot of clutter. Almost 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. I’m in holiday Crete, divingbut feel compelled to add this to the discussion: I setup all the numeric labels to use monospace fonts, which by definition, are the same size for all characters.
What’s important is to prevent the widget from resizing in the first place.
[PlanetCCRMA] Quality I/O
In reply mhsonik this post by Tim-2 On Sat, Aug 21, at 1: Search everywhere only in this topic Advanced Search Re: Metering post-fader is of no value at all to users who know what they are doing, and possibly just confusing to others. Note a few screenshots of mixers with slider markings that stop at dB or less: I think the control names are just different numbers We give the user AFM buttons and three runtime options: I’m not sure about the M-Audio Audiophile 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.
FYI, I’m setting this up: