I am well-pleased with the $130 CreativeLabs Soundblaster Roar 2 speaker used with Linux and Android devices. I recommend the Soundblaster Roar 2 over competing devices, even those costing over twice as much.
Soundblaster Roar 2 FCC ID:
Dual device pairing + analog in seamlessly
The Roar 2 allows simultaneous Bluetooth pairing with two devices while getting analog audio from a third device, and will automatically switch playback audio from one to the other if you push pause on one and play on the other device. Additionally, if you are streaming music from one device (say your laptop) and get a phone call on the other device (your smartphone), the SB Roar 2 switches instantly to your phone to ring on the SB Roar 2 speaker. This is an essential feature feature vs. forcing disconnection and connection manually like I have to do with inexpensive peripherals (headphones, speakers).
NFC enables instant pairing without going through phone menus. Even $40 Bluetooth speakers have NFC pairing now. NFC Tap-to-pair is an essential Bluetooth speaker convenience feature.
Why do you want the SB Roar 2 not to go into pairing mode when not connected? Because an unauthorized person could connect to your Bluetooth speaker in two-way headset mode and eavesdrop on your home/office! So the SB Roar 2 mitigates this risk very common to cheap speakers, by requiring a button press to go into Bluetooth pairing mode. Perhaps the assumption rightfully is that most people will pair via NFC.
The SB Roar 2 can only receive calls – you cannot initiate calls from the SB Roar 2. I find the audio performance to be very good on phone calls. No, it’s not of the quality of a Polycom conference phone, but for single users, the microphone location just left of bottom center of the speaker face seems very adequate for single user conference calls. I have not tried multi-user conference calls with the SB Roar 2 on it’s back (speakers facing up).
“OK Google” audio muting
SB Roar 2 does NOT go into headset mode when using voice prompts on a connected device – so “OK Google” from Android Wear or your smartphone use the microphones on those devices and NOT the SB Roar 2. This is an excellent design decision. The audio playback A2DP does mute of course since your device pauses playback.
Disable Voice Prompts
Tap (quickly press) “-” and multifunction key at the same time. This is very useful for comparing audio between normal/Terabass/Roar modes.
Enable Voice Prompts by quickly tapping “+” and multifunction key at the same time.
Bluetooth devices (legacy Bluetooth, not BLE) use FHSS (frequency hopping spread spectrum) techniques for maximum reuse of the busy 2.4 GHz band. This means even devices with outstanding antenna systems like the SB Roar 2 can have maximum range severely limited in dense urban areas or elsewhere were 2.4 GHz usage is very high. The dual PIFA antennas of the SB Roar 2 allow for polarization/anti-nulling diversity for greatly improved robustness for audio streaming applications. The PIFA antenna gain is just under 6 dBi specified, and the transmitter conducted output is about 0 dBm, so the Roar 2 EIRP is just under +6 dBm, or 4 mW.
I measured range as rock-solid to 25 meters line-of-sight, including phone blocked by body before stopping test. I believe 50+ meters may well be possible in low interference line-of-sight conditions. By comparison, a $2 Bluetooth speaker got about 12 meters range, and a $40 Bluetooth speaker got about 18 meters maximum range under the same test conditions.
However, the caveat is the above test was done under about -70 dBm maximum interference level from numerous Wifi routers in the area. I first attempted the test near a large apartment complex where the Wifi interference level was -60 to -50 dBm from 100+ Wifi APs. Under those conditions, the maximum range for all three speakers ($2, $40, and Roar 2) was about 12 meters.
SoundBlaster Roar 2 battery life is excellent–sometimes I forget to turn it off for a day and its low-power mode preserves most of the battery life. I find I only charge it every couple weeks.
At the time of this writing, the Linux Bluetooth stack only enables the SBC codec, although the other A2DP codec capabilities of the Roar 2–namely, AAC and aptX are recognized as available by Linux. My understanding is that the AAC and aptX require licensing, and it simply hasn’t been a priority for Linux users. I did not take the time to test via Windows or using Blackberry, which have aptX. Perhaps if one is ready for an audiophile session on Linux, they could plug in audio via the 3.5mm analog connection. Another alternative is the $40 CreativeLabs BT-D1, which has the aptX hardware transmitter and is said to present itself as a sound card to Linux/Mac/Windows.
You can confirm the A2DP codec on Linux via
- power off Bluetooth speaker
- start Bluetooth sniffer
- poweron speaker, connect over Bluetooth from your Linux PC
The output includes:
AVDTP(s): Discover rsp: transaction 4 nsp 0x00 ACP SEID 5 - Audio Sink ACP SEID 3 - Audio Sink ACP SEID 1 - Audio Sink AVDTP(s): Capabilities rsp: transaction 5 nsp 0x00 Media Transport Media Codec - non-A2DP (aptX) 44.1kHz 48kHz AVDTP(s): Capabilities rsp: transaction 6 nsp 0x00 Media Transport Media Codec - SBC 16kHz 32kHz 44.1kHz 48kHz Mono DualChannel Stereo JointStereo 4 8 12 16 Blocks 4 8 Subbands SNR Loudness Bitpool Range 2-53 Content Protection 02 00
(yes, the Roar 2 has aptX)
similar text is given for AAC and SBC, then finally the SBC codec is chosen:
AVDTP(s): Set config cmd: transaction 7 nsp 0x00 ACP SEID 1 - INT SEID 1 Media Transport Media Codec - SBC 44.1kHz JointStereo 16 Blocks 8 Subbands Loudness Bitpool Range 2-53
Terabass reasonably boosts low frequency content. It’s good for volume at all levels, especially low volume.
Roar mode is audio compression and brightening for high volume listening. It alters audio characteristics. For high fidelity listening, leave Roar Mode off. Roar Mode is about blasting sound, cranking it to 11.
Note as per the Roar 2 user manual, maximum loudness in “roar” mode is achieved with the speaker externally powered, and I can confirm there is a tangible improvement in loudness being plugged in.
I noticed that I could visibly see the side drivers moving down to 2.8 Hz with “roar” mode enabled and at full volume, though the motion was slight so many 10’s of dB down. The low frequency rolloff seems to steepen below about 58 Hz or so. This was done using an Android frequency generator over Bluetooth A2DP; if someone is really interested I could do a hard-wired test with a lab signal generator.
The sound is much more pleasant that that built into most flat screen TVs or sub-$100 bluetooth speakers overall, more than enough for a city backyard gathering of a small group of friends. You would have to get one of those $300 Bluetooth giant party speakers to get a worthwhile upgrade in volume for parties.
Note that online reviewers have commented that the MegaStereo OMTP cable does NOT work with Roar 2. It is 4 rings on one end and 3 rings on the other, requiring audio output from the Roar, but the Roar 2 is said to NOT have this so you apparently cannot link two Roar 2 together.
I use the $10 CreativeLabs mesh case to carry the Roar 2. By design it is not waterproof at all nor does it afford much drop protection, as it is meant to give a shoulder strap with transparent audio characteristics. It feels sufficiently light to carry this way, although many might put it inside a backpack. There is a $20 silicone case available from CreativeLabs for more shock protection.