User manual SOUNDCRAFT SAPPHYRE LC

[. . . ] Even if the cursor is moved away from the current cue, since [NEXT] will always recall the cue sequentially following the last recalled cue, the arrow will not move, and can therefore be useful for location of the current scene position when scrolling through the list (remember also that the [CANCEL] switch will always return the cursor to the last recalled cue). If [EXECUTE] is pressed with a non-sequential cue highlighted, however, then the arrow will jump to the cue following the cue just recalled out of sequence. 7. 4 SAPPHYRE LC Playing Back Cues and Mixing Mixing The various control elements of the console (i. e. the faders, switches and rotary controls) may be moved at any time. They will always show the real value of the audio with the exception of VCA offsets to Input faders. [. . . ] Of course, since BANKs 1 and 2 have not been changed, the user may still operate as before if required. As a backup measure, try assigning BANKs 1-4 as required on input surfaces 1 and 2, then assigning BANKs 5-8 on input surface 1 as per 1-4 on i/s 2, and BANKs 5-8 on i/s 2 as per 1-4 on i/s 1. In the event of failure of one surface, this programming style gives an immediate replica of the 4 lost BANKs via the redundant surface. We refer to this type of surface programming as reverse assignment, and it does give peace of mind to users who require 4 BANKs or fewer. Ripple Ripple is a system which allows the user to make changes to the whole show by editing just one Cue. Note that NAMES (the 8 names per input and output) are changed per PROJECT, and NOT per CUE. So, on an unprogrammed system, changing the name of the default offset group (the first group) will effectively change the name of that input throughout the show. However, fader assignments, VCA assignments, offset group selection and stereo channel selection will follow the Ripple law. 8. 4 SAPPHYRE LC Hints and Tips This works as follows: When a change is made to an assignment of the type listed above (for example an input to fader assignment), the console will leave that change active on the surface until an incoming Cue makes a manual reassignment to the same fader. So, for example: The six Cues shown above are set up in a show. The assignment was actually set up in Cue 1, and this is therefore a hard assignment (**). Since no changes are made below, the console presumes that the following Cues require the same assignment. The user now wants to assign input 7 to fader 1 in Cue 3. If all is well, the number of inputs and outputs should match up. If the input number is short, then the Input Rack has caused a problem. If the outputs are short, then the output rack is the cause. If the number of Input Surfaces does not match, then there is a problem with an Input Surface (note however that some users choose to change the number of input faders on their system after a project is created). More Flexibility In The Hardware There are a number of slightly unusual ways in which to use the rack hardware in Broadway to achieve even greater flexibility in any given system size. Those users needing more inputs to the console, especially those requiring returns from FX units or audience playback devices which require only level control, can take advantage of the number of GrAux outputs on the console. GrAuxes which are either unused, or acting simply as Aux Sends to external devices, can act as additional line inputs into the console. Simply feed the input signal into the Insert Return of the console, and switch the Insert point IN. This will result in the GrAux fader carrying the input signal, and the meter showing the post-fade level. The input signal may then be routed to any of the Main outputs, or the Matrix Outputs (if fitted). Of course, the limitations here are that there is no Mic Gain or EQ on the input, and only Level, Mute and Solo control are available. This may prove to be too much of a limitation, but might help the user out of a problem when a large number of Line level sources are suddenly required to be mixed together. [. . . ] The unit requesting information is said to be the bootstrap client. 4 SAPPHYRE LC Appendix A A. 7 Handles - Dynamic Position ID's Within any network, the problem of unit addresses is always a major issue. It would be easiest to presume that every unit had a unique address, and would always be referred to at that address. Unfortunately, this would require very long addresses, and some fairly tight regulation on the part of manufacturers. The alternative to the static ID solution is to allow the system to allocate new soft ID's to every component on the system each time the network is powered up. [. . . ]