Roland Duo-Capture

[tmiddle]

I'm new to jamkazam and just connecting today.  My interface is a Roland Duo-Capture.  Jamkazam does not recognize it in the audio settings.  Is it the interface or am I missing something in Jamkazam.

[blandis]

Hi, and welcome.
Could you please provide a little more information so that others can help and offer suggestions, such as your computer (PC or Mac, and the operating system version, including if it is 32-bit or 64-bit), the Roland software drivers you installed and are using and if they are working properly with any other audio programs such as a Digital Audio Workstation (DAW) or recording program. In very simple terms, JamKazam "works" for distance-separated musicians by minimizing the time delay (called "latency") of communications end-to-end between those musicians, including the latency introduced from physical input (microphone, guitar cable) through the interface and through the computer to the network gear that connects to the Internet. Keep in mind that there are delays both in the input direction, as well as the output direction. Plus the delay across the Internet itself, which JamKazam cannot improve. For JamKazam to minimize those "local" delays on each end, it takes advantage of the variable settings of those specialized audio drivers of the interface, whereby the user chooses settings of minimal buffer sizes, which can be at the expense of audio quality, ultimately choosing a setting that is a compromise of the 2.
That's a long-winded explanation. Put simply, if you did not download and install any Roland specialized audio drivers with your interface but rather chose a "plug-&-play" approach, you may not be set up to take advantage of audio format and latency settings needed by JamKazam. That may be why JK is not recognizing it. For example, standard Windows audio doesn't really care about latency, and for backwards-compatibility reasons audio settings often default to old, poor performance legacy formats and drivers. This is usually not something to even consider if all you want to be able to do is listen to the audio of a YouTube video for example. But it matters a whole bunch when performance matters, like in JamKazam.
Hope this helps

[tmiddle]

Hi, and welcome.
Could you please provide a little more information so that others  can help and offer suggestions, such as your computer (PC or Mac, and the operating system version, including if it is 32-bit or 64-bit), the Roland software drivers you installed and are using and if they are working properly with any other audio programs such as a Digital Audio Workstation (DAW) or recording program.  In very simple terms, JamKazam "works" for distance-separated musicians by minimizing the time delay (called "latency") of communications end-to-end between those musicians, including the latency introduced from physical input (microphone, guitar cable) through the interface and through the computer to the network gear that connects to the Internet.  Keep in mind that there are delays both in the input direction, as well as the output direction.  Plus the delay across the Internet itself, which JamKazam cannot improve.  For JamKazam to minimize those "local" delays on each end, it takes advantage of the variable settings of those specialized audio drivers of the interface, whereby the user chooses settings of minimal buffer sizes, which can be at the expense of audio quality, ultimately choosing a setting that is a compromise of the 2. 
That's a long-winded explanation.  Put simply, if you did not download and install any Roland specialized audio drivers with your interface but rather chose a "plug-&-play" approach, you may not be set up to take advantage of audio format and latency settings needed by JamKazam.  That may be why JK is not recognizing it.  For example, standard Windows audio doesn't really care about latency, and for backwards-compatibility reasons audio settings often default to old, poor performance legacy formats and drivers.  This is usually not something to even consider if all you want to be able to do is listen to the audio of a YouTube video for example.  But it matters a whole bunch when performance matters, like in JamKazam.
Hope this helps

---

Hi, and welcome.
Could you please provide a little more information so that others  can help and offer suggestions, such as your computer (PC or Mac, and the operating system version, including if it is 32-bit or 64-bit), the Roland software drivers you installed and are using and if they are working properly with any other audio programs such as a Digital Audio Workstation (DAW) or recording program.  In very simple terms, JamKazam "works" for distance-separated musicians by minimizing the time delay (called "latency") of communications end-to-end between those musicians, including the latency introduced from physical input (microphone, guitar cable) through the interface and through the computer to the network gear that connects to the Internet.  Keep in mind that there are delays both in the input direction, as well as the output direction.  Plus the delay across the Internet itself, which JamKazam cannot improve.  For JamKazam to minimize those "local" delays on each end, it takes advantage of the variable settings of those specialized audio drivers of the interface, whereby the user chooses settings of minimal buffer sizes, which can be at the expense of audio quality, ultimately choosing a setting that is a compromise of the 2. 
That's a long-winded explanation.  Put simply, if you did not download and install any Roland specialized audio drivers with your interface but rather chose a "plug-&-play" approach, you may not be set up to take advantage of audio format and latency settings needed by JamKazam.  That may be why JK is not recognizing it.  For example, standard Windows audio doesn't really care about latency, and for backwards-compatibility reasons audio settings often default to old, poor performance legacy formats and drivers.  This is usually not something to even consider if all you want to be able to do is listen to the audio of a YouTube video for example.  But it matters a whole bunch when performance matters, like in JamKazam.
Hope this helps

Thanks for posting.  I'm running Windows 10, 64 bit.  with a Roland Duo-Capture EX audio interface.  It has Roland 1.03 driver installed which it s the latest version I could find.  My computer recognizes the AI, but JK does not.

[tmiddle]

I'm new to jamkazam and just connecting today.  My interface is a Roland Duo-Capture.  Jamkazam does not recognize it in the audio settings.  Is it the interface or am I missing something in Jamkazam.

I finally got the Roland to connect after re-connecting a thousand times.  Would not function with ASIO driver, had to use WDM so the latency would pass the test.  Even at that it was barely fair.  At least I know it's not me or the computer.  Getting a new interface.

---

Hi, and welcome.
Could you please provide a little more information so that others  can help and offer suggestions, such as your computer (PC or Mac, and the operating system version, including if it is 32-bit or 64-bit), the Roland software drivers you installed and are using and if they are working properly with any other audio programs such as a Digital Audio Workstation (DAW) or recording program.  In very simple terms, JamKazam "works" for distance-separated musicians by minimizing the time delay (called "latency") of communications end-to-end between those musicians, including the latency introduced from physical input (microphone, guitar cable) through the interface and through the computer to the network gear that connects to the Internet.  Keep in mind that there are delays both in the input direction, as well as the output direction.  Plus the delay across the Internet itself, which JamKazam cannot improve.  For JamKazam to minimize those "local" delays on each end, it takes advantage of the variable settings of those specialized audio drivers of the interface, whereby the user chooses settings of minimal buffer sizes, which can be at the expense of audio quality, ultimately choosing a setting that is a compromise of the 2. 
That's a long-winded explanation.  Put simply, if you did not download and install any Roland specialized audio drivers with your interface but rather chose a "plug-&-play" approach, you may not be set up to take advantage of audio format and latency settings needed by JamKazam.  That may be why JK is not recognizing it.  For example, standard Windows audio doesn't really care about latency, and for backwards-compatibility reasons audio settings often default to old, poor performance legacy formats and drivers.  This is usually not something to even consider if all you want to be able to do is listen to the audio of a YouTube video for example.  But it matters a whole bunch when performance matters, like in JamKazam.
Hope this helps

---

Hi, and welcome.
Could you please provide a little more information so that others  can help and offer suggestions, such as your computer (PC or Mac, and the operating system version, including if it is 32-bit or 64-bit), the Roland software drivers you installed and are using and if they are working properly with any other audio programs such as a Digital Audio Workstation (DAW) or recording program.  In very simple terms, JamKazam "works" for distance-separated musicians by minimizing the time delay (called "latency") of communications end-to-end between those musicians, including the latency introduced from physical input (microphone, guitar cable) through the interface and through the computer to the network gear that connects to the Internet.  Keep in mind that there are delays both in the input direction, as well as the output direction.  Plus the delay across the Internet itself, which JamKazam cannot improve.  For JamKazam to minimize those "local" delays on each end, it takes advantage of the variable settings of those specialized audio drivers of the interface, whereby the user chooses settings of minimal buffer sizes, which can be at the expense of audio quality, ultimately choosing a setting that is a compromise of the 2. 
That's a long-winded explanation.  Put simply, if you did not download and install any Roland specialized audio drivers with your interface but rather chose a "plug-&-play" approach, you may not be set up to take advantage of audio format and latency settings needed by JamKazam.  That may be why JK is not recognizing it.  For example, standard Windows audio doesn't really care about latency, and for backwards-compatibility reasons audio settings often default to old, poor performance legacy formats and drivers.  This is usually not something to even consider if all you want to be able to do is listen to the audio of a YouTube video for example.  But it matters a whole bunch when performance matters, like in JamKazam.
Hope this helps

Thanks for posting.  I'm running Windows 10, 64 bit.  with a Roland Duo-Capture EX audio interface.  It has Roland 1.03 driver installed which it s the latest version I could find.  My computer recognizes the AI, but JK does not.

I finally got the Roland to connect after re-connecting a thousand times.  Would not function with ASIO driver, had to use WDM so the latency would pass the test.  Even at that it was barely fair.  At least I know it's not me or the computer.  Getting a new interface.