From the original SynthMaker forum (2004–2014), with its members’ names and dates.
tester ·
I'm having a problem with wireless connections, and don't know whether this is a bug or something in wireless philosophy.
Let say that I have a wireless receiver and two wireless transmitters to that receiver (and to be precise - connection type are set to triggers). Sometimes, when I connect second wireless transmitter, then the first one gets deactivated, and they just behave that way - one acivated, second one deactivates, as if they could not transmit at the same time. As far I can observe - sometimes this is between "wireless out" and "module wireless out" primitives, and sometimes between the same kind of wireless. Is this somehow related to hierarchy of modules? How to solve it? What is going on here?
loopeytunes ·
The "module output wireless" can only send messages from out of a module and then down into another module or down into modules within that module.
The "wireless output" can only send messages into other modules or down into modules within that module.
Loopey
loopeytunes ·
also you have to name them the exact same and make sure the they are the same connectors
tester ·
You misunderstood.
Read again please.
Sometimes - working wireless transmitter (no matter which type) stops working (deactivates connection) after another transmitter gets the same name. It happens sometimes (in some situations), not always, and I don't know what determines that kind of behaviour. Wireless have fixed connection types.
loopeytunes ·
I understood.
You need to make sure that when you attach the wireless output/input you make sure you select the connector type by right clicking on the circle on the wireless output/input and select the connector type (trigger in your case).
If you connect the wireless output/input to an output/input is does show the connector type but by default the connector type is still set to nothing, so if you then disconnect/connect another wireless elsewhere you then need to choose the same on that one.
If it still automatically disconnects after you've done this then I can't suggest anything else apart from like you say it must be a bug.
Loopey 😀
tester ·
So you misunderstood. 🙂 Everything was checked. It looks like a bug, but I suspect, that there might be some module hierarchy (in which connectors are stored; like folder hierarchy) behind that.
loopeytunes ·
I've never had a problem with wireless connectors by doing it the way I've stated above.
🙂
tester ·
If I find some time, I decompose the schematic to leave only problematic part inside. Maybe you are just making very simple schematics 🙂
I bypassed the problem by redirecting with differently named wirelesses, which connect to wireless inside proper modules. However it seems to be a discrete hierarchy problem there.
stw ·
tester wrote: If I find some time, I decompose the schematic to leave only problematic part inside. Maybe you are just making very simple schematics 🙂
Providing an osm containing a potential bug is always much more meaningful than throwing in some complaining about it which often discovers as a misunderstanding of operating methods inside SM!
So if you expect precise help in a certain topic please try to provide test environments which narrow as far as possible to the topic you're referring to!
Telling willing helpers that they just didn't dig as deep into SM shematics as you though they're dealing with it much longer than you sounds a bit snooty...
tester ·
I just asked if someone encountered similar problems with no intention to dig deeper right now. If someone would experience similar things, then it would show that there is something going on, and this topic needs further exporation... somewhen later. That's all. Maybe I'm just a little bit tired after hours of mechanical work, so I'm sorry if someone felt touched.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker