News:

Version 1.20 is ready to download

Main Menu

Strange behaviour VaSynth

Started by garciarob, July 25, 2020, 10:29:18 AM

Previous topic - Next topic

garciarob

Hi,
can you help me with this strange behavior?

I had installed Halion on the VST 10 and occasionally saved the "startup config" both as a bank and preset.
At some point I started having a "vasynth error" when loading varranger.

To be able to use again the program I worked on the file vArranger2.ini and
I have deleted the data in the fields
VST10=
VSTControl10=
VSTControlInvert10=
VSTControlSwitch10=
VSTFX1_10=0
VSTFX2_10=0
VSTFX3_10=0
VSTChl10=
VSTTopMost10=

So Varranger started correctly without Halion.


At this point I tried to load halion back on the VST10. I went out, started varranger again and continued to have vaSynth blocking error.

I deleted the reference to halion again on the varranger.ini fields and tried to load halion on the VST11. So I had no more errors, even exiting and reopening vArranger.


So it would seem that, despite removing the data from vArranger.ini, the VST10 "keeps in memory" something related to Halion's old configuration (default saves?).

How can I solve it?

(Halion standalone doesn't give any kind of problem)

claudio

@Garciarob

Try to reinstall vArrangerSynth.

Can be by deleting in the Sounds / VSTPRESETS folder the file (s) VST10 ....... FXP which correspond to the installation of VST Halion.  :)

Claudio

garciarob

Hi Claudio,
problem solved!

Thanks a lot for your help!

(I had really old files there...  ;D )