automated audio driver selection in application

Jun 12, 2007 at 12:10pm

automated audio driver selection in application

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.

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.

best,

Bruce

#32428
Jun 12, 2007 at 1:18pm

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
> 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.

ej

#106659
Jun 12, 2007 at 3:04pm

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…

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P hidden newex 84 99 61 196617 loadmess 1;
#P user ezdac~ 84 121 128 154 0;
#P user umenu 131 138 117 196645 1 64 154 0;
#X add None;
#X add ad_rewire;
#X add CoreAudio “Built-in Audio”;
#X add NonRealTime;
#P hidden newex 254 138 78 196617 adstatus driver;
#P hidden connect 3 0 2 0;
#P hidden fasten 1 0 0 0 136 156 233 156 259 135 259 135;
#P hidden fasten 0 0 1 0 259 158 259 158 229 136 136 136;
#P window clipboard copycount 4;


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

#106660

You must be logged in to reply to this topic.