SynthMakerbones ·
1. What does the Poly to Mono component do?
2. How can I see what is coming our of different outputs? i.e. SE's CV-gate paradigm makes it easy with a volt-meter and scope. What are the SM equivalents?
BONES' Special Questions - Simple Answers Required
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Nu Audio Science ·
I use a float in the data section and connect it to the offending output 🙂
On the Poly 2 Mono i would be guessin so i wouldn't be too useful to be honest 😉 I only came from SE myself about a month ago or so 🙂
infuzion ·
bones wrote: 1. What does the Poly to Mono component do?
Poly = multiple audio streams at once, so all Poly to Mono does is to reduce a Poly to one stream. I think you can connect a Code:Text View to the String output some fancy machine code as you play.
bones ·
If that's true, why is it that without one before output, all you get is a continuous stream of low-pitch sound that doesn't respond to MIDI input? Clearly it is doing way more than you describe.
stefan ·
bones wrote: If that's true, why is it that without one before output, all you get is a continuous stream of low-pitch sound that doesn't respond to MIDI input? Clearly it is doing way more than you describe.
Not really, the main issue here is that SM, if directly conneting a Poly section to a Mono connector (like the outputs), SM will pretend that the poly section is a mono section. And this is too unclear at the moment. Basicly, what needs to be done, is disallowing such connections without the user specifically and visually in the schematic "converts" the poly section to a mono one (not the signal, the section).
malc ·
Hi bones,
1. You're right, the Poly to Mono does more than just merge the mult-channel data into one audio stream. It compiles the Poly section into machine code. Without this no sound processes can begin and so you won't hear anything.
2. Have a look at the example below. You can use the Poly To Graph to observe a signal passing through the Poly section and Mono To Graph to look at the signal in a Mono Section. These two work slightly differently. The Poly To Graph only looks at the first 2048 samples of the signal. The Mono To Graph takes a user defined number of samples every time you send it a trigger. I've used a Ticker25 to do this 25 times per second. The outputs from both components are fed to displays.
You should be able to do more dynamic analysis with the Poly To Graph, we just haven't got round to doing this yet.
[old link]
I'm in the process of writing some documentation on how the sound works to go alongside Jorge's tutorial which I hope will help but in the meantime do please keep asking questions.
bones ·
Just remember that you said that. I can guarantee you will come to regret it sooner rather than later.
skOre ·
Nope, I'm always surprised by the devs patience !
malc ·
bones wrote: Just remember that you said that. I can guarantee you will come to regret it sooner rather than later.
Whilst I did encourage you to ask questions I didn't promise to answer them 😉
...but I will of course 🙂
(bracing myself for an avalanche)
Rellik ·
I've got a question that goes with BONES's questions...
How come if I connect a Float data module to a Mono output, I don't see anything reflected in the module? And if I connect the output of the Float data module to an output, I don't hear the signal being made by the original mono output - shouldn't it just be accurately reproducing the signal?
The reason I'm trying to do that is because I wanted to make sure that the headroom is from -1 to 1, in value
malc ·
Hi Rellik,
All the green connectors represent triggered data. This flows through the schematic based on events which we call triggers. Link one Float to another, type in the first one and you'll see the other one update. When the value changes in the first float it sends a trigger to it's output, this flows to the input of the next float which then asks the first float to tell it it's value. In short data only flows when something changes.
Mono and Poly data are completely different. For Mono (and for Poly when a note is played), data is constantly flowing at sampling rate. You can't feed this into the triggered data directly because it would lock out the system - changes would be too frequent.
What you can do is use the Mono To Float or Mono To Graph components to look at the Mono signal at frequent intervals. Connect the trigger input of these components to a Trigger25 and you'll get a refresh 25 times per second.
Nu Audio Science ·
Keep askin the Qs, I'm learning loads here 🙂
bones ·
Here's another one - I noticed when dragging things into the Schematic that, on very rare occassions, connections are made automagically. I often see the dotted line as I drag one component over another but on a coupel of occassions it has made connections for me. Is there a trick to this?
unkargherth ·
Yes. You can control this behavour on Options>>Schematic
Tom7777 ·
Here's another one - I noticed when dragging things into the Schematic that, on very rare occassions, connections are made automagically. I often see the dotted line as I drag one component over another but on a coupel of occassions it has made connections for me. Is there a trick to this?
I think this must be because you have Automatic Linking turned on, to turn it off click on Options and then just make sure that it is not ticked. That should sort it out for you. And just select it again if you want to use it.
skOre ·
bones wrote: connections are made automagically
😀
Remember that this will only work if you have one module at hand. I think it should go on the todo-list of the devs to make this work even when you have more modules dragged.
malc ·
Yeah that's on the list skOre thanks.
As Unk suggested bones, if you look in the options you'll see that there are a number of ways of configuring the automatic linking. Personally I like to have it switched on but have it so that links are not created after a time period. Instead, I right-click to turn a suggested link (dotted line) into a proper one when I want to. I use this all the time.
bones ·
OK, so its inconsistent because its a time-out thing. Cool, thanks.
If you want to use what we call "kissing" to make connections in the Schematic in Flame [film/video compositing], you just hold down the ALT key while you are dragging and it makes connections. Leave the ALT key alone and you have to make the connections manually. Much better than a Preference setting, no?
Wrote something here? To have a post removed or your name hidden, write to [email protected].