Topic: Unusual behavior in Podium

Viewing 6 posts - 1 through 6 (of 6 total)
  • April 7, 2008 at 16:27 #1579
    sam c
    Participant

    Frits, probably along the lines of some other issues folks have experienced, I have files that when I hit play will play at a 10 to 12% CPU hit (which seems correct). When I hit stop the CPU meter on Podium spikes to 45% and will not reduce until I either hit play again or stop and restart the engine. I believe this is new to 1.98.

    I have experienced this with three different files in the last few days.

    April 8, 2008 at 07:16 #12096
    druid
    Participant

    That sounds oddly like a denormal. When you say it takes that much CPU, is that because it’s one core of two (thus one CPU is likely to take up towards 50%), in other words, measured by using task manager? Could you insert a denormal plugin such as Normalizer and see if that changes anything?

    Purely speculative, at this moment.

    April 8, 2008 at 13:53 #12102
    sam c
    Participant

    well, the task manager follows podiums cpu pretty close.

    no dual core here. still on a P4, 2gig RAM. 3.4Ghz. still humming along too.

    to me the key is that this did not happen in 1.97.

    April 8, 2008 at 15:02 #12104
    druid
    Participant

    P4 means you almost definitely have hyperthreading. If you have hyperthreading enabled (by default it is), you might still only get that near 50 rating (I think). It’s worth trying just to see if it changes it. Even if a plugin fixes it, I suppose it might mean something changed in Podium, too.

    Naturally, since that was the only suggestion I made, it’s the only one I can think of…

    April 8, 2008 at 15:08 #12106
    sam c
    Participant

    druid, i appreciate your suggestion! i have disabled hyperthreading to test but the results are not only the same, my computer does not like it when i disable. it gets noisy as hell!

    i believe it is podium………….or the cyber goonie!

    April 8, 2008 at 16:28 #12111
    Zynewave
    Keymaster

    To test whether it is a plugin that is the cause for the CPU rise:

    Once you’ve stopped playback and the CPU has risen to 45%, start bypassing your plugins one by one using the X button on the tracks, and see if there is a particular plugin that causes the CPU to fall back to normal.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.