View Issue Details

IDProjectCategoryView StatusLast Update
0020073MMW 5Playbackpublic2023-11-15 00:38
Reporterpeke Assigned To 
PriorityimmediateSeverityminorReproducibilityalways
Status feedbackResolutionreopened 
Target Version5.1.1Fixed in Version5.1 
Summary0020073: Seekbar do not follow Start/Stop Time settings
DescriptionSeekbar/WaveBar do not follow Start/Stop Time settings it shows full track time instead of Start/Stop time.

Playback is unaffected only UI.
TagsNo tags attached.
Attached Files
image.png (75,576 bytes)   
image.png (75,576 bytes)   
image-2.png (17,749 bytes)   
image-2.png (17,749 bytes)   
Fixed in build2815

Relationships

related to 0018201 feedbackrusty Bookmarks: Handling of Multiple bookmark/s 
related to 0020226 closedLudek CUE part fails to cast when auto-conversion is involved 

Activities

michal

2023-09-11 09:55

developer   ~0072755

Seekbar works the same way in MM4 too.

michal

2023-09-11 15:06

developer   ~0072757

Fixed in build 2815.

lowlander

2023-09-18 18:21

developer   ~0072801

Last edited: 2023-09-18 18:23

On 2815 the Seekbar shows just the time between Start and Stop time as specified.

1) However, this means a user can't seek before Start time or after Stop time if they wish to do so as this isn't available on the Seekbar. Instead it would be better if the Seekbar shows full file, and instead shows markers for Start/Stop Time or a different color shade for Start/Stop time segments of the file. This would visually indicate the Start/Stop Time, but also allow users to still seek in those segments.

2) Bonus would be if user can adjust Start/Stop time by moving marker on seekbar.

3) Length field should maybe show playable times/full file length, where full file length shows greyed out.

michal

2023-09-18 19:00

developer   ~0072804

Last edited: 2023-09-18 19:00

1) it is expected, data before start time and after stop time are not intended for playing. I tried another app and it behaves the same like MM5 now
3) the same - it is not intended to play, so why show it, it would be confusing

Anyway your suggestions are very different from the original from this issue. Assigning to Rusty to decide, as I cannot do both.

rusty

2023-10-19 19:07

administrator   ~0073172

This feature/implementation seems problematic for the reasons described by LL: no indication that a track has modified start/stop times (before the user could at least see that start/stop was at a different point in the track) and no indication of what the original times are (which makes it difficult to change the start stop time if the start/stop time is set incorrectly).

So my feeling is that this should be reverted until we have a chance to spec & implement it in a manner that addresses the concerns raised. Peke do you agree?