DSP Robotics Support

X11 Updated to 2.05 (Download from first post)

This is the Ruby re-build.....stage 1
* Timing system re-built and bussed through whole synth..
* Wave seq and 4 Note seq added
* The 4 Mods re-built
* Vst Plug-In or Standalone

@Trog
Thanks again for the Ruby Counter...allowing this re-build to happen

It must have been my narrow-minded approach to get the timing right with
the 2.05 update, that made me miss something very important.
I've blown it on cpu......something's terribly wrong....
Every version released of X11 runs at (SM/FS CPU) 6-8, peak 10-12
On my CPU, in a host, this translates to about 20....peaking at 25.
On my CPU, in a host, just a vsti runs at 15..so I've always been real happy about X11 CPU usage..
in FL Studio, top FL synths like Sawer run at about 20 as well...
so I've always used that as a sort of "benchmark" to keep track of things...
Anyway, I'm plugging away at this 2.06 update, and i can swear i can hear audio breaking up,
checking the cpu I'm sitting mid 20's, more than 3 times what X11 should be, and
getting insane peaks of 40 - 50+....WTF......
So i begin checking all previous versions down to SM 1.32, to see where the issue has
arrived...they were all good till i got to 2.05.
This was where the Seq Module was fully re-built, and the green clock/timing that ran
through the synth was switched to ruby.
At first , I was worried that bussing ruby thoughout was to blame...so I pulled the
Seq Module out to test and it runs at 10(FS).....should be 1-2max....
So there's a bug in that Seq module at the moment
Can't wait to find out what' the bug is....hopefully it's the only one causing the CPU issue.

billv wrote:causing the CPU issue

Looks like the timer itself.....when I changed it to ruby....
Green version is fine....
Big CPU rise in FS not translating over to standalone or VST that much,
only 5 point rise in VST.....Might just wear it and keep building....

X11 Has been updated to 2.06 Download fist post.

OPTIMIZATIONS:

* More than 700,000 un-nessesary parts were removed...
* Is now 250.000 parts..

NEW STUFF:

NEW PRESET SYSTEM

* 999 Program slots.
* Everything in X11 can now be saved..!!
(except wave files in wave osc if loaded by user...)
* 1-Click system....with no manual file loading....all your work is
loaded automaticly when re-started.
* Also features a 'sub-preset' system in some of the larger modules
* Create normal synth presets
* Create compositional presets
* Create presets that randomly change with time
* Create new presets quickly with the 'sub preset' system

MORE NEW STUFF:

* Host Sync Button
* Arp module added to 'Host/User' Mode
* New 'send' selector in Ticker section.
* Info page
* Clear Audio Control
* Default Seq behaviour Control
* Freestyle Mode Control

* 4 NOTE SEQ
* New Arp mode
* New 'Shift" control
* New 'Random' control
** The 10 slots in 4 Note Seq don't need to be saved anymore..is done for you..

CHANGES/IMPROVEMENTS & FIX'S

* Osc 1 and 2 behaviours were fixed, so that after Osc modulation the Wave selector's
are returned to the initial user selection.
* and also, so that after Osc Automation the Sin/Saw selector's are returned to the
initial user selection.
* Bug in Matrix master division selector fixed
* Rotation can now be used without sending a modulator to it.
* Matrix section was fully re-built.. matrix was re-built...

Note:
This new fsm dosn't run well in FS on my cpu, forcing the suspension of X11 development
till the day my cpu blows up and i get a faster one.
Meanwhile the Standalone and VST are running great...so the release goes ahead.

In other words, i can't recommend running X11 in FS if you have a crappy cpu...
.use FSM for reference..make standalone or VST and have fun.....please post any issues....thanks...

Congrats!

Need to see it!

BTW, for exe I would add somewhere scaling buttons (or FS context menu) to resize gui on smaller screen (otherwise full gui is not visible; GDI limits on that?)

Bug 1: When clicking on editbox of preset ("Program 1:..." thing) - text becomes invisible until exit from editing.

BTW2: where is "start" button? Oh, found it.

Bug 2: on stop (exe), show list, when trying to change the program - app crashed.

Hi Bill!
How are you?
I admire your perseverance and skilfulness, but I fear that you will grow old beside of X11. I actually did not dare to open it on my poorly computer. It would disintegrate. He-he...
Anyway, I wish you much success.
Cheers!
I said to myself... watching here...

tester wrote:otherwise full gui is not visible

S##t...I did notice the gui was wrong on the laptop......I thought it was my laptop!!!
Don't recall this issue before.....did it come with FS or now with 'raindrop'..??

tester wrote: text becomes invisible until exit from editing.

Yeh I did a last minute fix there.....was using Prest manager prim to save titles,
but got annoyed with the character limits, so changed it to a simple array.
Did see that bug, but got lazy at the time and let it go..

tester wrote:Bug 2: on stop (exe), show list, when trying to change the program - app crashed.

I can't replicate the error here....
Can you make the error happen again tester ??? (thanks for your time)

tester wrote:Need to see it!

This update was a ballbreaker man...3 pages of notes and fix's....
I remember in one of your posts you mentioned the logic of putting everything on smaller
arrays for saving presets. I did have a small plan when i started preset stuff, but
wasn't too sure how it would end up....Seems to work OK the way I've done it....
Would like to know what you think on this tester.....ideas to improve..???

pall wrote:How are you?

Alright mate..resigned my job last month.....un-employed in a few days...

pall wrote: I fear that you will grow old beside of X11

My hands are shot with arthritis and tendonitis, making it a bit hard to play instruments...
I think FS will play a big part in my retirement....

S##t...I did notice the gui was wrong on the laptop......I thought it was my laptop!!!
Don't recall this issue before.....did it come with FS or now with 'raindrop'..??

Nope, from the beginning (SM). That why I work to make the gui's fit certain "minimum" screen resolution, adding tabs if necessary. On your place I would add more space by adding some tabs - easy to do and can handle a lot of stuff. This would also help to split the logic of things I guess. If you play with sequences, then you don't play with modulators for example, and so on.

I can't replicate the error here....
Can you make the error happen again tester ??? (thanks for your time)

Need to switch computer (tomorrow). FYI C2D 2GB Ram XP and no virtual memory set.

This update was a ballbreaker man...3 pages of notes and fix's....
I remember in one of your posts you mentioned the logic of putting everything on smaller
arrays for saving presets. I did have a small plan when i started preset stuff, but
wasn't too sure how it would end up....Seems to work OK the way I've done it....
Would like to know what you think on this tester.....ideas to improve..???

//edit: next post. Seems to work fine here (tested under load and heavier gui, but will be tested further when I finish the basis - maybe within the month or two). But as I said - I think it's best for static switches, non-automated and slowly refreshed values, otherwise may will kill the app. I guess there might be a borderline of amount of parameters (somewhere between 1000-1500?), that determine whether to store individual values or arrayed strings.

Here is draft preset logic I suggest. It generally works. If it has some bugs in complex implementations (trigger order), then should be simple to fix. You can group that way various switches and values. But as I said - the bigger single array you make - the more problematic it will become, especially if there are lags from some incoming nested modules. I would not add there any trigger blockers, let the array pass through always.

Here is some logic to follow. (It also refers to hoping in streams). If you have 1:1 system, then it's heavy. if you have 8:1 system, then it's 8x lighter (8000 parameters vs 1000 parameters or 40% CPU vs 5% of CPU). It's like with MP3 compression - some aratio is fine.

p.s.: if you are using it in synced modules, then don't change the indexes via "gui properties" on float prim; just go inside the module and change the value in the float prim. Synced modules don't copy user values sent from gui.

tester wrote:Nope, from the beginning (SM)

Thanks tester...
will fix standalone online straight away with "include context menu for zoom & exit "
Don't think i'll re-tab it......think the X11's gone too far.....
After seeing trog's knob( that dosn't sound right does it..? ) I started getting visions
of a new X11, one that wasn't an experiment from start to finish, taking everything
I learned in X11 over last two years and try to build a commercial version....
I don't know.....toying with lots of ideas......most of 'em go nowhere

tester wrote:That why I work to make the gui's fit certain "minimum" screen resolution

Ok..create within the insurance policy.... so that's 800x600..???....yes..??

tester wrote:Seems to work fine here (tested under load and heavier gui, but will be tested further when I finish the basis

great..thanks.....take your time...
EDIT:
and looks like vst version needs the zoom prim put in the fsm ...not in the build menu..
EDIT2:
thanks for fsm.....going through it now..
EDIT:3
damn..'exe" zoom really does mean exe......hmmmm
could make an extra vst, shrink it down in FS, and offer a small version as well if anyone
in vst world complains about size...