KVR Audio

Zero dB · Post by **Zero dB** » Wed Sep 24, 2008 12:27 am

I definitely agree that the patch browser could do with better categorization. It's all very well having the cool funky names and categories but ideally we also need need simple categorizations such as lead, bass, pad etc. I know we use the search box but frankly it doesn't feel creative to be typing into a search box when browsing for sounds - feels a bit too like Google!

Also agree about the interrupting patch load pop-up. Very annoying. That's surely got to go.

I've asked this before and go no response - where are the keyboard shortcuts? Ideally you want these for everything in the synth but absolutely essential for previous and next patch. Seems a major oversight no? I've had no luck whatever getting previous and next patch to work with my MIDI controller either. Anyone had any joy with that?

Cheers

ZdB

iaminsane+ · Post by **iaminsane+** » Wed Sep 24, 2008 6:10 am

Zero dB wrote: Also agree about the interrupting patch load pop-up. Very annoying. That's surely got to go.

Yes please. Throwing a modal dialog box up like this is bad form! How many hundreds or more likely thousands of times will I end having to click this dialog over the next few years? PLEASE remove it!

I had two crashes in the first hour of usage, and none in the last 12-15 hours. I don't know. Seems fairly stable.

Takes 20-30 seconds to load on a quad q6600. That is tolerable, but I find the lazy response within the sound browser to be very annoying. Load times of some big patches can be long. I can live with that, but heaven forbid I click another sound while this is happening and up comes that dialog box (please remove this)

So my biggest beefs with it's performance and behavior is the slow response while browsing, and the pop up dialog. I can live with the rest.

Zero dB wrote: I definitely agree that the patch browser could do with better categorization. It's all very well having the cool funky names and categories but ideally we also need need simple categorizations such as lead, bass, pad etc. I know we use the search box but frankly it doesn't feel creative to be typing into a search box when browsing for sounds - feels a bit too like Google!

The categorization isn't working well for me either, I like NI's browser MUCH MUCH better. I don't get the search box, it seems normal windows conventions are kinda set aside at times, which results in a confusing experience. Am I looking at sounds found by the search? did the search work? how to I remove the search filter? I dunno...

There is some really cool stuff it it, and I trust Spectrasonics will iron out some of the kinks. Frankly, I am opening omnisphere less and less and am going back to my NI stuff (absynth, massive, reaktor, and pro53) cause I know where stuff is, and I'm not getting quick, predictable results out of omnisphere...

aaastronomer · Post by **aaastronomer** » Fri Oct 10, 2008 7:31 pm

krraqk wrote:
aaastronomer wrote:for those of you currently using omnisphere, are you using it with less than the specified 2GB of RAM? any problems?
Hi
Im not want to be rude, but I cant understand your question (which I think I have seen in some other omni thread).

If you are thinking about to purchase a $500 piece of software would not make much more sense to purchase an additional 1 gb of ram which is only $20 and be in the safe side???

Maybe you can run it but its very much obvious that with that limited ram you will get in to trouble with Omni or with many others softsynths very easily.

Dont you think?

eMachine 6811 has a max ram capacity of 1.25GB!

FrankT · Post by **FrankT** » Fri Oct 10, 2008 9:23 pm

phatty wrote:god i hate the ram limitation in XP.

So true. This limitation totally sucks. But XP will stay around quite a while. The more I think VSTs with large sample libraries need to offer a function that allows for purging loaded samples. I've tried a generic Windows tool to free RAM, but that is not the same as dedicated purging (as e.g. is offered in Kontakt).

Zero dB · Post by **Zero dB** » Fri Oct 10, 2008 10:37 pm

