Hi,

I'm testing lastest Omnisphere 2 version 2.3.2h, from PC Windows 7 (x64).

No problem during patch & "challenge/response" operations (R2R patch/kg).

But everytime I use this menu : UTILITY / MIDI Learn and Automation / Show Current Assignments
any DAW I'm using always crashes (REAPER 5.35, Live 9.7.1 Suite, Studio One 3 v3.3.4 - all 64-bit)

DAW crash type are always "BEX64", involving "Omnisphere.dll" module...

I don't know if I'm alone to have this issue.
If not: I don't know if these crashes also occur from legit Omnisphere version.

Thanks in advance for your reports.

 

FL studio 12.4/Live 9.7, Win10x64 no issues here

 

Thank you for your report, I don't know exactly what's happen on my config. Are you using from legit Omnisphere 2?

EDIT: I have tested on another (sandbox) Windows 7 Pro SP1 x64 OS and it works (generated "MidiLearnReport.html" and displayed in FireFox, without crash - from REAPER). BTW something is wrong from my "regular" Windows 7.

 

Last edited: Mar 21, 2017

Studio One 3 v. 3.3.4 (43933) WIN 8.1 x64
Works fine (with R2R Patch / Keygen)
Of course you must start Studio One with administrator rights!

I also have legit Omnisphere on seperate PC, there funtioniert it also

 

Was it stable with a previous version of Omnisphere?

When you say something is wrong with your W7, what do you mean? If its Omnisphare that always crashes it must be a problem with Omnisphere. Unless it is the only plugin you use.

 

My Windows account is as administrator, disabled UAC. I've tried to use "Run as administrator" (was set from shortcut properties for all DAWs) but having same issue when using this menu especially.

I don't have tested with previous Omnisphere 2 versions (I've trashed previous .dlls). Lastest Omnisphere 2 v2.3.2h (64-bit VSTi) seems stable during usage, except from "UTILITY MIDI Learn and Automation / Show Current Assignments" menu (for my main Win7 OS only), instead of displaying current CC assigments in separate "webpage" (from Firefox) the DAW crashes instead. Not occur when doing this from another Win7 OS (sandbox OS) on same physical PC.

This menu works fine on sandbox Windows 7, but causing crashes from my regular Windows 7 (all Windows 7 Pro SP1 64-bit).

I'm using other plugins (both VST & VST3, always 64-bit) - some are legit (Avenger, DUNE 2 etc), some other else are warez (like XILS or FabFilter) - but without any problem, from mentioned DAWs (always 64-bit). Only VST from Ableton because this DAW doesn't support VST3 plugins.

 

Last edited: Mar 21, 2017

Cracked. Try using another browser as default.

 

Thank you for a thorough answer MozartEstLa. Gosh, there are so many things that could go wrong with the OS and software configurations vary wildly. It's hard to pinpoint the problem when you might be using programs in the background I'm not familiar with. It might be one of these programs, or maybe it could be a different version of MS Visual C++ that crashes Omnisphere. Try comparing the systems, the one within VM and your normal W7. What is different? Pay attention to background processes and Visual C++ runtimes. Maybe some MS update screwed your main OS? None of the systems I assemble go online and are being updated. These updates are only useful for online computers anyway. There's like one in a hundred Microsoft update that fixes an important feature for audio.

 

@SineWave thank you too, of course they're obviously some differences between two systems I'm using. Also I precise my "sandbox" Windows 7 is a real Windows 7 - I mean, booting from separate physical HDD - not inside a virtual machine (VM) such VMware or VirtualBox. Of course this sandbox OS is clean (minimal installation such required drivers and ASIO driver) and it can be easily restored by using Acronis TrueImage.

About Omnisphere 2 it's not a drama because I don't use it as regular instrument, but this is only for testing purposes (and nothing else) simply I'm curious and I like to experiment/test (I assume I've enough legit and freeware plugins/softwares - all are described in my Profile > Personal details). Of course, MSVC++ runtimes (installed) versions may be the culprit (VC++ is a nice can of worms, you're right). Another tip I can use is another default browser such Chrome, as suggested by jkst above (thanks). The mysteries of computer science...

 

Sorry if this is going off topic, but where did you find the new update?

 

From "sister" website - I not sure it's allowed to give links (or site name) here, sorry.

 

Well seems I got lucky
Now, I have another problem which might pertain to the topic. Mine is crashing whenever I paste the response code instead.

 

I've seen that same issue around here recently. Can't remember what the solution was though. Try the search function. There was seriously a thread about this like a week ago so hopefully you'll get an answer pretty easily.

 

Thanks man. At least now I know its not the update, because I tried downgrading to 2.3.1 and I still had this issue :/

Edit: Couldn't find the thread

 

Last edited: Mar 26, 2017

Sounds like it's DEP or VC redist related? Try reinstalling them? Worked fine for me on all the DAWs u tried, as well as Cubendo.

The solution is apparently to keep restarting VSTi & paste the same response until it works. It can take a few tries, I rememeber it took about 5 times before it accepted it for me, beards ago...

 

I've probably done it around 30 times now...still keeps crashing...

Edit: Doesn't crash when I paste something that isn't the response code, but it does with the actual response code

 

Last edited: Mar 27, 2017

It prolly shouldn't matter, but are u sure u patched all versions of Omnisphere? There's sometimes plugs installed in programdata/spectrasonics for example. Even though it's unlikely they're scanned. Also check which dirs ur DAW scans, maybe u forgot one / mixup x64/x86 / only patched x86 while trying to reg x64 / whatev? I think there were issues registering w/ one DAW (FL i think) so maybe try registering it w/ another? Keygen does work. Eventually! I would also make sure u c/p the same code each time...

 

Last edited: Mar 27, 2017

As I've indicated above, for me it's not critical because I don't use Omnisphere 2 as regular instrument (not in my arsenal), it's only for testing purposes, and nothing else. BTW I don't worry about this very specific issue - and maybe it will help Spectrasonics developers if they're reading this topic for future enhancements/fixes. Probably an updated library/runtime is the culprit, such .NET Framework 4.x or one (of ton) of installed VCREDIST...

@Cav Emp: thank you very much for your report about your legit Omnisphere 2 and Windows 10.