View Issue Details

IDProjectCategoryView StatusLast Update
0014002MMW v4Playerpublic2017-05-05 00:04
Reporterpeke Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Target Version4.1.16Fixed in Version4.1.16 
Summary0014002: Playback: Track cut off if bookmarking is enabled
DescriptionTo replicate follow these settings:

Playback Rules -> Music -> Enable bookmarking -> Disable all others
Output Plugin -> Enable Crossfade (>7 Seconds) and enable all 4 options (gapless and smooth)

On playback play track that have Fadeout and/or small silence on end (2-4s) cut off at crossfade setting.
TagsNo tags attached.
Fixed in build1834

Activities

Ludek

2017-02-11 18:26

developer   ~0047256

Peke, isn't this expected? I guess that also non-bookmarkable tracks are cut off (when the crossfade option include remove silence at the end)?

peke

2017-02-11 22:46

developer   ~0047257

Last edited: 2017-02-11 22:49

No, it is not expected as if crossfade is enabled along with bookmark and remove silence then end of track would be cut off instead of crossfade.

Example:
Enable bookmarks for MUSIC collection
Track 1: Silence end 2s (checked in audio editor)
track 2: silence beginning 1s
Crossfade set to 10s, remove silence enabled

Nowplaying list:
1. Track 1
2. Track s

Player Track 1 is playing and on -10s from end track 1 MMW cut track 1 and Track 2 starts playing without crossfade and result is 8s of Track 1 is cut off.

Ludek

2017-02-12 21:21

developer   ~0047259

Last edited: 2017-02-12 21:34

I was finally able to figure out the steps to reproduce, the Track 2 _needs_ to be played before and with set bookmark.
Then your statement is valid and Track1 is cut off once Track2 starts playback from the previously bookmarked position (without crossfading).

i.e. MM fails to crossfade to the middle of the next track.

jiri

2017-02-13 08:51

administrator   ~0047262

It's a bit unclear what to do in such a situation, whether crossfading into a middle of another track makes sense. I think that technically it would be easiest to make it an exception, i.e. to tell the output plugin to _not_ crossfade in such a case.

Ludek

2017-05-04 10:44

developer   ~0047908

The solution suggested by Jiri implemented in 4.1.16.1834 + merged to 5.0.0.2066

peke

2017-05-05 00:04

developer   ~0047921

Verified 1834