01-05-2021, 08:52 PM
Success...
Running Ubuntu 18.04.5 LTS. Downloaded the new JK client, unpacked it into a JamKazam directory. Did a chmod +x to run.sh and got the client to run by executing ./run.sh
I am using a Line 6 POD HD500 for both my mic and guitar inputs. When I initially plugged it into the PC, and ran the Audio Setup, JK saw the HD500 but would not let me use it as an output. I noticed a bunch of services installing, so when they were done, I closed the client, opened it again, re-ran the Audio Setup -- HD500 was recognized for both the input and output however the latency was initially very high (like 200ms).
I completed the audio setup and went into a test session. Latency was much slower than the audio setup. I was getting some very poor audio quality and found that if I increased my Audio Frame Size to 5 or 10ms that the sound quality improved substantially. At 5ms, I would get the odd audio pop but at 10ms, it sounds quite good. I entered an Open Session with some players from the East Coast and EU (I am West Coast) and was able to play along and sing without any JK issues at all.
JK shows my Audio Interface latency at 0.0ms -- once in a while Jitter climbs a bit but always stays green or yellow. Gear Driver shows as JamBlaster and currently Frame Size is 10ms so shows Red but seems to work quite fine.
I have 2 machines -- an older Lenovo T420 that runs Ubuntu and a newer Lenovo X1 Carbon running Windows 10. While the W10 machine works, every once in a while the machine crashes while running JK. Not sure what causes the crash -- but it may be the ASIO Driver. The native driver that Line 6 provides can only be configured to provide me 16ms of interface latency at best. I've switched to the ASIO4All driver and got the Input Latency down to 4ms but I am not sure if this driver causes the stability issues.
Will test out the Ubuntu client for a while and see if it provides better stability.
Running Ubuntu 18.04.5 LTS. Downloaded the new JK client, unpacked it into a JamKazam directory. Did a chmod +x to run.sh and got the client to run by executing ./run.sh
I am using a Line 6 POD HD500 for both my mic and guitar inputs. When I initially plugged it into the PC, and ran the Audio Setup, JK saw the HD500 but would not let me use it as an output. I noticed a bunch of services installing, so when they were done, I closed the client, opened it again, re-ran the Audio Setup -- HD500 was recognized for both the input and output however the latency was initially very high (like 200ms).
I completed the audio setup and went into a test session. Latency was much slower than the audio setup. I was getting some very poor audio quality and found that if I increased my Audio Frame Size to 5 or 10ms that the sound quality improved substantially. At 5ms, I would get the odd audio pop but at 10ms, it sounds quite good. I entered an Open Session with some players from the East Coast and EU (I am West Coast) and was able to play along and sing without any JK issues at all.
JK shows my Audio Interface latency at 0.0ms -- once in a while Jitter climbs a bit but always stays green or yellow. Gear Driver shows as JamBlaster and currently Frame Size is 10ms so shows Red but seems to work quite fine.
I have 2 machines -- an older Lenovo T420 that runs Ubuntu and a newer Lenovo X1 Carbon running Windows 10. While the W10 machine works, every once in a while the machine crashes while running JK. Not sure what causes the crash -- but it may be the ASIO Driver. The native driver that Line 6 provides can only be configured to provide me 16ms of interface latency at best. I've switched to the ASIO4All driver and got the Input Latency down to 4ms but I am not sure if this driver causes the stability issues.
Will test out the Ubuntu client for a while and see if it provides better stability.