rtmp: no sub-second seek granularity

[GoogleCodeExporter]

What steps will reproduce the problem?
1. rtmp setup
2. $f().seek(20.9)

What is the expected output? What do you see instead?
Expected: a seek to 20.9 seconds position (as over http)
Instead: a seek to 20

Sample:
http://flowplayer.blacktrash.org/test/seekkeyframes.html#player1

Works with http pseudostreaming:
http://flowplayer.blacktrash.org/test/seekkeyframes.html#player2

There seems not need for casting the seek target as int in rtmp. JWPlayer can 
do it (it has other problems though).

See http://flowplayer.org/forum/support.html?id=99639
According to customer the offending line is 270 in RTMPStreamProvider.as

Unneeded, and prevents e.g. framestepping scripts (with appropriately encoded 
clips of course) in conjunction with a solid streaming protocol.

Original issue reported on code.google.com by blacktrashproduct on 2 May 2012 at 8:51

[GoogleCodeExporter]

It's rounding the seek time, im not sure why that is the case. 

Original comment by electrot...@gmail.com on 2 May 2012 at 3:45

[GoogleCodeExporter]

http://dl.dropbox.com/u/3394987/flowplayer.rtmp-3.2.8.zip

This is fixed, does not round the seek time. 

Original comment by electrot...@gmail.com on 2 May 2012 at 4:00

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, Dan.

Original comment by blacktrashproduct on 2 May 2012 at 5:20

[GoogleCodeExporter]

This build contains the fix: 
https://flowplayer-releases.s3.amazonaws.com/info/dist.html

Original comment by anssip@gmail.com on 8 May 2012 at 7:42