Revision [1377]

This is an old revision of WindowPatchBay made by admin on 2009-12-30 00:09:55.

 

PARIS' Patch Bay Window



Quick access: Common applications for your Patch Bay

The following detailed tutorials cover some of the Patch Bay's more commonly-used applications




[the following stub article is unfinished and not yet fact-checked - feel free to add or correct]

An overview of the Patch Bay


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 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.

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.

What's in your Patch Bay?


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.

These objects are representations of external parts of your PARIS hardware:

These objects are representations of internal parts of your PARIS software:

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, 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.

4) You cannot patch across submixes - eg you can't patch Mixer-A FX into Mixer B's inputs.

What You Need To Know About Storing And Recalling Patch Bay Setups


To come - tutorial on how PARIS stores the setups.

More notes on patching-related topics, which will eventually be sorted and compiled here, are available at John Bercik's excellent Paris Notes site.
There are no comments on this page.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki