selected module should show a stable higlightled wires...
Archive · 200918 old posts
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
noise_maker ·
I also think that the wires should be gray and thin by default (or just thin, but very thin...), and when you select a module, it will show the wires that connected to it and from it green and thick (and the wires highlighted until you press-mouseclick on another module or on the empty surface)
I know that right now there is a small highlight when you press on a module, but it goes away when you move your mouse over other wires and it isn't highlighted enough anyway.
Having a stable highlighted wires will be really useful for issues like in the picture.
sunsynth ·
Hmm,
i've made many such picassos when i started with SM... 😉
You better use the magical Wireless Links or/and the great Bus-System SM offers U!
Check it out!
Walter
Nu Audio Science ·
Yeah i used to have serious issues like that too
Wireless is your best friend 😉
NAS
noise_maker ·
Nu Audio Science wrote: Yeah i used to have serious issues like that too
Wireless is your best friend 😉
I use tons of wireless connections already, but sometimes wireless is not the best choice (like in the current module in the picture, because with wireless I would need to write about 120 different names one by one, and everytime I duplicate this module I will need to write new names so the selectors will not effect all the modules as one...)
oddson ·
It's an interesting suggestion... as such Ideas and Requests seems like the right place for it.
As for whether there's a better way to manage the complexity there are some tricks that may help but sometimes the wire nest practically unavailable.
I'm working on a knob matrix where the values are written into an array of floats. A single integer value keeps track of which knob is being tweaked so that only those receptors with that address will get the message to use a Get At primitive to extract the changed control.
stw ·
A similar request is already adressed here:
invisible links
Nu Audio Science ·
oddson wrote: I'm working on a knob matrix where the values are written into an array of floats. A single integer value keeps track of which knob is being tweaked so that only those receptors with that address will get the message to use a Get At primitive to extract the changed control.
I'm currently working on a dynamic control section in my plugin that uses a similar technique heheh
NAS
oddson ·
Here's a sketch. The issue of presets would still need to be addressed and I sure a dozen other little problems but it's a proof of concept.
aliasant ·
oddson wrote: Here's a sketch. The issue of presets would still need to be addressed and I sure a dozen other little problems but it's a proof of concept.
What about a VST parameter Array for the presets. Instead of that Float Array ?
kirkagur ·
Hi
Ad GUI For Easy Link&Midi Learn&Monitor
You can look at this......its all what you want. 🙂
just copy the knob and its in the list!!!!
noise_maker ·
cool stuff guys, but you can't ignore wires...we need them 🙂
It can't be a bad thing to make the links more thin by default, and when selecting a module the links that connected to it will be more highlighted and stable untill I click on another module or the surface with a mouse click.
even if you guys have great ideas of wireless, it can't hurt to have a better wires system.
oddson ·
oddson wrote: It's an interesting suggestion... as such Ideas and Requests seems like the right place for it....
It's worth a post in the the Ideas section. OutSim doesn't read everything anymore but Malc tells me they do review the ideas and bugs sections.
noise_maker ·
oddson wrote:
oddson wrote: It's an interesting suggestion... as such Ideas and Requests seems like the right place for it....
It's worth a post in the the Ideas section. OutSim doesn't read everything anymore but Malc tells me they do review the ideas and bugs sections.
can you move it to the ideas section? (I see that you are a mod)
Nu Audio Science ·
Dah dah 😀
Done
NAS
TomC ·
noise_maker wrote: I also think that the wires should be gray and thin by default (or just thin, but very thin...), and when you select a module, it will show the wires that connected to it and from it green and thick (and the wires highlighted until you press-mouseclick on another module or on the empty surface)
I think it'd be a good idea in general to have the wires to selected modules in a different color
On an additional note, if your schematic (or a part of it) looks like yours it's a good time to re-think your architecture in general to be able to break it down into simpler sub-modules. This one's a mess.
As a rule of thumb for beginners, as soon as you need above average concentration to follow a link in your schematic it's time to make sub-modules with self-explanatory names. The longer you wait to do this, the harder it will be.
You will thank me later.
Tom
noise_maker ·
TomC wrote:
noise_maker wrote: I also think that the wires should be gray and thin by default (or just thin, but very thin...), and when you select a module, it will show the wires that connected to it and from it green and thick (and the wires highlighted until you press-mouseclick on another module or on the empty surface)
I think it'd be a good idea in general to have the wires to selected modules in a different color
thank you.
On an additional note, if your schematic (or a part of it) looks like yours it's a good time to re-think your architecture in general to be able to break it down into simpler sub-modules. This one's a mess.
As a rule of thumb for beginners, as soon as you need above average concentration to follow a link in your schematic it's time to make sub-modules with self-explanatory names. The longer you wait to do this, the harder it will be.
it is harder for me to explain to you why I need those wires...but believe me, they are needed in this case...they save me lots of time when I want to duplicate that same module in away that I won't need to rename 12 outs and 12 ins everytime that I want to add more controllers without selector conflicts.
Basically if I will use wireless in this issue, I will get Selectors conflict, and I will need to change the wireless in/out names 1 by 1.
TomC ·
noise_maker wrote: it is harder for me to explain to you why I need those wires...but believe me, they are needed in this case...they save me lots of time when I want to duplicate that same module in away that I won't need to rename 12 outs and 12 ins everytime that I want to add more controllers without selector conflicts.
Basically if I will use wireless in this issue, I will get Selectors conflict, and I will need to change the wireless in/out names 1 by 1.
I'm not talking about wire vs. wireless connectors. Someone who writes what's called 'spaghetti-code' will always say that he needs all those lines of code, and he's most probably right.
What's wrong is the general approach, and the missing/wrong modularization.
Tom
noise_maker ·
I guess that you are right in your own way.
I was a reaktor user for than 8 years, 2 weeks ago I decided to move to SM, I have a lot to learn and I'm very excited about it ^^
Anyway, I hope that Malc will adjust the spaghetti's thickness and highlight the chosen sticks 😀
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker