Prometheus VST Engine&Presets Update, Anomaly Fusion Edition

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

biodiode wrote:I hope if anyone else gets the same problem they will either post here or e-mail you direct. What would be helpful is if they post the app/daw that they are using for Prometheus as it may just be Cakewalk thing.

Adrian
Not just a Cakewalk thing. I'm using Acid Pro 6d here and had the same issue. I fixed it using your WINI edit.

Post

higain_guitar wrote:John, May I ask if Prometheus VST is based on Wusik 4.2.4 engine or an older build?
It's 4.2.4

Post

Can those of you who have the problem with the wIni files check the entries for the DATA folder on, say, the FX version of Prometheus as well?

The setting for the DATA folder in the wIni files that are in the instrument installer have that as blank, so it should ask you where your DATA folder is located and let you point to it.....

Post

dnekm wrote:Can those of you who have the problem with the wIni files check the entries for the DATA folder on, say, the FX version of Prometheus as well?

The setting for the DATA folder in the wIni files that are in the instrument installer have that as blank, so it should ask you where your DATA folder is located and let you point to it.....
Automatically points to Wusik DATA rather than prompting for Prometheus DATA as well.

Post

Looks like it's picking up the VST id in the system registry for Wusik instead of Prometheus. Sounds like a job for Super William :lol:
I invite you to 'voyage' over to https://adrianearnshaw.com, sign up for some fun e-mail 'blasts', and look forward to helping you launch your ears - and projects - into the stratosphere.

Post

John, are you planning to update one of the installers to address this issue? I want to know if I should wait before I burn my dvd-rs...

Thanks,
HG

Post

higain_guitar wrote:John, are you planning to update one of the installers to address this issue? I want to know if I should wait before I burn my dvd-rs...

Thanks,
HG
When we figure out what's going on, we'll deliver a fix, but I can't say when. So you do need to do your backup at once, in any case.

Everything works, it's just this one little spot of weirdness that is easily correctable by either editing the wIni files, or by copying the soundsets, presets and so on to your Wusikstation folder. I've heard from people who have done both, and are satisfied. So those are the things you can do now to use the instrument. Sorry about this unexpected development, but as VST install problems go, it's a small one.

This who are interested in Prometheus but are NOT Wusik users will not have this problem, as this will be your first installation of any WusikEngine DATA folder.

The investigation will continue, and a solution will be found. In the meantime, use either fix, and enjoy Prometheus.

Post

John, that's cool. I actually like editing ini files so its not a problem for me. I'll begin burning away.

Thanks again,
Robert

Post

Hmm, well I've run into a strange issue.

In the Presets\Synths 2 menu is a preset called LED-Disturbed Lead-dk. If I load this preset, play it, and then load the one above it, Breathing Lead, my host crashes. If I load Disturbed Lead and then switch to any other preset, everythings fine. If I load Breathing Lead and then Disturbed Lead, everything's fine. When I load Disturbed Lead, play a note, and then switch to Breathing Lead...CRASH! I've tested this repeatedly and it happens every time.

This happen to anyone else? It might just be random weirdness on my system.

Post

RJ Fielder wrote:Hmm, well I've run into a strange issue.

In the Presets\Synths 2 menu is a preset called LED-Disturbed Lead-dk. If I load this preset, play it, and then load the one above it, Breathing Lead, my host crashes. If I load Disturbed Lead and then switch to any other preset, everythings fine. If I load Breathing Lead and then Disturbed Lead, everything's fine. When I load Disturbed Lead, play a note, and then switch to Breathing Lead...CRASH! I've tested this repeatedly and it happens every time.

This happen to anyone else? It might just be random weirdness on my system.
Confirmed, in Chainer and Cantabile Lite. Observations so far: despite the fact that many other presets use similar settings of the glide function, when you combine those two soundsets, Baliwood and Xenolith with glide, you get a crash. (I created such a patch from the Init preset, and got the same crash after dialing in glide.) No other patches using glide in this set crash. No other patch I listened to just now using either of those soundsets, but not glide, crash. Life is filled with mysteries.

