page 2 - 9
Aura8ip / Jan 2012
A u r a 8 i p G U R U G U I
• The Guru GUI can only modify virgin
Factory
presets.
Guru GUI relies on known starting points within the Factory presets before it can
make modifications. Therefore the only presets that can be modified by the Guru
GUI are Factory
presets.
• Once a Factory preset has been modified by GUI Professional it cannot be
modified using Guru GUI.
If a Factory preset has been modified by the Professional GUI it is no longer a
“Factory” preset and therefore it is not allowed to be modified using Guru GUI.
Understanding the Differences Between Factory, Legacy, and
Guru Presets
•
Factory presets are those created by the Factory using specialized tools.
•
Legacy presets are presets that are created by a customer using the full control
Professional GUI, or those created and saved by the Guru GUI.
• The biggest difference between the two types of presets is that the Guru GUI is
permitted to modify only Factory presets.
• If while using the Guru GUI you receive the “Restricted Preset” dialog, shown be
-
low,
and
you know for sure that the preset being adjusted is a virgin Factory preset,
simply recall the preset again using the Guru GUI and the error should disappear.
Additional Notes on Aura8ip and Network to GUI Connectivity
Aura8ip utilizes both TCP/IP and UDP to communicate with the remote GUI.
TCP/IP utilizes Port 55901 and the first available UDP port in the range of 60001 to 60010
during communications sessions.
TCP/IP - The TCP protocol is used for controlling the Aura8ip and reporting its
control settings back to the GUI because TCP repairs
any transmission errors that might
have occurred on the network. Using TCP for this function guarantees that the Aura8ip
controls always
do exactly what the GUI tells them to do, and that the control settings
seen on the GUI are in perfect agreement with what the Aura8ip hardware
thinks they are.
UDP - Metering between the Aura8ip and the GUI works differently. For this task we
chose the UDP protocol, a simple data transmission model without any hand-shaking to
drive the meters. We used UDP for metering because of its very low overhead at both ends
of the link, and because we don’t mind if an occasional meter data packet (or a bunch of
meter packets) gets lost on the network. Metering data is updated frequently so a missed
metering packet here or there has an inconsequential effect on the visual appearance and
no impact whatsoever on the sound.