Popping sounds on track change in foobar?

Off-Topic
1

Hey didn’t seem like there was a appropriate place to ask this question, but I’ve been experiencing a pop every time I change tracks manually in foobar… It does not happen when I let the track change naturally.

This has only been happening recently since I switched to the enog2pro dac, and I was guessing it might have something to do with it (maybe optical?) the strange thing is that it only happens with foobar. I checked with musicbee and I have no pops whatsoever.

I’m running foobar in wasapi (event) and I already tried it with push mode and direct sound and I still get the pops, so I don’t think it is wasapi related. output data format in foobar is set to 24bit.

anybody have a idea of what could be causing this? I was almost certain it was the Enog2pro but since i don’t get pops in musicbee I’m now thinking it’s a foobar issue or perhaps a combination of both…

Any help will be greatly appreciated

2

Could be that the moment you change track an incomplete package (data unit) is sent to the DAC.
In what driver mode have you had MusicBee?

I know in WASAPI (excl.) I get a moment of “incomplete frame” playing over my Focusrite 2i4 too. Does not happen in ASIO.

3

Musicbee is using wasapi shared… just checked with exclusive and it does seem to be popping as well in musicbee but no where near as loud as foobar… so i guess a issue with wasapi exclusive? it’s just strange though that I never noticed until i started using the enog2pro…

Edit: just installed wasapi shared for foobar and no popping! weird.

1 Like
4

Is it more of a clicking sound?

5

somewhat… I don’t know. Sometimes it is very apparent and it sounds like a pop other times it’s more subtle and not as intrusive, more of a low click sound… kinda confusing actually.

6

I know some DACs will click whenever they switch between bitrates (like when you play a new track) – mine does in particular.

7

Which is perfectly normal, my bifrost 2 does that too. Might not be anything to worry about. If it only happens with wasapi, it’s defnitely just a bitrate change, where as in directsound, it just goes off of whatever bitrate you have set in your OS, so it doesn’t click.