There are a couple of changes that you may notice with the rollout that happened this week.
The player now has automatic refresh and connect if it encounters any problems with connecting to the stream.
The player also has a low bandwidth mode. This can be set in the portal when setting up events or on the player itself. Setting this will cap the bitrate at 800k. Use this if your receive site has low bandwidth and keeps trying to push up to a higher bitrate level. This will minimize buffering and any freezes that may occur while the player tries to go to those higher levels.
Also with the player, it will detect if there is too much buffering at very low bitrates (300k and lower) and set the player to audio only.
Also, there are different regions that can be chosen while scheduling an event. The regions with the 2.0 at the end designate regions with the new types servers utilizing cloud services. Please feel free to test these out and if you so chose use them on events.
Finally, if you find anything that you have a question on regarding the system or a bug that I happen to miss or something weird happens....please let me know.
Conversations around originating a webcast for conference, including cameras and mixers.
3 posts • Page 1 of 1
There is a known issue with using the Mono Left or Mono Right settings for audio on the terradek. Using this setting causes the audio to become unusable. Using the Stereo setting on the terradek works fine. The Stereo setting is the default setting for audio on the terradek. We are working to correct this issue.
Who is online
Users browsing this forum: No registered users and 1 guest