View Issue Details

IDProjectCategoryView StatusLast Update
0000482OpenMPTUser Interfacepublic2014-02-09 21:48
ReporterReally Weird Person Assigned To 
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionwon't fix 
Platformx64OSWindowsOS Version8
Product VersionOpenMPT 1.22.07.* (old testing) 
Summary0000482: Play Time Wrapping Point
Description

I see that the play time wraps (goes back to 0 hours, 0 minutes, and 0 seconds). I am guessing that the intent was to make that occur at the 24-hour point. But, it seems to occur at 24 hours, 51 minutes, and 20 seconds, not precisely 24 hours. I am not sure if there is something that I am missing (as 24 hours, 51 minutes, and 20 seconds equals 89,480 seconds or 1,491-1/3 minutes) or if there is a bug which causes an incorrect wrapping point in the timer.

Steps To Reproduce

Allow a module to play for 1 day, 51 minutes, and 20 seconds

Additional Information

The quickest way to reproduce the behavior is to temporarily change the pattern quantity in the code to a number greater than or equal to 32,480, load [url=https://skydrive.live.com/#cid=00BD6492FE45944E&id=BD6492FE45944E%21116]this file[/url], and play patterns 11,251 (at which the play time is 24 hours) and 11,652 (at which the play time wraps).

TagsNo tags attached.
Has the bug occurred in previous versions?
Tested code revision (in case you know it)

Activities

Saga Musix

Saga Musix

2014-02-09 21:48

administrator   ~0001500

The playback position is counted in samples, not seconds, and the 32-bit sample count will wrap around at about 24 hours when using a playback frequency of 44KHz. Not going to fix that since it's just ridiculous.

Issue History

Date Modified Username Field Change
2014-02-09 21:41 Really Weird Person New Issue
2014-02-09 21:48 Saga Musix Note Added: 0001500
2014-02-09 21:48 Saga Musix Status new => closed
2014-02-09 21:48 Saga Musix Resolution open => won't fix