Newbie HELP

[mm@soundsight.net]

Your bitrate setting won't matter - you can input 24 bit but the data stream is compressed (akin to MP3)

I use 48KHz, mainly because all my hardware is clocked to 48, and my jam partner is using 48, and we don't have problems with it. 44.1 is chosen by others, also no problems that I know of

You will NEVER get "green across the board" and you don't need to. Sometimes I see myself green, then amber, then red, then green again - and never hear anything change. I don't think the "metering" of those parameters is very accurate. Trust your ears, not just your eyes.

Regarding the Guitar Rig issue - I can't speak to that, but there are some threads around here that relate to the topic, so searching might be helpful

Thank you
Some said  96000 Sample rate......so thats whats 'working'.......and bit rate seems to want to be below 64
I still trying.............

---

Welcome, and I totally understand your frustration.  Here are some pointers:
For sample rate and bit rate, start with 44,100Hz, 16-bit; and choose the lowest latency/buffer setting that works with minimal clicking.  Yeah, you haven't used those 'old skool' settings in recording for years, but this is jamming, not studio recording.  And I do mean "minimal" (tolerable) and not necessarily "no clipping", as the biggest challenge in jamming over the Internet is total latency between players, and your interface's contribution to the latency is important.  This means you will likely have to keep adjusting interface settings each time you use and audio app.  If the Focusrite app doesn't keep the settings for you, try setting it in a blank session in Presonus or CW first, exit the DAW, and then go into JamKazam.
As for the green:  kepp in mind that yellow sort of represents about a 25% degradation in latency.  If your interface latency is a very small number, like 4ms, than a 25% degradation to about 5ms may cause it to go yellow.  But you can't hear that 1ms difference, so dont sweat it.  But if your interface latency is marginal to begin with (like, greater than 10ms), then a 25% degradation would be noticeable.  The jitter is the variation in that latency, and these typically fluctuate throughout sessions, as your computer does other things in the background.  Obviously closing all other apps and optimizing your PC for max performance (like DAWs) helps a lot.  Now the (possible) bad news:  even though JamKazam is a 64-bit Windows app, it ONLY supports 32-bit versions of VST effects. (those installed under the "Program Files (x86)" folder).  I see from the NI website that GuitarRig 5 requires 64-bit Windows, but it doesn't state whether both 64 and 32-bit versions of the VST exist in the download, and I'm seeing mixed info online.  If there's a guitar rig .dll in that (x86) folder, and JamKazam has been pointed to that folder during the audio setup, you should be able to load GR5 as an audio FX on your guitar channel.  If not, then you will have to look at other VSTs (such as Overloud TH3 CW edition in Cakewalk, which loads as 64 and 32-bit), although I am not aware of any that include the looping or tape deck functionality of GR.
Hope this helps

Very Kind of you
I'm having multiple problems now   grrrr
Maybe cause of Guitar Rig  ( Video subsystem failures )

I can demo JamK by myself with NO problem!  Using the built in Looper even ! :-)))

Using 44.1 or 48 didn't seem to wanna work

Andddd I tried to join a public jam and could not hear anyone  :-(((((((((((
Anyone know of what setting in my router could be doing this?