Skip to main content
April 5, 2012
Question

Upgrading from FMS_4_5_0_r297 to FMS_4_5_1_r484 using ffmpeg will kill recording append ability

  • April 5, 2012
  • 1 reply
  • 1003 views

I would like to warn anyone using ffmpeg that upgrading to FMS_4_5_1_r484 will kill your append recording.

As discussed in http://forums.adobe.com/message/4280166 even fmle encoders are having problems appending recordings with absolute time enabled.

Reseting the recording with this query "adbe-live-event=croaporter&adbe-record-mode=record" or a change in your main.asc might be a solution for some but this will cause a disruption for clients connected to the stream.

For myself and I'm sure many others this is not a solution it seems like a bug. We need a solution that does not require a client to reset their browser page or client application which means overall disruptions in the viewer experience.

I can vouch that in FMS_4_5_0_r297 appending to a recording was done seemlessly on  a 24/7 stream (and i have over 30 streams running). Sometimes for some reason an encoder will attempt to republish or will require a flush (forced restart) and with FMS_4_5_1_r484 this is not possible. Yes you can start a new recording but what happened to appending the recording, it was working.

I have tried to insert into the Event.xml a maxrestartage and removed absolute time code from Application but it will not work.

I dont know if FFmpeg has absolute time code implemented in the librtmp libraries to emulate fmle time synchronisation but even fmle users have this problem so I believe that this should be fixed in the next upgrade but for now I suggest all others who want to use a more efficient encoder such as ffmpeg as compared to fmle to be very careful when upgrading.

I did notice some new hls buffering issues that have arised from this new upgrade as well which 4.5.0 didnt have.

I am even willing to pay for support to solve this problem because 4.5.1 seems to have better monitoring in the administration console. But for now I am downgrading to FMS_4_5_0_r297 because it works.

Regards

Bashir

    This topic has been closed for replies.

    1 reply

    April 6, 2012

    Wow. No comment from Adobe employees? Does this mean that the bug will be fixed? I am ready to devote encoders to test this thoroughly with your development team if need.

    It doesnt make sense to disable the append feature for all encoders except for fmle. Now I am running 4.5.0 and it is appended recording at anytime the encoder restarts up to 8 times a day on one machine no problem. Yet with 4.5.1 I couldnt get it to append once so i gave up.

    Adobe Employee
    April 7, 2012

    Can you please let me know the parameters you are using with ffmpeg for publishing?

    I would like to setup a repro of the case at my end.

    April 7, 2012

    ffmpeg -i rtp://239.255.0.1:4444 -acodec libfaac -vcodec libx264 -vb 1124k -ab 128k -r 25 -async 1 -bf 4 -refs 2 -aspect 16:9 -g 45 -deinterlace -f flv rtmp://192.168.100.150/devtest/devtest1?adbe-live-event=devtest1

    ffmpeg git:

    ffmpeg version git-2012-02-14-f89f9bd

    built on Mar 22 2012 15:57:58 with gcc 4.6.1

    (source is mpeg2 - mpegts 720 x 576) with ffmpeg you can copy the mpegts timecode with the -copyts option but that didnt help and I also tried -timestap now but no luck.

    Thanks for your response.