zipb

I've made an app for someone else who is using different hardware, so 

he needs to choose the proper driver for his setup.

When I doubleclick the dac~ object in the standalone to bring up the 

DSP Status window, it looks funny and there's no way to choose anything.

How is one to supposed to deal with standalones & choosing a 

Thanks for any insights/tips/pages in the manual.

I've made an app for someone else who is using different hardware, so  
he needs to choose the proper driver for his setup.

When I doubleclick the dac~ object in the standalone to bring up the  
DSP Status window, it looks funny and there's no way to choose anything.

How is one to supposed to deal with standalones & choosing a  
CoreAudio driver?

choosing-an-audiodriver-in-a-standalone-appvs5

Hm. I get a whole slew of missing objects errors when I hit dac~ in 

the standalone. Basically, it looks like all the components of the 

DSP Status are missing. Is there an easy way to include these?

Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende geschreven:

> I've made an app for someone else who is using different hardware, 

> so he needs to choose the proper driver for his setup.

> When I doubleclick the dac~ object in the standalone to bring up 

> the DSP Status window, it looks funny and there's no way to choose 

> How is one to supposed to deal with standalones & choosing a 

> Thanks for any insights/tips/pages in the manual.

Hm. I get a whole slew of missing objects errors when I hit dac~ in  
the standalone. Basically, it looks like all the components of the  
DSP Status are missing. Is there an easy way to include these?

> I've made an app for someone else who is using different hardware,  
> so he needs to choose the proper driver for his setup.
>
> When I doubleclick the dac~ object in the standalone to bring up  
> the DSP Status window, it looks funny and there's no way to choose  
> anything.
>
> How is one to supposed to deal with standalones & choosing a  
> CoreAudio driver?
>
> Thanks for any insights/tips/pages in the manual.
>
> Best,
>
> Zip
>
>
>
>


Can't you just use 'include patcher' in the collective

building script to include the DSP Staus patch ? It's

at ~Max5/Cycling '74/interfaces/DSP Status.maxpat

I'm sure I've done this in the distant past,

> Hm. I get a whole slew of missing objects errors

> the standalone. Basically, it looks like all the

> DSP Status are missing. Is there an easy way to

> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het

> > I've made an app for someone else who is using

> > so he needs to choose the proper driver for his

> > When I doubleclick the dac~ object in the

> > the DSP Status window, it looks funny and there's

> > How is one to supposed to deal with standalones &

> > Thanks for any insights/tips/pages in the manual.

Can't you just use 'include patcher' in the collective
building script to include the DSP Staus patch ? It's
at ~Max5/Cycling '74/interfaces/DSP Status.maxpat
 I'm sure I've done this in the distant past,
cheers
Roger

> Hm. I get a whole slew of missing objects errors
> when I hit dac~ in  
> the standalone. Basically, it looks like all the
> components of the  
> DSP Status are missing. Is there an easy way to
> include these?
>
> Best,
>
> Zip
>
> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het
> volgende geschreven:
>
> > I've made an app for someone else who is using
> different hardware,  
> > so he needs to choose the proper driver for his
> setup.
> >
> > When I doubleclick the dac~ object in the
> standalone to bring up  
> > the DSP Status window, it looks funny and there's
> no way to choose  
> > anything.
> >
> > How is one to supposed to deal with standalones &
> choosing a  
> > CoreAudio driver?
> >
> > Thanks for any insights/tips/pages in the manual.
> >
> > Best,
> >
> > Zip
> >
> >
> >
> >
>
>

Thanks for your prompt reply. Do you mean 'Include File...' from the 

build script window? I just tried that a couple of times, the builder 

says it's including it, but the slew of 'objects not found messages' 

is still there in the resulting app, together with the funny look of 

Op 11-jun-2008, om 16:17 heeft ROGER CARRUTHERS het volgende geschreven:

> Can't you just use 'include patcher' in the collective

> building script to include the DSP Staus patch ? It's

> at ~Max5/Cycling '74/interfaces/DSP Status.maxpat

> I'm sure I've done this in the distant past,

>> Hm. I get a whole slew of missing objects errors

>> the standalone. Basically, it looks like all the

>> DSP Status are missing. Is there an easy way to

>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het

>>> I've made an app for someone else who is using

>>> so he needs to choose the proper driver for his

>>> When I doubleclick the dac~ object in the

>>> the DSP Status window, it looks funny and there's

>>> How is one to supposed to deal with standalones &

>>> Thanks for any insights/tips/pages in the manual.

Thanks for your prompt reply. Do you mean 'Include File...' from the  
build script window? I just tried that a couple of times, the builder  
says it's including it, but the slew of 'objects not found messages'  
is still there in the resulting app, together with the funny look of  
the resulting DSP Status windows.

> Can't you just use 'include patcher' in the collective
> building script to include the DSP Staus patch ? It's
> at ~Max5/Cycling '74/interfaces/DSP Status.maxpat
>  I'm sure I've done this in the distant past,
> cheers
> Roger
>
> --- Zip Boterbloem  wrote:
>
>> Hm. I get a whole slew of missing objects errors
>> when I hit dac~ in
>> the standalone. Basically, it looks like all the
>> components of the
>> DSP Status are missing. Is there an easy way to
>> include these?
>>
>> Best,
>>
>> Zip
>>
>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het
>> volgende geschreven:
>>
>>> I've made an app for someone else who is using
>> different hardware,
>>> so he needs to choose the proper driver for his
>> setup.
>>>
>>> When I doubleclick the dac~ object in the
>> standalone to bring up
>>> the DSP Status window, it looks funny and there's
>> no way to choose
>>> anything.
>>>
>>> How is one to supposed to deal with standalones &
>> choosing a
>>> CoreAudio driver?
>>>
>>> Thanks for any insights/tips/pages in the manual.
>>>
>>> Best,
>>>
>>> Zip
>>>
>>>
>>>
>>>
>>
>>
>
>


Can't get much simpler than this. Build an app with or without 

including the DSP Status Patcher. Doubleclick the adc~ object in the 

Op 11-jun-2008, om 16:41 heeft Zip Boterbloem het volgende geschreven:

> Thanks for your prompt reply. Do you mean 'Include File...' from 

> the build script window? I just tried that a couple of times, the 

> builder says it's including it, but the slew of 'objects not found 

> messages' is still there in the resulting app, together with the 

> funny look of the resulting DSP Status windows.

> Op 11-jun-2008, om 16:17 heeft ROGER CARRUTHERS het volgende 

>> Can't you just use 'include patcher' in the collective

>> building script to include the DSP Staus patch ? It's

>> at ~Max5/Cycling '74/interfaces/DSP Status.maxpat

>> I'm sure I've done this in the distant past,

>>> Hm. I get a whole slew of missing objects errors

>>> the standalone. Basically, it looks like all the

>>> DSP Status are missing. Is there an easy way to

>>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het

>>>> I've made an app for someone else who is using

>>>> so he needs to choose the proper driver for his

>>>> When I doubleclick the dac~ object in the

>>>> the DSP Status window, it looks funny and there's

Can't get much simpler than this. Build an app with or without  
including the DSP Status Patcher. Doubleclick the adc~ object in the  
resulting app. What do you see?

> Hi Roger,
>
> Thanks for your prompt reply. Do you mean 'Include File...' from  
> the build script window? I just tried that a couple of times, the  
> builder says it's including it, but the slew of 'objects not found  
> messages' is still there in the resulting app, together with the  
> funny look of the resulting DSP Status windows.
>
> Any idea?
>
> Best,
>
> Zip
>
> Op 11-jun-2008, om 16:17 heeft ROGER CARRUTHERS het volgende  
> geschreven:
>
>> Can't you just use 'include patcher' in the collective
>> building script to include the DSP Staus patch ? It's
>> at ~Max5/Cycling '74/interfaces/DSP Status.maxpat
>>  I'm sure I've done this in the distant past,
>> cheers
>> Roger
>>
>> --- Zip Boterbloem  wrote:
>>
>>> Hm. I get a whole slew of missing objects errors
>>> when I hit dac~ in
>>> the standalone. Basically, it looks like all the
>>> components of the
>>> DSP Status are missing. Is there an easy way to
>>> include these?
>>>
>>> Best,
>>>
>>> Zip
>>>
>>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het
>>> volgende geschreven:
>>>
>>>> I've made an app for someone else who is using
>>> different hardware,
>>>> so he needs to choose the proper driver for his
>>> setup.
>>>>
>>>> When I doubleclick the dac~ object in the
>>> standalone to bring up
>>>> the DSP Status window, it looks funny and there's
>>> no way to choose
>>>> anything.
>>>>
>>>> How is one to supposed to deal with standalones &
>>> choosing a
>>>> CoreAudio driver?
>>>>
>>>> Thanks for any insights/tips/pages in the manual.
>>>>
>>>> Best,
>>>>
>>>> Zip
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>


i have had similar problems in the past which seemd to be cured when i 

gave the preference-file an app-specific name in the appropriate field 

Am 11.06.2008 um 15:45 schrieb Zip Boterbloem:

> Hm. I get a whole slew of missing objects errors when I hit dac~ in 

> the standalone. Basically, it looks like all the components of the 

> DSP Status are missing. Is there an easy way to include these?

> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende geschreven:

>> I've made an app for someone else who is using different hardware, 

>> so he needs to choose the proper driver for his setup.

>> When I doubleclick the dac~ object in the standalone to bring up 

>> the DSP Status window, it looks funny and there's no way to choose 

>> How is one to supposed to deal with standalones & choosing a 

>> Thanks for any insights/tips/pages in the manual.

i have had similar problems in the past which seemd to be cured when i  
gave the preference-file an app-specific name in the appropriate field  
in the standalone object.
maybe worth a try.

> Hm. I get a whole slew of missing objects errors when I hit dac~ in  
> the standalone. Basically, it looks like all the components of the  
> DSP Status are missing. Is there an easy way to include these?
>
> Best,
>
> Zip
>
> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende geschreven:
>
>> I've made an app for someone else who is using different hardware,  
>> so he needs to choose the proper driver for his setup.
>>
>> When I doubleclick the dac~ object in the standalone to bring up  
>> the DSP Status window, it looks funny and there's no way to choose  
>> anything.
>>
>> How is one to supposed to deal with standalones & choosing a  
>> CoreAudio driver?
>>
>> Thanks for any insights/tips/pages in the manual.
>>
>> Best,
>>
>> Zip
>>
>>
>>
>>
>


Op 11-jun-2008, om 22:55 heeft hans w. koch het volgende geschreven:

> i have had similar problems in the past which seemd to be cured 

> when i gave the preference-file an app-specific name in the 

> appropriate field in the standalone object.

Where is that field exactly? In the Script Builder thingy? I'm afraid 

> Am 11.06.2008 um 15:45 schrieb Zip Boterbloem:

>> Hm. I get a whole slew of missing objects errors when I hit dac~ 

>> in the standalone. Basically, it looks like all the components of 

>> the DSP Status are missing. Is there an easy way to include these?

>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende 

>>> I've made an app for someone else who is using different 

>>> hardware, so he needs to choose the proper driver for his setup.

>>> When I doubleclick the dac~ object in the standalone to bring up 

>>> the DSP Status window, it looks funny and there's no way to 

>>> How is one to supposed to deal with standalones & choosing a 

> hi zip,
>
> i have had similar problems in the past which seemd to be cured  
> when i gave the preference-file an app-specific name in the  
> appropriate field in the standalone object.

Where is that field exactly? In the Script Builder thingy? I'm afraid  
not following you.

