Revision history for WindowPatchBay


Revision [1973]

Last edited on 2015-12-26 15:14:43 by admin
Additions:
The Patch Bay is one of the most useful features of PARIS. It gives PARIS a flexibility and power that is more akin to a "studio mainframe" rather than a classic DAW. The Patchbay is accessed by pressing the letter B on your computer keyboard, or the number 7 followed by a period on your C16.
Deletions:
The Patch Bay is one of the most useful features of PARIS. It is accessed by pressing the letter B on your computer keyboard, or the number 7 followed by a period on your C16.

Revision [1659]

Edited on 2010-02-27 18:41:01 by admin
Additions:
Many musicians have reported finding PARIS' patch bay difficult to understand. This might well be due to our training; your guitar's OUTPUT has always gone to your distortion pedal's INPUT; your keyboard's Midi OUT has always been patched to your Midi interface's IN. That's the way we do things in the audio world - "outs" go to "ins" - and when you're patching between objects that represent *software* in your Patch Bay (the Mixer to the Mixer inserts, for example) it's done the same way - by patching "ins" to "outs".
But when you're patching from software to hardware - how would you tell PARIS' Patch bay that you want the signal that's being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? By patching from MEC MASTER A's Input 1 //to the IN of Mixer A's Channel One//.
That's right: when you're patching between the patchbay objects that represent software and the patchbay objects that represent hardware - you have to connect "ins" to "ins" and "outs" to "outs". It might be easiest to view connections between PARIS' software and its hardware as //mapping// instead of //patching//; you're mapping "MEC Input 1" to "Mixer Channel 1".
Deletions:
Many musicians have reported finding PARIS' patch bay difficult to understand. This might well be due to our training; your guitar's OUTPUT has always gone to your distortion pedal's INPUT; your keyboard's Midi OUT has always been patched to your Midi interface's IN. That's the way we do things in the audio world - "outs" go to "ins".
So when you're patching between objects that represent *software* in your Patch Bay (the Mixer to the Mixer inserts, for example) it's done the same way - by patching "ins" to "outs".
But when you're patching from software to hardware - how do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? By patching from MEC MASTER A's Input 1 //to the IN of Mixer A's Channel One//. That's right: you patch an "in" to an "in". It might be easiest to view connections between PARIS' software and its hardware as //mapping// instead of //patching//; you're mapping "MEC Input 1" to "Mixer Channel 1".

Revision [1658]

Edited on 2010-02-27 18:38:43 by admin
Additions:
So when you're patching between objects that represent *software* in your Patch Bay (the Mixer to the Mixer inserts, for example) it's done the same way - by patching "ins" to "outs".
But when you're patching from software to hardware - how do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? By patching from MEC MASTER A's Input 1 //to the IN of Mixer A's Channel One//. That's right: you patch an "in" to an "in". It might be easiest to view connections between PARIS' software and its hardware as //mapping// instead of //patching//; you're mapping "MEC Input 1" to "Mixer Channel 1".
Deletions:
How do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? You patch from MEC MASTER A's Input 1 //to the IN of Mixer A's Channel One//. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//. It might be easiest to view connections between PARIS' software (eg Mixer A) to its hardware (eg MEC MASTER A) as //mapping// rather than //patching//; you're //mapping// MEC Input 1 to Mixer Channel 1.

Revision [1657]

Edited on 2010-02-27 18:34:08 by admin
Additions:
- MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards) or a combination such as an 8i, an 8o and an ADAT card that add up to the maximum of 16 I/O per group of modules.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//. It might be easiest to view connections between PARIS' software (eg Mixer A) to its hardware (eg MEC MASTER A) as //mapping// rather than //patching//; you're //mapping// MEC Input 1 to Mixer Channel 1.
Deletions:
- MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards) or a combination such as an 8i, an 8o and an ADAT card.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//. It might be easiest to view connections between PARIS' software (eg Mixer A) to its hardware (eg MEC MASTER A) as //mapping// rather than //patching//; you're //mapping// MEC Input 1 to Mixer Channel 1. You're //showing// MEC Input 1 where you want its audio sent.

