![]() Information on setting up virtual audio routing on Linux seems to be so difficult to get configured correctly, because JACK Audio seems to do any 1 of 3 things You get up to 6 separate audio tracks you can record audio, and each one can be dedicated to output a specific audio to. I want to be able to use virtual audio routing for specific applications to feed audio from one thing and pipe it to another so that audio management can be independently controlled per application when recording with OBS, so they are put into specific audio tracks. I’m in need of a specific setup for Virtual Audio routing for recording and such with applications like OBS. It turns out that in my case the left channel was muted.I’ve been trying to find a good comprehensive guide for configuring and setting up JACK Audio for setting up Virtual Audio routing, but most guides and videos I can seem to find online are very old and outdated, and don’t even explain very well with how setting up audio with JACK Audio. I then used the builtin audio test of Mate and had the same problem there. I had a very weird problem where only one channel was playing of the two I saw playing in Ardour. You will notice quickly enough if you hear too many sample drops. I also tried LMMS and found that a sample rate of 192k didn't work very nicely with synthesis, as that is rather heavy on the CPU. I didn't test the upper limit well, but 192000Hz samplerate at 4096 frames buffer also seems to run fine. ![]() Don't go lower as it will keep jackdbus hanging rather badly. I managed to get jackd running in realtime with buffer sizes from 128 frames at a sample rate of 44100hz. I had 32 mono tracks smoothly playing in Ardour with a few plugins on the side and the temperature didn't rise above 57 degrees C. The performance of the board is pretty good. The latency will go down, but keep in mind that as soon as the CPU-temperature goes over 80 degrees Celsius, the CPU will be throttled. When using jack on the Pine64, be aware that how smaller the buffer size is the more work it has to do. From here you can use qjackctl or any other tool to start jackd. You can now stop this process by pressing Ctrl-C. If you do see the bit of text above, you now successfully installed jackd2 and it is running. The first thing we need to do is to install the old version of jack, because we need to make the system think that jackd is installed. If you are running a different image, the same process will apply, but you might need to adjust some actions. This tutorial assumes you are working with either the Ubuntu Basic Image, or the Ubuntu Mate image. If you use a 2.0A rated power supply, the board might crash in the middle of the process (as has happened to me). Also: make sure that your pine64 board has enough power. This is not as difficult as it might sound, but it requires some tinkering in the terminal. In later versions of jackd this has been solved, but as there is no package, you're currently required to compile it by hand. (Edit: strangely enough this error still occurs even if you are using a more recent image with jackd2 v1.9.11.) ![]() As many people have found, the default jackd version that comes with the Pine64 Ubuntu image (which is version 1.9.10) will crash as soon as you start it with a bus error and a message in the kernel log about an aligment problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |