Skip to content

Commit 44f09b9

Browse files
authored
Update README.md
1 parent b66ffc1 commit 44f09b9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,11 @@ To install the scripts as script cues, use the script "~/00 Import scripts to cu
1818

1919
To install the scripts to your user's Library folder, in "Script Libraries", I suggest you run the script "~/00 Import all to library.applescript" from the script editor. Select the base folder of the repository, and you can now quickly access any script. Within Qlab, call the script (probably from within a `tell application "Qlab" to tell front workspace` block) like so:
2020

21-
`tell script "01 Mixing Desk Programming/Choose Desk to program" to run`
21+
`tell script "Mixing Desk Programming/Choose Desk to program" to run`
2222

2323
### User Defined Variables
2424

25-
Many scripts also contain User Defined Variables. With these, when you call the script within Qlab, you can declare these variables globally and set them from within Qlab. This is particularly useful for using the same script for different purposes: e.g. you could have 2 versions of `04 Fades/1 Create fade`, one which creates a fade down and one a fade up. The syntax for this would be as follows:
25+
Many scripts also contain User Defined Variables. With these, when you call the script within Qlab, you can declare these variables globally and set them from within Qlab. This is particularly useful for using the same script for different purposes: e.g. you could have 2 versions of `Fades/Create fade`, one which creates a fade down and one a fade up. The syntax for this would be as follows:
2626

2727
```applescript
2828
global userLevel, userPrefix
@@ -40,7 +40,7 @@ set userPrefix to "Fade down: "
4040

4141
Many of these variables will stay the same for your template from show to show - some others depend on the design. These are set from within Qlab, as the notes of a cue.
4242

43-
Using the example `03 Levels/Bump level`, the variables from Qlab are `audioChannelCount` and `minAudioLevel`.
43+
Using the example `Levels/Bump level`, the variables from Qlab are `audioChannelCount` and `minAudioLevel`.
4444

4545
To set these variables, you must set as a User Defined Variable `variableCueListName`. This is the cue list that you have stored your notes cues in. I recommend using Memo cues. In this instance, you would name one cue `Output channel count` and the other `Min audio level`. You do not need numbers for those cues.
4646

@@ -53,7 +53,7 @@ The total list of Qlab Note variables required for the entire script library is:
5353

5454
### Template cues
5555

56-
The current generation of scripts in `09 Routing` work using templates. This means you can quickly and easily set levels, crosspoints, etc. to multiple 'defaults' via a quick dialog box.
56+
The current generation of scripts in `Routing` work using templates. This means you can quickly and easily set levels, crosspoints, etc. to multiple 'defaults' via a quick dialog box.
5757

5858
To use these, you must set `templateCueListName` and `templateGroupCueName` in User Defined Variables. It will then use every audio file in the group cue as an option, and copy the appropriate routing from there, up to the count of your "Output Channel Count" value.
5959

0 commit comments

Comments
 (0)