INVISIBLE WIRES

infuzion · 14 Dec 2007

There are wireless connectors already. It would be neat to be able to hide & show the connectors with a key press though. And when hidden, show only the connectors to a selected module/primitive.

BALTHOR · 14 Dec 2007

If I connect everything together with wireless how does wireless know which connections are mated.

BALTHOR · 14 Dec 2007

If you could label the wireless connectors to match the input and output then your entire construction could be wireless.I have provided an example of wireless.

http://www.speedyshare.com/573854937.html

tention · 14 Dec 2007

BALTHOR wrote: If you could label the wireless connectors to match the input and output then your entire construction could be wireless.I have provided an example of wireless.

http://www.speedyshare.com/573854937.html

Like explained in the component reference document...

BALTHOR · 15 Dec 2007

Here is an exact example of wireless connectors.Right click on the circle end of the connector to change the connection type!If the wireless link out did not work then use the module wireless output type.

http://www.speedyshare.com/332308164.html

infuzion · 15 Dec 2007

BALTHOR wrote: If I connect everything together with wireless how does wireless know which connections are mated.

You do not connect everything 100% wireless since it can become confusing. I usually keep the main audio path as regular links for example. In one of your files, it is too much work to rearrange the audio paths as one is doing more editing (you have to go inside atleast 2 sub-modules). There are some wireless conventions (assumptions) that the SM devs and most of us assume; use a wireless View in for all the typical GUI controls for example.

Sometimes as I'm developing a schematic, I add links between INs & Outs, then move pieces from outside to inside the sub-module so I don't have to use those Ins & Outs, combine multiple Outs into a single bus, or turn a wired Out into a Wireless Output... Just like regular programming, you make alot of changes. More changes if you do not diagram your program before you write it.

sunsynth · 15 Dec 2007

exactly infusion:

You do not connect everything 100% wireless since it can become confusing

This is the reason why i asked 4 a Parts-/Connection-List in SM!

After some weeks even myself cannot remember all this wireless Cons of my own schematics... 😉 🙁

SUNsynth

BALTHOR · 15 Dec 2007

In 'Examples' I show SM's synth as wireless.I write a synth in Synth Edit or Synth Maker then render it as a VST dll for FL Studio and another SM as a stand alone exe.The VST synth in FL Studio sticks and glitches and the exe synth sounds uncolored and cleaner,it even operates better.I have two of my synths displayed also in 'Examples'.I will try anything to get my Synths to run better.For me wireless just might do it.So what is digital?It's not transistors or tubes.It's a file line that sits in the computer's memory and as the memory is clocked the digital runs.My exe synths render at about 1.3 mb.My computer's memory is one gig.

infuzion · 16 Dec 2007

BALTHOR wrote: I ... render it as a VST dll for FL Studio and another SM as a stand alone exe.The VST synth in FL Studio sticks and glitches and the exe synth sounds uncolored and cleaner,it even operates better.I have two of my synths displayed also in 'Examples'.I will try anything to get my Synths to run better.

The connectors have nothing to do with the glitches in FL. It is likely: 1) Audio buffer in FL not set right. 2) When computers have a too busy CPU, you'll get bad audio. FL might have a CPU meter, but the better one is from the OS. In WinXP I [CTRL-ALT-DEL], Processes tab, & look at the CPU % column. Also look at "System", since I think that is the OS stuff like audio, HD usage, etc.

BALTHOR · 16 Dec 2007

My original request was for invisible wires.When I construct a synth the wires get so thick that I can not click on a module.Wire bending is fine but in the throws of design there just isn't enough time to bend the wires.When the buffer length is set in FL with their 'Diminishing Returns' slider a choice has to be made.Either high fidelity and a delayed keyboard response or the opposite.The GUI in my synth sticks in FL Studio but not in the exe.My synth sounds colored and squashed in FL Studio but not in the stand alone exe.Somebody is going to say that I designed my synth wrong but the exe works just fine.1.3 mb shouldn't overstress anybody's host.The SM modules contain all of the file information necessary for the functioning of the file.So what does the CPU do?Some will say that the CPU does all the math for the reverb unit but I say that this information is self contained in the module.When the computer boots the OS is copied from the hard drive to the RAM memory---so what does the CPU do?I don't like the term CPU usage--it's nonsense.