The attached picture shows the diagnostics for someone I was playing with. The audio interface latency is 6.0 ms (mine was the same) and the internet latency is 14.5 ms. These add to 20.5 ms and yet the total latency is showing as 51 ms. The numbers were fairly steady. Even if you add in the jitter (should you?) the sum only comes to 27 ms. Would you expect the sum of individual latencies to add up to the total? In other sessions with different people I find they usually do.
Subjectively we could detect no effect of any latency on our ability to keep together. It felt just like playing in the same room. In a session with someone in Rhode Island (I am near London) we had a total latency of 80 ms of which 60 was internet. It was impossible to keep together with that amount of latency. One of us had to lead and the other to try to keep with that. Not very satisfactory. If 80 ms is almost unplayable it seems unlikely that 51 ms should be perfect. I am therefore wondering if the reported 51 ms is wrong and that it was actually nearer the 20 ms sum of interface and internet latencies.
On a separate point I notice that Frame Size is 10 ms and red. What causes that and can I change anything? We each have the Frame parameter set to 5 ms. Is that the same thing?
I'm just getting started with Jamkazam and am playing electric guitar into my apogee ensemble interface.
As you know the signal straight out of an electric guitar is a very poor sound and needs processing. In my computer I'm running Ableton 10 for my DAW and using a native instruments plugin called Guitar Rig 5. This is the processing I need to hear.
But when I turn off direct monitoring from the interface I get dry signal only, and when I record into Jamkazam I get dry signal only. I assume that's what my jamming partner 50 or 60 miles away will also hear when we connect.
How can I make the processed signal the one that Jamkazam uses? Thank you so much.
This is just for info since I have solved the problem. I had my internet connection routed through a wireless access point (WAP). I was using a wired connection but still got "no audio". My set-up was: main router to Netgear 8 port un-managed switch, to Netgear R6250 router set to WAP mode (i.e. all router functions disabled), to laptop running JK. All via Cat 5e cable. On the R6250 user interface all the security options were greyed out so you would assume that it was not doing any policing. I was just using the R6250 as a switch and also as a WiFi extender. The "No-audio" problem disappeared as soon as I removed the R6250 from the chain so it was obviously doing more than acting as a simple switch.
Just posting this in case anyone else has a similar problem.
Last night I tried using my Kemper Profiler with Jamkazam, via S/PDIF, and all I could get was maybe 5 seconds of audio from the Kemper after entering a solo session. After that, the S/PDIF audio was muted, and I could not figure out how to get it back. Are there any special settings that need to be made, to keep my S/PDIF connection active in Jamkazam, during a session?
A little additional info on my setup. I'm using a Roland Quad Capture USB interface in Windows 10. I connect my vocal microphone to input 1, and I route S/PDif from my Kemper to channels 3&4 of the Quad Capture . In Jamkazam, I have one audio input for the vocal mic (input ch1), and another audio input for guitar (ch3&4 selected).
Upon starting Jamkazam, and a new session, I can hear the Kemper via S/PDIF for about 5 seconds while the VST scan happens. Once the scan ends, the S/PDIF appears to get muted, and I can no longer hear the Kemper. Even if I leave the session and start a new one, it remains muted. If I shutdown the Jamkazam app, and reopen, It will work again for 5 seconds then the same thing happens. I'm not using any VST's on either channel of this profile BTW.
As a side note, If I open Cakewalk Bandlab, add a channel, and put that channel in record arm mode, I find that the S/PDIF from the Kemper is working perfectly. It just seems to be an issue with the Jamkazam software or configuration.
Is anyone else having tremendous stability and cra$ng issues? Since the last update on 6.23.2020 jamkazam is now useless with my MAC. Mac with OS X 10.11.6
I have in new Behringer UMC404 HD and I have it apparently correctly installed in JamKazam with the UMC ASIO driver 4.59 When I plug an instrument into channel 1 of the UMC, the signal appears on my live tracks (on both channels, if only input port 1 is activated in the audio setting of jamkazam) When I plug instruments into channels 2-4, no signal appears in my life tracks (but I can hear the signal in my phones on UMC) When I activate Input port 1 and 2, signals from channels 1 and 2 of the UMC appear in my life tracks (channel 1 left, channel 2 right, but visible only in the volume-controller), no signal comes from instruments in channels 3 or 4. Do you have an idea for a solution of the problem ?
Had a good session today with a friend , both of us using the new version of the program... It behaved properly after I rebooted my laptop... There is 1 thing I noticed that could be a bug ....not every time but sometimes when I open an audio file from within jamkazam ( not one of their jam tracks but a file I converted to OGG format) It plays but then when I go to close it to move on to some other song file it won't close... that means you're going to have to exit your session and restart the application before you can go to the next jam track or Audio file..
When I am broadcasting through JamKazam on FB Live, the video seems to be jerking quite frequently every 10-15 secs. Has anyone faced this issue? Would like to hear some suggestions to prevent this issue.
Would also like to know if the Audio Sync delay is always stable or keeps changing.
During the broadcast I am acting as a performer & broadcaster for the session. Only me and one more performer in the session.
