Red5 sometimes writes webcam video files with a large offset in the
video frame offsets, sometimes up to 30 or even 60 seconds. However,
the start event in the events.xml file corresponds to the time at
which red5 received the first keyframe (recorded frame) in the video.

The end result is that the video will sometimes appear to be
delayed (out of sync) in the processed recording.

The correction is simple: We're already reading video metadata,
including the timestamp of the first frame, so we just have to apply
a correction during video processing to undo the frame timestamp
offsets in the video file.

Limited screensharing FPS to 5-10, resolution to screen size and fixed chrome extension prompt

Fix bbb conf 2

Force reading config.xml in utf-8 format

[HTML5 Client] Adjustments in handling of reconnected voice users

Prevent error on settings change with userlist open

[HTML5 Client] Self mute/unmute from userlist for attendees.

Fixed exceptions thrown during meeting destruction and presenter assignment 

Also fixes the extension prompt for chrome users in the HTML5 client

Updates to bbb-conf to support HTML5

Revert "Give mongod a moment to startup before bbb-html5"

Redirect Android, iOS users to html5 except on Puffin browser

Give mongod a moment to startup before bbb-html5

Remove 1935 from firewall message

Show record button for all users

Fix when button is disabled cursor does not appear not-allowed.

Adjusted the source for recording meeting status

Merging this but some edge cases will be addressed in an upcoming PR

Fixed the logging of the Meteor server-side methods