[DanKParticipant]

Sound associates and sennheiser make assisted listening systems that modulate audio into infrared light and the end user has a headset that requires line of sight to operate. This system has the lowest latency.

RF based systems may be more useful because they don’t require a direct sight line to the emitter but are potentially more expensive.

Either of these kinds of systems can be fed via a mix or matrix out of the QU series.

[DanKParticipant]

Audacity doesn’t natively support ASIO as far as I know.
There are instructions to compile audacity (potentially with ASIO support) from source, and some precompiled (although likely outdated) ready-to-run binaries you might be able to find.

More tech-heavy answers here as to why it doesn’t work out of the box: https://wiki.audacityteam.org/wiki/ASIO_Audio_Interface

[DanKParticipant]

Adding my support for this request. Qu-pad (or qu-droid I guess!) may be a tall order for us green robots, but there’s clearly a demand for Android compatible monitor mix control app.

[DanKParticipant]

I would dig a feature similar to that…on my 01V and 02r consoles, tweaking EQ or dynamics settings will make the selected channel’s parameters pop up on screen.

For a board that uses freely spinning rotary encoders AND doesnt have LCD strips for channel parameters (01v, Qu, LS9) the contextual screen helps keep a handle on things. I really wish that on my Qu24, the channel processing parameter I was tweaking with hardware controls in the selected channel section would pop up on screen. Maybe I’m missing a setting on the Qu.

[Author]

Posts