From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Tom7777 ·
Not sure, if this is possible but i think a view alpha would be cool, so basically a use would be when you turn something off and then to show this a control sets to half transparancy to show it's off, this is simple enough to do with a bitmap control etc but for complex custom vector controls you have to do this through the color controls for each part of the control (i think) which means alot more work than it would be if you had this module, maybe if not a seperate module that you would place at the start of a view path ( like the smooth) then as an extra control on the MGUI componant which would only effect the view if it had a set value going in (because it would be annoying going through all old projects), but imo a seperate module might be best because you could use it with wireless controls etc rather than going into a module. Maybe both would be best, but imo it would be useful for vector controls, thanks
Acrobat ·
Tom7777 wrote: Not sure, if this is possible but i think a view alpha would be cool, so basically a use would be when you turn something off and then to show this a control sets to half transparancy to show it's off, this is simple enough to do with a bitmap control etc but for complex custom vector controls you have to do this through the color controls for each part of the control (i think) which means alot more work than it would be if you had this module, maybe if not a seperate module that you would place at the start of a view path ( like the smooth) then as an extra control on the MGUI componant which would only effect the view if it had a set value going in (because it would be annoying going through all old projects), but imo a seperate module might be best because you could use it with wireless controls etc rather than going into a module. Maybe both would be best, but imo it would be useful for vector controls, thanks
That's a great idea, Dan! +1!!
I'd see it more like an extra MGUI input than as a separate module, because, like lots of inputs in SM already, it could be automatically setted to 255 by default when no integer input is connected. Otherwise, as a single module, could allow to fadeout single primitives a lot easier.
Anyway it's something I'd really use!
Tom7777 ·
Yeah, MGUI option would be great for sure, i was thinking maybe a seperate module also because you could use it on a upper level that was sending wireless links for example without having to have a MGUI based sub module, but either/both would be great imo. 😀
oddson ·
I would think, if it's implemented, it would be a primitive component similar to the translate and rotate primitives in that it could affect V data connected to its output.
A colour matrix input would allow both transparancy changes and other colour effects.
For a quick fix you could just overlay a semi-transparent colour field in the same colour as the background overtop of the disabled feature.
Tom7777 ·
I would think, if it's implemented, it would be a primitive component similar to the translate and rotate primitives in that it could affect V data connected to its output.
Yeah i was thinking along those lines, it would just need a float input 0-255 range, so just a 2 in 1 out type thing, but if you really want to do something special you have RGB inputs also which colorize the whole view in a similar way to the matrix 😉
oddson ·
If there was a 'Colour Shift' primitive that took a colour matrix as an input then and 'Set Alpha' module could easily be made from it.
Acrobat ·
oddson wrote: If there was a 'Colour Shift' primitive that took a colour matrix as an input then and 'Set Alpha' module could easily be made from it.
Think I saw something like that inside the ol' AudioOak collection...
Tom7777 ·
Bump for this, views therough busses, reset trigger input on the mono to float and a solution for stuck midi notes please 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker