4 ms·
That's because the device is input only. By default Ardour uses the same device for capture and monitoring. The reason is that different audio devices have thei
by bitbang 8y ago
That's because the device is input only. By default Ardour uses the same device for capture and monitoring. The reason is that different audio devices have their own internal clocks, and using more than one devices introduces clock drift.
You get around this be setting JACK to use the snowball device for capture only (and by doing so you are using its clock) and then attach whatever device you are using for monitoring as a JACK client using zita_j2a from the zita-ajbridge tools package.
- hellcow 8y agoThat makes a lot of sense. Speaking for the "hobbyists" out there, it'd be great to have that as an option in Ardour itself and not have to fiddle with setting up client/server/bridges just to plug in a microphone (which seems like a really common use-case!). FWIW I don't even need live monitoring where latency matters -- I just want to record, then stop recording, then play it back and edit it. I do know that programs like Adobe Audition on Windows offer that in a plug-and-play way.
- chupasaurus 8y agoThe only way to handle JACK I've found which wasn't PITA is by using Cadence and Catarina from KXStudio which are nice GUIs to manage JACK server. However, there is "but": because I use Debian, it was a lot of tinkering with apt-pinning and getting one very old lib (can't remember which one though) which is used in Ubuntu since 12.04 to build Ardour with.