Welcome, Guest Login

Support Center

How The JamBlaster Works

Last Updated: Dec 10, 2016 09:09AM CST
The JamBlaster is both a computer and an audio interface in one device, but it does not have a built-in display. So to control the JamBlaster, you need to use a “companion app” running on a device with a display – in order to display the user interface.
In the initial JamBlaster release, you can run this companion app on either a Windows or Mac computer. The companion app is the same JamKazam app you have been using to play on JamKazam with traditional audio interfaces, but we have enhanced this application to work seamlessly with the JamBlaster.
In this configuration pattern, the JamBlaster handles all the audio processing to support your sessions, while the computer on which the JamKazam app is running: (1) displays the user interface that you use to control the JamBlaster; and (2) handles all video processing if you are using video in sessions.  

In order to optimize audio latency and quality, you will need to connect your JamBlaster to your home router using an Ethernet cable. The computer on which you are running the companion app may also be connected to your home router via an Ethernet cable, or you may connect your computer to your home network via WiFi. The companion app communicates with and controls your JamBlaster over your home network. 

If you are just playing live in sessions using the JamBlaster, it doesn't matter if the computer running the JamKazam app is connected to your network via Ethernet cable or WiFi. But if you want to use backing tracks or JamTracks in your sessions, or if you want to make recordings during sessions, you will want to connect your computer to your network with an Ethernet cable rather than WiFi. The reason for this is that in the case of backing tracks, JamTracks, and recordings, audio will be streamed between the JamBlaster and the JamKazam app running on your computer, and WiFi can introduce jitter and other issues that can impact audio performance in these cases.

seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found