Revision [1651]

Edited on 2010-02-26 19:33:27 by admin
Additions:
[the following article is unfinished and not yet fact-checked - feel free to add or correct information]
The Patch Bay is one of the most useful features of PARIS. It is accessed by pressing the letter B on your computer keyboard, or the number 7 followed by a period on your C16.
The Patch Bay also contains certain peculiarities and assumptions that can reduce even seasoned PARIS users to despair. Included below are a couple of general observations about the Patch Bay that are worth bearing in mind.
Deletions:
[the following stub article is unfinished and not yet fact-checked - feel free to add or correct]
The Patch Bay is one of the most amazing features of PARIS. It is accessed by pressing B on your computer keyboard, or the number 7 followed by a period on your C16.
The Patch Bay also contains certain peculiarities and assumptions that can reduce seasoned PARIS users to despair. Included below are a couple of general observations about the Patch Bay that are worth bearing in mind.

Revision [1608]

Edited on 2010-02-17 01:24:57 by admin [added section "The First Thing To Understand"]
Additions:
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//. It might be easiest to view connections between PARIS' software (eg Mixer A) to its hardware (eg MEC MASTER A) as //mapping// rather than //patching//; you're //mapping// MEC Input 1 to Mixer Channel 1. You're //showing// MEC Input 1 where you want its audio sent.
Deletions:
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//. It might be easiest to view connections between PARIS' software (eg Mixer A) to its hardware (eg MEC MASTER A) as //mapping// rather than //patching//; you're //mapping// MEC Input 1 to Mixer Channel 1.

Revision [1607]

Edited on 2010-02-17 01:23:30 by admin [added section "The First Thing To Understand"]
Additions:
How do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? You patch from MEC MASTER A's Input 1 //to the IN of Mixer A's Channel One//. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//. It might be easiest to view connections between PARIS' software (eg Mixer A) to its hardware (eg MEC MASTER A) as //mapping// rather than //patching//; you're //mapping// MEC Input 1 to Mixer Channel 1.
Deletions:
How do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? You patch from MEC MASTER A's Input 1 //to the IN Mixer A's Channel One//. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//; you aren't really patching, you're //mapping// MEC IN 1 to Mixer Channel 1.

Revision [1606]

Edited on 2010-02-17 01:21:15 by admin [added section "The First Thing To Understand"]
Additions:
Many musicians have reported finding PARIS' patch bay difficult to understand. This might well be due to our training; your guitar's OUTPUT has always gone to your distortion pedal's INPUT; your keyboard's Midi OUT has always been patched to your Midi interface's IN. That's the way we do things in the audio world - "outs" go to "ins".
Deletions:
Many musicians have reported finding PARIS' patch bay difficult to understand. I believe this is due to our training; your guitar's OUTPUT has always gone to your distortion pedal's INPUT; your keyboard's Midi OUT has always been patched to your Midi interface's IN. That's the way we do things in the audio world - "outs" go to "ins".

Revision [1605]

Edited on 2010-02-17 01:18:10 by admin [added section "The First Thing To Understand"]
Additions:
Many musicians have reported finding PARIS' patch bay difficult to understand. I believe this is due to our training; your guitar's OUTPUT has always gone to your distortion pedal's INPUT; your keyboard's Midi OUT has always been patched to your Midi interface's IN. That's the way we do things in the audio world - "outs" go to "ins".
How do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? You patch from MEC MASTER A's Input 1 //to the IN Mixer A's Channel One//. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//; you aren't really patching, you're //mapping// MEC IN 1 to Mixer Channel 1.
Deletions:
Many musicians have reported finding PARIS' patch bay difficult to understand. I believe this is due to our training; your guitar's OUTPUT goes to your distortion pedal's INPUT, and your distortion pedal's OUTPUT goes to your amp's INPUT; your keyboard's Midi OUT is patched to your Midi interface's IN and your Midi interface's Midi OUT is patched to your keyboard's Midi IN - right?
So how do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? You patch from MEC MASTER A's Input 1 //to the IN Mixer A's Channel One//. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//; you're telling the former to send its signal to the latter. You aren't really patching - in fact you're //mapping// MEC IN 1 to Mixer Channel 1.

