Forums > MaxMSP

Cant stop the Click Noise!

October 13, 2013 | 10:41 am

Hi, its been driving me insane to work this out, any help would be much appreciated.

Ive put all the details in the attachment.

<code>

– Pasted Max Patch, click to expand. –

</code>


October 13, 2013 | 1:59 pm

sorry for posting twice


October 14, 2013 | 5:54 am

try maybe the resample 1 message to groove~. Give a look at the "grooveduck" abstraction, or "grooveduck2". There are some topics on these forums about that kind of problem, it’s a non-trivial problem. Try here : http://cycling74.com/forums/topic/millerpuckettes-switchramp-reworked-in-gen/


October 15, 2013 | 10:04 am

but really, isn’t the click in this case caused by the volume envelope still being open and then instantly set to zero? Or is this what you mean, Vichug ( I never fully grokked the switchramp)


October 16, 2013 | 2:36 am

good question :x


October 16, 2013 | 4:12 am

Difficult to advise as it is difficult to work out what it’s intended to do? Maybe worth explaining a bit more.

But…

Function needs to be triggered with a bang. Use the setdomain message to change the duration of the envelope.

As far as I know, scrubbing around on the rslider while the groove~ is playing will always click, even if you convert to signals – what are you trying to achieve here? You can set the loop point before you trigger, but not halfway through, it’s like jumping through a waveform while it’s playing.


October 16, 2013 | 4:27 am

Unfortunately, you seem to have fallen foul of a common problem: blindly adding functionality without testing each step of the way. I’ve been using Max for several years now and I really can’t determine what you’re trying to achieve in this patch. There are numerous objects in here that have absolutely no bearing whatsoever on the problem your are vaguely describing. Can I suggest that you strip it down, tidy it up; and please don’t assume everyone on this forum will have a MIDI keyboard attached to their computer while viewing your patch, and that we will somehow *know* how your patch works or should work.

Brendan


October 16, 2013 | 5:01 pm

Im sorry Brendan that my vagueness has offended you lol, its quite a large patch i have made with all bits and peices i have put together from previous patches so thats why its messy at the moment. Thanks for the help guys anyway. I will post back if i work out some solution.


Viewing 8 posts - 1 through 8 (of 8 total)