Topic: CPU & CPU usage meter: Pretty weird. (Solved)

Viewing 8 posts - 46 through 53 (of 53 total)
1 2 3 4
  • February 24, 2009 at 03:02 #14580
    bfloyd6969
    Participant

    @Zynewave wrote:

    A buffer size of 512 should be fine.

    512 is what I have been using (along with the other hosts) but this is also when I was seeing the higher cpu in the Podium meter than other hosts. I maxed out the buffer which set it at 2048. This reduced the orignal load which was 20% (512) for two tracks down to 13% (2048).

    Perhaps my computer just doesn’t like Podium as much as I do 🙁

    February 24, 2009 at 17:00 #14585
    LiquidProj3ct
    Participant

    Now in the new 2.10 beta 1, I can use six gladiator tracks without problems with the option you added (and seven with artifacts). Thx you very much. Oh, and the GUI doesn’t freeze when CPU is overloaded! 🙂

    Good work!! Thanks!!! 😀 😀 😀 😀 😀

    EDIT: As I said in the 2.10 discussion, since GUI doesn’t freeze, I think you should disable that option by default, so those people with non-optimized pcs haven’t problems with this and think that podium is CPU expensive.

    February 25, 2009 at 02:21 #14591
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    Now in the new 2.10 beta 1, I can use six gladiator tracks without problems with the option you added (and seven with artifacts). Thx you very much. Oh, and the GUI doesn’t freeze when CPU is overloaded! 🙂

    Good work!! Thanks!!! 😀 😀 😀 😀 😀

    EDIT: As I said in the 2.10 discussion, since GUI doesn’t freeze, I think you should disable that option by default, so those people with non-optimized pcs haven’t problems with this and think that podium is CPU expensive.

    Glad to hear this works better for you 🙂 . But let me just emphasize: The new option does not change the fact that CPU overload does occur, so there will be sound glitches. The heavy pad sound you use in your project can mask out the glitches so it can be difficult to hear. And I will also postulate that the glitches/spikes also will occur in other hosts, even though they may not give a visual indication of it.

    I’ve changed the default of the new option to be off. The automatic bypassing was implemented years ago, on an older Windows version running on a single-CPU PC. Without the automatic bypassing, the PC could freeze up completely, requiring a cold-boot. Today multi-core machines are more common, and on these machines you seldom have problems with GUI freezes.

    February 25, 2009 at 07:56 #14599
    LiquidProj3ct
    Participant

    Yes, I understand. Me and my friend, RxO here, are very happy with this 🙂

    February 25, 2009 at 13:30 #14604
    RxO
    Participant

    Yes.

    Very,very 😀 😀 Thanks

    Saludos!

    March 4, 2009 at 10:34 #14642
    Conquistador
    Participant

    @LiquidProj3ct wrote:

    Now in the new 2.10 beta 1, I can use six gladiator tracks without problems with the option you added (and seven with artifacts). Thx you very much. Oh, and the GUI doesn’t freeze when CPU is overloaded! 🙂

    Very interesting feedback. Even more CPU usage out of Podium quite a result 🙂

    EDIT: As I said in the 2.10 discussion, since GUI doesn’t freeze, I think you should disable that option by default, so those people with non-optimized pcs haven’t problems with this and think that podium is CPU expensive.

    Seems like a very good idea. That might be the best way forward to avoid confusing new users. I had my fair share of issues with it in the past. I wasted a huge amount of time troubleshooting it sadly.

    I’ve changed the default of the new option to be off. The automatic bypassing was implemented years ago, on an older Windows version running on a single-CPU PC. Without the automatic bypassing, the PC could freeze up completely, requiring a cold-boot. Today multi-core machines are more common, and on these machines you seldom have problems with GUI freezes.

    Something to consider Frits….most demo users IMO will not post their thoughts on a forum and may silently compare CPU usage with their current host. I really think it is better to leave the new option on instead.

    Better to have one demo the product on an equal CPU playing field with other hosts than to lose a customer who immediately thinks ” this is a no go…the CPU usage is much higher with Podium than my current host”

    While I completely understand your admonitory tone (makes perfect sense), I think LiquidProj3ct’s suggestion to make it the default really will simplify the CPU issue and lower the learning curve considerably for anyone trying the demo.

    Just look at how many recent posts on CPU usage there have been from new and even existing users.

    Less time fire fighting these issues for you as well. Even if someone posted an issue with glitches I see no problem there as the CPU reading will mirror other hosts. So it is a very unlikely scenario as a user will almost certainly use similar plug ins in a new host (at least initially) so they are unlikely to complain about Podium having glitches compared to anything else…LiquidProj3ct’s excellent feedback seems to back this up.

    March 4, 2009 at 15:39 #14647
    Zynewave
    Keymaster

    @Conquistador wrote:

    I’ve changed the default of the new option to be off. The automatic bypassing was implemented years ago, on an older Windows version running on a single-CPU PC. Without the automatic bypassing, the PC could freeze up completely, requiring a cold-boot. Today multi-core machines are more common, and on these machines you seldom have problems with GUI freezes.

    Something to consider Frits….most demo users IMO will not post their thoughts on a forum and may silently compare CPU usage with their current host. I really think it is better to leave the new option on instead.

    I think you misunderstand. Having the option on will result in the same behaviour as previous versions, where plugins are bypassed when overload is detected.

    March 4, 2009 at 15:56 #14649
    Conquistador
    Participant

    @Zynewave wrote:

    I think you misunderstand. Having the option on will result in the same behaviour as previous versions, where plugins are bypassed when overload is detected.

    Correct yes! In that case I meant off not on LOL and agree with yours and LP’s suggestion, thanks 🙂

Viewing 8 posts - 46 through 53 (of 53 total)
1 2 3 4
  • You must be logged in to reply to this topic.
© 2021 Zynewave