Unable to initialise sound device (error=BASS_ERROR_DRIVER)

[Oxb78]

MusicBee v3.1.6512.37408 (Win10.0), 14 déc. 2017 17:51:

#=quNSXZemwORqHO5QqjC7ijhXVLfzpQsJwh1VUBeeWjw4=: Unable to initialise sound device (error=BASS_ERROR_DRIVER)
   à #=q_i_LrTKK7BwuATKOua8qmqutzCW6b15xw1dKCwcv_Zc=.#=q36MFYyP0JJ0gJ7U0phM70A==(#=qccM21pX5G5sd6tbVaj0MyKyngxtuC2v87b0lcla4rbY= #=qTLDI2SZOe2inY4_HCaMpHw==, String #=qZJixqmOCNOLB2KDiGj9Hb_3avtxDGPo9Gh6tOZdMNN8=, #=quUsQu7wW7Q8y0$dMYNdliw== #=qig0YJosWFsI_2yqlkXqrTKNjf3bx$xjwtnNQNP452GE=, Int32 #=qrK$OiSL_YnfcZhIkwj3NLA==, String #=qnkZ6LKFdJjQrAdRfUFhC$Q==, IntPtr #=qvoWXCntRJbbttJfWnERskA==)
   à #=qmZhwHJF$AlGFGV33nuDlwmVP4G9dMChTV_8ROnXyWzGrduk0XGGp3964ylGmgjU_.#=qDodk6x9AWvGRrHce$$oEKgpuSbf4sp_urJjTnJ8P1xo=()
   à #=qZJ30YCwuBFanakMMQNelUnMMaghJdejTh5mHfa96C0fHNtgdQmInxQJERThPFEuc.#=qfyBnp4O9lWfnRHNmuK1fjg==()

[phred]

Try white-listing bass.dll in your AV/Security software.

[Oxb78]

Hello,

Thank you for the tip, it runs.

I have excluded the complete directory in Avast. Sound is working now on my bluetooth speakers.

I just want to mention that, by excluding also the application in Avast, solves the second issue I had, start the application (outside the sandbox).

[phred]

Please report this to Avast via their forum. Steven has been fighting with them to get MB off their radar for quite some time and the more folks complain to Avast, the better chance there is that they will fix it.

[Steven]

I do wonder how sound output would be a security threat. And how setting the windows 8 compatibility flag defeats its very robust security guards. Definitely quality software from a responsive company that cares about its clients.

[phred]

I do wonder how sound output would be a security threat.

Maybe they want to be the arbiter of what we should listen to. In most countries, this would be called censorship.

But seriously, I, like you, think Avast just doesn't care enough to do anything about it. They've got their algorithms working and they don't have to do any more.

[CritterMan]

Symantec does the same. Playing hell with my music at work. I literally have to reinstall my portable installations .dll and .exe files before every time I launch MB. My IT dept has whitelisting locked down.

[Steven]

Symantec does the same. Playing hell with my music at work. I literally have to reinstall my portable installations .dll and .exe files before every time I launch MB. My IT dept has whitelisting locked down.

did you try submitting musicbee to Symantec for whitelisting?

[CritterMan]

did you try submitting musicbee to Symantec for whitelisting?

Yep.

[stevearowell]

NO OUTPUT!!!!

[phred]

NO OUTPUT!!!!

You'll be to be a lot more specific if you expect help getting this resolved.

What version of MB are you using? (Help > About)
How was MB installed? (Installer, Portable, Store)
Have you whitelisted MB in your AV software?
What are you audio player settings for output and device?
Have you updated your audio drivers?

[lacheesy101]

Hi all,

Just wanting to share another fix as I have had the same error(s)  (ERROR=BASS_ERROR_DRIVER) and (ERROR=BASS_ERROR_ALREADY)

MB Version: 3.4 and 3.5

My issue was using a Bluetooth speaker to output, once it disconnected then had to manually select the device back to "Default" under the Windows settings - it was not an issue with MB player, none of the preference settings can fix. These are the settings I needed to ensure that were selected to rectify the error.