Revision [1604]

Edited on 2010-02-17 01:15:26 by admin [added section "The First Thing To Understand"]
Additions:
So how do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One? You patch from MEC MASTER A's Input 1 //to the IN Mixer A's Channel One//. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are //hardware//, and Mixer A is //software//; you're telling the former to send its signal to the latter. You aren't really patching - in fact you're //mapping// MEC IN 1 to Mixer Channel 1.
Deletions:
So how do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One?
That's right; you patch from MEC MASTER A's Input 1... to the IN Mixer A's Channel One. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are hardware, and Mixer A is software; you're telling the former to send its signal to the latter. You aren't really patching - in fact you're //mapping// MEC IN 1 to Mixer Channel 1.

Revision [1603]

Edited on 2010-02-17 01:13:55 by admin [added section "The First Thing To Understand"]
Additions:
====The Very First Thing You Need To Understand About Your Patch Bay====
Many musicians have reported finding PARIS' patch bay difficult to understand. I believe this is due to our training; your guitar's OUTPUT goes to your distortion pedal's INPUT, and your distortion pedal's OUTPUT goes to your amp's INPUT; your keyboard's Midi OUT is patched to your Midi interface's IN and your Midi interface's Midi OUT is patched to your keyboard's Midi IN - right?
So how do you tell PARIS' Patch bay that you want sound being sent into INPUT ONE on your MEC to go IN to Mixer Channel One?
That's right; you patch from MEC MASTER A's Input 1... to the IN Mixer A's Channel One. That's right: you patch an IN - to an IN.
Why? Because MEC MASTER A and MEC MODULES A are hardware, and Mixer A is software; you're telling the former to send its signal to the latter. You aren't really patching - in fact you're //mapping// MEC IN 1 to Mixer Channel 1.
===Additional general observations: ===
Deletions:
===General observations: ===

Revision [1392]

Edited on 2009-12-30 03:07:00 by admin [added section "The First Thing To Understand"]
Additions:
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card appear to be different: Mixer A's output is the sum of all submixes while Mixers B and higher appear to output *only the mixed audio from their respective submix*. Unexplored potential might therefore exist for sophisticated patching to enable special applications like parallel bus compression etc.
Deletions:
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Unexplored potential might exist for sophisticated patching to enable parallel bus compression etc.

Revision [1391]

Edited on 2009-12-30 03:05:36 by admin [added section "The First Thing To Understand"]
Additions:
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Unexplored potential might exist for sophisticated patching to enable parallel bus compression etc.
Deletions:
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that might permit things like parallel bus compression - patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then into a pair of Mixer A's channel strips.

Revision [1390]

Edited on 2009-12-30 03:04:19 by admin [added section "The First Thing To Understand"]
Additions:
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that might permit things like parallel bus compression - patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then into a pair of Mixer A's channel strips.
Deletions:
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.

Revision [1389]

Edited on 2009-12-30 03:01:42 by admin [added section "The First Thing To Understand"]
Additions:
- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.
This offers a lot of flexibility in routing from software to software or software to hardware.
4) You cannot patch across submixes (eg you can't patch from Mixer-A FX into Mixer B's inputs) internally via the Patch Bay alone. //However//, you //can// use hardware cables to patch between MECs - which suggests some interesting possibilities.
Deletions:
- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A. Brian Tankersley invented a great system for
4) You cannot patch across submixes - eg you can't patch Mixer-A FX into Mixer B's inputs.

