Author Topic: MB Player stopped working: keeps hanging after 3 seconds  (Read 2128 times)

WimYogya

  • Sr. Member
  • ****
  • Posts: 473
Hello,
Since a few days I cannot use MB anymore if I want to play music from my library.
Even after applying the newest patch of Jan15 (3.0.6224) each track stops in an endless hickup after around 3 seconds.
One time I saw a message that the audio device was locked up (or something like that) and I was advised to restart MB.
With the same result, however...

With other players outside MB there is no problem.

These are the newest error log messages:


16.01.2017 19:04:00 - X:\MB ORIGINAL\! MUSIC\:Thread was being aborted.
16.01.2017 19:07:31 - X:\MB ORIGINAL\! MUSIC\:Thread was being aborted.
16.01.2017 19:41:29 - X:\MB ORIGINAL\! MUSIC\:Thread was being aborted.
16.01.2017 22:05:40 - 6.1.7601.65536 - 3.0.6224.39247 - #=qQchOs9Qam2jixOzOiZQZVVcW5TguQZZUDeiy91T04Fb33oQZmHCfukaJvS2EAgJc: Exception of type '#=qQchOs9Qam2jixOzOiZQZVVcW5TguQZZUDeiy91T04Fb33oQZmHCfukaJvS2EAgJc' was thrown.
   at #=qczuRJlV0i05najoo$HZgsxc1csf4OhnWldqJxrc9HGk=.#=qOm1BRScHYzt1yIpKGY8d7w==(Boolean #=qCPNFzCDRuJWJQmY8jRN90w==, #=qBIKnE$4cMuxSPJid1AAkuNvgwNScC9krUyCk9KCtTLo= #=qCkkH0$R9yGe4T2iJjhVOkA==, Int32 #=qQP6HF6ksYlWU1t2fSZiRKM5$EWu2lrcMX1BXGthq7cQ=)
   at #=qczuRJlV0i05najoo$HZgsxc1csf4OhnWldqJxrc9HGk=.#=qpbHQYoZVDcVM9iwkn2DSJA==(Boolean #=q3JXbwiIoWO5Ubf0QkLnKqJcIqFigP89lS3djAGc8qVs=, Boolean #=qv$qKcS8FAaq_6wVF84qkrxqWiyzmtCZyiGHsOmM6fBw=, Int32 #=qdcA5_ET6icDJX31f2cPeNWlOuV5b02beUu2fPt918gM=)
   at MusicBee.Media.PlayManager.#=qwgUdf4_Bd1xZKVf0yGeycVHYYjMbSiwcFwRn5JGmmtE=(Boolean #=qqtvIuTJmhxzzMNUtEjpCow==, Boolean #=q1QeT04wubF41Jld2U9Q7NRjN0DQ351GHns2alcyhF24=, Boolean #=qvwpwRaHAn3kC4MyKFUhGxHVdZuQZ4b75xKyeJw3XZr4=, Int32 #=qHL4tHlvYejZsdG5iZfxp9sB3s7xqQWAt4sUjU0XCJuY=)
   at #=qgAgN0yD6QUw$ivGvlEsiH84b4XMN7Wr20vaDv3BV3nf_3kY51eMUCLsw0NJUIguw.#=qxGxVbmuTBrNcZPRNjfsMHGOaXqHLTmDUaLWjdDojubI=()
   at #=q667WbFKCkIfd3KTGDsQMBpQQcxZaCPnysgLKHLRWsvmk4wmQvcbujxPrlQ5l7qXm.#=qvF$KhVAo_$wbJ99pr06EYw==()

