The PARIS Forums


Home » The PARIS Forums » PARIS: Main » Paris limitations and workarounds tutorial part 1
Paris limitations and workarounds tutorial part 1 [message #80149] Fri, 16 February 2007 00:56 Go to next message
Dimitrios is currently offline  Dimitrios   
Messages: 1056
Registered: August 2005
Senior Member
Hi,
To remind us of some things and their possible workarounds...

1)Paris lets you use only 64 DX plugins at once.
For this by using the free FFX4 DX chainer which is stable too, there is
an update bin3 for it, can overcome this by far.

2)VST's do not work well directly with Paris,
You can either use FXpansion 3.3 and transform them to DX or use Chainer
which is a fantastic Paris addition.Chainer can have up to 99 vst plugins
on every Paris vst slot.
NOTE that the 64 limit DOES NOT APPLY FOR VST'S !!

3)Solo a hefty of Paris tracks ACROSS submixes was an impossible (almost)
task under Paris. FADERWORKS enables you to solu ,mute ,change their volume,
group up to 32 times certain audio tracks and works without the need of any
chainer just straight from Paris vst...

4)Paris crashes sometimes (or many times) when you quit the program.
For that the only thing you have to do is move entire ParisPro folder to
c root and this will go away.

5) VSTI support for Paris.
I am working on this...
By now the best candidate is Fruityloops incredible program that works as
VST plugin !
The only major problem is the time sync which would be solved if Fruityloops
could accept MTC as input.
For now it only sends MTC but Paris refuses to sync to Fruityloops mtc output
in anyway I tried...
If you email them asking for MTC input implementation at fruityloops maybe
they do that for us...

6) Sending many audiotracks to a Paris eds effect controlling the dry and
effected signal with no phase problems.
Just use aux1 as stereo and prefade for dry Aux2 as wet, mute all related
audiotracks and put under aux1 and aux2 the same stereo eds effect, like
compressor...
On aux1 just don't compress 0 treshold and on aux2 compress the hell out
of it...

7) Using DX reverb or DX/VST buss compression /effect on several Paris audio
tracks.
First obvious workaround is use native submix where you can load a mono DX
effect on auxes. There you might use two auxes for stereo with same DX effect
on each and then pan them L and R and use the auxes sends for the needed
stereo placement.
The other task which is more adventourous is either using a second computer
with audio card or on same computer using another audio card like rme or
pulsar and a VST host like Cubase or simplier VST chainers like Chainer or
SpinaudioFX.
Lets say you wanna use a DX reverb like Waves Rverb or better.
You use aux1 as stereo feed for the channels you wanna send to the reverb
and put on aux1 external.
Then you patch this to your spdif or adat or analog in/out connected to the
audio interface either on same computer or on second computer.
You audio card must be set to low latency (most can do that nowadays) and
pop up the desired DX/vst effect on desired platform like Cubase.
The return of the reverb can be patched on AUX1 effect return.
For Pulsar users the same applies to use either masterverb Pro or Timeworks
4080L (nice), benefit here is that we have no latency issues with pulsar
cards...

8) Using Paris as a mixing engine only.
You can use wormhole for that wrapped ONLY under FXpansion 3.3 (the usual
Paris wrapper) and then you can have at least 32 fully synced down to sample
audio tracks from computer 2 using Cubase to get mixed inside Paris.
You can use automation in realtime this way because you will be always on
time as Paris sees the audiotracks the time they get inside it so there is
no latency in automation here !
OR you can use 3-4 adat cards and do the same.
With wormhole though you can have 32bit coming in to Paris which at worse
will truncate down to 24 bits !
ADAT cards are 20 bit.

9) Latency compenation with DX/VST EDS effects.
First you can use 0 latency plugins like most late plugins use , especially
compressors eq;s etc...
EDS effetcs though appear to haev their latency whatsoever especially with
big lookaheads...
FADERWORKS again specially implemented after our kind suggestin for us Paris
users is the only latency compensator plugin around with all the other aspects
it has.
You only have to type the latency (you must claculate it) on the "delaying"
track and all other faderwoks instances get delayed for that amount...

I hope I will update this or maybe you can do that ...
Regards,
Dimitrios
Re: Paris limitations and workarounds tutorial part 1 [message #80265 is a reply to message #80149] Sun, 18 February 2007 11:30 Go to previous messageGo to next message
gene lennon is currently offline  gene lennon
Messages: 565
Registered: July 2006
Senior Member
"Dimitrios" <musurgio@otenet.gr> wrote:

>5) VSTI support for Paris.
>I am working on this...
>By now the best candidate is Fruityloops incredible program that works as
>VST plugin !
>The only major problem is the time sync which would be solved if Fruityloops
>could accept MTC as input.
>For now it only sends MTC but Paris refuses to sync to Fruityloops mtc output
>in anyway I tried...
>If you email them asking for MTC input implementation at fruityloops maybe
>they do that for us...
>

Do you mean FL Studio 7? Can you get MIDI into this from an external source
when it’s running inside Paris as a VST plug? Do you have any other tricks
for loading VSTi instruments inside Paris and triggering them from an external
sequencer?

Thanks as always.
Gene
Re: Paris limitations and workarounds tutorial part 1 [message #80306 is a reply to message #80265] Mon, 19 February 2007 01:45 Go to previous message
Dimitrios is currently offline  Dimitrios   
Messages: 1056
Registered: August 2005
Senior Member
Hi Gene,
I will do some more testings and will inform you about these !
Regards,
Dimitrios

"Gene Lennon" <glennon@NOSPmyrealbox.com> wrote:
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>
>>5) VSTI support for Paris.
>>I am working on this...
>>By now the best candidate is Fruityloops incredible program that works
as
>>VST plugin !
>>The only major problem is the time sync which would be solved if Fruityloops
>>could accept MTC as input.
>>For now it only sends MTC but Paris refuses to sync to Fruityloops mtc
output
>>in anyway I tried...
>>If you email them asking for MTC input implementation at fruityloops maybe
>>they do that for us...
>>
>
>Do you mean FL Studio 7? Can you get MIDI into this from an external source
>when it’s running inside Paris as a VST plug? Do you have any other tricks
>for loading VSTi instruments inside Paris and triggering them from an external
>sequencer?
>
>Thanks as always.
>Gene
>
Previous Topic: London studios in the 60s
Next Topic: 8 out cards
Goto Forum:
  


Current Time: Sun Mar 23 18:49:00 PDT 2025

Total time taken to generate the page: 0.01438 seconds