> maybe worth a try.
>
> h
> www.hans-w-koch.net
>
>
>
>
>
> Am 11.06.2008 um 15:45 schrieb Zip Boterbloem:
>
>> Hm. I get a whole slew of missing objects errors when I hit dac~  
>> in the standalone. Basically, it looks like all the components of  
>> the DSP Status are missing. Is there an easy way to include these?
>>
>> Best,
>>
>> Zip
>>
>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende  
>> geschreven:
>>
>>> I've made an app for someone else who is using different  
>>> hardware, so he needs to choose the proper driver for his setup.
>>>
>>> When I doubleclick the dac~ object in the standalone to bring up  
>>> the DSP Status window, it looks funny and there's no way to  
>>> choose anything.
>>>
>>> How is one to supposed to deal with standalones & choosing a  
>>> CoreAudio driver?
>>>
>>> Thanks for any insights/tips/pages in the manual.
>>>
>>> Best,
>>>
>>> Zip
>>>
>>>
>>>
>>>
>>
>


its in the inspector of the standalone-object.

Am 11.06.2008 um 23:15 schrieb Zip Boterbloem:

> Op 11-jun-2008, om 22:55 heeft hans w. koch het volgende geschreven:

>> i have had similar problems in the past which seemd to be cured 

>> when i gave the preference-file an app-specific name in the 

>> appropriate field in the standalone object.

> Where is that field exactly? In the Script Builder thingy? I'm 

>> Am 11.06.2008 um 15:45 schrieb Zip Boterbloem:

>>> Hm. I get a whole slew of missing objects errors when I hit dac~ 

>>> in the standalone. Basically, it looks like all the components of 

>>> the DSP Status are missing. Is there an easy way to include these?

>>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende 

>>>> I've made an app for someone else who is using different 

>>>> hardware, so he needs to choose the proper driver for his setup.

>>>> When I doubleclick the dac~ object in the standalone to bring up 

>>>> the DSP Status window, it looks funny and there's no way to 

> Hi Hans,
>
>
> Op 11-jun-2008, om 22:55 heeft hans w. koch het volgende geschreven:
>
>> hi zip,
>>
>> i have had similar problems in the past which seemd to be cured  
>> when i gave the preference-file an app-specific name in the  
>> appropriate field in the standalone object.
>
> Where is that field exactly? In the Script Builder thingy? I'm  
> afraid not following you.
>
>
> Thanks for your reply.
>
> Best,
>
> Zip
>
>> maybe worth a try.
>>
>> h
>> www.hans-w-koch.net
>>
>>
>>
>>
>>
>> Am 11.06.2008 um 15:45 schrieb Zip Boterbloem:
>>
>>> Hm. I get a whole slew of missing objects errors when I hit dac~  
>>> in the standalone. Basically, it looks like all the components of  
>>> the DSP Status are missing. Is there an easy way to include these?
>>>
>>> Best,
>>>
>>> Zip
>>>
>>> Op 11-jun-2008, om 15:22 heeft Zip Boterbloem het volgende  
>>> geschreven:
>>>
>>>> I've made an app for someone else who is using different  
>>>> hardware, so he needs to choose the proper driver for his setup.
>>>>
>>>> When I doubleclick the dac~ object in the standalone to bring up  
>>>> the DSP Status window, it looks funny and there's no way to  
>>>> choose anything.
>>>>
>>>> How is one to supposed to deal with standalones & choosing a  
>>>> CoreAudio driver?
>>>>
>>>> Thanks for any insights/tips/pages in the manual.
>>>>
>>>> Best,
>>>>
>>>> Zip
>>>>
>>>>
>>>>
>>>>
>>>
>>
>


For now a simple workaround is to add an instance of ["dsp status"] to your patch in an object box (yes, you need the quotes). The build script should then automagically find that you need all those objects to run the DSP Status window and include them in your application.

We'll have a look at making this less annoying in the future.

P.s. Please do not, under any circumstances, cross-post to support and the forums with the same issue. We read both, and it makes us really cranky when we have to read the same thing twice. Please make your choice before hitting Send.

Hi,
For now a simple workaround is to add an instance of ["dsp status"] to your patch in an object box (yes, you need the quotes).  The build script should then automagically find that you need all those objects to run the DSP Status window and include them in your application.

P.s.  Please do not, under any circumstances, cross-post to support and the forums with the same issue.  We read both, and it makes us really cranky when we have to read the same thing twice.  Please make your choice before hitting Send.


choosing an audiodriver in a standalone app(vs5)