Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Neco]

I have a Behringer UMC404HD  USB Audio device which I recently picked up for recording synths  but now use as my primary sound device (works great, sounds great).   

When I set MC to use its ASIO driver, it works fine  -  but when I close MC I lose all sound on the system unless I unplug the unit and plug it back in (USB).

It seems like MC is not releasing something when it is done?    When my system loses sound I can still open MC and hear audio from my media files.   

I can change the audio device settings to use i.e  WASAPI, DirectSound, etc and it will switch over fine while running, and then my system will have sound again.     Problems with doing that on WASAPI are audio pop when starting and exiting MC (also volume control lags),  and if I choose DirectSound  it works pretty good but then I got audible pops when seeking a stream.

I don't have any of those problems with the ASIO driver,  so I'd prefer to use it.   Just not sure what's going on here and why MC is causing me to lose sound when I exit the program

[JimH]

You can probably avoid the pops on startup (a DAC problem) by setting MC to "Play leading silence".  The options page has a search window at the bottom.

The ASIO driver may not be working as expected.

For the 64 bit version of MC, you need 64 bit drivers.

[Neco]

I have been running the 32bit version of  MC.   So I downloaded and installed the 64 bit version (verified via the help menu) however the problem with losing sound on exist while using ASIO still remains.     Is there anything else that I can do to try and troubleshoot this?

The audio interface works fine in all other programs.

[ferday]

what are you using as an ASIO driver

older ASIO4ALL drivers had this problem commonly

[Neco]

I'm using the driver supplied by my hardware's manufacturer.

http://www.musictri.be/Categories/Behringer/Computer-Audio/Audio-Interfaces/UMC404HD/p/P0BK1/downloads

[JimH]

Did you try playing leading silence with WASAPI, as I mentioned above?

[Neco]

Jim, sorry I didn't actually mess with that before I upgraded from MC 32 - > 64

If you are referring to the option shown in the attached file,  then it was already set to none.   I'm not sure if that is due to the reinstall / upgrade process or if it was always set like that.   I am, so far, not getting audio pops on  MC startup like I was before so I'm not sure if the switch to x64 simply fixed that.

WASAPI seems to work OK except now, (turning up the volume a  bit to test) I can detect  clicks/pops  on  Track start  (NOT always),  Track Change (NOT Always seems to alternate with tracks), and Track Seeking (Always).    I don't have crossfades or smoothing enabled  (I usually only set gapless for tracks), and I'll probably turn on the most minimalist of crossfading for other stuff if I can stand it.    I've also noticed since the volume is up, I get a similar  static-y  pop/click type sound when moving the volume control  up/down  quickly. 

I understand a lot of the crossfade/smoothing options can help hide this kind of stuff, I'm just wondering how normal it is overall.  I get very picky about what I like as far as crossfades/smoothing goes and generally I like VERY fast change response.   I don't like to seek a stream or change a track and have things "blend" together or stuff like that.   But I  do realize I am being very picky here.


It's a shame I have problems with the ASIO driver, because  I have virtually none of these problems when using it.  The most I seem to get is what I consider a more "normal" type of  pop/click artifact when seeking the stream  (in WASAPI the sound is more pronounced).

Could some kind of buffer setting fix any of this in WASAPI ?    Directsound is marginally better so I guess I could stick with that but it just annoys me I can't use my ASIO driver

[JimH]

The ASIO driver may or may not work.  It's provided by the manufacturer of your device.

With WASAPI, I may have missed it, but did you try the option to "Play Leading Silence"?  It's in MC in the Audio settings.  It may prevent the pops.  The pops are coming from your DAC, not from MC.

[Neco]

yes I have tried  both with and without the leading silence.
Not sure if things were this bad with my onboard sound, or my discrete  X-fi based card since its been a while since I've actually used MC.

Without using gapless for manual track changes checked, it does decrease incidents of popping, and adding the smooth(fast) option for track seeking I believe eliminates the seeking pops.   Gapless does work during normal playback on track changes for tracks which transition into each other so at least there is that.  It seems to be mostly manual intervention that causes my issues.   I suppose with things the way they are right now I can live with it.  Just annoying in that "doesn't work perfectly" kind of way. 

[RENI]

Same problem here. Win10 1709 Exclusive mode+64bit MC23 with ASIO driver from the USB DAC (a MATRIX Mini-i Pro 2) manufacturer. All sounds lost after closing MC, have to OFF and ON the DAC again to get the sounds working.

[Awesome Donkey]

I'd contact the DAC manufacturer about it and see what they say, because it seems to me it's an issue with the driver(s) or the DAC itself.

[tyler69]

exaSound updated their ASIO DAC drivers recently (15.11.17). Changenote is: "USB driver updated to comply with Windows 10 Signed Driver Enforcement".
Maybe this is interesting with regard to the OP's matter.