Comment 2 for bug 1666050
Revision history for this message
| Uwe Klotz (uklotzde-deactivatedaccount) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
This has now happened multiple times when setting a cue point. Only one deck is affected, it doesn't matter if another deck is playing or not. The engine code for calculating the sample offser when setting cue points is definitely broken!