Synth: X11

[tester]

Visions, job resignation... What did you smoke man?

As for resolution, I think the typical smallest resolution is 1024x768 (or x600 on tablets?) or so. Minus some borders (for menu start, app borders and so on). The old magical 800x600 is rather no longer in use.

Zoom and full screen don't work for VST, because gui is managed from within the DAW. Some DAWs will eat your screen, some will add scroll bars (like Reaper). Your app can be exported just "as smaller" (FS view = exported view), but it means - all is smaller.

[tester]

Could not replicate that error yet, but as far I can say - the app tends to behave unstable (hangs) rather often than rarely, Sometimes when switching gui/streamy parts, sometimes when requesting load of something.

I had similar issues in my apps, so few things you could play with are:

- turning whole audio off/on when performing some stream switches or external data loads (and/or turing off/on access to that streamy parts, remembering about green trigger order for what is off at first),

- backgrond running of multiple operations (if CPU is not an issue) and quasi-selectors (*1 + *0 vs *0 + *1),

- if possible - changing FS streamy selectors/multiplexers into green designs (may require some redesign of schematics),

- using ruby for switches and trigger arrangements - only if needed and not "because you can"; somewhat I have a feeling that ruby engine may turn off in certain cases, producing other sort of queue overloads in the system; in other words - focus ruby routines only on independent stuff and processing units only, but separate it from the rest of the nested (dependent on each other) party.

- bridging/separating the samplerate primitive; it tends to cause unexplained trouble for some reason.

[billv]

the app tends to behave unstable (hangs)

not good....havn't seen this yet...
I'm using standalone, making presets and hunting for bugs..
(found 4 very minor bugs so far) but no issues in general behaviour yet...

ruby engine may turn off in certain cases,

.....still a lot of things I'm taking on faith with ruby ....being a noob and all...
...was lots of weird stuff i saw during this update i still can't account for....
So i did try to limit what was changed to ruby......I was quite carefull not to go to far.....
700,000 parts sounds like a lot....but it's not much really, considering what they were..
500,000 was just from the selector....
A 200,000 'bonus' came from matrix re-build...
(I finally found the redraw bug I created in Myco's re-designed Matrix trigger, which allowed
me to delete 36 triggers, and use 1 matrix trigger for all 3 divisions, like Myco had originaly
designed in his re-design)..was real happy about that...

- bridging/separating the samplerate primitive

...struggling to get my head around that one....

Visions

Standard thing if you are creative..

job resignation

Standard thing every 12 months in my trade.....got to ask yourself...
do i really want to cook this stuff for another 12 months....???
am i learning anything in this kitchen...??
am i working or just sleepwalking through the day because I'm bored s##tless...
Chef's are never "out of work", only 'not' working by choice....everyone's got to eat...
Always heaps of work out there if I'm silly enough to apply....

What did you smoke man?

Only the best i can get..of course..

[tester]

bridging/separating the samplerate primitive
...struggling to get my head around that one....

Directly connected SR primitive may cause crashes in certain situations. If you don't know what I'm talking about - just forget it. If you encouter an often-crash situation with no ordinary reason, check if this behavior replicates when instead of SR prim - fixed value is provided. If there is a difference, then either you may need to turn off/on some stream on the go, or redesign SR theme (get SR on load/switch -> redistribute SR value -> disconnect SR).

So i did try to limit what was changed to ruby......I was quite carefull not to go to far.....
700,000 parts sounds like a lot....but it's not much really, considering what they were..
500,000 was just from the selector....
A 200,000 'bonus' came from matrix re-build...

As for amount of prims in FS vs stability/functionality - it's an illusion. App may have 700 000 elements and still be very stable. Crucial parts like selectors/switches (pass through type) decide about how it behaves.

[billv]

instead of SR prim - fixed value is provided

Get what you mean now...thanks for that.
there's about 6 SR prim's in the fsm....
If I start getting crashes in standalone or vst....will put in the fixed value...and try it
Will try it now in fsm to see if I can get an improvment in FS...

As for amount of prims in FS vs stability/functionality - it's an illusion

I got...smaller size exe and dll, bit faster load times...switching a bit faster......
But yeh...not seeing the stability in FS...in fact, that parts a disaster, cause
my cpu + X11 in FS is just wrong. Can't make any critical judgments in there...
Stuck on the outside with the standalone..

Crucial parts like selectors/switches (pass through type) decide about how it behaves.

I'm hoping it's just some bad coding....

[billv]

I'm hoping it's just some bad coding....

Need some 'ruby ' advice on some suspect code i got.....

This code works.

ScreenShot287.png (12.95 KiB) Viewed 30293 times

But to me, code is wrong....
I'm not telling ruby which input is "v"...
Should read 'if @state' , not 'if v'

But code works....
my question is....
should i bother changing it.....will it make a difference..???

I have about 60 of these in important positions in fsm...

EDIT:
Ok..so why does it work..??
Because @bank is used in the code...
So ruby automaticly process next available input as 'v'...??
So is ruby working harder to calculate this within the code...??

[billv]

Preset system got bugs.....
Online versions will be soon be re-adjusted and re-uploaded.
Start again.....hopefully get it right by Xmas...

[billv]

X11 UPDATED TO 2.07

* Preset system is under re-development and currently un-available...

[trogluddite]

You might need to change your 'suspect' code.

'v' is always the value of whichever input just changed - so it will work fine when the value of '@state' changes. But when the '@bank' input changes the code won't do anything because 'v' will contain the array, which can't be compared to a Integer. So you would be better off using the '@state' variable - that way, when the array changes, it will still look up the correct index.

[billv]

X11 UPDATED TO 2.08

* Preset System fixed.

The fix was in the heart of the preset system, so.....
The 2.06 "X11Data" folder is obsolete, as this is a 'new' system.
If you have a "X11Data" Folder, delete it before install.)
Note: This is a 'one-off' request...In future, the "X11Data" Folder is not to be
deleted as it holds all your saved data.
The X11 will automatically load any data found in the X11Data Folder,
so, to be on the safe side, it's better the 2.06 X11data folder be deleted,
as the system is slightly different.
* I created about a dozen quick presets, they are nore like small 'tutorials'..
where the preset will have only a few things on, so new users can see
how individual parts of the synth work.
*GREY AREA'S:
* If in "host/user" mode, and you switch to other Seq's, all on/off
switch's are turned off, as this is the default for the other seq's.
So your current preset will diss-appear. It's not a bug. If needed,
get your preset back be re-selecting it in the main index (or list).
* The following is not possible..
Saving a preset in host/user mode, with any of the 4 Mods routed
to Port or Gate. X11 will turn the mod off, and leave the Port or
Gate Modules in the synth 'ON' instead.
While this can't be saved in host/user mode...it can still be used....

*THE Sub Preset System:

What does that really mean...???
The whole Preset System can be controlled in sections...
Throughout the synth, you will find small up/down selectors like these..

These allow you to mix-up your presets and
easily create new ones.
To create with it, select the Program number you
wish to save at, in the "Master Preset Module".
Then flick through the sub-presetselectors and hit
save when done. Everything will now be saved at
the program number that was selected.

NEW STUFF:

* Added into the master Preset module is a button called "R".
It will give you a random title for the preset if your stuck. Thanks "Yuroun"


* Matrix Shifter/Randomization


* Using the knob will shift the whole matrix array...
* The Button will give a random array shift...
This is something I've always wanted, because the current
"Random triggers" always fills the trigger up too much...
Hit it, and the matrix is always 70% + full up...
So the shift can be seen as a different form of random,
where no new triggers are created, it's just shifting what's already there.
So If you use "shift" to randomize a sparse arrangement..
you will get back a sparse arrangement..

OTHER BUGFIX'S:

* Kill/Re-load triggers button behavior fixed .