16.01.2017 22:05:52 - 6.1.7601.65536 - 3.0.6224.39247 - #=qQchOs9Qam2jixOzOiZQZVVcW5TguQZZUDeiy91T04Fb33oQZmHCfukaJvS2EAgJc: Exception of type '#=qQchOs9Qam2jixOzOiZQZVVcW5TguQZZUDeiy91T04Fb33oQZmHCfukaJvS2EAgJc' was thrown.
   at #=qczuRJlV0i05najoo$HZgsxc1csf4OhnWldqJxrc9HGk=.#=qOm1BRScHYzt1yIpKGY8d7w==(Boolean #=qCPNFzCDRuJWJQmY8jRN90w==, #=qBIKnE$4cMuxSPJid1AAkuNvgwNScC9krUyCk9KCtTLo= #=qCkkH0$R9yGe4T2iJjhVOkA==, Int32 #=qQP6HF6ksYlWU1t2fSZiRKM5$EWu2lrcMX1BXGthq7cQ=)
   at #=qczuRJlV0i05najoo$HZgsxc1csf4OhnWldqJxrc9HGk=.#=qpbHQYoZVDcVM9iwkn2DSJA==(Boolean #=q3JXbwiIoWO5Ubf0QkLnKqJcIqFigP89lS3djAGc8qVs=, Boolean #=qv$qKcS8FAaq_6wVF84qkrxqWiyzmtCZyiGHsOmM6fBw=, Int32 #=qdcA5_ET6icDJX31f2cPeNWlOuV5b02beUu2fPt918gM=)
   at MusicBee.Media.PlayManager.#=qwgUdf4_Bd1xZKVf0yGeycVHYYjMbSiwcFwRn5JGmmtE=(Boolean #=qqtvIuTJmhxzzMNUtEjpCow==, Boolean #=q1QeT04wubF41Jld2U9Q7NRjN0DQ351GHns2alcyhF24=, Boolean #=qvwpwRaHAn3kC4MyKFUhGxHVdZuQZ4b75xKyeJw3XZr4=, Int32 #=qHL4tHlvYejZsdG5iZfxp9sB3s7xqQWAt4sUjU0XCJuY=)
   at #=qgAgN0yD6QUw$ivGvlEsiH84b4XMN7Wr20vaDv3BV3nf_3kY51eMUCLsw0NJUIguw.#=qxGxVbmuTBrNcZPRNjfsMHGOaXqHLTmDUaLWjdDojubI=()
   at #=q667WbFKCkIfd3KTGDsQMBpQQcxZaCPnysgLKHLRWsvmk4wmQvcbujxPrlQ5l7qXm.#=qvF$KhVAo_$wbJ99pr06EYw==()

No clue what they mean or indicate.
The last one may refer to my erroneous attempt to change the audio-settings of MB from DirectSound into anything else.

Help will be highly appreciated - as usual.
Thanks in advance!

Wim
WimYogya
retired Dutchman (1944) in Yogyakarta, Indonesia

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34312
the error messages means the bass library is locked up when accessing the audio-device. I will improve the error handling for when you switch to DirectSound but that wont help with the general playback issues

WimYogya

  • Sr. Member
  • ****
  • Posts: 473
Hi Steven,
Thanks for your speedy reaction. I am, however, not sure if I understand it.
Bass library locked up? By whom or what or how? What does it mean?
Directsound: as far as I know that is the default audio setting. Am not aware of any chosen or changed setting by myself.
So if you improve the error handling on your side, what must *I* do to guarantee errorfree performance (as up till a day or so ago?)

Hope you can clarify.
Thanks,
Wim
WimYogya
retired Dutchman (1944) in Yogyakarta, Indonesia

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9299
"locked up" means "frozen" - it's not responding. For any one of a number of reasons. Especially if you were switching back and forth between output devices.

If you already exited and restarted MB and it was still locked up, then try restarting your computer.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

WimYogya

  • Sr. Member
  • ****
  • Posts: 473
@phred I did NOT switch between output devices, wouldnt even understand which one is more preferable than what i had...
DIRECTSOUND has been selected, but not by me. Default?
Restarting MB did not help, restarting my PC neither.
After that I tried to select another audio option than DIRECTSOUND (without understanding which one it should be) but that too failed...
Wim
WimYogya
retired Dutchman (1944) in Yogyakarta, Indonesia

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9299
@phred I did NOT switch between output devices, wouldnt even understand which one is more preferable than what i had...
Except that here you say you did:
The last one may refer to my erroneous attempt to change the audio-settings of MB from DirectSound into anything else.

Quote
DIRECTSOUND has been selected, but not by me. Default?
Yes DirectSound is the default.

Quote
Restarting MB did not help, restarting my PC neither.
After that I tried to select another audio option than DIRECTSOUND (without understanding which one it should be) but that too failed...
I find it odd that restarting the PC didn't unlock it. Perhaps someone else will have some input on this.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

WimYogya

  • Sr. Member
  • ****
  • Posts: 473
@phred:
Yes, I already 'admitted' that I tried to change the setting - in the end, after every other solution failed.
This one too (creating a different error message), so I quickly switched back to DIRECTSOUND.
WimYogya
retired Dutchman (1944) in Yogyakarta, Indonesia

WimYogya

  • Sr. Member
  • ****
  • Posts: 473
Problem SEEMS to have solved itself - mysterious...
Several attempts to replace the player failed, numerous restarts of MB and/or the PC did not help.
After a 3 hour power cut at home the problem seemed to be gone - but 10 mins later it restarted again, but the hickups stopped after 5 mins, smooth playing, hickups again for 5 mins etc.

Slowly slowly things went better, without me changing any setting.
At this moment normal playing seems to be back again.
I keep my fingers crossed...
Thanks
WimYogya
retired Dutchman (1944) in Yogyakarta, Indonesia