On an MP3-encoded file, I am trying to setPosition() using FMOD_TIMEUNIT_MS. With 1 particular file, at 1 particular target I have experienced the following behavior: after repeated calls to getPosition(), my position is 1 ms away from the target and never reaches the target.
Is this an artifact of the MP3 compression?
I am aware of the FMOD_ACCURATETIME flag, but I’d prefer not to burden all of my file opens with the additional time or memory to build a seek table. Is there any guarantee, for example, that a seek will get within 1 ms of the target? Do I need to loosen my target time to a range of times? Or is ACCURATETIME really the only reliable solution?
- rcohen asked 7 years ago
Please login first to submit.