If you mean shutdown windows without exiting musicbee and windows classifies it as a critical shutdown, then v3.4 will not attempt to save the settings file (MusicBee3Settings.ini) to avoid file corruption.
Could it please be an option?That looks like asking for an option to possibly introduce file corruption.
Could it please be an option?you will either change how you shutdown windows - its only when windows needs to shutdown without allowing apps to save data that MB skips the settings save or go back to using v3.3
I just signed up because I have a similar issue. I like to have music playing while I sleep. So I have a Windows task to launch Music Bee at 9pm, and a separate task to shut it down at 9am. Music Bee is configured to resume playback (not position). This worked fine for a long time, but then about a year or so it stopped working, and I have to manually start the playlist again every evening.The developer directly addressed the issue of improperly shutting down the program and gave mitigation suggestions in the post right above yours, so I'm not sure what you hope to accomplish reiterating the problem.
I don't care that it starts from the previous position, only that it starts playing again.
This feature must be able to deal with unexpected shut downs.
The developer directly addressed the issue of improperly shutting down the program and gave mitigation suggestions in the post right above yours, so I'm not sure what you hope to accomplish reiterating the problem.
Task Scheduler shut downs are like killing the task from the Task Manager. It is not the proper way to close a program. MusicBee has a timed shutdown feature (File->Activate Auto-Shutdown) which closes the program properly on a timer.
5) The obvious conclusion is that Music Bee needs better support for unexpected shutdowns (something Windows is notorious for) or needs a better scheduler.As was explained by the developer in the post directly above your first post, the the result you're seeing in later versions is the "better support for unexpected shutdowns." Prior to this change, a risk of corrupted files existed. Problem solved.
I posted a thread in the wish list, but I still think it's a bug that needs to be addressed.
PressTheKey:
Send, {ctrl down}{shift down}{F4}{shift up}{ctrl up}
In case anyone stumbles upon this thread and they have the plugin "windows 10 media control overlay" this may be at fault
is the same issue also happening because you are using that plugin? Otherwise you should try the v3.4 patch version which made a change to how cached data is saved on windows shutdownIn case anyone stumbles upon this thread and they have the plugin "windows 10 media control overlay" this may be at fault
Not much of a solution, more of a compromise.