@ronin wrote:
After playing around a while I’ve noticed the comparable low performance of Podium. As it turns out it doesn’t use both cores of my system. The “Enable multiprocessing” is greyed out and can’t be enabled with the menu. Setting the switch manually in the config file doesn’t work either.
But: setting the affinity of the podium executable via the task manager to both cores and setting the switch manually works. After reinstalling and testing around it seems like that Podium was not able to detect the dual core correctly. is there something which could prevent Podium from using both cores?
Which Windows version are you running?
If there is only one core enabled when you open the task manager and show process affinity for Podium.exe, then the problem must be in the way that Windows launches Podium. On XP I think there was a setting in the Windows properties for Podium.exe that allowed you to set a desired process affinity. Looking now in Vista I can’t find this option anywhere.
p.s. i’ve noticed something more: I did some testing on another core duo (everything works fine here). after loading 10 instances of a ambience (free reverb) into one track the cpu time meter rises to 60%. just one core is used with 60% (according to the procexp taskmanager). if I load 10 more instances on another track the Podium cpu time meter rises to 80% and suddenly both cores are used with 40%. maybe this was interesting 🙂
Serially chained plugins cannot be multiprocesed. Each plugin must complete its processing before the next plugin in the chain can start its processing. When you have two tracks with identical chains, then plugins from each track can be processed in parallel.
.
