I have MMW set as the default program to open mp3 files.
Since the last update (3154) whenever I double click an mp3 in an Explorer window, MMW closes and restarts before playing the file. In previous versions it would just open the mp3 straight into the running instance of MMW without closing and restarting.
Opening an mp3 from Explorer closes and restarts MMW [#21612]
Moderator: Gurus
Re: Opening an mp3 from Explorer closes and restarts MMW
I have not been able to reproduce. What state is the Player in when this happens? Is it Stopped, Paused or Playing?
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Opening an mp3 from Explorer closes and restarts MMW
Makes no difference whether MM is playing or stopped, if I double click an mp3 file in Explorer it shuts down MM and then relaunches it and starts playing. Only started doing this behaviour since the last release.
Re: Opening an mp3 from Explorer closes and restarts MMW
Rolled MM back to previous version 3153 and it doesn't do it there - all works fine as expected. Double clicking an mp3 launches it in MM without quitting it first (although Task Manager still shows the same multiple entries for MM even though I'm only running 1 instance).
Re: Opening an mp3 from Explorer closes and restarts MMW
That's normal and many programs do this, different features run in their own instance.
Does going back to 3154 have the issue return?
Does going back to 3154 have the issue return?
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Opening an mp3 from Explorer closes and restarts MMW
Yes, this was a regression in 3154 already fixed as
https://www.ventismedia.com/mantis/view.php?id=21612
So please wait for 3155 or use 3153 instead
https://www.ventismedia.com/mantis/view.php?id=21612
So please wait for 3155 or use 3153 instead