What a weird and embarrassing bug. Sorry about this. When we get a fix, we'll post it. For now, like the joke goes, if it hurts when you go like that, don't go like that.

Post

I just confirmed this in energyXT..... It crashes going up from Disturbed Lead to Breathing Lead, but not going down from Breathing Lead to Disturbed Lead, which is why I did not find this when making the Library files.... :D

Here is a fix:

CrashAvoidance.zip

Unzip and insert this preset - LED-Crash Avoidance Lead-dk in the Synths 2 preset folder.

This preset also uses the two new custom dBu FX that are in Prometheus....

Post

dnekm wrote:I just confirmed this in energyXT..... It crashes going up from Disturbed Lead to Breathing Lead, but not going down from Breathing Lead to Disturbed Lead, which is why I did not find this when making the Library files.... :D

Here is a fix:

CrashAvoidance.zip

Unzip and insert this preset - LED-Crash Avoidance Lead-dk in the Synths 2 preset folder.

This preset also uses the two new custom dBu FX that are in Prometheus....
That's a pretty neat sounding new preset there. Unfortunately, it only magnified the issues on my setup. If I play a note using Crash Avoidance and then try to switch to anything else...CRASH. If I play a note using Breathing or Disturbed Lead and switch to Crash Avoidance...hang then CRASH. And now when I try to play any of the three trouble makers occasionally the note will stick and hang my host. I don't know if theres a problem with my system or something else now...

EDIT: Well I seem to have come up with a solution for my setup. I simply moved the Breathing Lead into the Synths 1 folder and removed Crash Avoidance all together. Now everything seems to work fine and dandy (though I still encounter the occasional, non-reproducable crash when playing and switching between the LEDs in Synth 2) I don't know what to do with the Crash Avoidance Lead as no matter where I put it it becomes the Crash Un-Avoidance Lead. Too bad, cuz its a groovy preset.

Post

Try downloading the file above again, I have added another preset to it....

Place the Crash Avoidance and Creeping Shadows presets in your Synths 2 preset folder.

I've been able to switch between the 4 - Breathing Lead, Crash Avoidance, Creeping Shadows and Disturbed Lead - moving up and down with no issues.....

Post

William and I are sorting out the DATA folder thing. It seems that all Wusikngine instruments are meant to share the same DATA path. This may change. However, unless William syas otherwise, please do use the manual wIni file edit to set your Prometheus DATA folder path. Again, this is a non-issue for non-Wusikusers.

We will be addressing the issue of crashing presets shortly.

Thanks for your patience and thanks for being Prometheus users. There's a lot of great music in this fire-stealer.

Post

As I feared one of the big files I downloaded was downloaded improperly and I got this error message during the installation:

"...\Pad114.WusikSND
An error occurred while trying to copy a file.
The source file is corrupted.

Click Retry to try again, Ignore to skip this file (not recommended), or Abort to cancel installation."

It turns out the problem was "DB_PrometheusA-1c.bin".

As I mentioned in an earlier post, if we were given sfv or .md5 files, I would have known days ago that the file I downloaded had the wrong checksum and I could have redownloaded it. Instead, I had to download 9 files (2.11 gigabytes of data) to figure out which one was corrupt.

I am not angry, but it would be nice to have .md5 or .sfv files since they are so small and convenient and free: http://www.quicksfv.org/

For anyone who might have the same problem here are the correct checksums for "A" of prometheus:

DB_PrometheusA-1a.bin 7E07256F
DB_PrometheusA-1b.bin 49782680
DB_PrometheusA-1c.bin D43382B6
DB_PrometheusA-1d.bin F80FAB51
DB_PrometheusA-1e.bin 32E5B127
DB_PrometheusA-1f.bin AA3E9D97
DB_PrometheusA-1g.bin 62D44464
DB_PrometheusA-1h.bin 6797294D
DB_PrometheusA-1i.bin 36BEF2FF
DB_PrometheusA.exe 3A34EEBE
DB_PrometheusDATA.exe AB1E70C3
DB_PrometheusInstrument.exe 29CBAA02

Post Reply

Return to “Instruments”