shopping_cart
Showing 1 of 220 conversations about:
savvy
21
Nov 12, 2016
bookmark_border
I'm on Windows 10 and can only get 32bit/192khz to work. When I try to set the format to 32bit/384khz it says "Format not supported by this device.". I have the drivers installed. I would really like to get this thing to run at its optimal settings as I have some DSD files I'd like to test out for the first time!
Nov 12, 2016
muggy
53
Nov 14, 2016
bookmark_border
I wasn't aware that this unit supported DSD...
Nov 14, 2016
savvy
21
Nov 14, 2016
bookmark_border
Well, playing a DSD file at 32/384khz is better than 32/192khz. Thanks for the super helpful comment!
Nov 14, 2016
muggy
53
Nov 26, 2016
bookmark_border
I got my unit today, tried the various drivers linked on this forum - same result. Everything works fine up until 32bit 192khz, but 32bit 384khz produces the same error "Format not supported by this device".
Nov 26, 2016
savvy
21
Nov 27, 2016
bookmark_border
Dang. Oh well. 32 192khz is still pretty damn good! lol
Nov 27, 2016
muggy
53
Dec 2, 2016
bookmark_border
I think I may have found part of the answer...for foobar there are various components you can install that bypass windows DirectSound. You can get ASIO or WASAPI. The SMSL M6 I believe was made for ASIO.
In the Foobar settings you can choose to output to ASIO or WASAPI, and then I believe if you can force 384khz sampling rate. I found that I like the WASAPI output, set to give exact bitrate output (i.e., I use flac files that are 44.1khz, and it outputs 44.1khz).
Let me know if you're able to get your DSD files to work, I'm sure you had to go through lengths to play them through software in the first place.
Dec 2, 2016
muggy
53
Dec 4, 2016
bookmark_border
I was able to play DSD64 files through foobar, the files I had were 352.8khz, and the unit played at this rate just fine under WASAPI output.
Dec 4, 2016
savvy
21
Dec 7, 2016
bookmark_border
thanks for the info! :D
Dec 7, 2016
Thumps22
35
Dec 30, 2017
bookmark_border
i got mine to work in windows 10 with windows native driver. i had to uninstall driver and software then rollback to microsoft driver after the auto install of cmedia driver. settings working on 32bit/384. Im on windows 10 latest update to todays date. first thing i did was uninstall the cmedia 2.0 driver. then i went into sound panel, playback devices, right clicked on smsl m6, properties, then properties again, change settings, uninstall device and check the uninstall software box. turn off smsl and restart computer. once back on turn on the smsl m6. hopefully it natively installed the windows drivers before it defaults to cmedia driver. if it does auto install just rollback the driver to windows and done. 32bit/384 work flawlessly. not sure if windows finally includes this or im a lucky 1.
Dec 30, 2017
savvy
21
Jan 5, 2018
bookmark_border
dang, thank you for the detailed info! i'll give that a try today. :)
Jan 5, 2018
Thumps22
35
Jan 5, 2018
bookmark_border
Np mang! Remember make sure its running the windows driver and not c-media.
Jan 5, 2018
savvy
21
Jan 6, 2018
bookmark_border
Got it working. Your method worked flawlessly, except that MusicBee kept giving me buffer and initialization errors when trying to play through the DirectSound driver (WASAPI and ASIO worked fine, but those don't pair nicely when trying to multi-task). Thankfully I saved a restore point and reverted. After reverting my system somehow noticed a driver was out of date and instantly rebooted and installed Windows updates...
For future readers in similar issues, I'm currently sitting on C-Media Inc. driver version 10.0.12.9 and successfully running my SMSL M6 at 32bit/385khz on Windows 10 Home - Version 1709 - Build 16299.192.
Jan 6, 2018
Thumps22
35
Jan 6, 2018
bookmark_border
Yep i had the same issues with the windows driver. So you got cmedia to run 385 in settings? I already returned mine and got a m8a so i cant do any furthur testing on the m6.
Jan 6, 2018
savvy
21
Jan 6, 2018
bookmark_border
Indeed! Everything is working as before, but now running at 32bit/385khz. :) Thank you!
Jan 6, 2018
View Full Discussion