The percent you see is the CPU percentage!
OK.
The progress meter starts from 0 again ...
I do not understand what you mean. Perhaps it is because I do not have
a Real Audio file to test. If I want to seek 10 minutes into my Real
Player movie, I use:
mplayer -ss 600 test.rm
and I let it play for a time, and then I quit. My status line looks
like this:
A: 0.0 V: 0.0 A-V: 0.016 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0
A: 603.8 V:602760.0 A-V:-602156.250 ct: -0.100 2/ 2 ??% ??% ??,?% 0 0
A: 603.9 V: 602.6 A-V: 1.260 ct: -0.096 3/ 3 ??% ??% ??,?% 0 0
[more lines ...]
A: 606.3 V: 605.4 A-V: 0.975 ct: 0.200 71/ 71 2% 0% 0.4% 0 0
Exiting... (Quit)
mplayer -ss 900 test.tm gives:
A: 0.0 V: 0.0 A-V: 0.022 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0
A: 901.0 V:900040.0 A-V:-899139.000 ct: -0.100 2/ 2 ??% ??% ??,?% 0 0
A: 901.1 V: 899.9 A-V: 1.198 ct: -0.096 3/ 3 ??% ??% ??,?% 0 0
[more lines...]
A: 903.3 V: 902.4 A-V: 0.944 ct: 0.170 64/ 64 4% 0% 0.5% 0 0
Exiting... (Quit)
So in the first case, the movie started playing at 603.8 seconds (I
wanted to started at 600), and I quit at 606.3 seconds, and in the
second case, it started 901 instead of 900 and I quit at 903.3 seconds.
The accuracy of seeking depends on the keyframe interval, because
MPlayer can only seek to a keyframe. But as I said, maybe none of this
is relevant to a file that has no video.
Perhaps you should use MEncoder to convert your file to a format that
is acceptable to the other programs that you mentioned.
_______