Review of Audioquest JitterBug - USB Data & Power Noise Filter.

[Ultrainferno]

   
It's pass-through, like a Schitt Wyrd or an iFi iUSBPower. The DAC on the other end is what your laptop "sees".

 
Thanks. That's what I figured, yet with the JB in between it doesn't see my DACs

 

[magicalmouse]

i had this problem using my beresford dac - when the jitterbug was in line the dac would not accept the input, i asked stanley beresford and he said i was using a reclocking chip in the dac (it is the latest firmware) and this was casuing issues as the jitterbug was also reclocking. I have now put the jitterbug in one of the other usb outputs on my laptop.
 
No problem using the jitterbud with the dragonfly though.

 

[Ultrainferno]

It does work with the Fiio E10K, for a few seconds, then it crashes
But I don't even use the Fiio normally
Oh boy

 

[Krutsch]

  i had this problem using my beresford dac - when the jitterbug was in line the dac would not accept the input, i asked stanley beresford and he said i was using a reclocking chip in the dac (it is the latest firmware) and this was casuing issues as the jitterbug was also reclocking. I have now put the jitterbug in one of the other usb outputs on my laptop.
 
No problem using the jitterbud with the dragonfly though.

 
I thought all the JitterBug did was provide a filter on the 5v line. It's "re-clocking" the USB data? What does that even mean for async data transfer?

 

[Mediahound]

If it's removing a DAC in the bus from being recognized by the computer, that's no good. 

 

[volly]

  i had this problem using my beresford dac - when the jitterbug was in line the dac would not accept the input, i asked stanley beresford and he said i was using a reclocking chip in the dac (it is the latest firmware) and this was casuing issues as the jitterbug was also reclocking. I have now put the jitterbug in one of the other usb outputs on my laptop.
 
No problem using the jitterbud with the dragonfly though.

I'll jump in here and say that I'm experience the same issues here, I have my Halide Devilsound dac plugged in to the jitterbug and I've now experienced the issue quite a few times now. A simple restart seems to fix this but sometimes a complete uninstall of the usb driver had to be done. 
 
I've also experienced the same thing with a similar product from Hifimediy! 
 
When it's working, I do enjoy the sound much better than without the jitterbug, it becomes that little more pleasurable to listen to than without. Could I do without a jitterbug, sure, but I really like what I hear.
 
I wonder if people have similar issues with the wyrd or regen?

 

[bixby]

   
I thought all the JitterBug did was provide a filter on the 5v line. It's "re-clocking" the USB data? What does that even mean for async data transfer?

If it works like a hub, there there are at least two clocking schemes involved, one for the usb packet data in the hub and one again in the usb device (in our case a dac).  It is complicated for me to understand all of it and try to explain it.  
 
So I will stop there, but a trip to the USB org site shows just how freaking complex USB is.  The fact that we get really good sounding audio is amazing.

 

[Ultrainferno]

Just put it in between the ALO CDM and my laptop, and for the first time it works like a charm. Not sure if it sounds better yet, but at least it's working for the first time

 

[stuartmc]

I got my bug today and boy is it buggy in my system. I have a Lenovo ThinkPad as a dedicated music server playing either Tidal or flac files through JRM20. The jitterbug is plugged into the tablets only USB port and the cable runs to a Tanly USB-DDC and then on to my Gustard X20 dac via I2S. Most of the time I get no sound at all. Playing around with resetting things will get it to pass the signal when using Tidal, but it's hit or miss. When I use JRiver I always get sound but it freaks it out - skipping from one song to the next and shutting off and on in a few second intervals. I'm really wondering if I got a defective unit. I can't fathom this level of incompatibility if it is functioning properly.

 

[zilch0md]

Hey Stuart!  
 
Long time no interface. 

 
I just got my Jitterbug today, too.  
 
Early on, I was convinced that it was DOA, but despite being an allegedly "passive" device - as Audioquest states on their FAQ page - it did not want me to use my 3-wire, "data only" USB 2.0 cable between itself and the DAC. 
 
The Jitterbug was a lump of coal, no matter where I tried to use it (multiple ports on two laptops, a desktop PC, or my iPad 3) until I replaced my "data only" USB cable with a "normal" four-conductor USB cable. It's not as passive as they claim, perhaps.
 
And it still refuses to work with my iPad 3 > CCK.  I think this "passive" device pulls more power than the iPad can deliver. I'll try testing it with a USB Y-cable later, supplying power to the input of the Jitterbug with a 5V LPS, while data comes from the iPad 3 > CCK.
 
I think that's what you'll have to try to use the Jitterbug with your tablet.  Their FAQ page talks about tying a powered USB hub, if it's misbehaving.  The Jitterbug may be "passive," but it's at least a little bit sensitive to what's upstream as well as what's downstream, or it can lie down and play dead - or have tantrums, as you're seeing.  
 
To be fair, Audioquest's use of the word "passive" appears to be limited to the context that it doesn't need any special drivers.
 

 
Mike

 

[Deftone]

  Do they include the cable? Because I would certainly not want something like this hanging off my usb port (from Audioquest's Instagram):
 
 
 

 
 
If they actually intend this setup, it seems like a total design fail. 

this is when audioquest should develop an all in 1 filter,dac and amp because i can see the daisy chain thats going on getting damaged easy.

 

[stuartmc]

Mike, you're like my audio savant! You nailed it again for me with a very cogent post. I was using an uber expensive Audience AU24 dual lead USB cable and apparently it was causing most if not all the problems. I went back to my more conventional Oyaide Neo class S cable and the jitterbug is now working as advertised. This is really weird. The AU24 only separates the power and data into separate jackets, but they are attached conventionally to single connectors at both ends. How the heck does this freak out the jitterbug?

I'm not real happy about it because as much as I hate to admit it, the Audience cable sounds superb compared to the Oyaide-the latter having a flattened stage and more strident treble. I don't know whether the jitterbug will provide enough improvement to overcome the cable difference. I will let it burn in for a few days before I decide.

I'm getting a Regen in a week or so and maybe that will act like the powered hub AQ mentions. I'll be thrilled if it solves the jitterbug cable problem and yields some audible improvements of its own.

 

[castleofargh]

reading you guys, it seems to be even worst than what I was expecting. and my expectations where somewhere between ferrite bead and snake oil. 

 

[stuartmc]

reading you guys, it seems to be even worst than what I was expecting. and my expectations where somewhere between ferrite bead and snake oil. 

The jury is still out for me. I need to let it burn in and then do some critical listening. Up until an hour ago I would have placed it between a hardened turd and a paper weight, lol.

 

[dmbr]

Is this essentially the same as the Schiit USB Decrapifier?