The PARIS Forums


Home » The PARIS Forums » PARIS: Main » Paris vst/dx plugins problems and solutions !
Paris vst/dx plugins problems and solutions ! [message #99371] Fri, 27 June 2008 12:32 Go to next message
Dimitrios is currently offline  Dimitrios   
Messages: 1056
Registered: August 2005
Senior Member
Ok based to many real word tests (like mixing records...) Paris does not like
much the DX plugins.
I don't know if this is related to DX 9 but anyway there are many unhandled
exceptions occuring.

Vst's are working smoother with Paris.
Now for Waves users while many DX versions of waves cause these unhandled
exception if you will use the VST versions of waves with Paris then this
will be a life saver.
You will need for these the shell2vst.exe which is a free little app that
can extract from waves waveshells their related plugins.
Chainer is a must have as thru it waves vst (by using this shell2vst.exe)
works smooth !
Chainer does not see the waveshells directly as other chainers too.

Now API plugins do mot show thru Chainer as vst because the gui cannot load
at all.

The only way to see API vst plugins inside paris (not the DX) is by using
the free multifxvst chainer ONLY from inside chainer because Paris will crash
if you try to load multifxvst directly !

So to summarize till now.

Get chainer !!
Get shell2vst.exe (free)if you have wave plugins , get multifxvst (free)
if you have api plugins.

DISABLE DX for Paris from Paris cfg.
To use some essntial DX plugins needed like autotune !! use the FREE FFX4
chainer which will be seen from Paris as vst but will load from itself DX
plugins (no vst here)
Also FFX4 does NOT se mono DX plugins.

NOW if you wanna use the SSL waves AGAIN Chainer cannot openm the SSL gui.
To use the waves SSL you can use the Effectchainer which is a free chainer
using VST and DX !
Now why not use this for all plugins ?
Well you could if you would use only VST plugins, DX causes problems still
due to Paris handling DX.
Effectchainer CANNOT load the API gui at all too.
so multifxvst is needed again.

AGAIN shell2vst is needed to extract waves as usable vst plugins.

Anyway my consumptions are that DX a no no , use vst instead.

To complete my tests I will use the old vdx33 dx chainer but why use vst
plugins seen as DX when you can use directly vst plugins ??

Make a directory only seen by Paris named like Parisvst and put inside ONLY
, chainer , effectchainer, Faderworks, FFX4.

All your other vst plugins can be put in a directory named VST.
Let chainer and/or effectchainer see that directory only.

Disable DX as to have a clean drop down DX/vst Paris menu.

This for now.
Regards,
Dimitrios
Re: Paris vst/dx plugins problems and solutions ! [message #99372 is a reply to message #99371] Fri, 27 June 2008 13:32 Go to previous messageGo to next message
Dimitrios is currently offline  Dimitrios   
Messages: 1056
Registered: August 2005
Senior Member
OK,
Some corrections.
Multifxvst DOES NOT WORK with mono plugins versions and 24bit !
So don't use this.

effectchainer which is free will load the SSL waves VST just fine.

API as vst is a no no.

So use the shell2vst.exe to extract vst plugins from all waves waveshells
and use the free effectschainer (ONLY from VST menu !) the vst waves.

There is NONE unhandled exception from using VST plugins with Paris

regards,
Dimitrios

"Dimitrios" <musurgio@otenetNOSPAM.gr> wrote:
>
>Ok based to many real word tests (like mixing records...) Paris does not
like
>much the DX plugins.
>I don't know if this is related to DX 9 but anyway there are many unhandled
>exceptions occuring.
>
>Vst's are working smoother with Paris.
>Now for Waves users while many DX versions of waves cause these unhandled
>exception if you will use the VST versions of waves with Paris then this
>will be a life saver.
>You will need for these the shell2vst.exe which is a free little app that
>can extract from waves waveshells their related plugins.
>Chainer is a must have as thru it waves vst (by using this shell2vst.exe)
>works smooth !
>Chainer does not see the waveshells directly as other chainers too.
>
>Now API plugins do mot show thru Chainer as vst because the gui cannot load
>at all.
>
>The only way to see API vst plugins inside paris (not the DX) is by using
>the free multifxvst chainer ONLY from inside chainer because Paris will
crash
>if you try to load multifxvst directly !
>
>So to summarize till now.
>
>Get chainer !!
>Get shell2vst.exe (free)if you have wave plugins , get multifxvst (free)
>if you have api plugins.
>
>DISABLE DX for Paris from Paris cfg.
>To use some essntial DX plugins needed like autotune !! use the FREE FFX4
>chainer which will be seen from Paris as vst but will load from itself DX
>plugins (no vst here)
>Also FFX4 does NOT se mono DX plugins.
>
>NOW if you wanna use the SSL waves AGAIN Chainer cannot openm the SSL gui.
>To use the waves SSL you can use the Effectchainer which is a free chainer
>using VST and DX !
>Now why not use this for all plugins ?
>Well you could if you would use only VST plugins, DX causes problems still
>due to Paris handling DX.
>Effectchainer CANNOT load the API gui at all too.
>so multifxvst is needed again.
>
>AGAIN shell2vst is needed to extract waves as usable vst plugins.
>
>Anyway my consumptions are that DX a no no , use vst instead.
>
>To complete my tests I will use the old vdx33 dx chainer but why use vst
>plugins seen as DX when you can use directly vst plugins ??
>
>Make a directory only seen by Paris named like Parisvst and put inside ONLY
>, chainer , effectchainer, Faderworks, FFX4.
>
>All your other vst plugins can be put in a directory named VST.
>Let chainer and/or effectchainer see that directory only.
>
>Disable DX as to have a clean drop down DX/vst Paris menu.
>
>This for now.
>Regards,
>Dimitrios
Re: Paris vst/dx plugins problems and solutions ! [message #99373 is a reply to message #99372] Fri, 27 June 2008 15:11 Go to previous message
Don Nafe is currently offline  Don Nafe   CANADA
Messages: 1206
Registered: July 2005
Senior Member
As always thanks for the heads up




"Dimitrios" <xxxx@otenet.gr> wrote in message news:48654e4c$1@linux...
>
> OK,
> Some corrections.
> Multifxvst DOES NOT WORK with mono plugins versions and 24bit !
> So don't use this.
>
> effectchainer which is free will load the SSL waves VST just fine.
>
> API as vst is a no no.
>
> So use the shell2vst.exe to extract vst plugins from all waves waveshells
> and use the free effectschainer (ONLY from VST menu !) the vst waves.
>
> There is NONE unhandled exception from using VST plugins with Paris
>
> regards,
> Dimitrios
>
> "Dimitrios" <musurgio@otenetNOSPAM.gr> wrote:
>>
>>Ok based to many real word tests (like mixing records...) Paris does not
> like
>>much the DX plugins.
>>I don't know if this is related to DX 9 but anyway there are many
>>unhandled
>>exceptions occuring.
>>
>>Vst's are working smoother with Paris.
>>Now for Waves users while many DX versions of waves cause these unhandled
>>exception if you will use the VST versions of waves with Paris then this
>>will be a life saver.
>>You will need for these the shell2vst.exe which is a free little app that
>>can extract from waves waveshells their related plugins.
>>Chainer is a must have as thru it waves vst (by using this shell2vst.exe)
>>works smooth !
>>Chainer does not see the waveshells directly as other chainers too.
>>
>>Now API plugins do mot show thru Chainer as vst because the gui cannot
>>load
>>at all.
>>
>>The only way to see API vst plugins inside paris (not the DX) is by using
>>the free multifxvst chainer ONLY from inside chainer because Paris will
> crash
>>if you try to load multifxvst directly !
>>
>>So to summarize till now.
>>
>>Get chainer !!
>>Get shell2vst.exe (free)if you have wave plugins , get multifxvst (free)
>>if you have api plugins.
>>
>>DISABLE DX for Paris from Paris cfg.
>>To use some essntial DX plugins needed like autotune !! use the FREE FFX4
>>chainer which will be seen from Paris as vst but will load from itself DX
>>plugins (no vst here)
>>Also FFX4 does NOT se mono DX plugins.
>>
>>NOW if you wanna use the SSL waves AGAIN Chainer cannot openm the SSL
>>gui.
>>To use the waves SSL you can use the Effectchainer which is a free chainer
>>using VST and DX !
>>Now why not use this for all plugins ?
>>Well you could if you would use only VST plugins, DX causes problems still
>>due to Paris handling DX.
>>Effectchainer CANNOT load the API gui at all too.
>>so multifxvst is needed again.
>>
>>AGAIN shell2vst is needed to extract waves as usable vst plugins.
>>
>>Anyway my consumptions are that DX a no no , use vst instead.
>>
>>To complete my tests I will use the old vdx33 dx chainer but why use vst
>>plugins seen as DX when you can use directly vst plugins ??
>>
>>Make a directory only seen by Paris named like Parisvst and put inside
>>ONLY
>>, chainer , effectchainer, Faderworks, FFX4.
>>
>>All your other vst plugins can be put in a directory named VST.
>>Let chainer and/or effectchainer see that directory only.
>>
>>Disable DX as to have a clean drop down DX/vst Paris menu.
>>
>>This for now.
>>Regards,
>>Dimitrios
>
Previous Topic: Need some help with Paris stops when heavy graphics plugins !!
Next Topic: ALIVERB 6
Goto Forum:
  


Current Time: Sat Apr 20 03:46:49 PDT 2024

Total time taken to generate the page: 0.01520 seconds