advertisement


M2 TECH,Extremely poor show!

ports1000

pfm Member
So Mavericks has been out for 3 months now and M2Tech have still nor developed
the new drivers for The Young Dac.
Their customer service is non existent. I have sent off several emails enquiring when the new drivers will be available.....NO REPLY...
Such a shame because their Young dac is excellent,even comparing to newer dacs!
Shame because I will never buy another product from them again....
rant over!!
 
Yes it is poor, and there is no excuse, I believe their original programmer has not released
the source code and reconstruction is taking longer than expected.
Tey have offered a HiAce 2 at cost to Young dac owners, as a short term fix.
Keith.
 
Keith,you've always been as helpful as you can be under the circumstances! But I would just appreciate an answer to my emails to them,just common courtesy really?
Can you please give me more details about the hiface offer? I would certainly like to take them up on that!
Thanks Andrew.
 
Andrew Hi, I will ask for you, I know you have to provide the serial number of your M2Tech device.
Do I have your email address?
KR Keith.
 
Does this problem also apply to the HiFace USB DAC?

I have put off updating to Mavericks so far just in case.
 
At which point do we no longer expect hifi manufacturers to support old kit with new drivers for new OS? 3 years, 5 years? What's a reasonable expectation?
 
Use a native USB converter, takes all the driver support out of it. M2tech were not the only ones.
 
At which point do we no longer expect hifi manufacturers to support old kit with new drivers for new OS? 3 years, 5 years? What's a reasonable expectation?
There's are basically two main ways how to do these things from a marketing standpoint.

a)
You use custom plugs/sockets, custom drivers, custom XYZ, because
  • you want to push your customers into buying more of your gear
  • you want something that nobody else has
  • since you have absolute control, you can rather easily change any piece of code with pretty much no regard for standards or customs
  • it's often cheaper - you don't need to comply with anything, it just has to work with your limited set of products
The downside is that you need to extensively support your products.

b)
You use standards and push for including your improvements into a standard form, because
  • it has a potential for greater sales - it invites other manufacturers and creates a larger user base for your products
  • (in case of an existing standard) allows integration of your products into other setups, resulting in more units sold
  • almost zero maintenance (when compared to custom solutions) - others do it for you or it's simply not needed
The downside is that standards tend to be limited in lots of ways and pushing for new revisions may take a lot of resources and several years ... and be unsuccessful in the end. Also some manufacturers think of their drivers (or ie. interfaces) as trade secrets and don't want the competition benefiting from their R&D.

I believe it's the limited user base (audiophiles) that leads manufacturers to (a), along with the intention to generate bias ("foo"). But there are indeed examples of (b), like SPDIF, RCA, ...
There are also examples of companies switching from (a) to (b), like Apple did with ALAC, making it a competition for FLAC, but are rather rare. The lack of support from other manufacturers doesn't really help (Microsoft and unsupported UAC2).

With regard to audio industry, I understand that computer audio is something that's been here only a very small portion of the entire history (since ~1900 ?) and is therefore exhibiting more of (a), very much like the early boom of smartphones and tablets (very volatile hardware and software) in the world of mostly-standard PCs (incl. PC components).
 


advertisement


Back
Top