Setting a "Start time" fails to skip to beginning

Get answers about the current version of MediaMonkey 5

Moderator: Gurus

ChristianA
Posts: 10
Joined: Thu Jun 01, 2017 11:01 am

Setting a "Start time" fails to skip to beginning

Post by ChristianA »

Hello everyone,
This is a universal problem that is persisting across reboots and versions, so I'm not sure why I'm the only person reporting it. When I set a start time (to skip talking at the start of a live track, or the dull "toccata" part of a toccata and fugue, eg.) the track always begins from 0:00 instead of the time I requested.
- I know the program is getting the update, because the total track time decreases appropriately
- I have enabled bookmarks for all genres not just the relevant one, in case that matters somehow
- This is a problem on both android (fine) and windows (not fine); has been a problem since 4.2, now using 5.1.0.2832
- This is a problem both within and between genres (going from music to classical music and vice versa, or staying within either music or classical)
I'd rather not physically edit tracks to the right starting time since I want to have the option to hear the rest of the track, and also it takes a lot of time. Let me know if you have any ideas about why this might be happening.
Lowlander
Posts: 56884
Joined: Sat Sep 06, 2003 5:53 pm
Location: MediaMonkey 5

Re: Setting a "Start time" fails to skip to beginning

Post by Lowlander »

It works for me, can you try a different Output Plugin?
ChristianA
Posts: 10
Joined: Thu Jun 01, 2017 11:01 am

Re: Setting a "Start time" fails to skip to beginning

Post by ChristianA »

Interesting! It seems to be working some of the time for MediaMonkey DirectSound but never for MM WASAPI. There seems to be some kind of conflict between bookmarks and start time, so that if the bookmark is set to a time before the start time it defaults to the bookmark. However, if I manually jump to some other time on the playback bar, it rescales to the time it should be. However, when it gets to the end of the track, it does NOT reset the bookmark to the desired start time, but resets to 0:00, and so it starts from the undesired beginning again.
I mentioned this before, but if the bookmark is set to a time AFTER the stop time, it starts from the bookmark, plays the last few seconds, then moves to the next song WITHOUT resetting the bookmark, which means you just hear the last few undesired seconds over and over and over.
This is happening with both DirectSound and WASAPI.
MattTown
Posts: 279
Joined: Sun Mar 15, 2009 5:09 pm
Location: Australia

Re: Setting a "Start time" fails to skip to beginning

Post by MattTown »

I also utilise the start and end time settings to get specific subsets of long tracks, but have found that it can be tricky to get the new settings recognised.

In particular, if you edit a file that is in the Now Playing list for start and finish time, then you have to remove that file from the Now Playing list before the new settings are recognised. Its almost as if the Now Playing functionality has a cache of the original file in it and you have to force that to be replaced with the edited version.

I generally only have a small number of files in the Now Playing list. If I edit one of those for start/finish time then after OKing the edit I remove the file from Now Playing, then briefly play a different song. After that, selecting Play Now on the edited file from the Main List should get the playing happening with the new timings as intended.

Generally this is only a problem for me while fine tuning the start and end times via repeated edits/replays. After the edits are concluded and other files have been played, I find that the start/end times are reliable.

Cheers

Matt
MM 2024.3019 (WEF 4 May 2024, Portable Mode), Gold lifetime license, user since 2009.
Currently 27K files. Library and music files are on a separate partition (E:\) on external USB drive.
Windows Surface Book (Original), i5, 8GB RAM, 250GB SSD.
Win10 Home 64 bit, update: 22H2 19045.3570
MMA 2.0.0.1103, Android 13 on Nokia XR20, music files on SD card.
ChristianA
Posts: 10
Joined: Thu Jun 01, 2017 11:01 am

Re: Setting a "Start time" fails to skip to beginning

Post by ChristianA »

