Author Topic: Tracks Automatically Playing After Another Media Source Ends  (Read 437 times)

blitstikler

  • Newbie
  • *
  • Posts: 9
Hello, I'm encountering an issue with MusicBee on Windows 11 where it automatically starts playing whichever track from the library is in the bottom player pane whenever media from other applications (like Bandcamp or YouTube) finishes. How can I prevent MusicBee from taking over playback in this manner? I'd appreciate any guidance on adjusting settings or configurations to resolve this.

Thanks!

hiccup

  • Hero Member
  • *****
  • Posts: 9133
That seems odd indeed.

Could you provide exact steps so that anyone can replicate what you are describing here?

blitstikler

  • Newbie
  • *
  • Posts: 9
Sure, it just happened again.

I have Youtube running in a window on Chrome, and Music Bee open as well.  Music Bee is open but not playing anything, a track is queued up but I haven't hit play or anything yet.

I watched half of a long video on Youtube, skipped around, and closed the window.  As soon as I closed the window with the Youtube video in it, the track queued in Music Bee started playing.

This also happens in situations when a youtube video, bandcamp file, or other video/music file finishes playing in my browser and doesn't go on to another file (like next up in Youtube or the next track in bandcamp).

This is super annoying and I have to close MusicBee anytime I'm not using it.

Thanks!

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10274
You had this same issue a year and a half ago. The issue then started off the opposite of what you're saying now, but by the fourth reply the behavior was the same as now.
https://getmusicbee.com/forum/index.php?topic=38788.msg211601#msg211601
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

blitstikler

  • Newbie
  • *
  • Posts: 9
Yeah, I'm sorry if this is confusing, as it's confusing to me as well.

I only reposted the question because previously I thought the blue tooth player had something to do with it, but I've since found that it most likely isn't it since it happens no matter what the output device is (laptop speaker, headphones, etc.)

I normally would've bumped that old thread but I didn't want to confuse anyone with the bluetooth info.  As you can see it wasn't resolved and I've just kind of dealt with it since then.  Hoping a year later maybe some new insight is out there.

hiccup

  • Hero Member
  • *****
  • Posts: 9133
It's good that phred found your other post/thread on this matter.
I think that mentioning bluetooth is an important factor here, and my guess is that it is the culprit indeed.

Try to:
 - completely remove your bluetooth drivers and any related bluetooth feature software/drivers
    (disabling them might also be possible, but simply removing them would be better to make sure)
 - make sure to unplug any physical bluetooth devices from your computer (or when on-board disable them through the bios)
 - restart your computer
 - check if no bluetooth drivers were automatically installed again in the background

Then try again and report back?
Last Edit: July 16, 2024, 07:40:19 AM by hiccup

BoringName

  • Sr. Member
  • ****
  • Posts: 916
Interesting that it has persisted from Windows 10 to Windows 11.

Did you try the suggestion in the last post of the other thread - Setting the audio player output to WASAPI (Exclusive)

blitstikler

  • Newbie
  • *
  • Posts: 9
I did try the original suggestion last time with no luck.  I will try setting player output to WASAPI (Exclusive) again and if that doesn't work, I'll try hiccup's suggestion and report back.

Thanks for all your help.