Kostrowitzky.
frollo9386does it happens with every preset of the vsti?
if yes does it happens with every vsti that you try?
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_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 …
adimatisI can only suggest you try Podium on other computer and see how it works. Each machine is a very unique mixture of hardware and software, and it is possible, given the “right” mix that something goes wrong.
In my case, Podium is not lighter than Reaper, but it’s not heavier on CPU than Studio One or Cakewalk (X1 LE). I have some screenshots, but no means to post them here.
See what happenes.
kingtubbyI did my own little cpu usage test, basically the same as michi_mak – one looped wav with 1 effect, in this case D16 toraverb and the results were:
podium 3.0.1 = 4-5%
energyxt 2.6 = 2-3%
ableton live8 = 2-3%
flstudio 10 = 1-2%
update:
Interestingly, I re-ran the test on Podium, then minimized it to the taskbar whilst still playing and the cpu usage dropped from 4-5% to around 1-2%
michi_mak@kingtubby wrote:
I did my own little cpu usage test, basically the same as michi_mak – one looped wav with 1 effect, in this case D16 toraverb and the results were:
podium 3.0.1 = 4-5%
energyxt 2.6 = 2-3%
ableton live8 = 2-3%
flstudio 10 = 1-2%update:
Interestingly, I re-ran the test on Podium, then minimized it to the taskbar whilst still playing and the cpu usage dropped from 4-5% to around 1-2%
running a daw minimized to the tray does not help too much, does it?
kingtubby@michi_mak wrote:
running a daw minimized to the tray does not help too much, does it?
I wasn’t suggesting that of course – it was just an observation. Anyway, my little test kinda supports your original complaint.
michi_mak@kingtubby wrote:
@michi_mak wrote:
running a daw minimized to the tray does not help too much, does it?
I wasn’t suggesting that of course – it was just an observation. Anyway, my little test kinda supports your original complaint.
i did understand your point – was ment to be a joke – sorry!
thanx for sharing your findings !
i can’t understand why a host like energyXT ( which does NOT even support multiple cores ) can compete with Podium in this regards…
Zynewave@michi_mak wrote:
latest 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 …
If those percentages are from Windows Task Manager, then the percentages include the entire application, including UI updating. That is why kingtubby notices that running Podium minimized results in lower CPU usage, because the UI in that case does not need to be animated. The Podium UI has been programmed to use available CPU power to animate the UI smoothly. The UI thread is lower priority than the audio engine, so if the audio processing takes a lot of CPU, then the UI CPU usage is reduced. You need to measure plugin CPU usage at a higher total percentage, to get comparable numbers. The most important comparison factor IMO ought to be how many plugin instances you can run simultaneously before the CPU overloads.
michi_mak@Zynewave wrote:
…The most important comparison factor IMO ought to be how many plugin instances you can run simultaneously before the CPU overloads…
this is where i started – as a rather small project overloaded Podium but not the other hosts i tried for comparison …
Zynewave@michi_mak wrote:
@Zynewave wrote:
…The most important comparison factor IMO ought to be how many plugin instances you can run simultaneously before the CPU overloads…
this is where i started – as a rather small project overloaded Podium but not the other hosts i tried for comparison …
Then please reread my posts in this topic. I asked you twice which plugin was causing this, and I still haven’t gotten an answer. I suggested a method you could use to figure out which plugin caused the CPU overload. If you experience 100% constant CPU load, then the problem is most likely due to denormals in a plugin, and not a general problem with Podium performance.
michi_makwell, to name the plug in : Mokafix Audio BassRider – BUT even without this obvious cpu hog the shoot out still proves Podium to use more cpu for the same task than other hosts …
EDIT : kingtubby provided his/her own shoot out with a different plug in on a different machine and came to the same conclusion …
Zynewave@michi_mak wrote:
EDIT : kingtubby provided his/her own shoot out with a different plug in on a different machine and came to the same conclusion …
Please reread my post earlier on this page, where I explained why kingtubby observed higher CPU usage.
kingtubbyI don’t know what the system specs are on the machine michi_mak is running, but on my 4 year old quad-core, the couple of extra percentage points of cpu use to support the super smooth and lovely Podium UI is fine by me. 🙂
michi_mak18% against 2% – playing 1!!!! wav file with 1!!!! vst fx – even the prettiest GUI is no choice with this hogging…