Podianer.
acousmodHi,
I’ve this problem for a time, and I have not found a logical reason for it :
some times, generally after a certain amount of time of use, often just after having change something in the arrangement (splice or move a sequence, change a level…) Podium have irregular CPU spikes (goes to red and returns to the actual value very fast) which result in clicks or very small drop outs.
The average CPU value in this project is between 20 and 30 % and I dont’use any plugin.
There is only audio tracks with 8 or 16 channels files, but it doesn’t seem to be relative to the number of active tracks, since it happends sometime with only one or two files playing.
Sometimes, if I stop 10 or 20 seconds before start, the play is good. But sometimes I need to shut down and reopen Podium and it goes well up to the next time (the passages that had previously CPU spikes are played at the average %, without clicks).
I have defragmented my drives and no other application is running (like Spybot !).
I can’t compare with another software, since I can play my 16 channels audio files only in Podium…
But I have used before a similar setup in Nuendo with a lot of 8 and 12 channels files without this sort of problem, so I suppose that the Multifaces and the computer are not the cause.
Does this means something for you ?
Thanks !
stuHi Jean,
Ive had this problem to, it seems to be somthing to do with when you use 96khz. I mentioned this to Frits a while ago now, he said that using a higher sample rate will use more cpu (true), so I started using 44100hz instead and everything was running just fine. He said that because 96khz is nearly double 44100hz twice as much cpu is needed. The thing is I can probably run about triple or more at 44100hz than at 96khz, theres somthin not quite right about it 😕 . Anyway thats all I can say about the matter, just try switching to 44100hz for now, thats if your not already at 44100.
Stu
acousmodThanks stu, but all my files are 48 khz / 16 bits.
The curious thing is that all can goes well at 20/30 % without any spike during 30 minutes or one hour and that the apparition of the spikes is not progressive.
They are also sometimes nearly regular, about 1.5 second.
I’ve thought about something related to temperature, but it stays correct (CPU and HD about 45°C) and if I shut down and immediately restart Podium the spikes disapear (for a certain time…).
acousmodTest made with Nuendo with the same setup :
10 tracks at once with the same 16 channels files (I can hear only the 12 first channels due to the bus limit of Nuendo) = CPU 5% stable / HD between 30 and 60 % (logical !), no drop out, no clic, no CPU variation…
My config : P4 3.2 GHz HT, RAM 1 Go, 2 RME Multiface
The swap file is turned off since when it is on, Podium makes “pauses” (a few seconds silences) when the screen scrolls.
Why is the average CPU so high in Podium (20 to 30%) with only two or three files playing and no plugin ?
ZynewaveWhy is the average CPU so high in Podium (20 to 30%) with only two or three files playing and no plugin ?
I hope that percentage is from the Task Manager and not the CPU indicator in Podium. The task manager will always show a high percentage due to a currently rather inefficient drawing of audio in the arrangement editor. You’ll be happy to know that I’m currently working on optimizing this. I originally meant to spend a couple of days with this, but so far I’ve spent a week on it. I’m continuing work on the optimization, as the speed gains I have managed so far are huge.
acousmodI hope that percentage is from the Task Manager and not the CPU indicator in Podium.
No, it is the one of Podium…
But a strange thing is that withe the same files in an empty arrangement the CPU in lower, between 10 and 20 % (my current arrange has 60 or 80 files opend).
Perhaps that my problem is related to the slow graphic thing ? (causes by the 16 channel files and the number of them ?).
If I play without making any editing the CPU stays in its average value (with no virtual memory as said before). The spikes, holes in sound and clicks appear for example after adding a point on a volume curve (in the separate editor). The passage was good and when I replay, the CPU indicator has red bursts etc. I must wait 10 seconds or more to be able to play normally (sometimes it doesn’t change anything).
You’ll be happy to know that I’m currently working on optimizing this.
Very !!! 😛
You know, I’m always requesting some improvements, but this is because the actual version of Podium has a so huge potential, and I’m a bit frustrated and impatient because I’ve no doubt about you (and also because now I work only with it !). It’s only a matter of time for Podium being the best multitrack software (from my point of view…).
It is like when we are young and waiting for Christmas, when we know the gift that we will have, and we count all the days !
The “rather inefficient drawing of audio” was one of these days…
Thanks.
PodianerToday I found Podium acting the same way.. Irregular cpu spikes.. My samplerate and resolution are 44KHz and 16 bit.. Average CPU use: 15%.
Not sure, but I think this behaviour is new since I use 1.36…
Zynewave@Podianer wrote:
Today I found Podium acting the same way.. Irregular cpu spikes.. My samplerate and resolution are 44KHz and 16 bit.. Average CPU use: 15%.
Not sure, but I think this behaviour is new since I use 1.36…
I need more details. Are you using plugins? Does it happen only during playback? When the cpu spikes occur, does the Podium CPU indicator go red and jump to 100% and then fall back down to 15%?
If you’re using plugins, try bypassing in turn each plugin, until the CPU spikes stop. If you find a plugin that is causing the spikes, then try changing to another preset.
There is nothing new in the 1.35/1.36 releases that should cause these problems. On the contrary, the optimized graphics should reduce the chances of spikes.
PodianerI need more details. Are you using plugins?
Yes, I use 2 VSTi: The Grand and Sampletank. Furthermore there is Glaceverb on one track.
Does it happen only during playback?
No, I don’t have to play anything to make these spikes occur, e.g. my midikeyboard or simple playback.
When the cpu spikes occur, does the Podium CPU indicator go red and jump to 100% and then fall back down to 15%?
Yes, the cpu meter goes suddenly to 100% (red) and then falls back to 15%. They are unpredictable. I moved my Podium directory to another hard drive, perhaps that has something to do with streaming from my second hard drive..
ZynewaveI moved my Podium directory to another hard drive, perhaps that has something to do with streaming from my second hard drive..
Moving the Podium program or the project folder should have no effect on this. If you moved the plugin files, then there can be problems if they are using disk-streaming to play the samples. Does the spikes occur only when you play notes on your keyboard, or can they occur when you do nothing and the plugins are silent?
Try bypassing either the Grand or the Sampletank plugin and see if that removes the spikes.
PodianerDoes the spikes occur only when you play notes on your keyboard, or can they occur when you do nothing and the plugins are silent?
The spikes occur even when I do nothing … I’ll bypass the VSTi and wait a few minutes to see if the spike is gone..
ZynewaveI’ll bypass the VSTi and wait a few minutes to see if the spike is gone.
You could also try to increase the ASIO buffer size. A low CPU usage and occasional CPU spikes is a typical problem with very low ASIO buffer settings. When the buffer size is small, there is a greater risk that timer critical events in the OS or application can disturb the ASIO buffer processing. What soundcard and what latency are you running currently?
PodianerI use the M-Audio Delta1010LT with a latency of 256 samples. I’ll increase the samples… My project just crashed a few minutes ago.. I did’nt save… 😥 No I have to record it once again.. perhaps the spikes are gone with the new sample value.
ZynewaveMy project just crashed a few minutes ago
You mean Podium crashed? When this occurs, please try to remember what you were doing before the crash, and try to recreate the crash scenario. Otherwise I have no chance of fixing these bugs.
PodianerI was in the sequence editor.. I held ctrl+alt leftmousebutton and then I moved the mouse in order to zoom out.. The zoom-out was very fast and then the program crashed.. I could manage to make Podium crash twice, but the other times everything went fine..