Am I Able To Resume Playback Position At App Restart?

[Dryst]

I have many continuous playback tracks in my music library that are over thirty minutes long. I am playing one right now that is over one hour in length. Is it possible for MMW5 to resume playback position of this track upon application restart? If no, I will submit another feature request.

[Dryst]

Oh incidentally, I have now gotten into the habit of daily restarts of MMW5. This prevents crashes that happen during continuous playback run. I am most likely a unique users in allowing the app to continuously play media nonstop 24/7.

[Lowlander]

Do you have Bookmarking (Tools > Options > Playback rules) enabled?

[Dryst]

No. It was not enabled, but I just enabled it.

[Dryst]

Do you have Bookmarking (Tools > Options > Playback rules) enabled?

This solved the issue. Thank you.

One thing to note after making this change my music library looks different. some but not all lengths of tracks have blue underlines now. I am not sure what this represents.

Here is a screenshot to show what I mean:

https://www.dropbox.com/scl/fi/1jqlw0vu ... 3ip7c&dl=0

[CrashMonkey]

This prevents crashes that happen during continuous playback run. I am most likely a unique users in allowing the app to continuously play media nonstop 24/7.

Happens here too multiply times a day. Do you get the Error popups, or crashes with a white screen?
Would be handy for the devs if people make bug/crash reports. I am also reporting the bugs that are preventing running the app 24/7.
viewtopic.php?t=86643 Option 4.

[Dryst]

I have not seen an error pop-up in a very long time, but I used to get those in earlier versions.

I see the complete white screen most of the time with the app completely frozen.

[Lowlander]

some but not all lengths of tracks have blue underlines now

That indicates the length of the file played (the bookmark position).

For crashes, please capture them in debug logs (step 4b) and attach them to a Support Ticket: viewtopic.php?t=86643

That will allow a developer to analyze why they happen on your setup.

[Dryst]

That indicates the length of the file played (the bookmark position).

Okay. If the file has been played in full, is there a point in displaying a complete blue underline? Does it make more sense to indicate it for partially played files that are pending restart position?

[Dryst]

For crashes, please capture them in debug logs (step 4b) and attach them to a Support Ticket: viewtopic.php?t=86643

That will allow a developer to analyze why they happen on your setup.

I suspect that the white screen crashes are related to leaks. My daily restart that prevents it seems to confirm this.

Some code resource leaks are happening that build up and eventually cause the crash is what I suspect.

[CrashMonkey]

Could be, in version 5 i used to get GC(Garbage collectors) errors, in the 5.1 i don't see them anymore.