I Could be wrong, but it seems to be a limitation in the ts reader.
I don't think it will be fixed any time soon. I just get by with the skip, which seems a bit half ....... anyway.
I Could be wrong, but it seems to be a limitation in the ts reader.
I don't think it will be fixed any time soon. I just get by with the skip, which seems a bit half ....... anyway.
In short, it is caused by two different things:
1) TsReader aren't supporting other than 1.0x playback rate
2) No one knows how to allow audio renderer to render faster than 2.0x rate (no, it wont help to mute the audio...).
So, its a known issue with no available sollution (yet). Also it is pretty low on priority (as all developers are finding the skip steps much better way for navigation ).
If someone knows how MS DVD navigator does it's trick with the audio renderer, please let us know. After that is known its possible to fix the issue.
I think it used to work well with tsfilesouce (remember that?!). Certainly a feature I miss, but it's only useful if it's very responsive and fast. Anyhow I can understand that it's not a priority right now though .
And why, for some users, it works very well ???
And why, for some users, it works very well ???
Depends on codecs, steam and CPU / HD performance. Here's how MP currently handles the fast forward / rewind.
loop until seeking stopped
{
1) seek to calculated position
2) play a little bit
}
Calculated position is depending on the seeking rate.
1) TsReader aren't supporting other than 1.0x playback rate
2) No one knows how to allow audio renderer to render faster than 2.0x rate (no, it wont help to mute the audio...).