29.08.2014 Views

GeniusPro/Lightpalette Operator's Manual - Strand Lighting

GeniusPro/Lightpalette Operator's Manual - Strand Lighting

GeniusPro/Lightpalette Operator's Manual - Strand Lighting

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Server Software<br />

TOKEN = VALUE<br />

Do not change the TOKEN names. If you do, an error (‘User file token is invalid’) will appear in the<br />

status log every time that user logs in. You can change the VALUE however. If you leave the value<br />

blank, the existing value for that token in the console will be used; a blank password means that none<br />

needs be entered.<br />

It is recommended that all users’ access rights are explicitly set, to avoid inheriting too many or too few<br />

rights from the previous logged-in user. To find out what user setup values are used in the file,<br />

experiment by saving user setup when logging out, and look at the file each time.<br />

Configuring Access Rights<br />

Each user’s access rights are defined in their user file. This example shows all access rights enabled;<br />

to disable any one, replace the 1 with a 0:<br />

acc_record = 1 Can record from Live.<br />

acc_patch_fix = 1 Can patch new fixtures (requires Tracker).<br />

acc_spec_grps = 1 Can change special groups (display, partition, etc).<br />

acc_stp_user = 1 Can change User Setup.<br />

acc_stp_show = 1 Can change Show Setup.<br />

acc_stp_cons = 1 Can change Console Setup.<br />

acc_cons_mode = 1 Can change console mode at the login display.<br />

acc_printer = 1 Can use the printer.<br />

acc_show_loc = 1 Can save or delete shows on local disk drives.<br />

acc_show_svr = 1 Can save or delete shows on the server disk drives.<br />

acc_chan_ctrl = 1 Can use channel control to set levels.<br />

acc_playback = 1 Can run cues on the X playbacks.<br />

Console Access Rights<br />

Each console as well as each user has a login configuration file. This allows physical consoles to have<br />

particular rights, irrespective of who logs in. For example, a designer’s console may have all channel<br />

control disabled.<br />

Console files are in the same format as .USR files: they are called .CON files instead. The name<br />

should match the ShowNet node name defined in the 220NODE.CFG file. The console called MAIN<br />

will need a file called MAIN.CON. A default file is installed with the operating software to act as a<br />

template: its name is CONSOLE.CON. This file is used if no specific .CON files are created. You can<br />

create a .CON file for each console and PC by copying CONSOLE.NEW, which is created with the<br />

software.<br />

file:///C|/LIGHTP/HELP.ENG/page21.htm (7 of 10)11/2/2004 3:02:57 AM

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!