dirtdawg's latest activity
-
dirtdawg reacted to baskingshark's post in the thread Knowledge Zenith (KZ) impressions thread with Like.
-
dirtdawg reacted to Brain Damage's post in the thread Knowledge Zenith (KZ) impressions thread with Like.Would add the ZS10 Pro X to the like list. Punches way above it's price point.
-
dirtdawg replied to the thread [FiiO BTR15/BTR5 2021/BTR5]Bluetooth DAC and Headphone Amplifier Discussion & Impressions Thread.Great vid, thanks! I really appreciate your reviews, very informative.
-
dirtdawg reacted to cleg's post in the thread [FiiO BTR15/BTR5 2021/BTR5]Bluetooth DAC and Headphone Amplifier Discussion & Impressions Thread with Like.My video about BTR15 In my opinion, this device offers great value, as it's not only a capable BT receiver, but also a good USB DAC...
-
dirtdawg reacted to baskingshark's post in the thread Knowledge Zenith (KZ) impressions thread with Like.Yep, they release a new KZ pokemon into the wild every 7 days!
-
dirtdawg reacted to salamero's post in the thread Knowledge Zenith (KZ) impressions thread with Like.I just received KZ-Castor My last KZ was ZS5 and I am really impressed for 15 dollars. I am playing them with Aiyima A5-PRO and they...
-
dirtdawg replied to the thread Knowledge Zenith (KZ) impressions thread.The way this was worded made it sound like it's a collab between CCA and HBB. Made me do a double take.
-
dirtdawg replied to the thread [FiiO BTR15/BTR5 2021/BTR5]Bluetooth DAC and Headphone Amplifier Discussion & Impressions Thread.This worked, thank you!!
-
dirtdawg reacted to amery's post in the thread [FiiO BTR15/BTR5 2021/BTR5]Bluetooth DAC and Headphone Amplifier Discussion & Impressions Thread with Like.The same happens to me
-
dirtdawg replied to the thread [FiiO BTR15/BTR5 2021/BTR5]Bluetooth DAC and Headphone Amplifier Discussion & Impressions Thread.Yes, that issue. Car mode is OFF.
-
dirtdawg replied to the thread [FiiO BTR15/BTR5 2021/BTR5]Bluetooth DAC and Headphone Amplifier Discussion & Impressions Thread.I just updated today to the latest firmware version (2.2) and started having this issue myself. I didn't have this problem before...