bbigelow

I am at a loss, and any help would be greatly appreciated...

All I want to do is loadbang an audio file that loops. However, sound will not output unless either: I open the Audio Tester window or, I double click dac~ and set audio to "on" in the DSP status window. Is it possible to send the DSP window messages? I assume that is what the toggle in my patch is already doing...yet to no avail.

Below is the patch, thanks a lot in advance!

All I want to do is loadbang an audio file that loops.  However, sound will not output unless either:  I open the Audio Tester window or, I double click dac~ and set audio to "on" in the DSP status window.  Is it possible to send the DSP window messages?  I assume that is what the toggle in my patch is already doing...yet to no avail.

1-min-for-a-noob-audio-playback-needs-audio-tester

I think you need to spend a little quality

audio on and off, sequencing the order in

which things happen, and the like are covered

with precision and completeness. An additional

benefit is that a good working knowledge of

these exceptionially basic skills will rescue

P.S. You might want to consider looking at

the trigger object and carefully studying

what you have done so far. This meditation

I think you need to spend a little quality
tutorial time. Doing things like turning
audio on and off, sequencing the order in
which things happen, and the like are covered
with precision and completeness. An additional
benefit is that a good working knowledge of
these exceptionially basic skills will rescue
you from a lifetime of patch grovels.

P.S. You might want to consider looking at
the trigger object and carefully studying
what you have done so far. This meditation
will be instructive.


Thanks...the worst quality of a noob is a reluctance to reevaluate tutorials...which Max certainly has some of the best. Sorry, but I was a bit panicked as my piece at a museum had faulty audio. After so much jitter work, the simplest of MSP messed me up.

I'm still confused as to why a "startwindow" message is needed, and why the toggle doesn't work...I only have one patch running. Well it works so for now I'm happy. Below is the corrected batch, for any other noobs that need it!

Thanks...the worst quality of a noob is a reluctance to reevaluate tutorials...which Max certainly has some of the best.  Sorry, but I was a bit panicked as my piece at a museum had faulty audio.  After so much jitter work, the simplest of MSP messed me up. 

I'm still confused as to why a "startwindow" message is needed, and why the toggle doesn't work...I only have one patch running.  Well it works so for now I'm happy.  Below is the corrected batch, for any other noobs that need it!

On Sep 22, 2008, at 12:07 PM, Ben Bigelow wrote:

> I'm still confused as to why a "startwindow" message is needed, and 

> why the toggle doesn't work...I only have one patch running. Well 

> it works so for now I'm happy. Below is the corrected batch, for 

Turning on the audio system programmatically has always been somewhat 

This edit of your patch uses a technique suggested by Johan @ 

> I'm still confused as to why a "startwindow" message is needed, and  
> why the toggle doesn't work...I only have one patch running.  Well  
> it works so for now I'm happy.  Below is the corrected batch, for  
> any other noobs that need it!

Turning on the audio system programmatically has always been somewhat  
problematic.

This edit of your patch uses a technique suggested by Johan @ http://www.jvkr.nl/

Chris Muir
cbm@well.com	
http://www.xfade.com

Thanks a bunch, if my original patch gives me any problems I'll try the other...

On Sep 22, 2008, at 11:45 AM, Gregory Taylor wrote:

> I think you need to spend a little quality

> tutorial time. Doing things like turning

> audio on and off, sequencing the order in

> which things happen, and the like are covered

> with precision and completeness. An additional

> benefit is that a good working knowledge of

> these exceptionially basic skills will rescue

While normally I'm in 100% agreement with Gregory on such matters, in 

the particular case of turning DSP on at loadbang time, I'm not sure 

the doc is sufficient. This has always been a little bit of a black 

art to get it to happen reliably. In the past, I've used a hodge-podge 

of delay and deferlow, but it still wasn't completely reliable. The 

approach that I nicked from Johan repeatedly bangs until it sees that 

the DSP is actually on, and is the most reliable approach that I've 

On Sep 22, 2008, at 11:45 AM, Gregory Taylor wrote:
> I think you need to spend a little quality
> tutorial time. Doing things like turning
> audio on and off, sequencing the order in
> which things happen, and the like are covered
> with precision and completeness. An additional
> benefit is that a good working knowledge of
> these exceptionially basic skills will rescue
> you from a lifetime of patch grovels.

While normally I'm in 100% agreement with Gregory on such matters, in  
the particular case of turning DSP on at loadbang time, I'm not sure  
the doc is sufficient. This has always been a little bit of a black  
art to get it to happen reliably. In the past, I've used a hodge-podge  
of delay and deferlow, but it still wasn't completely reliable. The  
approach that I nicked from Johan repeatedly bangs until it sees that  
the DSP is actually on, and is the most reliable approach that I've  
seen.

1 min for a noob? audio playback, needs audio tester