I have been looking into the I/O code and I've received feedback that the I/O issues that at least one person had are solved now, but at the cost of a higher latency. So I'm going to do some more tests tomorrow and make it configurable. Depending on the result of these tests, either with a single checkbox, or with a slider per sound card (the latter only if it has clear benefits, so far it doesn't look like that).
After that I'll look at the GUI remarks that were posted here. These things are exactly the type of feedback that we want
One thing that we hear a lot from people is that the ranges of sliders were far too big, so we have reduced a lot of them - and so far, we haven't heard any complaints about most of those range reductions. 64 dB/oct seems to be a bit excessive. Most processors don't go higher than 12, maybe 18. And very steep slopes can easily lead to very annoying effects. So: Can you explain why you want to go this high? Allowing entering out-of-range values would make sense here if we don't want to show sliders that go this high, so please convince us
(0.1 definitey makes no sense, the lowest part of the range is kinda nonsensical already as it is)
The =/ icon means "difference", so the difference between input and output. If you hear silence something is wrong (unless it's set to a frequency that's so high that you can't hear the stuff that's removed).
"The speed "db/s" (decibel per second) for the AGC" -> Do you mean the band upspeed/downspeed in dB/s/6 dB? That does still exist in the new GUI. Or do you mean something else?
Screen reader: I cannot explain that, unless it's what asagrbics says. For saving, you can store them internally (so without downloading and uploading a file through the web interface). Maybe that part doesn't work in the screen reader? If you want to get the files on your pc on which the browser is open, then you have to download and upload it. But you can store presets internally.
Register
Login
FAQ
Search
