What display resolution do you use?
Maybe there is somewhere in the display control panel where you can define how much of the system memory the gfx controller allocates? I remember many years ago, this was something you could set in the BIOS.
If you have other programs running while running Podium, try closing them to see if that makes the Podium CPU usage jump down. Even having just an Internet Explorer open will use up some graphics memory.
1280 x 1024.
No other programs ever open when I record. Only a few apps on the computer and all recording related.
Not sure where/if allocation of graphics can be adjusted?
Changing resolution to 1280 x 960 helped a bit. The next reduction changes things in appearance too much.
When you start the computer, you can press the delete key (or sometimes it needs F2 or another button) to enter the BIOS setup. Inside there, try not to change anything except the setting that you are looking for, which is often called “AGP Aperture Size”, or something like that. It usually has megabyte settings like 32, 64, 128, and even 256 in some cases. Depending on the BIOS, it might be in various submenus, but it’s in the one that deals with extra peripherals like PCI cards and so forth, and not the CPU.
If you can’t find that, post a response saying so and give me the model of your desktop, and I will see if I can look for a manual that details the BIOS online.
Good luck!
@druid wrote:
When you start the computer, you can press the delete key (or sometimes it needs F2 or another button) to enter the BIOS setup. Inside there, try not to change anything except the setting that you are looking for, which is often called “AGP Aperture Size”, or something like that. It usually has megabyte settings like 32, 64, 128, and even 256 in some cases. Depending on the BIOS, it might be in various submenus, but it’s in the one that deals with extra peripherals like PCI cards and so forth, and not the CPU.
If you can’t find that, post a response saying so and give me the model of your desktop, and I will see if I can look for a manual that details the BIOS online.
Good luck!
Thanks-I got into my Bios set up but after looking over and over I cannot see anything that resembles AGP-aperture size-or anything that might be similar….The only PCI option was stay off or on.
Sony Vaio VGC RB43
Argh, as I thought, Sony don’t have detailed a BIOS reference manual that I can find, nor can I find it on Google.
It’s a bit troublesome, but if you have a digital camera, you could take photos of the different parts and I could help you from there. I’m not sure what else to try, really, as I’m not familiar with all the different names.
I can say though, that you might end up unlucky. Many OEMs like Dell cut down the amount of control people have in the BIOS, and undoubtedly Sony does too.
Usually in BIOS, in motherboards that are purchased outside of OEM, there is a section called “Advanced BIOS” or “Advanced ~” something or other. In there is usually the Aperture Size. But yeah, it’s quite possible you don’t have it. I won’t know unless I can see the BIOS screen myself, since I am unfamiliar with your system.
sam, I don’t want to detour the help you are already getting but…
I had a similar problem a couple of years ago in another app. What sparked the memory was your mention of the cursor issue. For some reason my comp was having issues and the all revolved around the cursor. The program was drawing its own cursor instead using a system cursor (I have no idea how Podium handles this) and the only way to resolve it was to reduce the hardware acceleration of the video card. I could do it from the desktop using the display settings.
Some time later Nvidia updated the drivers for my card and the problems went away but knocking the slider down a couple of ticks did the job in the meanwhile. Not sure if this is the issue for you but I thought I would mention it since your issue reminds me of that one.
@UncleAge wrote:
sam, I don’t want to detour the help you are already getting but…
I had a similar problem a couple of years ago in another app. What sparked the memory was your mention of the cursor issue. For some reason my comp was having issues and the all revolved around the cursor. The program was drawing its own cursor instead using a system cursor (I have no idea how Podium handles this) and the only way to resolve it was to reduce the hardware acceleration of the video card. I could do it from the desktop using the display settings.
Hey UA!
That helped. I took it down two notches and my CPU is at25% with track/mixer open, an improvement of 32%! Might try another notch down.
What is strange is why all of the sudden? I have been trying to put off buying a new computer because this one has been flawless with programs like Podium. Hopefully this will get me by awhile longer before I dive into an i7!!
Thanks again for everyone lending a hand!!
I never found out why it worked either. I assumed it had something to do with the direct x version and the video card drivers. Of course it could be some other library as well. Only Frits would know for sure. Glad to hear it helped a bit.
@UncleAge wrote:
I had a similar problem a couple of years ago in another app. What sparked the memory was your mention of the cursor issue. For some reason my comp was having issues and the all revolved around the cursor. The program was drawing its own cursor instead using a system cursor (I have no idea how Podium handles this) and the only way to resolve it was to reduce the hardware acceleration of the video card. I could do it from the desktop using the display settings.
I think Sam referred to the Podium play cursor, and not the mouse cursor. Podium does not do anything non-standard with the mouse cursor pointers.
Normally I recommend that the hardware acceleration slider is set to maximum acceleration. For each step you move the slider down, you’re telling Windows that more of the stuff that normally is handled by the video card, should be emulated by the main CPU. That means less CPU time for the audio processing. But if there are problems with the video driver, reducing this setting is a solution. That seems to be the case here.
Sam, perhaps you could check if there are updated video drivers for your VAIO PC.
Well, I’m glad you reported this issue Sam, because it made me look at my UI updating code. I tried out an alternative method, that helps reduce the areas that are painted when only things like meters and the play cursor are updating. At least on my machine it meant a huge reduction in UI cpu usage π
If you want to test it, you can download the 2.26 beta9.
Let me know if this reduces your CPU usage further.
@Zynewave wrote:
I think Sam referred to the Podium play cursor, and not the mouse cursor. Podium does not do anything non-standard with the mouse cursor pointers.
This is right-but reducing hardware acceleartion has helped.
@Zynewave wrote:
Normally I recommend that the hardware acceleration slider is set to
Sam, perhaps you could check if there are updated video drivers for your VAIO PC.
There is but it did not help. π₯
@Zynewave wrote:
Well, I’m glad you reported this issue Sam, because it made me look at my UI updating code. I tried out an alternative method, that helps reduce the areas that are painted when only things like meters and the play cursor are updating. At least on my machine it meant a huge reduction in UI cpu usage π
If you want to test it, you can download the 2.26 beta9.
Let me know if this reduces your CPU usage further.
Way to go Frits!!! All the way down from 62% to 10% with hardware acceleration back to full and resolution back to 1280×1024-great work!
Now there’s an awesome solution! Sounds like everyone could win from it, too!