Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Playback doesn't work everytime for recorded archive

Avatar

Level 2

Hi,

My playback doesn't work all the time. Sometimes play wrong archive. Most of the time get following error:

Fri May 6 00:22:42 GMT+0600 2011    LCCS SDK Version : 1.4.0    Player Version : WIN 10,2,159,1
00:22:42 GMT+0600    requestInfo https://collaboration.adobelivecycle.com/Account/Room?glt=g:playback&mode=xml&x=0.3687733025290072
00:22:50 GMT+0600    #TicketService# ticket received: kq9qoyweb4et
00:22:50 GMT+0600    Getting FMS at https://na2.collaboration.adobelivecycle.com/fms?ticket=kq9qoyweb4et&playback=test1&proto=rtmfp, attempt #1/3
00:23:21 GMT+0600    result: <fms>
  <origin>fms2.acrobat.com</origin>
  <proto_ports>rtmfp:1935,rtmps:443</proto_ports>
  <retry_attempts>2</retry_attempts>
</fms>
00:23:21 GMT+0600    protocols: [object ProtocolPortPair],[object ProtocolPortPair]
00:23:21 GMT+0600    [attempt 1 of 2] Connecting to 0/1: rtmfp://fms2.acrobat.com/playback/.../Room/test1 #startProtosConnect#
00:23:26 GMT+0600    [attempt 1 of 2] Connecting to 1/1: rtmps://fms2.acrobat.com/playback/.../Room/test1 #onNextConnectTimer#
00:23:34 GMT+0600    onTimeOutTimerComplete
00:23:34 GMT+0600    [attempt 1 of 2] Trying fallback tunneling connection rtmps://fms2.acrobat.com/playback/.../Room/test1 #onTimeOutTimerComplete#
00:23:42 GMT+0600    onTimeOutTimerComplete
00:23:42 GMT+0600        incOriginsIndex: _originsIndex now:0 (origin:fms2.acrobat.com)
00:23:44 GMT+0600    [attempt 2 of 2] Connecting to 0/1: rtmfp://fms2.acrobat.com/playback/.../Room/test1 #startProtosConnect#
00:23:49 GMT+0600    [attempt 2 of 2] Connecting to 1/1: rtmps://fms2.acrobat.com/playback/.../Room/test1 #onNextConnectTimer#
00:23:57 GMT+0600    onTimeOutTimerComplete
00:23:57 GMT+0600    [attempt 2 of 2] Trying fallback tunneling connection rtmps://fms2.acrobat.com/playback/.../Room/test1 #onTimeOutTimerComplete#
00:24:05 GMT+0600    onTimeOutTimerComplete
00:24:05 GMT+0600        incOriginsIndex: _originsIndex now:0 (origin:fms2.acrobat.com)
00:24:07 GMT+0600    startProtosConnect calling onDoneRetryingTimerComplete
00:24:07 GMT+0600    Getting FMS at https://na2.collaboration.adobelivecycle.com/fms?ticket=kq9qoyweb4et&connect-error=true&origin=fms2...., attempt #2/3
00:25:11 GMT+0600    result: <fms>
  <origin>fms5.acrobat.com</origin>
  <proto_ports>rtmfp:1935,rtmps:443</proto_ports>
  <retry_attempts>2</retry_attempts>
</fms>
00:25:11 GMT+0600    protocols: [object ProtocolPortPair],[object ProtocolPortPair]
00:25:11 GMT+0600    [attempt 1 of 2] Connecting to 0/1: rtmfp://fms5.acrobat.com/playback/.../Room/test1 #startProtosConnect#
00:25:16 GMT+0600    [attempt 1 of 2] Connecting to 1/1: rtmps://fms5.acrobat.com/playback/.../Room/test1 #onNextConnectTimer#
00:25:20 GMT+0600    tempNetStatusHandler 1/2,NetConnection.Connect.Success
00:25:20 GMT+0600    isTunneling? false
00:25:20 GMT+0600    is using RTMPS? true
00:25:20 GMT+0600    #SessionManagerPlayback 157817 fms connected: [Event type="connected" bubbles=false cancelable=false eventPhase=2]
00:25:20 GMT+0600    #SessionManagerPlayback 157822 ======= onConnected: play __PacingStream

Regards,

John

5 Replies

Avatar

Employee

For one thing, it looks like you cannot connect to the system using RTMFP from your site, so there are a few retries and then the connection switches to RTMPS. If you know that you can't connect via RTMPF (and you are not using any of the P2P facilities) I'd suggest you use the LCCS swc for FlashPlayer 9 (that always request RTMPS). That should reduce your connection time (if you need the Player 10.x SWC for other purposes you can still force the connection to be RTMPS - check the documentation).

Regarding your specific problem, we did found a bug in the version currently deployed where if you do connect to the room fast enough, you may start your playback before FMS has finished fetching your recording archive (and at that point the client just doesn't play anything, or it may play a wrong recording).

The bug is already fixed and it will get into the next release (a few weeks away).

You can try to see if this is the problem you are having by delaying your plaback for a while (i.e. make the playback start when you push a button, start the room, wait something like 30 seconds or a minute - a shorter time would work too, but just for the sake of demonstrating the problem wait a little longer and then start your playback).

If that is your problem, again, we already have a fix for it and it will be deployed with the upcoming release.

Avatar

Level 2

Hi Raff.

Thanks for your seggestion. I can use rtmfp protocol now. Playback is working with rtmfp but if i restrict to rtmps, most of the time not works.

I see the following logs when playback not works:

requestInfo https://collaboration.adobelivecycle.com/ACCOUNT/ROOM?glt=g:playback&mode=xml&x=0.9567748224362731
getMeetingInfo: status=0
#TicketService# ticket received: 1v0fzvh32su05
Getting FMS at https://na2.collaboration.adobelivecycle.com/fms?ticket=1v0fzvh32su05&playback=video91, attempt #1/3
result: <fms>
  <origin>fms2.acrobat.com</origin>
  <proto_ports>rtmps:443</proto_ports>
  <retry_attempts>2</retry_attempts>
</fms>
protocols: [object ProtocolPortPair]
[attempt 1 of 2] Connecting to 0/0: rtmps://fms2.acrobat.com/playback/ACCOUNT/ROOM/ARCHIEVE #startProtosConnect#
tempNetStatusHandler 0/1,NetConnection.Connect.Success
isTunneling? false
is using RTMPS? true

#SessionManagerPlayback 67643 fms connected: [Event type="connected" bubbles=false cancelable=false eventPhase=2]

#SessionManagerPlayback 67648 ======= onConnected: play __PacingStream

But when it logs the following also when playback works:

#SessionManagerPlayback 62812 ======= onMetadata: 101147

#SessionManagerPlayback 62817 ======= onMetadata: play __StreamOffsets

Last Line

#SessionManagerPlayback 90970 ======= onPacing: 21986

Regards,

John

Avatar

Level 4

This looks like a bug Raffaele described in his original reply.  It is fixed in our upcoming recording feature refresh.

Thanks,

Nikola

Avatar

Level 2

Hi,

Thanks for informing me.

Regards,

John

Avatar

Level 1

Oh cool, we are waiting for the same fix ( it can be easily reproduced by the included test project in the LCCS sdk - sample applications ).

Alex G.