SynthMakeroddson ·
The schematic for this high-level module would be greatly improved by a wireless sample rate connection where needed.
Parametric EQ
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
stefan ·
As stupid as it might sound, I try to avoid using wireless connectors. I'm always afraid of conflicts with something else using the same name/type 🙂 In my own things, stuff that isn't supposed to be a module for the toolbox, I don't mind using them though.
I might have to change my behaviour if more people think I should I guess 😊
Tom7777 ·
Well i dont really think it matters that much, they sometimes help make the schematic simpler but i think that is often for someones own projects, when loading other peoples examples which are using wireless connections it can sometimes be annoying trying to find where the other wireless links are.
dasdeck ·
i think someone mentioned it, i think we need some "search in shematic for specific comps" feature. for example you could search for the name you gave the component, or the corrosponding ends of wireless conncections.
D3CK
sambean ·
As stupid as it might sound, I try to avoid using wireless connectors. I'm always afraid of conflicts with something else using the same name/type
I hadn't actually thought of that.. I tent to just go for the first name that comes to mind.. I noticed in Shif's ADSR he'd used quite complex wireless titles.
I may be a good idea for module developers to take heed, if they are using wireless connectors, they should perhaps prefix all their wireless connections names with a kind of ID code, so for example in my waveshaper, instead of just having 'X Mouse' I should perhaps use 'SM.Waveshaper.X Mouse', recuding the chance of a conflict..
Sam
Shifrin ·
sambean wrote: I may be a good idea for module developers to take heed, if they are using wireless connectors, they should perhaps prefix all their wireless connections names with a kind of ID code,
Couldn't agree more! It's a pros/cons thing as to whether to use wireless connectors or not - I find they can make things a lot simpler to understand (where dozens of wires may obscure signal flow...) but there are indeed pitfalls (like ambiguous/conflicting names...) and perhaps to someone else things may be less clear!
Shif.
oddson ·
I tend not to use wireless unless there is a significant benefit from doing so. I'd say this qualifies.
Since it's a universal property, and it's name is pretty much self explanitory, if a person is looking through the schematic and finds a wireless called "Sample Rate" they're going to assume that above somewhere is a wireless transmitter pumping out the SR from the timing info module.
stefan ·
oddson wrote: I tend not to use wireless unless there is a significant benefit from doing so. I'd say this qualifies.
Since it's a universal property, and it's name is pretty much self explanitory, if a person is looking through the schematic and finds a wireless called "Sample Rate" they're going to assume that above somewhere is a wireless transmitter pumping out the SR from the timing info module.
Actually, I've now decided that I _don't_ agree in this case. It'd be much better if I just would've placed TimeInfo components internally in the modules that need them.
oddson ·
Wouldn't that be slower than a single Timing Info component? 😕
dasdeck ·
oddson wrote: Wouldn't that be slower than a single Timing Info component? 😕
if SM pathes pointers to the timing info variables it should not matter, as it would pass a pointer each time you get the infos so and so.
i guess it gets optimised like if you make many modules in each other and path a variabel through them
stefan ·
oddson wrote: Wouldn't that be slower than a single Timing Info component? 😕
No, basically they all are referencing the same variable, if I've understood Jorge correctly 🙂
dasdeck ·
stefan wrote: oddson wrote: Wouldn't that be slower than a single Timing Info component? 😕
No, basically they all are referencing the same variable, if I've understood Jorge correctly 🙂
thats what i wanted to say with my post. your's was more elegant and short. 😉
D3CK
oddson ·
stefan wrote: oddson wrote: Wouldn't that be slower than a single Timing Info component? 😕
No, basically they all are referencing the same variable, if I've understood Jorge correctly 🙂
What about memory use, does SM allocate memory for each Timing Info component and would it be more than each wireless connection?
Wrote something here? To have a post removed or your name hidden, write to [email protected].