That trick didn't work for me. I moved my Now Playing list to a temporary other play list, created a new now playing queue, let it run for a minute, skipped to another track, let that run for a minute, and then went back to my Now Playing list and it still completely failed to start at the start time I asked for, instead starting at 0:00 on three different tracks, whether I clicked onto the
track, skipped tracks after a few seconds until I got to it, or let the previous song play to the end and then start.

I wasn't expecting it to work, since even tracks whose start times I have changed months ago and not heard since still start at 0:00 instead.

I'd like to point out that even if this trick HAD worked, it's still a painfully cumbersome process. I really want to use MM5, like I have been loyally doing since MM2, but if they can't get this fixed I may need to move on. :(
MattTown
Posts: 279
Joined: Sun Mar 15, 2009 5:09 pm
Location: Australia

Re: Setting a "Start time" fails to skip to beginning

Post by MattTown »

ChristianA wrote: Fri Mar 15, 2024 12:11 pm .. it still completely failed to start at the start time I asked for, instead starting at 0:00 on three different tracks ...
Yes, the same has happened to me. Unfortunately, the formatting of times in the Details pane is misleading. For an unmodified track, the Start time: in Filecontextmenu > Properties > Details shows 0:00 for a m:ss syntax, while the End time: shows (my example) 4:10.435, with a m:ss:ddd syntax, where ddd is decimal seconds down to thousandths.

What I have found reliable is to ignore the difference and just put a simple m:ss value in for both start and finish. For example in my file, if I put 1:01 into Start time: and 3:02 into End time: then I am confident (after clearing the now playing queue) that the file would start at 1:01 and end at 3:02 and would show a total duration of 2:01.

Most of the complexity for me arises from repeated edits to get the timing exactly right. If you don't have that issue then the start and end time should work for you as easily as anything else in MM.

Cheers, Matt
MM 2024.3019 (WEF 4 May 2024, Portable Mode), Gold lifetime license, user since 2009.
Currently 27K files. Library and music files are on a separate partition (E:\) on external USB drive.
Windows Surface Book (Original), i5, 8GB RAM, 250GB SSD.
Win10 Home 64 bit, update: 22H2 19045.3570
MMA 2.0.0.1103, Android 13 on Nokia XR20, music files on SD card.
ChristianA
Posts: 10
Joined: Thu Jun 01, 2017 11:01 am

Re: Setting a "Start time" fails to skip to beginning

Post by ChristianA »

Rounding off to whole seconds did not help.

However, in the 5.1.0.2382 version: if you (1) use the WASAPI output .dll AND (2) disable bookmarking AND (3) disable remove gap at start/end, it seems to work most of the time. I suspect the problem is mostly that start/end-time will not play well with bookmarking, so you can choose one or the other but not both. This is too bad, but I can live with it. Thanks to everyone who helped with this.
MattTown
Posts: 279
Joined: Sun Mar 15, 2009 5:09 pm
Location: Australia

Re: Setting a "Start time" fails to skip to beginning

Post by MattTown »

ChristianA wrote: Thu May 09, 2024 12:15 pm ... in the 5.1.0.2382 version: if you (1) use the WASAPI output .dll AND (2) disable bookmarking AND (3) disable remove gap at start/end, it seems to work most of the time. I suspect the problem is mostly that start/end-time will not play well with bookmarking, so you can choose one or the other but not both.
Agreeing with your suspicions - works for me with version 2024.0.0.3019, using the WASPI output and not using bookmarking nor removing start/end gap.

Cheers
Matt
MM 2024.3019 (WEF 4 May 2024, Portable Mode), Gold lifetime license, user since 2009.
Currently 27K files. Library and music files are on a separate partition (E:\) on external USB drive.
Windows Surface Book (Original), i5, 8GB RAM, 250GB SSD.
Win10 Home 64 bit, update: 22H2 19045.3570
MMA 2.0.0.1103, Android 13 on Nokia XR20, music files on SD card.
Post Reply