110 lines
5.5 KiB
HTML
110 lines
5.5 KiB
HTML
|
|
||
|
|
<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
|
||
|
|
|
||
|
|
|
||
|
|
<meta name="generator" content="Adobe RoboHelp 9">
|
||
|
|
<title>Compiling</title>
|
||
|
|
<!--[if lt IE 5.5000]><style type="text/css">@import "/wiki/skins/monobook/IE50Fixes.css";</style><![endif]-->
|
||
|
|
<!--[if IE 5.5000]><style type="text/css">@import "/wiki/skins/monobook/IE55Fixes.css";</style><![endif]-->
|
||
|
|
<!--[if IE 6]><style type="text/css">@import "/wiki/skins/monobook/IE60Fixes.css";</style><![endif]-->
|
||
|
|
<!--[if IE 7]><style type="text/css">@import "/wiki/skins/monobook/IE70Fixes.css?1";</style><![endif]-->
|
||
|
|
<!--[if lt IE 7]><script type="text/javascript" src="/wiki/skins/common/IEFixes.js"></script>
|
||
|
|
<meta http-equiv="imagetoolbar" content="no" /><![endif]-->
|
||
|
|
<!-- Head Scripts -->
|
||
|
|
<link rel="stylesheet" href="HtmlHelp.css" type="text/css">
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body class="ns-0 ltr">
|
||
|
|
<div id="globalWrapper">
|
||
|
|
<div id="column-content">
|
||
|
|
<div id="content">
|
||
|
|
<h1 class="firstHeading">Compiling</h1>
|
||
|
|
<div id="bodyContent">
|
||
|
|
<p id="siteSub">The graphical representation of the audio
|
||
|
|
system created in <a href="MAINIntroduction.htm">London
|
||
|
|
Architect</a> is correlated to processor code programs
|
||
|
|
that run inside the hardware boxes (e.g. the BLU and FDS
|
||
|
|
series). As the design is created it is itself continuously
|
||
|
|
compiled in the background ready to be uploaded to the
|
||
|
|
hardware at any time. Some systems, such as the <a href="Control_Panels.html">control
|
||
|
|
panels</a> and device configurations, can be changed in
|
||
|
|
real time.</p>
|
||
|
|
<p>In the System Menu there is an option to <a href="Recompile All Device Configurations.html">Recompile
|
||
|
|
All Device Configurations</a>. This can be used to ensure
|
||
|
|
that the system is updated with any design changes you
|
||
|
|
may have made. If you <span style="font-weight: bold;">Run</span>
|
||
|
|
the system the design will compile if necessary and go
|
||
|
|
<a href="MAINOnline_mode.htm">online</a> to the devices.</p>
|
||
|
|
<p><a name="bookmark"></a></p>
|
||
|
|
<h2>Resource Meter</h2>
|
||
|
|
<p><img src="Compiling.JPG" alt="image:compiling.JPG" title="image:compiling.JPG" style="border-width: 2px; border-style: solid;
|
||
|
|
margin-top: 0px; margin-bottom: 0px; margin-left: 0px;
|
||
|
|
margin-right: 0px;" width="611" height="38" border="2"></p>
|
||
|
|
<p>The compiler resource meter can be found on the blue
|
||
|
|
bar at the top of the Configuration Window for all devices
|
||
|
|
with DSP.  This shows the percentage of DSP resource
|
||
|
|
used for each box. The meter is green while the design
|
||
|
|
is using less than 100% and no errors. If there are any
|
||
|
|
errors in the design, such as unwired inputs, the meter
|
||
|
|
will be orange. If this is the case then check the compiler
|
||
|
|
report for any error messages or warnings and fix the
|
||
|
|
problem.</p>
|
||
|
|
<div class="editsection" style="float: right; margin-left: 5px;">
|
||
|
|
<h3>Out of juice?</h3>
|
||
|
|
<p>If the processing required outstrips the available
|
||
|
|
DSP the bar changes to red and warns that the amount
|
||
|
|
of processing objects used in this configuration won't
|
||
|
|
fit in the device, i.e. further devices will be required
|
||
|
|
to fulfil the extra DSP duties.</p>
|
||
|
|
<p>Hover the mouse over the resource meter a tool tip
|
||
|
|
states whether the compile is successful also. If
|
||
|
|
the meter colour changes to orange this suggests that
|
||
|
|
the configuration is unlikely to work; the tool tip
|
||
|
|
states that the compile has "warnings" and
|
||
|
|
to see the <a href="MAINCompiler_Report.htm">Compiler
|
||
|
|
Report</a> for further information. This could be
|
||
|
|
due to unconnected processing objects left in the
|
||
|
|
configuration layout; these should be removed if not
|
||
|
|
needed.</p>
|
||
|
|
<p>When processing objects are added to the layout
|
||
|
|
the resource meter, and its tool tip, states that
|
||
|
|
it is "Compiling". The status bar at the
|
||
|
|
bottom of the screen also shows a waveform animation
|
||
|
|
to represent the background activity.</p>
|
||
|
|
<p>A further "Advanced Resource Usage" dialog
|
||
|
|
is available by double clicking on the resource meter;
|
||
|
|
this displays further statistics relating to the DSP
|
||
|
|
loading and assignment.</p>
|
||
|
|
<p> </p>
|
||
|
|
<h2>Compiler Report</h2>
|
||
|
|
<p>The <a href="MAINCompiler_Report.htm">Compiler Report</a>
|
||
|
|
is available from the view menu or by selecting its
|
||
|
|
tab panel. It shows a list of any failed connections
|
||
|
|
within the device configuration. If any processing
|
||
|
|
object is not wired up an entry details whether it
|
||
|
|
is an input or output that is at fault and the device
|
||
|
|
that is affected. Red arrows represent the signal
|
||
|
|
flow. Double clicking on an entry will locate the
|
||
|
|
offending object by highlighting it in the design
|
||
|
|
window, making quick repairs possible - either wire
|
||
|
|
it up properly or delete it. A drop down box at the
|
||
|
|
top of the report allows the warnings to be shown
|
||
|
|
by particular device or, for the complete system.</p>
|
||
|
|
<p> </p>
|
||
|
|
<h2>System Output Panel</h2>
|
||
|
|
<p>A more in depth overview of the compilation process
|
||
|
|
is available through the System Output panel (View
|
||
|
|
menu or select its tabbed pane). This is listed by
|
||
|
|
time starting from the initial run of the application.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<p style="margin-bottom: 0;"> </p>
|
||
|
|
</body>
|
||
|
|
</html>
|