Greetings!

If I recall, the file plays fine; it is only on the fast forward, rewinds and pause / resume that there are issues. This implies a positioning / tracking problem very similar to the VBR without (or with broken) Xing headers. Granted, I realize we are dealing with CBR here, but it might be that the code for the seek is assuming a higher, more "standard" bit rate or (failing that) going to a VBR-esque seek, looking for a header or (failing that) trying to "fake it".* If so, it might be possible to manually craft a Xing header that would give the player application a roadmap to better locate positions in the file. After all, a CBR file is only a VBR file that doesn't vary very much...

* Note: all of this is speculation, never having seen the code that actually does any of this.