DFusion's Forum Page

What OS are you using (XP or Vista) ?

@Conquistador wrote:

@DFusion wrote:

Let me explain 🙂
If you have a single core it counts from 0 to 100%

Dual cores have a max of 50% on each core and Quad has 25% on Each core.

So if you use a program on a dual core setup and you disable Multithreading it only uses one core which maxes out at 50% and the other core works for background tasks outside of the program that is used.

So to sum it up:

Single core = 100%
Dual Core = 50+50 = 100%
Quad Core = 25+25+25+25 = 100%

So on a Dual core 50% is 100% on one core.

😀

Interesting. Thanks. How do you know this if I may ask? Any Microsoft links to read? 🙂

I don’t know if it is explained somewhere on the net but it is simple math 😉

A Dual core or Quad is recognized as 1 cpu and 1 cpu can never show more than 100% in Taskmanager.

So if you have a Multi Core cpu you have to divide 100 by the amount of cores on your cpu.

It doesn’t mean that 1 core on a Dual core is slower than a single core it is just that the numbering in cpu usage is different 😀

If you have a Dual core or a Quad you can try to disable multithreading in your music program and push it to the limit.

Then you will see that it won’t get past 25% on a Quad or 50% on a Dual Core no mather how hard you push it 😉

I just had to add a little Spanish in there 😳
That is how i learn new languages + my Uncle is Spanish 😀

Now that i see it clearer it seems like there is a bug in Podiums Cpu meter and that it is set to stop when it shows 100%

You are only using half of your cpu power on both cores so the only one who can help you there is Frits.

Hmm. that is weird.

To me it looks like you have Multithreading enabled in Reaper but not in Podium.

Btw. where have you got that cool dragon background?

@LiquidProj3ct wrote:

I noticed that CPU meter is very weird:
– Different values that task manager (aprox twice its value)
– When multicore processing is enabled it’s less CPU expensive…

See attached pictures

Best regards

This is because the max is 50% on each core so when you disable multicore it shows about half of what it does with it enabled 😉

So when multicore is enabled it counts the cpu cycles from 0 to 100% and with it is disabled it counts from 0 to 50%

@Zynewave wrote:

@UncleAge wrote:

When I press the “B” button I want it to “Bounce/Freeze”. Once the bouce was created the track and button would stay in that state. Clicking the button again would unload the bounce. I guess I fail to see the need for both the record and playback options. In my mind I see the track going into a “Bounce Playback” state automatically after I record/create the bounce.

That is precisely how I plan to implement it. The B button will then act precisely like the freeze button in other hosts. What you misunderstood is that the purpose of the “Activate Bounce Record” is to enable realtime-bounce recording, as opposed to rendering the bounced audio offline. You can ignore this option if you don’t have the need to bounce realtime for such things as external hardware, DSP hardware plugins and native plugins not capable of working faster than realtime. Perhaps this option will be more obvious if I renamed it to “Activate Realtime Bounce Record”?

I think this new bounce thing looks great 😀
But i also have to admit that the naming of the different bounce options could be very confusing.

I would name it like this:

Activate Slow Bounce

and

Activate Fast bounce

😀