I'm developing a streaming application that stream to nimble streamer via RTMP and when I consume the stream with the SLDP player, then sometimes the stream is not played and the following error appears on the web browser console (this is an example):
[10:37:42.212][SLDP_1000][Track audio]: sample is far away from expected 420696 1091634
I tried with different combination of Nimble/SLDP player versions but seems none of them work.
The problem seems to be triggered when the webpage is refreshed. If not, the stream is played as expected.
The log message you've encountered means that SLDP player receives completely un-synced video and audio frames. In your case it expects audio sample to have 1091634 timestamp to be synced with video stream, while in fact it receives sample with 420696 timestamp.
The most common reasons of such behavior are usually wrong video/audio timescale or irregular frame emission from a source. From you last message it looks like irregular emission is more probable. Please show your FFMPEG command. Do you use '-re' flag?
I don't use FFmpeg command line. It's a C/C++ application that uses the FFMpeg's libraries API.
Yes you're right, our application sends the content in bunches of audio/video content (i.e.: 90 video frames followed by 110 audio frames every 3 seconds).
We tested our application with Facebook Live/Periscope and it works, but with Nimble Streamer/SLDP Player shows this issue.
Is there any setting on Nimble Streaming or SLDP we can tweak to workaround this problem?
try to log audio|video timestamps and make sure they are on the same basis taking into account audio|video timescale
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the