How to set output device with adstatus?
Since the driver setting has changed, so that I can access input and output devices separately, I can't access/change the output driver with adstatus. I need to create a standalone and want simply select the interface with ins and outs together, like it was in the old days.
The helpfile of adstatus doesn't provide any help and seems to be the same as the ancient one.
I don't want to open anything to let the user set it, it has to be set in advance...
Any help is appreciated...
answer is in max text files which deal with audio settings.
if you read them, you will get idea how to send messages
which do what you want.
here is extract from one of many posts about that :
one can set prefered I/O devices using messages to #AD
example :
;
#AD dsinputdevicepref "Microphone (Realtek High Definition Audio)"
you can also combine
;
dsp setdriver ad_directsound;
#AD dsinputdevicepref "Microphone (Realtek High Definition Audio)" ;
#AD dsoutputdevicepref "Speaker/HP (Realtek High Definition Audio)"
Audio settings text files are written in user's
AppData/Roaming/Cycling '74/Max 8/Settings folder
AppData is Invisible and "normal" windows users have no rights to even look inside.
The solution is [adstatus option 1]! Its at the moment not well explained in the help file. And if you just type it in the object, its not activated at all. It needs to be reloaded after it has been saved, or it needs a loadbang message first. All this doesn’t make sense for me, but that way adstatus reports output devices correctly and they can be set with a filled menu…
Just for those who face the same problem…
Audio Status is patcher which used to get opened in older then max 9 versions
when one calls it from Options Menu , or use
; dsp open, or doubleclick adc~ or dac~ objects.
Which means all adstatus objects inside get initialised on patcher load.
That is how it works.
banging on them later brings nothing.
Only way to refresh all adstatus objects is to reselect audio driver.
or set it to none.
But you have different problem,
if I understand correctly, you want to automate audio driver setup
without user taking any actions on unknown computer, or ?
which can work only if audio device to be used is known, allways present
and ready to use.
More complicated on windows where another app could grab exclusive
use of same audio driver.
on Mac for example you can loadbang something like this:
dsp setdriver "Core Audio";
dsp prefsr 44100;
dsp prefiovs 128;
dsp prefsigvs 64;
dsp takeover 0;
dsp cpulimit 0;
dsp optimize 1;
#AD inputdevicepref "Microphone (Pink Front)";
#AD outputdevicepref "Headphones (Green Front)";
dsp start
which would activate VoodooHDA driver and set I/O devices
on my old hackintosh.