Set MM to always start as Administrator and the problem is gone.

Hi,
Are you using latest MMW Beta version as we have made some improvements recently and I can't replicate it?

Hi guys,
could you find any solution for that problem in the meantime?
Regards
Bienenfreund

To work around use My Computer (if you don't want Library) or a Library node (faster browsing) to select files to play.

Hi,

I've had an issue across versions for a while now - I have a basic MediaMonkey install...only use it to play tracks off my hard drive in Win10 - not using it as a library or anything unusual.

When I go to double click a track in explorer, it opens up MM and starts playing right away. If I double click a different track in explorer while it's playing, I get a circle spinning in windows for about 30 seconds (my last song is still playing), and then the last track is cancelled and the new track starts playing. Any idea what the pause is for?

If I load up 30 tracks in the queue, they all play back to back fine...if I add tracks to the queue directly, they add right away.. It's only the 'instant play' that hangs.

It's annoying me to use Windows Media Player as my default player for the time being, since it's happened in win8 and Win 10 over different versions of MM for about a year. The tracks open up and play right away in WMP.

Any info on how to trouble shoot this is appreciated!
Pete

Soon (http://www.mediamonkey.com/forum/viewtopic.php?p=425791#p425791)

See http://www.mediamonkey.com/forum/viewtopic.php?f=3&t=69841

Is there an ETA or publicly available roadmap for MM5?

[quote]You are right, but unfortunately there is nothing we can do at the moment with current MMW version, but we are improving that in MM5.[/quote]
Well that's excellent to hear, thank you for confirming that you're working on it. :D

[quote="Camus II"]The problem - MediaMonkey is not telling the OS, when a call is made, to check for an existing instance of the program first for properly processing the request. The delay is caused by the OS being unable to launch another instance of MM when 'Allow just one instance of MediaMonkey' is checked (see 1). You can test this by unchecking that option (Tools>Options>General), and you'll find that a request to play/queue another track from Windows File Explorer will open immediately - but only in a new instance of MediaMonkey (see 2).

1 Windows (to it's credit) actually does the MediaMonkey user a favour by managing to establish recourse to a verifiable running instance of the program for processing the request - eventually..[/quote]Actually you are wrong here a secong MMW instance is started and after Load which take around 15-30 seconds due the database lock MMW (new instance) send old MMW info from explorer to handle it. In All other aspects you are completely right.

[quote="cageygee3"]I have run into this problem for a long time and I'm also not happy with the lack of a proper fix. I call bullshit on those who say it's a Windows issue or an Explorer issue. If I configure my system to play MP3s with VLC, or Groove (on Windows 10), or Windows Media Player, and I try the exact same repro steps mentioned here, the new MP3 plays immediately [b]in the same player instance[/b]. This is what users expect and the behavior I see with, really, any file type and any program I use. Only MediaMonkey has this ridiculous problem of a 15-second delay when trying to play a new file with an instance of the player already open.[/quote]You are right, but unfortunately there is nothing we can do at the moment with current MMW version, but we are improving that in MM5.

I have run into this problem for a long time and I'm also not happy with the lack of a proper fix. I call on those who say it's a Windows issue or an Explorer issue. If I configure my system to play MP3s with VLC, or Groove (on Windows 10), or Windows Media Player, and I try the exact same repro steps mentioned here, the new MP3 plays immediately [b]in the same player instance[/b]. This is what users expect and the behavior I see with, really, any file type and any program I use. Only MediaMonkey has this ridiculous problem of a 15-second delay when trying to play a new file with an instance of the player already open.

The problem - MediaMonkey is not telling the OS, when a call is made, to check for an existing instance of the program first for properly processing the request. The delay is caused by the OS being unable to launch another instance of MM when 'Allow just one instance of MediaMonkey' is checked (see 1). You can test this by unchecking that option (Tools>Options>General), and you'll find that a request to play/queue another track from Windows File Explorer will open immediately - but only in a new instance of MediaMonkey (see 2).

1 Windows (to it's credit) actually does the MediaMonkey user a favour by managing to establish recourse to a verifiable running instance of the program for processing the request - eventually.

2 It's worth noting too that no auto-switching (to the other instance) takes place when a second 'Play Now' request is made from Explorer.

You must organize your windows installation so that all music- and videofiles are associated with programs [u]other than[/u] Media Monkey, for instance VLC. (If necessary, google [i]file association[/i]). That way, when you (double) click a file in Explorer, VLC nearly instantly begins playing.
Media Monkey must always be started by clicking on the program icon, then you can play the files [u]from within the program[/u] without having to wait.

No change with version 4.1.11.1783

Thanks for performing that test, mangel. I guess we at least have a work-around until it gets fixed :-)

I just want to add that I tried nealrogers suggestion to start MediaMonkey directly not from a music file and then clicked on various files and it seems to be working. No delay!