Revision [1377]

Edited on 2009-12-30 00:09:55 by admin [added section "The First Thing To Understand"]
Additions:
=====PARIS' Patch Bay Window=====
====An overview of the Patch Bay====
Deletions:
=====The Patch Bay Window=====
===PARIS' Patch Bay Window===

Revision [1376]

Edited on 2009-12-30 00:08:45 by admin [added section "The First Thing To Understand"]
Additions:
The following detailed tutorials cover some of the Patch Bay's more commonly-used applications
Deletions:
The following are detailed tutorials on commonly-used functions of the Patch Bay

Revision [1318]

Edited on 2009-12-24 02:45:50 by admin [added section "The First Thing To Understand"]
Additions:
1) A hardware input can feed multiple mixer inputs. For example, input 1 on MEC Master A can feed any or all of your mixer channels, should you need sixteen tracks containing the same information. However, the reverse is not true - each software input can only receive *one* input. You can't attach all four of your MEC's analog inputs to Mixer A's "Track One".
2) You can have eight modules installed in a single MEC - but you can only place them into four slots in the MEC Modules object in the Patch Bay. Hence you can't use more than four I/O modules at a time per MEC (each ADAT module counts as two modules - 8 channels of ADAT input and 8 channels of ADAT output). It may seem illogical to permit eight modules to be installed in your MEC when only four at a time can be accessed, but it has its uses; for example you can store one Patch Bay configuration that uses one group of modules and another that uses another group.
3) "One way" patches (ie a headphone send from an aux to an output and then to a headphone amp) will usually not work until you *complete the loop* - meaning the aux requires a connection both "from" and "to" it. Just "close the circle" by routing that aux's return to any input you aren't using such as an unused mixer in or Aux.
Deletions:
1) A hardware input can feed multiple mixer inputs. For example, input 1 on MEC Master A can feed any or all of your mixer channels, should you need sixteen tracks containing the same information. However, each software input can only receive *one* input. You can't attach Inputs 1 to 4 from MEC Master A all to Mixer A's "Track One".
2) You can have eight modules installed in a single MEC - but you can only place them into four slots in the Patch Bay. Hence you can't use more than four I/O modules at a time (each ADAT module really sort of counts as two modules - 8 channels of ADAT input and 8 channels of ADAT output).
3) Sometimes a patch will not work until you *complete the loop*, meaning to connect both "to and from" the target. This can be frustrating if for example you just want to send **to** a headphone amp, which usually only needs to be a one-way trip (there's nothing you want PARIS to receive //back// from that amp). Just "close the circle" by routing that aux's return to any input you aren't using such as an unused mixer in or Aux.
It may seem illogical to permit eight modules to be installed in your MEC when only four at a time can be accessed, but it has its uses; for example you can store one Patch Bay configuration that uses one group of modules and another that uses another group.

Revision [1317]

Edited on 2009-12-24 02:40:10 by admin [added section "The First Thing To Understand"]
Additions:
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[MixerLess permit live inputs to be monitored independently of their "record enable" status]], [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS via ADAT, render native effects onto a track (or even hardware effects) - all with (virtually) zero latency and pristine sound quality.
Deletions:
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, permit live inputs to be monitored independently of their "record enable" status, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS via ADAT, render native effects onto a track (or even hardware effects) - all with (virtually) zero latency and pristine sound quality.

Revision [1315]

Edited on 2009-12-23 23:51:31 by admin [added section "The First Thing To Understand"]
Additions:
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, permit live inputs to be monitored independently of their "record enable" status, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS via ADAT, render native effects onto a track (or even hardware effects) - all with (virtually) zero latency and pristine sound quality.
The Patch Bay also contains certain peculiarities and assumptions that can reduce seasoned PARIS users to despair. Included below are a couple of general observations about the Patch Bay that are worth bearing in mind.
The patch bay contains representations of both your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer), and allows you to patch between them digitally. //There is virtually no visual distinction between your hardware and software "inputs" and "outputs",// so it's important to keep clear in your mind what is software and what is hardware to avoid confusion. The patches you create work whether or not they are visible in the main window of the Patch Bay; you drag them into that window to *examine* or *change* their patching, but once you've done that you can drag them back into the "holding tank" (upper RH pane) without consequence.
Deletions:
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, permit live inputs to be monitored independently of their "record enable" status, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
The Patch Bay also contains certain peculiarities and assumptions that can reduce seasoned PARIS users to despair. We've included a couple of general observations about the Patch Bay worth bearing in mind.
The patch bay contains representations of your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer) and allows you to patch between them. //There is no visual distinction between the two,// so it's important to keep clear in your mind what is software and what is hardware to avoid confusion. They work whether or not they are visible in the main window of the Patch Bay, you drag them into that window to *examine* or *change* their patching.

Revision [1314]

Edited on 2009-12-23 23:47:08 by admin [added section "The First Thing To Understand"]
Additions:
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, permit live inputs to be monitored independently of their "record enable" status, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
- Mixer-A (or B or C or D etc) - The sixteen inputs represent the sixteen channels of your PARIS mixer; the two output pairs (Main L/R and Monitor L/R) represent the summed audio coming from that submix. The two output pairs are different, in that the Monitor pair is affected by "soloing" a channel and the Main pair isn't (this is meant to let you monitor independently of the signal going to tape). If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
- Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the Mixer A (or B etc). Thus (and this is where folks can get confused) its inputs and outputs are labeled in stereo pairs - 1 through 8 (L and R), but they can also effectively be used as sixteen discrete channels. Auxes are where you're going to do a lot of your routing work.
- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A. Brian Tankersley invented a great system for
Deletions:
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
- Mixer-A (or B or C or D etc) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
- Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.

Revision [1313]

Edited on 2009-12-23 23:39:01 by admin [added section "The First Thing To Understand"]
Additions:
----
**//Quick access: Common applications for your Patch Bay//**
----
===PARIS' Patch Bay Window===
Mastery over signal routing in the Patch Bay will give you the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
Deletions:
===Quick access: Commonly used Patch Bay techniques===
Mastery over signal routing in the Patch Bay gives the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.

Revision [1312]

Edited on 2009-12-23 14:14:10 by admin [added section "The First Thing To Understand"]
Additions:
===Quick access: Commonly used Patch Bay techniques===
[the following stub article is unfinished and not yet fact-checked - feel free to add or correct]
Deletions:
[this stub article is unfinished and not fact-checked - feel free to add or correct]

Revision [1311]

Edited on 2009-12-23 14:13:06 by admin [added section "The First Thing To Understand"]
Additions:
- MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards) or a combination such as an 8i, an 8o and an ADAT card.
Deletions:
- MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards).

Revision [1310]

Edited on 2009-12-23 14:12:12 by admin [added section "The First Thing To Understand"]
Additions:
====What's in your Patch Bay?====
==These objects are representations of external parts of your PARIS hardware:==
- MEC Master A (or B or C or D etc) - if you have a MEC this represents its built-in hardware I/O.
- MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards).
- Interface 442-A (or B etc) - this represents your IF-442 if you have one
==These objects are representations of internal parts of your PARIS software:==
- Mixer-A (or B or C or D etc) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
- Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.
Deletions:
What's in your Patch Bay?
**These objects are representations of external parts of your PARIS hardware:**
MEC Master A (or B or C or D etc) - if you have a MEC this represents its built-in hardware I/O.
MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards).
Interface 442-A (or B etc) - this represents your IF-442 if you have one
**These objects are representations of internal parts of your PARIS software:**
-- Mixer-A (or B or C or D etc) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
-- Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
-- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.

Revision [1309]

