Hey there,

as some of you might have seen it already in another thread: I'm working on this simple music player:


It works great except for the performance.
The fps aren't a problem but with a resolution of 1280x720 (720p) @ 60fps it uses one full core (~3.5ghz) - which is everything it can get and for me that's kinda strange.

so, what are you're experiences with acknex's performance and what can I do to minimize the cpu usage? (except for switching to another engine :P)

The engine is supposed to use full cpu power, I guess? If you limit the FPS via fps_max, usage should go down AFAIK.

But regarding the quality of your work, I am surprised I have to tell you this?!

I'm already limiting to 60 fps

however, even an A8-application which does nothing at all uses 8-10% at 60 fps. (1 core = 12.5%)

it was actually pretty easy...
some flat models, the fmod plugin, my hdrr pipeline and a little bit of math, that's all

so, can anybody help me?
otherwise I'll ask again in the 'ask the devs'-subforum

You could try to decrease the thread- or processpriority but IDK if this little boost helps you xD

Changing a process' priority doesn't change the amount of computation that needs to be done.

I guess your best bet is to reduce the complexity of the algorithms used.

@Uhrwerk, thanks but as I've said before even an application which does nothing at all needs ~10% cpu usage.

Well, that's exactly what I would expect. The engine has to do some management jobs. Even if nothings happens the the task scheduler will run for example. And even if you don't render anything at all still about half a gigabyte of pixel data has to be calculated per second (assuming fullhd @ 60fps) and moved to the screen buffer...

yeah... I just thought that maybe some of the background-management-stuff can be turned off (or modified / optimized).

An a8 application wich does "nothing" does not really do "nothing" ....

For any type op cpu intensive activity you should try and split those parts into threads thats what they are for..

However , i would not know what goes on in your app so i guess my advice is of no use.. Lite-c sucks anyway