Instead of technologies, talk about practicalities. Instead of separating developers from users, have discussions about innards where anyone interested is invited to have a look. This isn't about making things more accessible to end users, but helping the practice of making software more culturally grounded and relevant, opening the windows to let out the bad air.
I've given them plots and audio files.
I don't care what it is. I just want it turned off, if possible.
It's been a perfectly adequate DAC otherwise.
I'd like to take the time now to politely give AudioQuest a giant fuck you.
I write a highly detailed technical question to support, using proper terminology.
After weeks of pinging them, I get a response with things like:
"What you’re experiencing here is called latency and is usually due to the driver types and software commonly used with DAW / audio software."
"That implies that we are basically at the mercy of the operating system and your application."
"Our suggestion is to check if the software you are using can compensate for this or a third-party compatible driver that can hopefully reduce the latency."
Stop blaming others for your shitty hardware.
Finally got around to recording the output of my DAC.
Looks like a very aggressive peak limiter.
They finally got back to me. They are telling me it's "latency" and that I need to check my software and OS settings.
Not a satisfying answer. I will show them my data...
These DACs all feature a thing called a "minimum phase fast rolloff filter" for a "more natural sound". Perhaps that could be causing the issue? Dunno.
I should also mention: I A/B'd this with my Scarlett Solo USB interface. Transients were not clipped there.
No response from AudioQuest. So I went and bought the DragonFly Red, the next DAC up in the production line. Exact same weird transient issue on the test signal.
Calling it quits on these DACs. They seem pretty great for music listening as they give a nice strong signal, but for sound design and music production I cannot recommend.
This is so weird.
Progress: GestVM, Uxn, and Mnolth
I modified uxnasm to write to a memory buffer instead of a file.
Lua is used to metaprogram the gesture (TAL) and the sound (LIL) in one pass via mnolth.
Old way requires 2 passes with 2 separate files:
uxnasm foo.tal foo.rom
New way is just one Lua file, with TAL/LIL code embedded as Lua strings, which is then run via the mnolth Lua interpreter:
I teach computers how to sing.
A fediverse community for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.