Edited on 2009-12-23 14:10:38 by admin [added section "The First Thing To Understand"]
Additions:
-- Mixer-A (or B or C or D etc) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
-- Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
-- Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.
Deletions:
1) Mixer-A (or B or C or D etc) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
2) Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
3) Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.

Revision [1308]

Edited on 2009-12-23 14:10:12 by admin [added section "The First Thing To Understand"]
Additions:
What's in your Patch Bay?
The patch bay contains representations of your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer) and allows you to patch between them. //There is no visual distinction between the two,// so it's important to keep clear in your mind what is software and what is hardware to avoid confusion. They work whether or not they are visible in the main window of the Patch Bay, you drag them into that window to *examine* or *change* their patching.
===General observations: ===
Deletions:
The patch bay consists of representations of your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer) - and allows you to patch between them. //There is no visual distinction between the two,// so it's important to keep clear in your mind what is software and what is hardware to avoid confusion.
General observations:

Revision [1307]

Edited on 2009-12-23 14:07:44 by admin [added section "The First Thing To Understand"]
Additions:
MEC Master A (or B or C or D etc) - if you have a MEC this represents its built-in hardware I/O.
MEC Modules A (or B etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards).
Interface 442-A (or B etc) - this represents your IF-442 if you have one
1) Mixer-A (or B or C or D etc) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
2) Mixer-A FX (or B etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
3) Mixer A Insert (or B etc) - this represents the //"EDS inserts"// on each channel in Mixer A.
Deletions:
MEC Master A (or B or C etc) - if you have a MEC this represents its built-in hardware I/O.
MEC Modules A (or B or C etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards).
Interface 442-A (or B or C etc) - this represents your IF-442 if you have one
1) Mixer-A (or B or C) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
2) Mixer-A FX (or B or C etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
3) Mixer A Insert - this actually represents the //"EDS inserts"// on each channel in Mixer A.

Revision [1306]

Edited on 2009-12-23 14:06:41 by admin [added section "The First Thing To Understand"]
Additions:
The patch bay consists of representations of your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer) - and allows you to patch between them. //There is no visual distinction between the two,// so it's important to keep clear in your mind what is software and what is hardware to avoid confusion.
**These objects are representations of external parts of your PARIS hardware:**
**These objects are representations of internal parts of your PARIS software:**
Deletions:
**1) The patch bay consists of representations of your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer) - and allows you to patch between them. ** There is no visual distinction between the two, so it's important to keep clear in your mind what is software and what is hardware.
**Representations of your external PARIS hardware:**
**Representations of your internal PARIS software:**

Revision [1305]

Edited on 2009-12-23 14:04:54 by admin [added section "The First Thing To Understand"]
Additions:
The Patch Bay also contains certain peculiarities and assumptions that can reduce seasoned PARIS users to despair. We've included a couple of general observations about the Patch Bay worth bearing in mind.
Deletions:
The Patch Bay also contains certain peculiarities and assumptions that can reduce seasoned PARIS users to despair. So we'll attempt to make it simple, and to start here are a couple of general observations about the Patch Bay worth bearing in mind.

Revision [1304]

Edited on 2009-12-23 14:03:46 by admin [added section "The First Thing To Understand"]
Additions:
1) Mixer-A (or B or C) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits things like bus compression by patching the output of Mixer-B (ie, submix B) to the digital out of MEC Master B, connecting to external digital equipment and looping its output back to MEC A's SP/DIF input and then to a pair of channel strips.
Deletions:
1) Mixer-A (or B or C) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits bus compression - say by patching the output of that mixer back to a stereo pair.

Revision [1303]

