DSP Robotics Support

The .exe CPU bug needs to be fixed,
but I'm sure it will be.

Yeah nix - me too...

How could it be that my EXE's needs 4 times more in Raindrop (such as 12% instead of 3%, which is already 2 much) on my QuadCore , 3666 MHz - damn, my update support ends in less than a month...

Greetings,
Walter

Walter Sommerfeld wrote:such as 12% instead of 3%,

Is there any "Ruby" in the plug's....?????

...have troubleshooted X11 Cpu rise down to:

A: bad ruby programming..or
B: the price of using ruby .. or
C: A+B or something like that...

I've gone back about 5 versions, and X11 is normal on raindrop..
runs a smooth 8% in FS..22% in host..Bettter idea of what that means on this cpu...
( vsti module on its own in host is 15%) FL Synths run at 20%..

So now I'm going through all the ruby stuff in there....looking for clues....

I know the timer is up to 3% FS higher, the rest I'm blaming on the change
from green to ruby in the clock circuit, that runs through the synth and back.
The improvement in timing at very slow or fast host tempo's I got from this change
is preventing me from going back to green...

I'm not sure about your plugs, but in my case, it's probably bad coding/design.

Hope this helps...

We're not talking about something that can be rectified by the user.
An FS .exe with no modules in it uses 17% CPU on my quick laptop.
It should not use any.
DSPR need to fix it, as many of their robotics peeps will want .exe I imagine.
Damn hey
all success DSPR with this problem

nix wrote:An FS .exe with no modules in it uses 17% CPU

It 's 25% on my cpu. And dosn't seem to matter what you put in it....
A few connectors...25%
A vsti module..25%
X11...25%

That's the interesting part for me..why no variation here....don't get that at all......

billv wrote:It 's 25% on my cpu. And dosn't seem to matter what you put in it....
A few connectors...25%
A vsti module..25%
X11...25%

That's the interesting part for me..why no variation here....don't get that at all......

it was discussed here:

viewtopic.php?f=2&t=1680

Yeh i know...and everyone's hitting 50%....strange issue alright..

Not everyone. It's 100% at 1 core (thus - 50% on two cores or 25% on 4 cores); and although it's madness for hardware (especially for laptops with no good fan control), it's "low priority" usage (imagine it as a large tree that swings on gentlest wind). FS/SM apps operate on one core. Few more percents on other(s) cores are related to rest of the Windows operations (GDI? parts of ruby?). This issue will/should be fixed with incoming update.

X11 Updated to 2.09..(download via first post)

* New timer installed to fix rise in CPU usage.
* Clock start/finish controls fixed. These are now built in to the timer,
and give accurate results, so if you set a section to loop, the loop
will be accurate.
Also at clock finish, it will always restart at 1, and not 0, avoiding that
'zero' part where nothing is happening.
* Ticker send for Wave Osc 'wave' Selection fixed.
* Ticker send for Wave Osc Vol fixed.

* Another bug found in pre-set system. One connection was doubled ,
causing some wrong values to go into preset system.
If you are running previous version, these wrong values will be in the
X11 data folder, and when you install the 2.09 update, naturally the X11
will load those "wrong values" back in.

So, before installing the 2.09 update, either..
A: delete 'triggers.txt' from the X11 data Folder...or
B: just delete X11 data Folder

Sorry if you loose any great presets in the process.....
Preset system still in a type of 'beta' stage..but running with no issues now.

Development of the X11 is at its last stages.....

Only one more update planned....mostly graphics related...

http://d2bm3ljpacyxu8.cloudfront.net/wi ... 0Final.png

Did the sequencer remember u something Billv?
It's always the stealer sonix XTC.

CoreStylerz wrote:Did the sequencer remember u something Billv?
It's always the stealer sonix XTC.

...i can't seem to recall it....but i forget lots of stuff these days..
Sounds alright though....