Hi – I ran my own little test w/a sample and Kuassa Creme (looks nice, great price), got about 10-12%. Unfortunately I have no other studio to compare to…
For the most part I’ve had no problems with cpu in Podium with regards to uis. I’ve had spikes in the past though, but not very often, just certain plugs. Shortcircuit is a monster, though, I tells ya. The main screen will boost cpu up between 20 and 30%, whereas the other screen is around 2-5. I’ve read that many people have a prob with this in various daws, so oh well. Don’t know what solution to offer there…
BUT, if denormalisation remains a big issue, then give this a go:
Just found out accidentally about it in a KVR forum about Uhbik, as I’ve been debating with myself about money I shouldn’t spend – But the normaliser above is free, so hey! Good luck.
ps I’ll try the Uhbik plugs in Podium tonight, as Urs said 1.2 might be having denormalisation issues. Also, will get a demo or two of other daws, run my own tests no?
I’ve been hearing about Sytrus for a while, but I just never got around to checking it out…got the demo now, thanks for the heads up there.
Today’s my day off, I’ll try working on a little something…
Aalto demo videos are available on You Tube…also, on Soundcloud: http://soundcloud.com/groups/aalto-users-group-madrona-labs
I’m a cheap bastard when it comes to acquiring new gear, and Aalto’s the only synth VST I’ll probably ever buy. I forget I’m working on a vst when using it. It’s based on the Buchla modular, but I found it very easy to get into. The arpeggiator’s the bees knees and it adds a whole new dimension to the sound. And of course it can be turned off. If you’re looking for a “normal” synth sound, it’s possible with this, but for me it’s made for pushing sounds to the limit. It is a one developer project too, and the programmer Randy Jones is super helpful and responsive. Try the demo, mate, experiment with the presets and tell me what you think. The possibilities are through the roof with this thing. And…it’s good buddies with Podium.
ps I think I’ll do an “only Aalto” track, submit to both Podium and Aalto Soundcloud groups…two birds, one stone! Good day-
Why that’s an awesome ditty there Levendis…I only got to hear it through my crappy netbook speakers but I could tell you had some nice density going on…will check out more properly later. I’ll try to be productive next week so I can add a little something. A great start for the group—-
EDIT: Have you tried Aalto? Something tells me you’d like it…audio alchemy supreme.
Thanks man! I’ll check it out…
You’re welcome Cymatic. Many don’t know about this as it’s so dusty and all, pity. I’m using it for live clip triggering, which takes a minute to set up as do some other functions, but of course can be saved as a template. I love Phrazor’s handling of presets with its own programs…I’ve had issues with creating presets from certain vsts inside Podium, but none if using the programs.
One more thing -you’d said demo; did you get it from Gersic or Sonicbytes? Gersic’s is the fully functional beta, only a few steps behind the one Sonicbytes has. Or should I say had, as it’s not even for sale anymore. But they still have the demo, weird!
As Flav would say “rock that shit homey”
Aye it is, more than likely because Frits is on vacation, for a few more days at least. Spam is like weeds in a garden that you have to tend to constantly, no matter how great the soil…or somethin’ like that. Until Frits returns we can survive off Spamburgers…..
Good info, thank you. Phrazor is another one…the last beta is freely available at Gersic: http://www.gersic.com/plugins/index.php?daPlug=1693
It’s been discontinued for 5 years but is still great. It’s a host that is also a VST, a mini Ableton-ish workstation thingy. The interface and concepts require a little study but it’s not rocket science. The free beta is fully functional, and there are tutorials you can run inside of it. If you can’t get the MIDI plug aspect of it just post and I’ll explain.
Did a surface test with both versions – everything seems fine. In 64 I ran 5 tracks of Aalto at 40% cpu, which is great as Aalto is normally a big hog.
Aargh, now that 3 is out I have to crash before the workweek begins. I’ll get around to it tomorrow – thanks Frits.
Calling it 3.0 is fine with me too. Good for publicity too!
So glad you got a new computer Frits. I thought I was in heaven when I bought my dual core computer last year with 4 gigs of RAM (I’ve never had a new one before). But an i7 w/16 gigs, wow. You deserve it!
I’m curious: what are the six packages? My limited brain can only conceive of a 32bit and a 64 bit.
ps And Kontakt 4, aw man….
+1 here, but as one of several options. I like what the Shortcircuit sampler did with path variables, if I may quote from the manual:
When a sample is first loaded into shortcircuit, the path and filename of the sample are stored for later reference. This is later used for session recall and when storing a group or multi (remember, shortcircuit never saves the samples, they are only referencedso they still need to be there next time around).
But before storing the path, it is compared with the user configurable path variables. If a part of the path matches one of the path variables, that part is replaced with the matching variable name. When the sample is loaded the next time, the path variable is replaced with the corresponding path again, giving the correct filename to the filesystem.
The purpose of this system is that if a directory containing samples are moved to another harddrive and/or directory, the path variable can be updated to match.
$path1 is set to “c:samples” in the shortcircuit configuration.
The sample c:samplessubdirsample.wav is loaded. Internally it is remembered as $path1subdirsample.wav
The dir c:samples is moved to d:samples. $path1 is updated to match.
The filename $path1subdirsample.wav will now load the sample d:samplessubdirsample.wav instead.
End quote. Would be good to have a few choices eh?
I compared my 2.42 with the x86 and x64 betas, in CPU. In all three, the Zeq stayed at 0%. The Zpitch was about 2% in all three. The Zreverb was a little different, hitting about 4% on 2.42, and 3-4% on the new x86 and x64, and 2% every so often. Opening the Zreverb GUI added about 2% in all three but the other plugs GUI made no difference.
They all run fine, so there ya go.
That’s great about the Zplugs – they were already decent on CPU to begin with. I tried looking up info on installer tools, but quickly learned that I don’t know what I’m doing. Good luck on all of it.