Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
WANTED: Happy members who like to discuss audio and other topics related to our interest. Desire to learn and share knowledge of science required. There are many reviews of audio hardware and expert members to help answer your questions.
Click here to have your audio equipment measured for free!
OK, E30 owners -- mine just went dead. It lights up with an ominous "E - d" on the display and does not respond to the power button or the remote. Any idea what this might be -- and is there a remedy other than sending it back to the seller and hoping for warranty coverage?
Since the error code is private, the only way is to visit Topping.
If it cannot be restored even after unplugging the power plug and leaving it for about 2 hours, or if the factory default reset operation described in the user manual cannot be performed, it is a complete failure.
Since the error code is private, the only way is to visit Topping.
If it cannot be restored even after unplugging the power plug and leaving it for about 2 hours, or if the factory default reset operation described in the user manual cannot be performed, it is a complete failure.
Should (t)here be a knowledgeable & merciful soul to answer my simple question:
do I need to fix anything for my Topping E30 serial no. 2101... used exclusively for music streaming by phone via USB OTG (so no PC/laptop) ?
Thanks.
Should (t)here be a knowledgeable & merciful soul to answer my simple question:
do I need to fix anything for my Topping E30 serial no. 2101... used exclusively for music streaming by phone via USB OTG (so no PC/laptop) ?
Thanks.
The digital audio transceiver was changed from AK4118 to CS8416 in the wake of the AKM fire accident.
From this time on, S/PDIF connection failure began to be said, but I do not know if it will return to AK4118 again with this E30 ll.
The digital audio transceiver was changed from AK4118 to CS8416 in the wake of the AKM fire accident.
From this time on, S/PDIF connection failure began to be said, but I do not know if it will return to AK4118 again with this E30 ll.
The digital audio transceiver was changed from AK4118 to CS8416 in the wake of the AKM fire accident.
From this time on, S/PDIF connection failure began to be said, but I do not know if it will return to AK4118 again with this E30 ll.
My apologies if this topic has already been covered before.
I have an E30 connected to a Bluesound Node via USB. The E30 is in DAC mode. The Node recognizes E30 - I can select it as an output, and all plays fine.
However, I can control the volume in the BluOS app: change, mute, set min / max level. Is this expected?
My understanding was, that with an external DAC the Node will act as just a pass through and not process the signal in any way.
Before the Node I had a Raspberry-based Volumio set up and noticed that despite the E30 being in DAC mode, Volumio too was able to control volume. Setting the mixer to 'none' (vs. hardware and software options) never survived RPi reboot and the mixer reverted to 'hardware' every time.
Based on these similar experiences I conclude that E30 is the culprit.
Would appreciate any insights into the issue. Thanks!
That's true for SPDI/F but the XMOS firmware expose to USB a DAC with volume. So I suppose this volume is done by the XMOS.
As you have a raspy you could see and control it with the command :
alsamixer -c E30
That's true for SPDI/F but the XMOS firmware expose to USB a DAC with volume. So I suppose this volume is done by the XMOS.
As you have a raspy you could see and control it with the command :
alsamixer -c E30
My apologies if this topic has already been covered before.
I have an E30 connected to a Bluesound Node via USB. The E30 is in DAC mode. The Node recognizes E30 - I can select it as an output, and all plays fine.
However, I can control the volume in the BluOS app: change, mute, set min / max level. Is this expected?
My understanding was, that with an external DAC the Node will act as just a pass through and not process the signal in any way.
Before the Node I had a Raspberry-based Volumio set up and noticed that despite the E30 being in DAC mode, Volumio too was able to control volume. Setting the mixer to 'none' (vs. hardware and software options) never survived RPi reboot and the mixer reverted to 'hardware' every time.
Based on these similar experiences I conclude that E30 is the culprit.
Would appreciate any insights into the issue. Thanks!
I have a Chromecast audio connected to the E30 via optical and I'm still able to control the volume from my phone (while E30 in DAC mode). I guess there's a digital attenuation applied from the chromecast side just as your bluesound applies digital attenuation in its usb out. Only in DSD mode no attenuation is permitted and you should always have your Foobar2000 (PC) or other app in full volume to work.
I have a Chromecast audio connected to the E30 via optical and I'm still able to control the volume from my phone (while E30 in DAC mode). I guess there's a digital attenuation applied from the chromecast side just as your bluesound applies digital attenuation in its usb out. Only in DSD mode no attenuation is permitted and you should always have your Foobar2000 (PC) or other app in full volume to work.
I have tried optical from the Node to E30 - this setup allows enabling the fixed output mode in the BluOS app. It's the USB specifically, which provides no option for a fixed output.
So, I guess it's just how E30 is designed - it would advertise its volume control to devices capable of understanding that. And DAC mode would just lock the volume for the Topping's remote.
P.S. I tested another USB DAC: the CA DacMagic XS. Same thing - Node can control the volume. But then again, the XS is a pre-amp as well.
UPD: found a thread in Bluesound support forums with multiple reports of the Node not enabling fixed output for various external DACs, including E30. Supposedly, it's caused by the Node's Linux-based OS (which is plausible as I've seen similar behaviour with the Volumio / E30 setup).
