Bruce mowson

I've made a few application versions of patches to email to other people - but I'm getting reports back that the audio doesn't work.

I think part of the problem is getting the audio driver selected at their end. I've made pop-up interfaces that prompt the user to select their driver from the DSP status window, but no reliable solution there.

I'm imagining that I might be able to automate the selection of coreaudio as a driver. Any thoughts welcome.

Hi,
I've made a few application versions of patches to email to other people - but I'm getting reports back that the audio doesn't work.

automated-audio-driver-selection-in-application

On 12 juin 07, at 14:10, Bruce mowson wrote:

> I've made a few application versions of patches to email to other 

> people - but I'm getting reports back that the audio doesn't work.

> I think part of the problem is getting the audio driver selected at 

> their end. I've made pop-up interfaces that prompt the user to 

> select their driver from the DSP status window, but no reliable 

> I'm imagining that I might be able to automate the selection of 

> coreaudio as a driver. Any thoughts welcome.

DSP Status is just a patch, you can change the audio driver with the 

> I've made a few application versions of patches to email to other  
> people - but I'm getting reports back that the audio doesn't work.
>
> I think part of the problem is getting the audio driver selected at  
> their end. I've made pop-up interfaces that prompt the user to  
> select their driver from the DSP status window, but no reliable  
> solution there.
>
> I'm imagining that I might be able to automate the selection of  
> coreaudio as a driver. Any thoughts welcome.

DSP Status is just a patch, you can change the audio driver with the  
[adstatus driver] object.

> I think part of the problem is getting the audio driver selected at

> their end. I've made pop-up interfaces that prompt the user to select

> their driver from the DSP status window, but no reliable solution

> I'm imagining that I might be able to automate the selection of

I have the below code snippet in my clippings folder. Any main patch has 

this part in it. Especially if you hand out standalones, you'll need it. 

Its just a copy of the part in the DSP status. Users unknown to Max/MSP 

will have no clue, that audio has to be switched on. For that just add a 

In general if you can describe the user how to setup things, its better 

Though with drivers, its tricky, as any machine will have drivers of 

different names and if you can choose different ones, you don't want to 

But if the menu is right there in the patch it should be obviously 

Bruce mowson schrieb:
> I think part of the problem is getting the audio driver selected at
> their end. I've made pop-up interfaces that prompt the user to select
> their driver from the DSP status window, but no reliable solution
> there.
>
> I'm imagining that I might be able to automate the selection of
> coreaudio as a driver. Any thoughts welcome.

I have the below code snippet in my clippings folder. Any main patch has 
this part in it. Especially if you hand out standalones, you'll need it. 
Its just a copy of the part in the DSP status. Users unknown to Max/MSP 
will have no clue, that audio has to be switched on. For that just add a 
[loadmess 1] to your dac~/ezdac~...

In general if you can describe the user how to setup things, its better 
to make a patch which just does it...

Though with drivers, its tricky, as any machine will have drivers of 
different names and if you can choose different ones, you don't want to 
change it automatically.
But if the menu is right there in the patch it should be obviously 
enough how to set it...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


automated audio driver selection in application