Joseph Weidinger

Here's some simple partial code that should work for anyone (part of something larger). I've tried and tried to understand why line~ is not behaving like I would expect it. It's not smooth. It starts to fade away and then doesn't get to 0. Then most often it seems like it starts from a higher number than 1 seeing has how immediately after I bang it, it gets louder before it starts to fade away then abruptly cut off. Any suggestions?

Here's some simple partial code that should work for anyone (part of something larger). I've tried and tried to understand why line~ is not behaving like I would expect it.  It's not smooth. It starts to fade away and then doesn't get to 0. Then most often it seems like it starts from a higher number than 1 seeing has how immediately after I bang it, it gets louder before it starts to fade away then abruptly cut off. Any suggestions?


trouble-understanding-line

When two signal patch cords go into the same inlet, as is the case with the patch cords from the two line~ objects going into the right inlets of the *~ objects, they are added together. So, initially, the sum is 0, then when you click the button the sum goes instantly to 1 and fades to 0 in 1000 ms; when that has finished, the bang from the right inlet of that line~ object triggers the other line~ object to go to 1 in 50 ms and stays there forever (because nothing ever tells it to do otherwise). So the next time you click the button, the sum goes instantly to 2, then fades to 1. You can use a number~ object to view the value at any point in your patch; connect the left outlets of your two line~ objects to the inlet of the same number~ object, and you'll see what I've described.

Thanks, Christopher. I didn't realize that was going on. Line~ is a little perplexing because I didn't think that signal cable coming from line~'s outlet "carried" anything. Although it might not necessarily contain sound, I assume it carries the "size of the pipe" or something to that effect and by combining them it doubles the size (?).

Anyways, I fixed the problem by using 1 line~ and used a delay and more articulate message for line~ to get what I wanted anyways. Posted here below for reference. Thanks dude.

 object sends out a 'signal' just like any other MSP object. (That is, it provides a value for every single sample of the audio calculation, typically 44,100 sample values per second.) But it's not a signal that you listen to directly; it is used as a 

 signal to change a parameter of the sound (such as the amplitude, in your patch). Understanding control signals is pretty crucial to working successfully in MSP.

The line~ object sends out a 'signal' just like any other MSP object. (That is, it provides a value for every single sample of the audio calculation, typically 44,100 sample values per second.) But it's not a signal that you listen to directly; it is used as a control signal to change a parameter of the sound (such as the amplitude, in your patch). Understanding control signals is pretty crucial to working successfully in MSP.

Here's some information about the line~ object.

Max 6 version: MSP Tutorial 2: Adjustable Oscillator

Trouble understanding Line~