This is my drop..........

Augur in the house

Host fruityloops 10

6 X augur vst

15 X augur sampled ( augur is a cpu eater )

Effect came from host

Reverb , delay , some compression , and limiter for the end mix


So enjoy and enjoy

a.k.a fabrizio

... which is in common with most plugins.

Arhh CRAP!!!

I started out on my project a few days ago and was up to 4 instances. All fine and dandy but......when I re-opened it this morning I got access violation constantly. After launching FL like 6 times I gave up. According to windows message popping up (like 5000 times every time I open the song)the problem has to do with activating the Auger.dll file but since it's rather essential I'm kinda drawing a blank here
Things worked fine a few days ago, and all my other tracks works flawlessly regardless what whatever plugin I've been using.
I HATE computers - somebody give me a Steinway!

Classical "Augural" behavior... if you work on Win7, try the compatibility mode.

I'm on Vista.

D'oh! is there something like the compatibility mode?

There is and according to this:
http://www.howtogeek.com/howto/windows-vista/using-windows-v ista-compatibility-mode/
...it shouldn't be that hard. However, it deals with .exe files and Augur is a dll and can't be launched outside a host.

In fact you run your host in compatibility mode (not the dll)... as a consequence, the host should recall the dll in the appropriate mode.

Interesting. I'll try that out then. I still wonder how it can work in "normal" mode so to speak - only to stop a few days later.

It happens also with a small amount of Augur instances (4 or 5 here). You work without any problem for a while, but once you reopen the project, it crashes with a bunch of access violations - regardless of the host, according to the posts in this thread.

Oh sorry, I didn't go through the entire thread.
Anyway, I wonder if the developer is aware of this. (don't tell me you already discussed that too? )

Anyway, never worry if a plugin doesn't work.

FL Studio has a nice feature (and i think mostly of the daws) which you can delete the problematic synth or vst from the folders, FL Studio will scan for it when you reopen the project, this time it won't find it (because you deleted it) but you can still have the structure of the track there, and you can open it without any error.
Just install it again until it goes good and the project can be opened.

And don't forget to use the options, the multicore thingy, etc in the process options tab in FL Studio wrapper.

Have a good day and good luck.

THANK YOU! Now my ambient pad doesn't sound flat or like it has nausea!

Didn't even try to contact the developer as this is an older plug and he has even dropped it without a mention from his site so seems little point.

Weird that a working project will not re-open, but at least the trick Irion mention should at least make it open where things can be copied to a new one etc.

But I wonder if this issue of not being able to open projects is helped by saving with all plugins in off-line mode?

And how about the old trick for early Synthedit synths to make copies of the dll and rename them?

Hi V'ger,

Are we allowed to use amp/cabinet simulators?