Namm '09

[Gribs]

I'll be there Glenn, and the Specs booth is already on my list! Already located on the floor map and centered in. Are you up for answering any questions at NAMM, a 'la reporter style?

See ya there!

Brent

Koolkeys, hi.
If you're there a 'la reporter style, ask Glenn if they're thinking of solving the Omnisphere issues many of their users are having.

Thanks.

Also, I don't know Prorec.com so I'll be checking that out since I always respect your comments on different issues.

Ditto.

[Gribs]

It's odd, I have both products and use both products on my modest system with 3GB of RAMM, and never run out of memory. It's likely I'm just a lucky one, but I don't see how they are taking so much RAM for people. RMX uses loops, and most of Omni's patches are a couple hundred megabytes. I don't think they need to be 64 bit to fix the problems, as I doubt either one is actually using up more than a couple hundred MB of memory. It's likely a deeper issue, just judging by the size of the libraries and presets.

Yeah, I think this is both a system and a DAW-dependent issue. I don't have any problems running multiple instances of Omnisphere in Cubase 4.5 in Windows XP Pro. I have 4 GB of RAM and I put the /3GB switch in my boot.ini file and no overclocking even though my mobo is built to handle that. My system is a home-built quad-core with very high quality components. It is also pretty clean with a minimum of junk running in the background and I work to keep it that way

Cubase 4 is multi-threaded and I can see all 4 processors chugging away at about 5%-8% when I have one instance of Omnisphere running. If I switch to a DAW that is not multi-threaded like Live 7 then I see one processor going at something like 20%-30% full. So there are DAW-dependencies as well as system dependencies. Less memory, slower memory, slower hard drive, smaller cache on your drive(s), smaller cache on your processor, slower processor, extra junk running in the background, not remembering to turn on the /3GB switch, clogged up registry filled with all sorts of junk from stuff that is no longer around, etc., etc. will all slow you down.

[Paul Russell]

Yeah, I think this is both a system and a DAW-dependent issue.

Yes it is. To run in SONAR x64 RMX and Omnisphere have to run through Bitbridge, and because they are time based as well as synths, this causes a problem. Midi editing slows down to a crawl - you move one note it takes 3 or 4 seconds to register. It also becomes very crash prone.

That would be fine if someone would be doing something about it. For example, Camel Space was giving me similar issues, so I dropped at line to Camel and to Cakewalk's CTO Noel Borthwick, and within a few days the issue was fixed in a maintenance relese of Camel Space.

Do the same thing with Spectrasonics and they can't be bothered to talk to Cakewalk to even check to see if it's easily resolvable. Oxford (Sonnox) had the same attitude.

Last year I spend more than $20K on samplers and upgrades, including Omnisphere. From now on no-one gets my dollar unless the new product is x64.

[duglmac]

Hi Glen - would be cool to meet you in person as I really respect your work on Crystal and Omnisphere, so I'll definitely stop by the Spectrasonics booth and see if you're about - would also be good to see Eric again. Camel Audio doesn't have a stand but I'll be there wandering about checking out stuff. Like Glenn, I also always like to meet users of our stuff, so if anyone sees me wandering about (in a Camel Audio T-shirt), do stop me and say hi.

What day will you be there? Maybe I'll look both of you up. I'm a big Camel Audio fan.

[Meffy]

I'm a big Camel Audio fan.

Don't know if you intended it or not, but your nickname spelt backward is "camlgud".