Edited on 2009-12-23 13:56:37 by admin [added section "The First Thing To Understand"]
Additions:
[this stub article is unfinished and not fact-checked - feel free to add or correct]
The Patch Bay is one of the most amazing features of PARIS. It is accessed by pressing B on your computer keyboard, or the number 7 followed by a period on your C16.
The Patch Bay also contains certain peculiarities and assumptions that can reduce seasoned PARIS users to despair. So we'll attempt to make it simple, and to start here are a couple of general observations about the Patch Bay worth bearing in mind.
**1) The patch bay consists of representations of your external hardware (MEC and its associated modules, etc) and your internal software (PARIS mixer) - and allows you to patch between them. ** There is no visual distinction between the two, so it's important to keep clear in your mind what is software and what is hardware.
**Representations of your external PARIS hardware:**
MEC Master A (or B or C etc) - if you have a MEC this represents its built-in hardware I/O.
MEC Modules A (or B or C etc) - this represents any modules in your MEC, such as an ADAT module. Double click to open it and configure the modules you want to access. There is space inside the object for two blocks of 8 inputs (eg two 8i cards) and two blocks of eight outputs (eg two 8o cards).
Interface 442-A (or B or C etc) - this represents your IF-442 if you have one
**Representations of your internal PARIS software:**
1) Mixer-A (or B or C) - This represents the sixteen inputs into your PARIS mixer, and two types of output (Main L/R and Monitor L/R) If you have sixteen hardware inputs (say 2x 8i modules) you can connect each input to an individual mixer channel. An important note: the outputs of the mixers for each card are different! Mixer A's output is the sum of all submixes. Mixers B and higher output *only the mixed audio from their respective submix*. Thus unexplored potential exists for sophisticated patching that permits bus compression - say by patching the output of that mixer back to a stereo pair.
2) Mixer-A FX (or B or C etc)- this actually represents //Auxes 1 through 8// on the relevant Mixer A window. Its inputs and outputs are labelled in stereo pairs - 1 through 8 (L and R) - but they're sixteen discrete channels.
3) Mixer A Insert - this actually represents the //"EDS inserts"// on each channel in Mixer A.
General observations:
1) A hardware input can feed multiple mixer inputs. For example, input 1 on MEC Master A can feed any or all of your mixer channels, should you need sixteen tracks containing the same information. However, each software input can only receive *one* input. You can't attach Inputs 1 to 4 from MEC Master A all to Mixer A's "Track One".

2) You can have eight modules installed in a single MEC - but you can only place them into four slots in the Patch Bay. Hence you can't use more than four I/O modules at a time (each ADAT module really sort of counts as two modules - 8 channels of ADAT input and 8 channels of ADAT output).
3) Sometimes a patch will not work until you *complete the loop*, meaning to connect both "to and from" the target. This can be frustrating if for example you just want to send **to** a headphone amp, which usually only needs to be a one-way trip (there's nothing you want PARIS to receive //back// from that amp). Just "close the circle" by routing that aux's return to any input you aren't using such as an unused mixer in or Aux.
4) You cannot patch across submixes - eg you can't patch Mixer-A FX into Mixer B's inputs.
It may seem illogical to permit eight modules to be installed in your MEC when only four at a time can be accessed, but it has its uses; for example you can store one Patch Bay configuration that uses one group of modules and another that uses another group.
The following are detailed tutorials on commonly-used functions of the Patch Bay
Deletions:
The Patch Bay is one of the most amazing features of PARIS. It is accessed by pressing B on your computer keyboard, or the number 7 followed by a period on your C16.
Following are detailed tutorials on commonly-used functions of the Patch Bay

Revision [1250]

Edited on 2009-07-06 11:15:09 by admin [added "mixerless studio" link]
Additions:
- [[MixerLess Live monitor and record at the same time without re-patching]]

Revision [644]

Edited on 2008-04-10 14:21:44 by admin [added "mixerless studio" link]
Additions:
More notes on patching-related topics, which will eventually be sorted and compiled here, are available at John Bercik's excellent [[http://kfocus.com/paris/ Paris Notes]] site.

Revision [641]

Edited on 2008-04-10 14:07:05 by admin [added "mixerless studio" link]
Additions:
- [[TalkBack Setting up talkback]]
Deletions:
- Setting up talkback

