Forums > MaxMSP

waveform~ trouble


Ameqc
Nov 30 2011 | 6:45 am

im using waveform to display a sample from a buffer~ of course, and when i select a start point and an end point that is somewhere in the sample where it would be making sound, afterwards it has a continuous output of a humming sound… how do i fix this?


Chris Muir
Nov 30 2011 | 7:13 am

Without seeing your patch it’s difficult to say.


Ameqc
Dec 02 2011 | 6:42 pm

i checked a bunch of times, and just go to the play~ reference example from max and open a sample, make it start and stop somewhere midopint in the file, preferably when the sample is at a louder point. and itll generate a lingering sound thats either inaudible or audible, especially if you hook up a levelmeter to it and amplify the output.


Chris Muir
Dec 02 2011 | 7:19 pm

If you pause the sound, it stops wherever it was, and there may be a DC offset. This is not humming though.


Ameqc
Dec 02 2011 | 10:59 pm

when i turn the volume way up it clearly is making a tone, and when the sample ends where there is no offset it doesnt make a tone, i can even record it in to a buffer and it shows up.


Ameqc
Dec 02 2011 | 11:46 pm

i finally fixed it. it was a problem with the line~ object hooked up to the play~ object. thanks anyway. this was bugging me for a few days now.


Ameqc
Dec 02 2011 | 11:48 pm

more so, it seems that the line object still outputs a signal, and it is making a clear noise when i turn up the volume. and if its sub-audible i can see my bass speaker moving a fair bit. i just basically made it so when the sample is played it turns on the volume, and when the line is done playing, it turns off the volume.

but still, why does line~ do this?


Chris Muir
Dec 03 2011 | 1:43 am

post your patch


Ameqc
Dec 03 2011 | 8:31 pm

k, here it is. it appears to be the play~ object actually outputting it, but i think my solution was easier to cut back to the line object.

just load the snare sample i put in with the zip file, play it once backwards, and then turn up the volume and listen to the sine wave cut out. i dont understand. i have a feeling this would detract from certain things if i werent to have found a solution to it.

Attachments:
  1. playissue.rar

Chris Muir
Dec 03 2011 | 10:55 pm

play~ continues to output whatever level is in the buffer~ at the position that it was in when it stops playing. The reason the sine cuts out is that eventually the output is so saturated with DC that the sine wave can no longer wiggle it.

In this version of your patch, I show that the value that is being output is a DC level, the same as the beginning of your sample. By using peek~ to fetch the first sample.



-- Pasted Max  Patch, click to expand. --

Ameqc
Dec 04 2011 | 12:57 am

Thank you very much. I understand a lot clearly now. I’m fairly well versed in the max part of max/msp, but the msp part I basically just started getting in to.
thanks again.

Viewing 11 posts - 1 through 11 (of 11 total)
Forums > MaxMSP