Zynewave.
Zynewave
Conquistador@Zynewave wrote:
- Plugin processing is distributed on all available processors when running on a hyperthread enabled or multicore/multiprocessor PC. This allows plugin processing to be completed in a shorter period of time, and thus results in extra available CPU headroom. The actual CPU usage can be viewed in the Windows Task Manager, which can be accessed by right-clicking on the Windows taskbar.
- Added ‘enable plugin multiprocessing’ option in the preferences dialog. Clear this option if you encounter plugins that become unstable when using multiprocessing.
- Fix: Solved issue with corrupted Podium menus when unloading KarmaFX Synth.
Up a bit late? 🙂
Well well. Podium supports up to 32 proccessors. Very impressive. 8)
acousmodI was not at home these last days, so I’ve not worked a lot with this new version, but some things look to be better with my 3.2 GHz HT :
– with the 1.37, each time I was starting to play the CPU indicator was hitting the 100 %, and its background was always pink > it is no more the case
– I have not noticed a special CPU average consumption difference, perhaps 2 or 3 percents less, but the CPU indicator goes less often to 100 % and there is less clicks (but there were more in the 1.37 than in the 1.36)
– there is less “holes” in tracks due to “disc streaming issue” (?)
I have not yet tried to bounce.
ZynewaveI have not noticed a special CPU average consumption difference, perhaps 2 or 3 percents less
When you open the Windows Task Manager, do you have two ‘CPU Usage History’ panels? Do both panels show similar percentages when Podium is playing?
…but the CPU indicator goes less often to 100 % and there is less clicks (but there were more in the 1.37 than in the 1.36)
In the 1.38 release I removed the RME specific buffer underrun detection that was introduced in 1.37. Furthermore in this release I also boosted the Podium process priority when monitoring is activated. This will reduce occurences of CPU spikes, since other Windows tasks will less likely steal CPU time from Podium.
there is less “holes” in tracks due to “disc streaming issue” (?)
I don’t understand. Are you saying that audio file streaming/recording is improved with this release?
acousmodWhen you open the Windows Task Manager, do you have two ‘CPU Usage History’ panels? Do both panels show similar percentages when Podium is playing?
Yes.
In the previous version, the second graph was always lower than the first one. Now the second shows an activity which is more or less equal to the first.
I don’t understand. Are you saying that audio file streaming/recording is improved with this release?
For recording I don’t know, but yes, it seems to be the case.
The problem that I have described (short holes that jump from one track to another when the average CPU indicator is correct, about 50 or 60 %) occurs much less often.
A passage of which I had never been able to hear all the tracks at the same time is now read correctly. Nice !
ZynewaveIn the previous version, the second graph was always lower than the first one. Now the second shows an activity which is more or less equal to the first.
Great, then the multiprocessing is active. The distributed plugin processing may be the cause for your improved sound file playback. This is probably why you don’t see a big percentage drop in the Podium CPU indicator. The CPU time that is gained in the plugin processing is spent on the file streaming.