VST conflicts; VSTs not performing as required

kazai_shadow

This is my first time here as a poster, so hello I guess.

Anyway, I've been making a track in Acid Pro 6.0 that uses 4 VSTs at current.
These are:
iTCHY's RESONANCE - Own preset
iTCHY's PUNCH - SPOOKY preset
iTCHY's SUBBSONIC - modification of SUBBTOTAL preset
and last but not least, Edirol HQ-OR

All seems to be well, but if the loop using PUNCH is playing at the same time as the loop using Edirol, the loop with PUNCH will perform rather strangely. Instead of playing its usual eerie note, It plays a malformed version of it. Sometimes PUNCH will even keel over and die, showing +inf on both of the mixer's L and R side, and, afaik, can only be fixed by clicking the "Synth FX..." button.

Similarly, but not so bad, if I play the loop with RESONANCE at the same time as Edirol, one of the notes played is played much louder than the other notes. The same note each time, ironically.

The SUBBSONIC VST doesn't seem to malfunction.

Until now, these issues never showed up in the final render to MP3 originally, but after adding more it has now shown up in the render too.

I've tried a few things, such as increasing the buffer amount, changing it to Direct X but this has resulted in nothing. There's something wrong with the VSTs.

Can anyone provide any knowledge on this and perhaps a solution?

Neurojazz

Sometimes with VST glitches like this you can have a work around (assuming that this isn't another bug caused by something you added later)

Save the preset of the glitched VST, copy the midi data/audio data to another track that has no VSTs, delete that dodgy track, the vst from in the daw and save.

Restart the the DAW and load that track, see if bug appears somewhere else and if not then add the vst back into the track you copied the midi/audio data, apply the preset you saved off and start it again.

Give us some feedback after that.

Sometimes projects can go badly wrong, sometimes the VSTs themselves have coding problems when addressing memory or conflict with 64bit systems - the list is endless, if you are lucky there maybe a way to reset your daw and clean out that side also - but may have to put a support ticket in should this behavior continue.

kazai_shadow

Neurojazz wrote: »

Sometimes with VST glitches like this you can have a work around (assuming that this isn't another bug caused by something you added later)

Save the preset of the glitched VST, copy the midi data/audio data to another track that has no VSTs, delete that dodgy track, the vst from in the daw and save.

Restart the the DAW and load that track, see if bug appears somewhere else and if not then add the vst back into the track you copied the midi/audio data, apply the preset you saved off and start it again.

Give us some feedback after that.

I managed to get it work using a variant of your technique. I exported the PUNCH and RESONANCE loops to .wav files then brought them back as beatmapped files to use as whole tracks. I had to do this with PUNCH because it has some nasty delays on it that would've sounded awful if cut into a loop.

I soon discovered I didn't like the PUNCH loop with Edirol, so I've taken it out anyway.
But what I did do was create 1 loop of the RESONANCE, exported it and brought it back in as a loop which fixed the loud note issue, and could be played properly as a loop. I would of used your method, but the LFO for the VST performed differently in a new project for some reason

anyway, thanks for replying I'll keep this in mind if it happens again.