I am getting the above log message when seeking during an archive. The archive plays fine until I try to seek, then it goes crazy. Log below:
20:22:32 GMT-0500 | #SeekClient ======= onPlayStatus |
20:22:32 GMT-0500 | . [object] |
20:22:32 GMT-0500 | \\ |
20:22:32 GMT-0500 | .code [string]= NetStream.Play.Complete |
20:22:32 GMT-0500 | .bytes [number]= 9251 |
20:22:32 GMT-0500 | .level [string]= status |
20:22:32 GMT-0500 | .duration [number]= 0 |
20:22:32 GMT-0500 | #SessionManagerPlayback 291380 ...calling receiveNodes |
20:22:32 GMT-0500 | RECEIVENODES UserManager |
20:22:32 GMT-0500 | #SessionManagerPlayback 291380 ...calling receiveItems |
20:22:32 GMT-0500 | receiveAllSynchData UserManager |
20:22:32 GMT-0500 | #SessionManagerPlayback 291381 seekTime UserManager 39.930632846178106 |
20:22:32 GMT-0500 | #SessionManagerPlayback 291625 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291625 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291635 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291636 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291647 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291647 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291659 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291665 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291700 ======= seek 40705.63284617811 |
20:22:32 GMT-0500 | checkManagerSync:[object FileManager] |
20:22:32 GMT-0500 | #SessionManagerPlayback 291796 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291799 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291800 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291801 seek and play |
20:22:32 GMT-0500 | #SessionManagerPlayback 291801 ======= seek 40705.63284617811 |
20:22:32 GMT-0500 | checkManagerSync:[object RoomManager] |
20:22:32 GMT-0500 | checkManagerSync:[object StreamManager] |
20:22:32 GMT-0500 | checkManagerSync:[object UserManager] |
20:22:32 GMT-0500 | checkManagerSync: we should not get here! |
Any ideas on this?
Thank you.
Views
Replies
Total Likes
Can you reproduce this all the time ?
In the normal case (running room) this error gets thrown when checkManagerSync (a listener for SYNCHRONIZATION_CHANGE for the main manager classes) gets invoked after the room is fully synchronized (and we should have removed all listener).
I am wondering if in the playback case there is a glitch where we endup with ConnectSession.isSynchronzied==true but we seek to a place where we are still waiting for the managers to get synchronized.
Views
Replies
Total Likes
Hi Raff,
Yes, it happens everytime there is a seek event or a pause event on playback (i.e. ConnectSession.archiveManager.seek([some time]) or ConnectSession.archiveManager.pause([some boolean])).
Once this happens the streams never get back into sync until the end of the recording.
Thanks
Roger
Views
Replies
Total Likes
We'll try to reproduce this and work on a fix, but it may take some time.
Could you try something like the following and see if that can temporary fix your problem ?
- add a SYNCHRONIZATION_CHANGE listener on the ConnectSession
- when you get the SYNCHRONIZATION_CHANGE with isSynchronized==true try to read the current playhead position and store the value
- change your scroller (or whatever you use to seek) so that it never seeks to value less than the stored value
I am assuming that nothing really interesting happens before the room starts and it's synchronized so you shouldn't be losing anything by not being able to go all the way back to 0 (also, I am not very familiar with the playback code so this may or may not work as I think it does )
Views
Replies
Total Likes
Views
Likes
Replies