Duality SE Operator's Manual - Solid State Logic

More documents

Recommendations

Info

automationsetup GuidelinesFor A-FADA to work correctly it essential that the DAW track controlling the analogue channel is not also feeding its postfader signal into the channel, otherwise all level changes will be doubled – an effect which is probably unwanted. This canbe resolved in a number of ways, such as:Method 1: Create additional Daw tracksThis option allows automation to be written independently for analogue and DAW channels.Create 32 (or more if MCU control is in use) blank DAW tracks, and bank them to appear on consecutive console channelsstarting from channel 1. Now select A-FADA.If you have existing DAW automation you wish to re-use, copy it from the audio tracks and paste it to the blank tracks youhave just created. You will then need to either disable or delete the automation from the original tracks.If the automation is deleted rather than disabled, micro-automation (such as the removal of undesirable transients) can beperformed on the original audio tracks within the DAW using a mouse or trackball.Note that MIDI tracks should not normally be used as the fader position is displayed as a controller value (0 – 127)rather than in dB and they may be restrictions on copying data between tracks of different types.5-28 Duality se V3 Operator’s Manual
automationMethod 2: use pre-fade outputsThis option is suitable if you are working with up to 32 mono signals (or more with MCU DAW control).Route the DAW tracks pre-fader to the appropriate analogue outputs. In Pro Tools this can be done using a pre-fader auxsend and setting the aux gain to 0dB. In Logic, route an aux send to a different bus on each channel then route the busmasters to the appropriate analogue outputs.You now need to de-assign the main track outputs to avoid summing pre and post fader signals. As Pro Tools will deactivateany channels without an output, we suggest creating a dummy bus to which to route all channels, then ignoring itsoutput. Within the DAW, fader movements will now only affect the (unused) Master bus and any other post-fader sends.Method 3: use a dedicated Daw for analogue automationUse two DAW layers, one for your audio and one for your automation. This will require you to have two DAWs runningon either the same or two separate computers, and to enable both DAW layers within the console screen’s ssl > Misc> setup menu.See the Installation section for information regarding how to set up multi-computer configurations.A variation on this is possible with Logic, which allows two (or more) controllers to be configured. This allows one layerto be used as a normal DAW controller and the second to be locked to the dedicated automation tracks (up to a maximumof 48).Micro-automation (such as the removal of undesirable transients) could be performed on the original audio tracks withinthe DAW by entering DAW Focus mode and scrolling to those tracks.Duality se V3 Operator’s Manual5-29
Page 1:
Solid State LogicS O U N D V I S I
Page 4 and 5:
Manual ContentsFader Grouping 2-12F
Page 6 and 7:
Manual ContentsWorking with DaW aut
Page 8 and 9:
Manual ContentsseCtiOn 6: reMOte Br
Page 10 and 11:
This page is intentionally almost b
Page 12 and 13:
IntroductionThis page is intentiona
Page 14 and 15:
IntroductionCreative Versatility•
Page 16 and 17:
IntroductionThis page is intentiona
Page 18 and 19:
Page 20 and 21:
Console OperationsThis page is inte
Page 22 and 23:
Console OperationsSignal Processor
Page 24 and 25:
Console Operationsan Introduction t
Page 26 and 27:
Console OperationsAbove each bay of
Page 28 and 29:
Console Operationsrel/HOlD — This
Page 30 and 31:
Console OperationsChannel Output (C
Page 32 and 33:
Console OperationsChannel panAt the
Page 34 and 35:
Console OperationsMaster Channel Fa
Page 36 and 37:
Console OperationsTo edit any exist
Page 38 and 39:
Console Operations12342-16 Duality
Page 40 and 41:
Console OperationsCentral routing p
Page 42 and 43:
Console OperationsMain Output Funct
Page 44 and 45:
Console OperationsMaster FaderThe m
Page 46 and 47:
Console OperationsIf either MInI a
Page 48 and 49:
Console OperationsMonitor OptionsA
Page 50 and 51:
Console OperationsMonitor speaker C
Page 52 and 53:
Console OperationsMonitor level Dis
Page 54 and 55:
Console OperationsCue/Fx send Maste
Page 56 and 57:
Console OperationsMisc OptionsA num
Page 58 and 59:
Console OperationsThe following opt
Page 60 and 61:
Console OperationsMix reassign Matr
Page 62 and 63:
Console OperationsCentre section Me
Page 64 and 65:
Console Operationssetup MenuThe cen
Page 66 and 67:
Console OperationsDaw setupThe next
Page 68 and 69:
Page 70 and 71:
DaWplug-In editor 3-33Plug-In Edito
Page 72 and 73:
DaWThis page is intentionally almos
Page 74 and 75:
DaWConsole FocusThe console can be
Page 76 and 77:
Page 78 and 79:
DaWConnecting via physical MIDI por
Page 80 and 81:
DaWsetting your workstation(s) to c
Page 82 and 83:
DaWlogic pro 8When Logic is assigne
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
DaWDaW utility Buttons (9)This grou
Page 90 and 91:
Page 92 and 93:
DaWChannel solo and Cut panelsChann
Page 94 and 95:
DaWselect ModeWith the sel button (
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
DaWOther useful transport modesHalf
Page 102 and 103:
DaWselection Mode (Zoom/sel button
Page 104 and 105:
Page 106 and 107:
DaWselecting a DaW Channel for plug
Page 108 and 109:
DaWComparing your ChangesPressing t
Page 110 and 111:
DaWedit tools MenuEdit Tools (edts)
Page 112 and 113:
Page 114 and 115:
DaWautomation status DisplayPressin
Page 116 and 117:
Page 118 and 119:
DaWThe majority of DAW functions ar
Page 120 and 121:
DaWthe logic templateDuality SE emu
Page 122 and 123:
DaWnuendo/Cubase templateAs with ot
Page 124 and 125:
DaWDuality se’s nuendo Control sc
Page 126 and 127: DaWCHannel is unchanged and assigns
Page 128 and 129: DaWThe Transport Control buttons ar
Page 130 and 131: This page is intentionally almost b
Page 132 and 133: total recallThis page is intentiona
Page 136 and 137: total recalltOtal reCall anD prOjeC
Page 138 and 139: total recallrecalling a tr setupWit
Page 140 and 141: total recallresettInG COntrOlsautom
Page 146 and 147: automationThis page is intentionall
Page 148 and 149: automation5-ivDuality se V3 Operato
Page 152 and 153: automationworking with projects and
Page 156 and 157: automationCreating a new Mix passTo
Page 158 and 159: automationMix runningPress play on
Page 160 and 161: automationJoin and reviseAt any tim
Page 162 and 163: automationprotection ModesEach comp
Page 164 and 165: automationswitch automationPressing
Page 166 and 167: automationtrim lokTrim Lok (only av
Page 168 and 169: automationCopy and swapCopy and Swa
Page 170 and 171: automationautomation setup OptionsT
Page 172 and 173: automationTo set up MMC locates, se
Page 182 and 183: emoteThis page is intentionally alm
Page 186 and 187: emoteConnecting Duality se to the C
Page 188 and 189: emoteBacking up a projectTo create
Page 190 and 191: emotetOtal reCall taBHere you can r
Page 192 and 193: emoteexternals taBThis page allows
Page 198 and 199: Block DiagramsThis page is intentio
show all

Duality SE Operator's Manual - Solid State Logic

Create successful ePaper yourself

Delete template?

Save as template?