From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
In my quest of tring to squeeze the most out of SM up to the point of breaking, I wondered how flexable we can make the bus system. I came up with this idea to split data out of any bus with needing to know only one channel.
How about listing all of the channel names in the first channel?
Since you can have a string channel, just put a channel listing title name 1st in the listing, & connect the same Data:String to the first 2 connectors.
For this example, we'll edit Jorge's CustomParser2
When you want to split out the bus channels, you only have to remember the first channel name:
You may notice in the picture above that there are more than the origional items in the bus. That's because you can sum bus channels:
Channel order depends on the connection order. You can have the source bus have different names for it's channels. Let's look inside the second controller sub-module:
You may notice a trailing comma at the end of each Data:String for the channel listing. This is needed to keep values from running into eachother when you sum the busses.
--
This leads me to 2 questions:
• Would it be better if there could be some reserved words for the names assigned to the bus channel list for Extract to automaticly pull out channels (eg "all", "allMIDI", "allFloat")
• Should we start a certain naming convetion, so as we splice together eachother's modules, we can use someone else's modules quickly withought having to study their code to understand what each connector/bus channel is for?
cheers
jorge ·
infuzion wrote: How about listing all of the channel names in the first channel?
🙂, why didnt I think of that?
I think its a great idea.
skOre ·
Yeah, always having to put in the channel names is a real pain!
[edit]plus it would make self-scaling things very possible! Yummy![/edit]
jorge ·
skOre wrote: plus it would make self-scaling things very possible! Yummy!
You mean you'd add an input in the BusCreate and it would be automatically updated at the BusEnd? That's really good.
skOre ·
Uhm, I just meant "That would be great"... does it work?
jorge ·
skOre wrote: Uhm, I just meant "That would be great"... does it work?
I didnt try it. If it doesnt work, it should and we should change the code so it does.
infuzion ·
skOre wrote: Uhm, I just meant "That would be great"... does it work?
oh yea, all snapshots you see are live; it works perfectly, even with summing the 2 busses... . save a little bug that forces a reconnect of the first and second Extracts you see in the second picture :/ But reconnect & everything is fine. I didn't post the file becuse of that bug, & it will make people scratch their heads.
infuzion ·
Anothe caveat (if you don't know SM's bus system well) is that items are assigened numbericaly, not by name like passing variables in subroutines in VisualBasic or other programming languages. So if Sift made a module with a bus output & I build using it, Sift can't really add anything new the the bus output because my Extract connectors will be messed up if he does. Example:
VCFModule_Bus_v1.1 has:
• MonoLeft0
• MonoRight0
• MIDI
• View
Then Sift improves it so VCFModule_Bus_v2.0 has:
• MonoLeft0
• MonoRight0
• Poly0
• MIDI
• View
All my Exctract connectors that use his bus's output after MonoRight0 will be still connected, but vary incorrect.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker