From the original SynthMaker forum (2004–2014), with its members’ names and dates.
NothanUmber ·
Have tried to build some kind of semaphor mechanism with the aid of wireless inputs/outputs. My intuitive understanding of these links was that for each output a corresponding input is searched that has the same data type and the same name but that doesn't seem to be the case under all circumstances (e.g. when sender and receiver are used in the same hierarchy level in a module), so I wonder what the exact functionality of these components is and whether it is possible to somehow "trick them" to work like described above.
Greetings,
NothanUmber
oddson ·
...doesn't seem to be the case under all circumstances (e.g. when sender and receiver are used in the same hierarchy level in a module)...
Sender must be directly above the receiver in the hierarchy. You can trick it but making the receiver into a module by itself -- it's then at a lower level.
Of course if they're at the same level, what's wrong with a wire?
NothanUmber ·
Hi oddson, thanks for having a look!
Do you mean the left variant of the two from this example? Doesn't seem to work (but in theory it looks similar as it's done e.g. with the presets and gui stuff in the example synth so is this perhaps only working with yellow data streams? Or have I simply overseen a detail that's different (except the data types) in the example synth?)
Of course if they're at the same level, what's wrong with a wire?
Not(a th)Ing 🙂 It would just be nicer to have a generic solution were one doesn't have to care where the components are located but of course one can make different modules for the different cases.
Greetings,
NothanUmber
P.S.: for some reason the "receivers" module doesn't show the wire symbol in the upper right, presumably that's a bad sign...
NothanUmber ·
*sniff*, SynthMaker seems to hate me... 🙁
Here a schematic where I stripped down the example synth and my example to the minimal configuration - in my eyes they look absolutely identical - but in the one case it works and in the other one (of course my variant) it doesn't. (The only difference is that in the example synth variant the connectors are "glowing" and inside my module they don't - have no idea how to change that though...)
Greetings,
NothanUmber
malc ·
Hi NothanUmber,
I think the problem is that you have a Module Wireless Out (the label "Out" appears on the component) as opposed to a Wireless Output (the label "Link" appears on the component). I can see that the two look virtually the same so maybe we should do something to make them look more distinctive.
The Module Wireless Out effectively makes a module into a wireless transmitter/receiver.
NothanUmber ·
as usual... 😊
didn't look closely enough that there are two different wireless outputs, thanks for help!
Greetings,
NothanUmber
NothanUmber ·
Ah, the forum is up again, that gives me the possibility to ask another wireless links related question 🙂
Can the "Module Wireless Out" be used in order to send messages down the hierarchy (the opposite direction than the "link" links)? That would be very useful, indeed! (In contrary to that "interpretation" the description of the module says (as far as I understood) that a link between the parent module and modules that are below this module in the hierarchy would be established. So that would mean the difference to the normal link is that links that are at the same hierarchy level as the sender would also be able to receive the data?) Have tried to get the module to do anything in both directions (have actually placed receivers on every thinkable location up and down the hierarchy but none receives anything). Could anyone please give an example how the "Module Wireless Out" is supposed to be used? (Or is the matching receiver simply not implemented yet?)
Greetings,
NothanUmber
P.S.: Here my testfile.
angstrom ·
the best examples are in the 'style' of the example knobs under the /control group, notice that all the transmits for the styling parameters are "module transmits". They can transmit down into modules.
oddson ·
Just to clarify the wireless output component.
It transmits up 1 level only and then downwards from there. It is therefore equivalent to a wired output with an wireless transmitter connected to that one level up...
NothanUmber ·
Ah, thanks again angstrom and oddson,
haven't tested that variant (actually the sender is exactly searching for senders one hierarchy level up and a second one down again(*). Expressed in family relationships one could perhaps say he's searching for it's cousin 😉 ) Now a sender that searches for receivers all the way up to the root would be groovy 🙂 (That way one could place a module with global variables in a module located directly at the root of the hierarchy and then read (with the already available w-link connector) as well as modify these from every place of the schematic. E.g. optimal in order to have variables that are shared between all synchronized copies of a module (perhaps comparable to class variables or unique singleton objects in other languages).)
Greetings,
NothanUmber
(*) actually two hierarchy levels up and down...
oddson ·
On the family metaphor... can't talk to a cousin, just brothers, nephews and great nephews... 😉
NothanUmber ·
oddson wrote: On the family metaphor... can't talk to a cousin, just nephews and great nephews... Wink
was never good in memorizing family relationships... :P
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker