Subject:VSTi's not recalling patch in AP7

Posted by: Trim

Date:2/10/2009 2:14:38 AM

Hi Guy's
This ones totally perplexing me, hope someone can help.
Since AP4 I have been using a combination of audio and midi for my projects, the midi tracks feeding a variety of VSTi's, some free, some paid. Since trying AP7 I have found that after saving a project with VSTi's, when I open it again the instruments show up correctly in the Track List (including correct patch name!) and Mixer. BUT, the VSTi has defaulted back to patch 1, despite the fact that the correct patch is named in the Track List !!!, any idea whats going on ?. Of course the work around is to reselect my patches each time I open the project, but this is becoming a major pain, please help.

Subject:RE: VSTi's not recalling patch in AP7

Reply by: pwppch

Date:2/10/2009 8:25:08 AM

Can you give me an example of a specific VSTi (or two) that shows this behavior?

Thanks
Peter

Subject:RE: VSTi's not recalling patch in AP7

Reply by: davidottery

Date:6/28/2009 5:11:28 PM

high pch I am having same problem with acid music studio 7a
vsti's are
Oatmeal and Rez

also was having same problem with TAL bassline but is now working

regards david

Subject:RE: VSTi's not recalling patch in AP7

Reply by: pwppch

Date:6/28/2009 5:22:20 PM

Oatmeal and Rez

I don't know these. Who makes them and what versions are you using.

Could you provide me with a step by step description of exactly what you do, what happens, and what you expect to happen?

Peter

Subject:RE: VSTi's not recalling patch in AP7

Reply by: davidottery

Date:6/29/2009 12:43:39 AM

oatmeal is a free vsti made by fuzzpilz. after the vsti and midi channel is inserted, and the patch selected on the vsti, and i save the project, after shutting down acid and restarting it (say next day) the vsti has reverted to the first patch on its list instead of the one i was using for the track. The midi channel to which this vsti is inserted also reverts to the original sound/patch on its list. ie i use saw lead, but next time it shows a bass which is the first sound available on it. Oatmeal is freeware but is very well known and used widely
regards david.

Subject:RE: VSTi's not recalling patch in AP7

Reply by: pwppch

Date:6/29/2009 6:38:53 AM

We will take a look at it.

You didn't tell me who makes RAZ.

Peter

Subject:RE: VSTi's not recalling patch in AP7

Reply by: Bremen Cole

Date:6/29/2009 4:13:43 PM

Also, try the fix I give (and Peter gives one as well) in the Arp2600 thread below this one.....it might work....

Subject:RE: VSTi's not recalling patch in AP7

Reply by: Rockitglider

Date:6/29/2009 8:50:32 PM

Hello,

I'll bump in here, I have this problem with Halion 3, the selected program I load won't save with the project, I'll do some trials while you check the others, I'll load default patches and see if it's just the one I use that has the problem because there's no way for you to create it without owning NS kit7 unless you have it, let me know and I'll send you the config. I'll get back to this thread.

Thanks, Rockitglider

Subject:RE: VSTi's not recalling patch in AP7

Reply by: davidottery

Date:7/2/2009 7:05:06 AM

have the same problem with vsti
rez 2.0 by ugo audio

and also with vsti
analogue warefare 3.0 by angular momentum

will try the posted fixes
regards
david

Subject:RE: VSTi's not recalling patch in AP7

Reply by: Rockitglider

Date:7/2/2009 4:28:04 PM

Hello,

Mine started working even when I restart the computer. I have all my data on external drives on a laptop computer, maybe the drives would cause it to loose the wave data locations sometimes. The only vst that won't keep settings is EVE2 Full version, but it's probly not Acids fault. So I seem to be OK, sorry for the false alarm.

See ya, Rockitglider

Subject:RE: VSTi's not recalling patch in AP7

Reply by: Bremen Cole

Date:7/2/2009 9:01:06 PM

External USB drives can cause a bunch of problems, should be part of profile...... anyway...... As far as VSTi's and recalling patch issue.... I have the same thing with Tera 2. But the rest of the story is that for over 4 years now Tera 2 has not worked 100% with any host or host/computer combo. So, it's not a big deal to me that it screws up in Acid.....

These issues have made Tera 2 un-usable for me since I bought it, and is therefore the reason I have never "upgraded" to Tera 3. I mean why pay even more money for something that does not work?