XP here with 4GB of RAM installed (yeah I know, XP can't see it all...)

Is anyone else getting quite frequent "out of memory" errors in Omnisphere? I'm generally getting this if I try to run, say, around three instances of the plug in a project. I'd have thought this shouldn't be too taxing but maybe I'm wrong?

Also getting very frustrated by the slow load times which make you feel like your DAW has frozen, even when just re-opening the plug-in window

IMO, Spectrasonics really need to look at getting this thing running significantly smoother.

Using REAPER here, FWIW.

Cheers guys.

ZdB

Zero dB · Post by **Zero dB** » Fri Oct 10, 2008 11:33 pm

A quick update to this - I'm concluding that Omnisphere actually has a memory leak. Problems occur after flicking through a few patches in succession - obviously it's loading samples into RAM each time - and it doesn't seem to be unloading them. So, RAM use just creeping up and then things start grinding to a halt.

I've read a few posts on other forums that have alluded to this too. Does anyone know if Spectrasonics have acknowledged this problem?

zerocrossing · Post by **zerocrossing** » Mon Jan 05, 2009 7:57 pm

Hey,

I'm running the latest version of Omnisphere but last night I can't seem to make it respond to afterouch even in patches that previously had been working. Changing modulation sources didn't work. Adding new ones didn't either. I'm in Live using v 7.0.7 on XP with a Novation Remote 25sl. All my other instruments, including Atmosphere, seem to be working fine with aftertouch.

Zero dB · Post by **Zero dB** » Mon Jan 05, 2009 8:31 pm

zerocrossing - I don't know much about aftertouch I'm afraid. But I'd love someone to answer my question above on RAM problems. I've been avoiding using Omnisphere for a while now as I'm finding it way to slow, unweildy and crash prone.

There's not been an update for a good while, right?

Eric if you're reading this I'd love to hear your thoughts if you get a moment...

Thanks

ZdB

GlennO · Post by **GlennO** » Mon Jan 05, 2009 8:35 pm

Zero dB wrote: There's not been an update for a good while, right?

Yes, there has been an update since you posted that: Version 1.0.2. We're not aware of any problems, but if you believe you've found a problem in 1.0.2, please contact tech support for assistance. Thanks.

- Glenn

zerocrossing · Post by **zerocrossing** » Mon Jan 05, 2009 8:50 pm

Zero dB wrote:But I'd love someone to answer my question above on RAM problems.

I've not experienced any RAM issues, but it could be because I've got a healthy amount of ram on my system and I don't notice it. Have you tried customer support? I'm a little angry that you have to put in your serial number to utilize any support. I don't often have my software serial numbers with me when it's easy to access customer service. I guess I need to put it in my phone and put in a service request tomorrow.

Zero dB · Post by **Zero dB** » Mon Jan 05, 2009 9:03 pm

GlennO wrote:
Zero dB wrote: There's not been an update for a good while, right?
Yes, there has been an update since you posted that: Version 1.0.2. We're not aware of any problems, but if you believe you've found a problem in 1.0.2, please contact tech support for assistance. Thanks.

- Glenn

Thanks for the speedy reply Glenn.

Yes I am running 1.0.2 on XP on a Q6600 box with 4GB; there's no shortage of horsepower, zerocrossing

DAW is REAPER.

I get frequent "out of memory" problems when browsing through patches. Further investigation seems to show that Omnisphere is creating a memory leak and the more patches I browse, the more memory it eats up. Obviously with multiple instances this gets bad, fast.

It's interesting that you say you're unaware of this problem as I've read numerous posts outlining the same issue on the Northernsounds forum. Because of this I assumed you were on the case and an update addressing it was imminent.

Seems to be all PC users with the problem - not wanting to make accusations I do get the feeling that in-house you guys are much more Mac orientated! I have no doubt you do beta on PCs, but it does seem to be that Macs get more attention?

I'll copy and paste this to tech support too.

Thanks

Ben

Zero dB · Post by **Zero dB** » Mon Jan 05, 2009 9:06 pm

GlennO wrote:
Zero dB wrote: There's not been an update for a good while, right?
Yes, there has been an update since you posted that: Version 1.0.2. We're not aware of any problems, but if you believe you've found a problem in 1.0.2, please contact tech support for assistance. Thanks.

- Glenn

Btw, it seems there's no mechanism in place informing users of update releases? I only found out about this update by chance, from a forum - you surely can't expect users to discover your updates this way? I thought there would be an email notification - this would be sensible!

ZdB

Zero dB · Post by **Zero dB** » Mon Jan 05, 2009 9:09 pm

While I'm on a roll (sorry) I still find it very bizarre and frustrating that as far as I know there's still no PDF manual. Having no printed manual is one - annoying - thing but on such an expensive VSTi I really expected a decent and comprehensive PDF.

The initial HTML manual was something of a joke and I know this has been recently updated - I'll check it out. But, really, that's not a convenient format and you should at the very least turn this into a PDF if you haven't already.

Thanks

ZdB

GlennO · Post by **GlennO** » Mon Jan 05, 2009 9:21 pm

Omnisphere includes an automatic update checker. Just click on the logo to go to the credits page and click on "Check for Updates". It will show your update status for software, patches, and soundsources.

- Glenn

CypherOne · Post by **CypherOne** » Mon Jan 05, 2009 9:25 pm

I haven't had any problems at all since I stopped trying to use Omni...

Omnisphere - Post purchase Questions, Issues, Problems