michi_maklatest cpu shoot out :
1 wav file played in loop with 1 vst effect ( KUASSA Creme )
Zynewave : avg 18%
energyXT : avg 9%
REAPER : avg 2%
EDIT :
Studio One Pro : avg 11%
Live Lite 8 : avg 12%
i rest my case …
michi_makdid some further testing : it seems to be related to 2 circumstances
1) i get cpu spikes when using a synthedit plug in ( no matter which preset or dialed in sound ) – the only one i have tbh
2) sometimes Podium spikes AFTER i replaced effect plugins for a while
the general question is still : why does a single core host like energyXT not eat up that much cpu with the same project? when compared to other multi core supporting hosts it gets even worse for Podium…
michi_mak@frollo9386 wrote:
in my experience podium handle cpu very well… so maybe it’s something related to specific vsti issue… worth the effort to check out.
the exact same midi files played by the exact same presets of the exact same plug ins and a wav file take up much less cpu in other hosts ( according to Windows Task Manager as kind of judge ) than in Podium – the cpu spikes are just a “side” note…
michi_mak@Zynewave wrote:
What hosts?
: energyXT ( not multicore enabled ), Live Lite 8, Reaper 4
@Zynewave wrote:
You could try to pinpoint which plugin causes the high CPU usage. Bypass/remove your plugins one by one, until you find the one that causes the high CPU usage. Once you find the plugin, try changing preset. Etc. etc.
what do you hope to gain by changing presets?
atm it seems that Podium suffers from cpu spikes when various plug ins have been changed / added / deleted for some time – but why does Podium use so much more cpu power ( charged by Windows Task Manager ) than say REAPER?
michi_mak@kim_otcj wrote:
I’d check latency settings on your interface as well. I find that when I set my interface for the lowest possible latency, that has a pretty devastating effect on my CPU usage.
256 samples – the same settings that won’t kill other hosts …
michi_mak@Infinitoar wrote:
Not to start a comment war, but I highly doubt it’s Podium using a immense amount of CPU.
-When Podium is not in use of anything relating to software[just on idle or standby] isn’t your CPU at 0%, correct?[as far as Podium’s usage meter]
-But when you “use something” it cranks the CPU to this “dangerous level”, correct?
Then Podium[in my opinion] is ruled out of the cause of what is causing your CPU to clock so high.
And if there is nothing else running and your running Podium by itself and there is no CPU spike then of course it’s your plugins/hardware that you are telling Podium to use that cranks up the usage so high. Not Podium.
Try fully closing Podium then opening the project alone and apply your plugins/hardware.
But if Frits tells otherwise then I stand corrected. Until then I believe it’s not Podium, but in fact your hardware/software that you use “in” Podium.
the exact same plug ins with the exact same presets in the exact same project don’t overload other hosts …
michi_mak@Zynewave wrote:
@michi_mak wrote:
issue might be related to “left overs” when changing / swapping plug ins …
One way to find out, is to save your project, reboot, load Podium and the project again, and check if the CPU usage is lower?
i did – makes no difference
michi_mak– i don’t use Asio4All – there’s a dedicated ASIO driver for my M-Audio Audiophile 2496
– no skype, no email client, no firewall, no virus checker at all
– same plug ins with same settings don’t cause this cpu stress in other hosts
issue might be related to “left overs” when changing / swapping plug ins …
but the fact remains that Podium uses remarkably more cpu power than other hosts !!!
michi_maksupposed the plug in lets you route the midi out port – otherwise you need a “wrapper” like energyxt to host your plug and use energyxt to reroute the midi out port of your plug in…
michi_mak@Zynewave wrote:
- Fix: Starting MIDI recording on a new track could skip the first note, if the note was short and overlapped a bar line.
improved but not gone in my experience
michi_makdid some further testing : switching “Use time stamp from driver” ON and setting ASIO buffers to 256 samples did improve things ( Loop on or off does not affect things atm ) – issues occur less often but didn’t solve-
but still Podium “feels a little different” when recording beats with my MPD18 compared to Live – for lack of better words ( i’m not talking about auto quantize !!! )
but things did improve and Podium
michi_mak@Zynewave wrote:
… It happens when recording short notes that starts before the bar line and ends after the bar line. I just released 3.0.2 with a fix for this. I could not detect any “bad” timing, only the occasional dropped first note.
sounds like you’re describing my issues? just trying right now!
michi_makmaybe in your book it’s nope but it hearts my workflow big time !!!
michi_makafter spending hours with a clean install and stuff i came up with this :
switching LOOP OFF does matter as it seems !!!
when loop switched off i didn’t have this issue with a dropped or too early first note
when loop switched on i get this issue in about 50% of all recordings
what a pity – a sequencer that can’t record in loop is rather useless isn’t it ???
michi_makas a last resort i will do a clean install of xp sp3 and report back – keeping fingers crossed …