From the original SynthMaker forum (2004–2014), with its members’ names and dates.
beno ·
Often while working, I've added a few modules/components to a schematic to help me debug some problems that have occured. In my never ending quest to keep things as CPU efficient as possible, I've deleted these after the problem was fixed, only to find that I really still need them hanging about. It would really be helpfull if I could leave these in the schematic but somehow switch them to be active or not at a given time. I was thinking it would be cool if I could designate any module or component to be a "debug" module for the schematic, and then a switch/key command/menu item could globally enable/disable all modules assigned to be "debug". It would be like different build styles in the coding world. Would this functionality be usefull to anyone else? Am I explaining myself clearly?
Ben
Hengy ·
i like this idea
also i wonder if there could be some built in debug tools available within the synthmaker environment - maybe a debug mode that shows events and data flow (maybe showing the presence of triggers/data at a modules inputs and outputs, and/or a probe tool (thinking of the kinds of things labview has)
i'm not sure how feasible these would be, and maybe beno's idea is more useful. isn't there already the abiltiy to switch in and out modules? not as simple as a global debug on off switch though
rl ·
(since stefancrs is on vacation, I'm taking over the "its already doable" part):
if you connect your "debug modules" not directly to your schematic, but using a selector in-between you can disconnect or switch-off your modules. So they take no CPU-load.
But it's a nice idea, nevertheless
beno ·
rl wrote: if you connect your "debug modules" not directly to your schematic, but using a selector in-between you can disconnect or switch-off your modules.
Thanks I new about that method but that isn't very elegant and creates a much more messy schematic then I'd like. I think something along the lines of what I described could be really usefull. It could also be expanded to an arbitrary number of grouped components that could be switched in and out of the schematic at "compile time" so to speak. Could be usefull for trying out different implementations. But thanks for the help.
Ben
rl ·
beno wrote: ...and creates a much more messy schematic then I'd like...
This is a valid point. May be we need more ToChild, ToParent modules (for all kind of connector types). E.g. I'm playing around with midi automation: wires all over the place, looks almost loke my signature pic.
<===
Tom7777 ·
radio signal/wireless bus modules is what we need i think,
ect, each reciever module set to the senders signal would recieve the connections so you could have hundreds of the same group of things if you wanted. Thats what i think we need anyway, anyone like this idea? 🙂
Shifrin ·
Tom7777 wrote: radio signal/wireless bus modules is what we need i think,
ect, each reciever module set to the senders signal would recieve the connections so you could have hundreds of the same group of things if you wanted. Thats what i think we need anyway, anyone like this idea? 🙂
That's a very good idea, would make the creation of a mod matrix much cleaner (far less wires everywhere!).
Shif.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker