Skip to main content
M
Mr_Dave
Known Participant
December 27, 2011
Question

iOS device streaming working perfect but f4m quit on PC's now.

  • December 27, 2011
  • 1 reply
  • 645 views

The first event I streamed tonight worked fine for an hour or so then it stopped being accessible from the web . I had no problem viewing the stream on mobile devices though. The log file shows these errors.

2011-12-27 16:58:39 4172 (e)2611178 Error from libf4f.dll: Failed to swap in file 'C:\fmshome\livepkgr\streams\_definst_\bbc2011-BBC12\bbc2011-BBC12.bootstrap'. -

2011-12-27 16:58:39 4172 (e)2611178 Error from libf4f.dll: Failed to swap in file 'C:\fmshome\livepkgr\streams\_definst_\bbc2011-BBC13\bbc2011-BBC13.bootstrap'. -

2011-12-27 17:21:30 4172 (e)2611178 Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit. -

2011-12-27 17:21:30 4172 (e)2611423 Failed to record bbc2011-BBC23 (Unknown Error). -

I can see the three stream directories get created but only one of them has all the files- bootstrap,control,meta,f4f,f4x. The other two stream directories only contain a control file.

The event is streaming perfectly on iOS devices but not on PC's. The stream starts for a second then stops and displays the message 'Unable to connect to the content you've requested'.

Thanks,

Dave

    This topic has been closed for replies.

    1 reply

    N
    Adobe Employee
    NpComplete
    Adobe Employee
    January 2, 2012

    Sir,

    Can you please elaborate about your set-up..

    1. How many streams you hosted.

    2. Number of stream per event.

    3. Number of subscribers were there...

    Did a reclick on play button solved the issue.. It is highly unlikely that if there are some serious publishing issues (like Error from libf4f.dll etc).. then playback will be ok on devices and not on PCs. Were device and PC at that time susbscribing to different rendentions (bit rate stream) of same stream. It may happen that, PCs might be attacking a rendetion of stream which has stopped because of some error, while device might be on a different multi-bit rate rendetion of same stream ( that might be fine).. More about this can be understood by looking at the Apache's access logs.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices