• 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!

SMSL M500 DAC and HP Amp Review

I also sent the email and have no reply either. Also, I sent a message to @SMSL-Mandy and she didn't answer me either.

Definitely, they are winning a bad reputation campaign for bad post-sale attention in the networks.

I was thinking of purchasing the new SMSL M400, but this situation is unfortunate. The company's null response is disappointing. I think I'll go for Topping, especially now that it supports the ability to play Mqa.
 
I think it's a little unfair to expect perfect response time when support is mostly offline or crazy hectic due to corona.
Less people working at SMSL, more people at home to ask questions. I mean what do you expect.
 
jzsIkNg.png
 
anyone versed with XMOSUSBDACDfu. exe? maybe it some force mode is?
or it may through dfucons. exe?
 

@SMSL-Mandy also answered me. Although considering that I bought the product more than 3 months ago in London, United Kingdom and now I am in Santiago, Chile, the solution is quite disappointing.
It strikes me that SMSL has not warned in advance of the dangers of upgrading to version 2.01 for the product and furthermore, it strikes me that if the problem originated from an upgrade there is no software solution.
All this problem makes me regret having bought this brand of DAC and I believe that I will not buy or recommend SMSL brand products again if the company does not work on a satisfactory solution for its customers.

1588953857389.png
 
I do not believe that there is no software solution, people flashed phones and killed them completely and restored them later
I tried to flash the "XU216 read from flash file. bin" which weighs 512KB and also no results
 
I do not believe that there is no software solution, people flashed phones and killed them completely and restored them later
I tried to flash the "XU216 read from flash file. bin" which weighs 512KB and also no results

If it is possible to flash a phone and kill and recover it, it should be possible to do the same with our M500s, especially when they are still working. The only problem we have so far is not being able to access the 32 bits. Now, trying to return an equipment to the seller when the warranty has expired or when the distance does not allow it, I do not think it is a very useful solution. At the very least we should be able to return the equipment directly to the manufacturer and have it send new equipment to the customer at no cost.
 
Hello,

I had the same problem when the DAC was plugged on my PC USB 3.0 and USB 3.1 ports.
Try to use USB 2.0 ports if you still have them on your MAC.
Otherwise, try another USB port ...

https://www.audiosciencereview.com/...ac-and-hp-amp-review.9606/page-38#post-278507

My Mac only has USB 3.0 ports. I believe some have solved the problem by using a USB hub.. Could plugging a USB 2.0 hub to my Mac, then plugging the M500 to the hub fix the ticking/popping?

Or even USB 1.0? https://www.audiosciencereview.com/...l-m500-dac-and-hp-amp-review.9606/post-269865

I'm not sure I'm understanding all this correctly
 
It would be helpful for some transparency rather than short abrupt answers from support. If there is a hardware problem, it seems widespread. If it's just hardware why did they remove the 1.08 and 2.01 updates? Probably a valid reason, but it would helpful to know. Surely there is a software solution. Mine works fine most of the time, apart from the lack of 32-bit (which the 2.01 attempted software update removed).
 
My Mac only has USB 3.0 ports. I believe some have solved the problem by using a USB hub.. Could plugging a USB 2.0 hub to my Mac, then plugging the M500 to the hub fix the ticking/popping?

Or even USB 1.0? https://www.audiosciencereview.com/...l-m500-dac-and-hp-amp-review.9606/post-269865

I'm not sure I'm understanding all this correctly

Maybe, i haven't tried ...
However, a USB 1.0 hub will certainly not be enough for DSD>256.
Tried with a USB2.0 hub and tell us if it works ...

Did you try on another USB port? Maybe your MAC has two different USB controllers...
 
Last edited:
It may well be that the product's design has been outsourced to other team/company and they don't reply because they really don't have the answers, who knows.

Regarding the firmware updates, what I understand it's happening is that the flash eeprom has a write protected area with firmware 1.05 and when flashing fails it reverts to it. In fact it could be even worse and the units could end up completely bricked.

These are back in stock in amazon, I suppose that they should be the latest hardware/software version, but the lack of information from the manufacturer about the status of fixes for reported problems doesn't really give a lot of confidence.

It would be helpful for some transparency rather than short abrupt answers from support. If there is a hardware problem, it seems widespread. If it's just hardware why did they remove the 1.08 and 2.01 updates? Probably a valid reason, but it would helpful to know. Surely there is a software solution. Mine works fine most of the time, apart from the lack of 32-bit (which the 2.01 attempted software update removed).
 
Maybe, i haven't tried ...
However, a USB 1.0 hub will certainly not be enough for DSD>256.
Tried with a USB2.0 hub and tell us if it works ...

Did you try on another USB port? Maybe your MAC has two different USB controllers...

I actually don't own a M500.. just trying to gather information on whether it's worth buying vs M300 MKII as my next dac. According to the specs my Mac has 2 USB 3.0 ports (early 2015 Macbook Pro 13")
 
Back
Top Bottom