Think of each mode as handling the "log" in a different way, and each with some added features. The basic mode differences are actually how Maestro is handling the loading of the queue window.

Live Assist- In Live Assist, Maestro is not doing anything with the log. It's not loading the queue window, and it's not keeping track of exact time execute functions that are being called on by the log (if there are any XF's on the log). Operators have to manually load the queue window.

**As an added feature, under Workstation/Preferences/Options, the user may choose to "Halt Play at Directive", which means that after the user has loaded directives with carts into the queue window "manually", and activated the queue into an "auto segue" channel (channel with auto selected), every time we reach a directive it will deactivate the queue window.**

Cruise Control- When first moving to Cruise Control, Maestro will load the queue window based on the "closest" previous directive (LP, LS or LR) It will then keep a "minimum" queue count (Workstation/Preferences/More Options). So "if" the minimum queue count is set to 10, and we only have 9 items in the queue window, it will load the next item on the log. "if" that next item is simply a log note, it will only load that log note. "if" that next item is a directive (LS, LR, LP) it will load the directive and everything attached to that directive. That means there will be times when there could be 30 or more items in the queue window, but we will never go below the minimum queue count. Even with a setting of 1 as the minimum queue count, Maestro will continue to load and shouldn't run out. We do not care what type of directive is on the log in Cruise Control. Users can run into problems in Cruise Control by setting the minimum queue count too high. This could cause Maestro to attempt to load the queue window with elements "beyond" the four hours ahead that it can see on the log, which can cause Maestro to lose it's place on where it should be on the log. In Cruise Control, execute functions on the log can be triggered based on position. If the user wanted to execute that function after a specific song, commercial, etc, on the log, they could put a tilde [~] as the first character of the description line and the XF 'will' load into the queue window, and will execute when leaving the top of the queue window (after the cart before it has finished playing).

**As an added feature, under Workstation/Preferences/Options, the user may choose to "Halt Play at Directive", which means that an activated queue with an "auto segue" channel (channel with auto selected), will deactivate every time we reach a directive. (just like Live Assist)**

Local Automation- In it's basic structure, with no Automation Rule Sets on the log (ARS= statements) and "no" registry changes to "FlushQueueInAutomation" from the default 0, or off, Local Automation is pretty simplistic. When first moving to local automation it will load the queue window starting with the "closest" previous directive in time (regardless of directive type), then load to the next LR Directive. Since Local Automation assumes there is 'no user' in the control room, it will automatically activate the queue window and keep it active until something tells it to stop (like a user deactivating with the F10 key). It will continue loading from LR to LR directive from there on. So the user will see a point where there is only 1 item in the queue window, but as soon as it begins to play Local Automation will load the next block of log from LR to LR. Automation Rule Sets (ARS) can be added to the log on LS or LP directives between the LR's to tell Maestro to drop or add elements in an attempt to back time to the next LR or next Rule Set. By default, LR is ARS=00, which is intended to do nothing. Local Automation rule sets are intended for users who want Maestro to back time to live news casts, or hard timed points on the log. Rule Sets are created using the MRuleDef.exe configuration utility. Users requested a simpler way of 'soft synching' the log in Local Automation, so we introduced the ability to FlushQueue in Automation. By changing the registry setting "FlushQueueInAutomation" to 1, or on, each time we reach the 'time' of an LR directive, if there is anything in the queue window from the previous LR, we will flush it out and load the next block of elements. If however we run short of elements before the next LR, the basic functionality of Local Automation continues, meaning we will go ahead and load the next LR to LR and keep going. (Found under HkeyLocalMachine\Software\CCC\Maestro\3.3)

**Maestro must be closed to change the registry** Users can run into problems in Local Automation, especially with Flushqueue enabled, "IF" they don't have at least 1 LR directive on the log in the four hour period ahead that Maestro can see. Since we are loading LR to LR, if there were no LR directives for more than four hours, Maestro will load the entire four hours that it can see, which can cause it to lose it's place. In addition, if flushqueue is enabled, and if Maestro can't find the next LR, it will reset it's "Target Directive" back to the same LR it just loaded and then Flush the queue again, causing nothing to be in the queue window at all. In Local Automation, execute functions on the log can be triggered in two ways, exact time (based on the time of the XF directive), or at a specific place on the log. For instance, you can have an XF on the log at 10:10am (with NO tilde [~]). That directive would 'not' load into the queue window, and it would execute at 10:10am. But, if the user wanted to execute that function after a specific song, commercial, etc, on the log, they could put a tilde [~], or Time Approximate marker, as the first character of the description line and the XF 'will' load into the queue window, and will execute when leaving the top of the queue window (after the cart before it has finished playing).

Satellite Mode- In Satellite Mode, Maestro loads directive based on the 'time' of the directive, and can fill to the length of the directive with what ever carts are defined as "filler". So if the user had an LR, LS or LP directive at 10:00am, and the directive length was 0400 (4 minutes), 'and' within that directive traffic had only scheduled 3 minutes worth of spots, at 10am Maestro would load the 3 minutes, then pick another minutes worth of filler. IF at that point there is any time left over (say for instance 1 second), Maestro will use cart 0000 (Silence Delay) and split that second up between each element until the aux mark of the last cart lands at exactly 4 minutes. In Satellite mode, each time we load a directive we also place an "End Of Cluster" or "EOC" after the last cart loaded into the queue window. This will deactivate the queue window when the EOC leaves the queue, which happens at the beginning of play of the last cart. In Satellite mode directives are treated individually. LR means Load Required in Sat Mode. This means that if there is 'nothing' scheduled under that directive at 10am Maestro will go ahead and load 4 minutes worth of filler. LS means Load Optional in Sat Mode. This means that if there is 'nothing' scheduled under that directive at 10am Maestro will not load any filler. IF a function action Start PLay from Queue is then activated by a Satellite relay, the start play from queue will report nothing to do and perform the next action in the list. IF no further actions are in the list, you've basically just skipped the break and stayed with current satellite programming. If there is something scheduled with the directive we will load those items, and use filler to fill the break to the specified directive length. LP means Load and PLay in Sat Mode. This means that if we have an LP directive at 10am, it will load that directive at 10am and activate the queue window. There are different things you can do in Satellite mode with any of these directives. You can place a tilde [~], or Time Approximate Marker, as the beginning character of the log description of that directive, which means that regardless of the time of that directive, Maestro will not load that directive until the EOC of the 'previous' directive has left the queue window. So, if a user has an LR directive at 10am, and a ~LS directive at 10:10am, and the LR directive doesn't play until 10:15am, we will not load the 10:10am directive into the queue window until the last element of the 10am directive has gone to the play line. This also means that if we trigger the 10am directive at 10am, and it ends at 10:05, we will go ahead and load the ~LS 10:10 directive when the last cart begins playing at 10:05. You can also use the $ Clear Queue command in Satellite mode. This is the only mode of operation that the $ will do anything. IF a directive has a $ as the beginning character of the description line, when we reach the time of that directive we will flush out what ever is in the queue window and load that directive. In Satellite Mode, execute functions on the log can be triggered in two ways, exact time (based on the time of the XF directive), or at a specific place on the log. For instance, you can have an XF on the log at 10:10am (with NO tilde [~]). That directive would 'not' load into the queue window, and it would execute at 10:10am. But, if the user wanted to execute that function after a specific song, commercial, etc, on the log, they could put a tilde [~], or Time Approximate marker, as the first character of the description line and the XF 'will' load into the queue window, and will execute when leaving the top of the queue window (after the cart before it has finished playing).

*** It should be noted that functions can be triggered in any mode. If a user where to load an XF off the log into the top of the queue window in Live Assist, then activate the queue window, that function would do as it is told. In addition, any relays can perform functions 'regardless' of mode, so if you had a function that was designed to play a liner during a Satellite Show, 'and' that function was active in Live Assist, then the Liner would play from the function in live assist if you received the relay. **

Locks on Carts- In Live Assist, Local Automation and Cruise Control, a cart is locked when it reaches the top of the queue window and until it leaves the play deck. In Satellite mode 'all' carts in queue are locked.