View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020073 | MMW 5 | Playback | public | 2023-06-01 21:41 | 2023-11-15 00:38 |
Reporter | peke | Assigned To | |||
Priority | immediate | Severity | minor | Reproducibility | always |
Status | feedback | Resolution | reopened | ||
Target Version | 5.1.1 | Fixed in Version | 5.1 | ||
Summary | 0020073: Seekbar do not follow Start/Stop Time settings | ||||
Description | Seekbar/WaveBar do not follow Start/Stop Time settings it shows full track time instead of Start/Stop time. Playback is unaffected only UI. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 2815 | ||||
|
Seekbar works the same way in MM4 too. |
|
Fixed in build 2815. |
|
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. |
|
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. |
|
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? |