Revision [612]

Edited on 2008-04-10 11:46:46 by admin [added "mixerless studio" link]
Additions:
Following are detailed tutorials on commonly-used functions of the Patch Bay
Deletions:
The following are detailed tutorials on achieving different purposes using your Patch Bay.

Revision [539]

Edited on 2008-04-08 13:13:44 by admin [added "mixerless studio" link]
Additions:
===What You Need To Know About Storing And Recalling Patch Bay Setups===
To come - tutorial on how PARIS stores the setups.

Revision [538]

Edited on 2008-04-08 13:06:34 by admin [added "mixerless studio" link]
Additions:
Mastery over signal routing in the Patch Bay gives the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[PatchExternFx patch in external effects processors]], send a strip of audio SMPTE to an external output to drive an external sequencer without having to listen to it, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
Deletions:
Mastery over signal routing in the Patch Bay gives the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[PatchExternFx patch in external effects processors]], keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.

Revision [537]

Edited on 2008-04-08 13:05:19 by admin [added "mixerless studio" link]
Additions:
- Feeding PARIS signal from an eight-bus board
Deletions:
Feeding PARIS signal from an eight-bus board

Revision [536]

Edited on 2008-04-08 13:04:55 by admin [added "mixerless studio" link]
Additions:
Mastery over signal routing in the Patch Bay gives the ability to create [[PatchHeadphones individual headphone mixes]], or [[PatchClick route click tracks to headphones]], [[PatchHeadphonesWfx supply reverb/FX]] in different quantities to different headphone mixes, [[PatchExternFx patch in external effects processors]], keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
- [[PatchHeadphones Setting up headphone mixes]]
- [[PatchHeadphonesWfx Feeding Headphone auxes with effects (eg reverb)]]
- Setting up talkback
- [[PatchClick Setting up a "click track"]]
- Routing SMPTE timecode out of PARIS
- [[PatchExternFx Patching external effects processors]] into PARIS
Deletions:
Mastery over signal routing in the Patch Bay gives the ability to create headphone mixes, route click tracks to headphones, supply reverb/FX in different quantities to different headphone mixes, patch in external effects processors, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.
[[PatchHeadphones Setting up headphone mixes]]
[[PatchHeadphonesWfx Feeding Headphone auxes with effects (eg reverb)]]
Setting up talkback
[[PatchClick Setting up a "click track"]]
[[PatchExternFx Patching external effects processors]] into PARIS

Revision [535]

Edited on 2008-04-08 13:01:59 by admin [added "mixerless studio" link]
Additions:
[[PatchHeadphones Setting up headphone mixes]]
[[PatchHeadphonesWfx Feeding Headphone auxes with effects (eg reverb)]]
Setting up talkback
[[PatchClick Setting up a "click track"]]
Feeding PARIS signal from an eight-bus board
[[PatchExternFx Patching external effects processors]] into PARIS

Revision [534]

Edited on 2008-04-08 12:59:17 by admin [added "mixerless studio" link]
Additions:

The Patch Bay is one of the most amazing features of PARIS. It is accessed by pressing B on your computer keyboard, or the number 7 followed by a period on your C16.

Mastery over signal routing in the Patch Bay gives the ability to create headphone mixes, route click tracks to headphones, supply reverb/FX in different quantities to different headphone mixes, patch in external effects processors, keep live mics open for player feedback without recording them, route blocks of external tracks through PARIS - all with zero latency and pristine quality.

The following are detailed tutorials on achieving different purposes using your Patch Bay.


Revision [273]

Edited on 2008-04-05 20:48:36 by admin [added "mixerless studio" link]
Additions:
=====The Patch Bay Window=====
Deletions:
The Patch Bay Window

Revision [272]

The oldest known version of this page was created on 2008-04-05 20:48:19 by admin [added "mixerless studio" link]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki