Open poetaster opened 1 year ago
Hi, yeah as I remember PortAudio used just for output at MixerOutput. I tried to use QAudioOutput, but it has too big output latency at my device(maybe because this project has bad design in many places :) I think it is not hard to rewrite output used Qt libraries, you may try.
I haven't updated this project in a long time, and I think at this branch MIDI data just loading from midi files, not midi-device input
Hi, yeah as I remember PortAudio used just for output at MixerOutput. I tried to use QAudioOutput, but it has too big output latency at my device(maybe because this project has bad design in many places :) I think it is not hard to rewrite output used Qt libraries, you may try.
Ok, I'll see if I can get around the latency issue. I'll give it a shot. I do have a small interpreting synth using SDL2 that works quite well, so I could try using SDL2 if QAudioOutput doesn't do it. Thanks !
I was looking to make a mobile QML interface for this until I realized there is a port audio dep. That is 'only' used for MixerOutput, right? But audio / midi output?
What speaks against just using:
I would guess midi? I'm working on two targets, both a bit exotic (Sailfishos with pulseaudio and gstreamer, Ubuntu touch). I can't really support midi (well, via OSC) on those. But even on my laptop, installing pa dev wanted to rip out my current version of jackd (which is running alongside pulse).
Wouldn't a 'pure qt' approach get around these kinds of issues?