Limitations and known issues
This section includes known issues or limitations that affect functionality or usability and ways that you can work
around these limitations.
Affecting firmware upgrades to 4.8.1 (or later) with traffic shaping
If traffic shaping is already configured using the Pearl Mini API, observe the following before upgrading to 4.8.1 (or
later):
l
Traffic shaping that's configured using the API will continue to work after you upgrade the firmware. You
can clear traffic shaping for one or more channels using the API at any time.
l
If you reconfigure traffic shaping for a channel using the Admin panel after upgrading the firmware, the API
can no longer be used to configure traffic shaping for that channel. You must use the Admin panel going
forward. The other channels are not affected.
l
If you plan to use the Admin panel to configure traffic shaping for easy access and ease of use, you can
clear traffic shaping for all channels using the API before you upgrade the firmware or after the upgrade.
Keep in mind that you can no longer use the API to clear or configure traffic shaping for any channels that
were configured using the Admin panel.
Recommendation
: After enabling traffic shaping using the Admin panel, test a multicast stream using the auto
traffic shaping settings. If your low bandwidth network device is displaying poor video quality, then manually set
the limit bandwidth bitrate according to the bandwidth of your particular network device. See
Affecting firmware upgrades to 4.17
l
If Pearl power connection is interrupted after a recording has been stopped, but before the Automatic File
Upload has finished, Pearl will complete the upload after power has been restored but both the file saved
on the Pearl and the file uploaded to the AFU location will be corrupted.
l
If you start an event early in YuJa using any Pearl interface and then extend the event, the event appears to
extend but ends at the originally scheduled ending time.
l
Incorrect destination IP is shown on the Channel Status page under the Connections section when using
Listener mode for an SRT push stream, displayed IP address is 0.0.0.0.
Workaround:
To view the actual
IP address the user must go to the Streaming section of the channel and view the stream settings for that
SRT push stream.
l
When using the front headphone jack to monitor audio if the touch screen goes dark due to timeout and is
then tapped to wake it up sometimes the audio will not return.
Workaround:
Change screens, navigate to
a different section of the touch screen and then back to the channel and the audio should resume.
