FMLE absolute timecode fix in 0.8.2

When receiving absolute frames with big (>0xffffff) timestamps an error used to occur because RTMP type 3 chunks carry absolute timestamps. That’s undocumented feature which I have implemented long ago. However that was not properly tested.

I want to thank people who helped me with fixing that and provided detailed responses about publishing from FMLE. In 0.8.2 version that was completely fixed. Now nginx-rtmp has full support of long publishing from Adobe products.

Advertisements
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: