BrainModular

Hi all,

just to inform that a new section "user modules" has been created in the wiki to submit ideas for usine futur user modules developement, feel free to edit/udpate if you think you have a useful new module idea/improvement, and maybe some generous coders will make the toolz you/we dream about possible

link
http://www.sensomusic.com/wiki/doku.php ... ules:index

good idea
we are working hard with Martignasse on the future SDK implemenation.
will be a great improvement.

your list contains a good set of important modules.

great, i wish i could help you, but i can just submit ideas

the NOT Array will be included in the next release.
also all Logical operators will work on array's.

excellent!! woa all logical, crasy, will use that a lot!

from the wiki page

23fx23 wrote:RGB color : convert RGB (red, green , blue) values to usine color.

HSL color : convert HSL (Hue, Saturation, Luminosity) values to usine color.

For these modules, what value limits is better for manipulations in patch ?
- RGB module with R, G, B from 0 to 255
- HSL module with H from 0 to 360, S and L from 0 to 1

need feedbacks and point of view.

thanks

hi martignasse, great if you are looking at it;;;; good reflexion,

in fact its's hard to say in an objective way, but from what i feel with use, thinks' it's better to reduce to 0..1 range for all values, cause otherwise we might often add multpliers modules. RGB of 0..255 would be better for classical true color selection, but 0..1 would be easier to say "if sw is on then it's green, if off it's red, with less modules".

I had just a doubt for lum setting: in my pach aproachs from 0 to 1 color was going from black to satured color (unchanged) and from 1 to 2 is to lighter it (from satured to white) so 1 was unchanged color, was efficient when paching, reducing to 0...1 range would mean unchanged value become 0.5... and we may later often add /2 module... for uniforming might be better all 0..1 also....

Hue: 360 for hue is an interesting value cause i's really a cicle of colors, but thought of anothe,r maybe more handy solution:
as there are 7 colors in the raimbow hue circle (red,yellow,green,cyan,blue,purple,red again) a 0..6 range or 0..12 range could be (red,orange,yellow, yelgreen,green cyan,cyanblue,blue,bluepurple,purle,pink,red)
be a good solution to quick assign an integer as a color (I want it green, then hue is 5, blue is 7 ect..). that's the way ive chosen and seems powerfull. (also 12x30 is 360 so it's just a muliplier, but we might try to choose the solution that would require less extra modules while paching)

hard choice hehe, my feel if need to choose to have one uniformed range, to go for 0..1 range might be the best for paching. but It also depends if usine will deal will extenal datas that might be coded in 0..255 range...

otherwise my prefered solution, tested in my pachs as quite handy would be R (0,1) G(0,1) B(0,1) H(0,12) S(0,1) L (0,2)
exemple: if swich is on its blue, then if there is a note it's white, if off is unsatured, if off it's black would give the values: (H7,S1,L1) then (H7,S1,L2) then (H7,S0,L1) then (H7,S1,L0) (see the HSL in /data has this behaviour, can try to repost a tiny more clear version if can help)
but it's subjective, if someone has suggestions...

mmmm don't know if i really helped you there

hi 23fx23,

yes, you helped a lot.
your experience in manipulating the HSL domain in patch is very interesting.

like you said, it's very hard to make a choice, cause every use has his 'easier range of value' for manipulation with modules.

unification is very important to keep modules coherence, but shouldn't stop us to choice pertinent range when appropriate.

for the RGB module :
0->1 for RGB seems the right choice.

for the HSL module :
0->12 seems better for Hue, as it's synchro with the 12 basic colors.
the symmetry around 1 for Lum is important too, (black:0 -> saturated:1 -> white:2)

in fact my conclusion is the same of yours
R (0,1) G(0,1) B(0,1) H(0,12) S(0,1) L (0,2)

but for sure, other feedbacks are very welcome

cool if we have same conclusion.. this is how i was mapping RGB values for the hue in 0,12 range, don't know if can help, never know:
sorry hand made hehe

cool drawing

lot more sexy than the algorithm (ugly math code) i use for the module,

who i suppose do the same thing, at least done the same result.


but you'll have to wait the next version...

hehe no pb, you and senso are already faster than i could ever dream about

last question about these future modules,

what default color(when you bring up the module), black or white ?

mmm, hard to say, i would go for black maybe so if we bring lum in it lighten?

woa just checked the list and you already made alot of damage guys amazing job!