choosing an audiodriver in a standalone app(vs5)

Jun 11, 2008 at 1:22pm

choosing an audiodriver in a standalone app(vs5)

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

#38336
Jun 11, 2008 at 1:45pm

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

#133439
Jun 11, 2008 at 2:17pm

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

#133440
Jun 11, 2008 at 2:27pm

#133441
Jun 11, 2008 at 2:41pm

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

#133442
Jun 11, 2008 at 2:54pm

#133443
Jun 11, 2008 at 3:04pm

#133444
Jun 11, 2008 at 3:18pm

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?

Best,

Zip

– Pasted Max Patch, click to expand. –

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

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

#133445
Jun 11, 2008 at 3:22pm

#133446
Jun 11, 2008 at 8:55pm

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.
maybe worth a try.

h
http://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
>>
>>
>>
>>
>

#133447
Jun 11, 2008 at 9:15pm

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
> http://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
>>>
>>>
>>>
>>>
>>
>

#133448
Jun 11, 2008 at 10:06pm

hi zip,

its in the inspector of the standalone-object.

hth
hans

http://www.hans-w-koch.net

Am 11.06.2008 um 23:15 schrieb Zip Boterbloem:

> 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
>> http://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
>>>>
>>>>
>>>>
>>>>
>>>
>>
>

#133449
Jun 11, 2008 at 10:10pm

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.

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

AB

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.

#133450

You must be logged in to reply to this topic.