![]() Here is FFMPEG’s analysis of a non-compliant resolution: I read somewhere else that the chosen picture width should be a multiple of the x part of the aspect ratio. The Digital Rapids Stream encoder will author files with garbage aspect ratio metadata if the resolution isn’t exactly 16:9 to the nearest even number of pixels. I did have another problem – one of aspect ratios. I also discovered that QuickTime Player is not a reliable player to use for testing as it sometimes crashes, and will not play H.264+AAC streams which VLC has no issue with. S=Session Streamed by Digital Rapids Corp Stream ServerĪ=fmtp:97 streamtype=5 profile-level-id=1 mode=AAC-hbr sizelength=13 indexlength=3 indexdeltalength=3 bitrate=64000 config=1390Ī=fmtp:96 packetization-mode=1 profile-level-id=4D4020 sprop-parameter-sets=J01AIJZWDQ/8mApEAAADAAQAAAMAyhA=,KO8GDMg= ![]() What happens is that when you copy the SDP file into your Helix server’s Content/rtpencodersdp folder and try to connect to the stream pointing a media player at rtsp://helixserver/rtpencoder/live_stream.sdp it will fail, with the following error appearing in rmerror.log:Ģ 13:47:14.062 tmplgpln(6076): 32: Error retrieving URL `rtpencoder/live_stream.sdp’ (Invalid path)įollowing contact with Helix support, it turns out that the SDP file which the encoder creates does not declare the bandwidth of the audio track using a b= line as per RFC 4566 – though apparently this is an optional field. Digital Rapids apparently don’t support live broadcasting from their hardware encoder companion software ‘Stream’ to Helix Mobile Server even though the latter supports RTP and SDP, and the encoder clearly offers these up as possible exports when you’re using the Digital Rapids AVC for Web codec profile (an optional extra purchase): I had a few difficulties with getting this set up so it’s probably worth sharing them here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |