roger.carruthers

I'm trying to make a wrapper for the au~ object, so

that I can select AU's from a ubumenu and dynamically

However, although I can create an object called "au~

Compressor" manually, and it will work fine, if I

create an object "au~ Compressor" with scripting, I

get a message saying 'Selected Audio Unit not found'. 

Also, the list of AU's printed in the Max window when

you send a 'plugins' message to au~ bears little

Library/Audio/Plugins/Components folder - possibly

because there's a load of old non-UB stuff in there,

but there is also a bunch of Apple plugs listed (all

startng with 'AU'), which I can't locate with

I'm trying to make a wrapper for the au~ object, so
that I can select AU's from a ubumenu and dynamically
create new instances of au~.
 However, although I can create an object called "au~
Compressor" manually, and it will work fine, if I
create an object "au~ Compressor" with scripting, I
get a message saying 'Selected Audio Unit not found'. 
Any ideas ?
 Also, the list of AU's printed in the Max window when
you send a 'plugins' message to au~ bears little
resemblance to the AU's in my
Library/Audio/Plugins/Components folder - possibly
because there's a load of old non-UB stuff in there,
but there is also a bunch of Apple plugs listed (all
startng with 'AU'), which I can't locate with
Spotlight - where does Apple hide them?
cheers
Roger

au-scripting

Quote: roger.carruthers wrote on Thu, 24 May 2007 17:17

----------------------------------------------------

> I'm trying to make a wrapper for the au~ object, so

> that I can select AU's from a ubumenu and dynamically

> However, although I can create an object called "au~

> Compressor" manually, and it will work fine, if I

> create an object "au~ Compressor" with scripting, I

> get a message saying 'Selected Audio Unit not found'. 

Because you are trying to load an AU by its filename which is not its real name... ?

For example, MNSpectralAveraging is the filename displayed in the Finder and its real name is "Spectral Averaging" => [au~ "Spectral Averaging"]

> Also, the list of AU's printed in the Max window when

> you send a 'plugins' message to au~ bears little

> Library/Audio/Plugins/Components folder - possibly

[au~] looks for the content of your user folder too:

> because there's a load of old non-UB stuff in there,

> but there is also a bunch of Apple plugs listed (all

> starting with 'AU'), which I can't locate with

> Spotlight - where does Apple hide them?

About the Apple's AU (aufx filetype only) that come ship with Mac OS X, there's no specified location (hidden).

Quote: roger.carruthers wrote on Thu, 24 May 2007 17:17
----------------------------------------------------
> I'm trying to make a wrapper for the au~ object, so
> that I can select AU's from a ubumenu and dynamically
> create new instances of au~.
> However, although I can create an object called "au~
> Compressor" manually, and it will work fine, if I
> create an object "au~ Compressor" with scripting, I
> get a message saying 'Selected Audio Unit not found'. 
> Any ideas ?

Because you are trying to load an AU by its filename which is not its real name... ?
For example, MNSpectralAveraging is the filename displayed in the Finder and its real name is "Spectral Averaging" => [au~ "Spectral Averaging"]

> Also, the list of AU's printed in the Max window when
> you send a 'plugins' message to au~ bears little
> resemblance to the AU's in my
> Library/Audio/Plugins/Components folder - possibly

[au~] looks for the content of your user folder too:
~/Library/Audio/Plugins/Components

> because there's a load of old non-UB stuff in there,
> but there is also a bunch of Apple plugs listed (all
> starting with 'AU'), which I can't locate with
> Spotlight - where does Apple hide them?

About the Apple's AU (aufx filetype only) that come ship with Mac OS X, there's no specified location (hidden).
Below the list in OSX.4.

Thanks, Phillipe, but if I'm using the same name when entering it manually as I'm getting by scripting, then it must surely be the right name in both cases, as it works when created manually!

I'm guessing that this is something to do with the object itself, and thus a question for it's developer - I was just hoping that one of you dev types might confirm this, before i go bothering him with it...

It would be nice to be able to interface with this object in a less clunky way than having to manually enter plugs' names as an argument - scripting would be fine, if it worked...

It's a shame Apple have to hide their plugs in this way - I can't really see the point of it. Fair enough with the big boys like Space Designer, which they want you to buy Logic or Soundtrack Pro for, but it's not going to encourage the adoption of AU as a standard if they wont enable easy access to bog standard things like filters & dynamics processors,

Thanks, Phillipe, but if I'm using the same name when entering it manually as I'm getting by scripting, then it must surely be the right name in both cases, as it works when created manually!
I'm guessing that this is something to do with the object itself, and thus a question for it's developer - I was just hoping that one of you dev types might confirm this, before i go bothering him with it...
 It would be nice to be able to interface with this object in a less clunky way than having to manually enter plugs' names as an argument - scripting would be fine, if it worked...
 It's a shame Apple have to hide their plugs in this way - I can't really see the point of it. Fair enough with the big boys like Space Designer, which they want you to buy Logic or Soundtrack Pro for, but it's not going to encourage the adoption of AU as a standard if they wont enable easy access to bog standard things like filters & dynamics processors,
cheers
Roger


I wondered if you can write the actual parameters of a plug in into a ubumenu?

Quote: roger.carruthers wrote on Fri, 25 May 2007 10:41

> Thanks, Philippe, but if I'm using the same name when entering

> it manually as I'm getting by scripting, then it must surely 

> be the right name in both cases, as it works when created

Could be then a problem with scripting. [au~] seems to need a 'certain' amount of time to be initialized.

I just find that putting a dummy [au~] is working when building a collective. This one below could give you an idea:

> It's a shame Apple have to hide their plugs in this way

Ditto for ImageUnit and VideoUnit plug-ins too!

Quote: roger.carruthers wrote on Fri, 25 May 2007 10:41
----------------------------------------------------

> Thanks, Philippe, but if I'm using the same name when entering
> it manually as I'm getting by scripting, then it must surely 
> be the right name in both cases, as it works when created
> manually!

Could be then a problem with scripting. [au~] seems to need a 'certain' amount of time to be initialized.
I just find that putting a dummy [au~] is working when building a collective. This one below could give you an idea:

> It's a shame Apple have to hide their plugs in this way
> I can't really see the point of it.

Quote: hans.mittendorf@free.fr wrote on Fri, 25 May 2007 21:16

> I wondered if you can write the actual parameters of a plug in

Do you know how to extract any info displayed in the Max window from the Max window?

Quote: hans.mittendorf@free.fr wrote on Fri, 25 May 2007 21:16
----------------------------------------------------
> I wondered if you can write the actual parameters of a plug in
> into a ubumenu?
----------------------------------------------------

look at this patch. I was made by Gregory Taylor and is for vst, but that's the way to do it, I believe.

#P comment 388 468 156 196618 Choose a parameter for dial 4;

#P comment 388 436 156 196618 Choose a parameter for dial 3;

#P comment 388 404 156 196618 Choose a parameter for dial 2;

#P comment 388 372 156 196618 Choose a parameter for dial 1;

#P user ubumenu 155 468 233 196618 0 0 1 0;

#X setrgb 255 255 255 153 102 187 153 102 187 4 4 4 141 141 141 112 112 112;

#P user ubumenu 155 436 233 196618 0 0 1 0;

#P user ubumenu 155 404 233 196618 0 0 1 0;

#P comment 164 516 146 196618 controller messages from the midiparse object;

#P comment 314 399 191 196618 The zmap objects convert the 0-127 MIDI values to the range that VST parameters use (0.-1.0);

#P comment 339 29 140 196618 MIDI controller messages;

#P comment 44 474 245 196618 VST parameter messages for the vst~ object;

#P newex 293 375 94 196618 zmap 0 127 0. 1.;

#P newex 218 327 94 196618 zmap 0 127 0. 1.;

Hi,
look at this patch. I was made by Gregory Taylor and is for vst, but that's the way to do it, I believe.
max v2;
#N vpatcher 299 66 1052 834;
#P origin 0 108;
#P window setfont "Sans Serif" 10.;
#P window linecount 1;
#P comment 388 468 156 196618 Choose a parameter for dial 4;
#P comment 388 436 156 196618 Choose a parameter for dial 3;
#P comment 388 404 156 196618 Choose a parameter for dial 2;
#P comment 388 372 156 196618 Choose a parameter for dial 1;
#P user ubumenu 155 468 233 196618 0 0 1 0;
#X setrgb 255 255 255 153 102 187 153 102 187 4 4 4 141 141 141 112 112 112;
#X add Gain;
#X prefix_set 0 0  0;
#P user ubumenu 155 436 233 196618 0 0 1 0;
#X setrgb 255 255 255 153 102 187 153 102 187 4 4 4 141 141 141 112 112 112;
#X add Gain;
#X prefix_set 0 0  0;
#P user ubumenu 155 404 233 196618 0 0 1 0;
#X setrgb 255 255 255 153 102 187 153 102 187 4 4 4 141 141 141 112 112 112;
#X add Gain;
#X prefix_set 0 0  0;
#P window linecount 2;
#P comment 164 516 146 196618 controller messages from the midiparse object;
#B color 12;
#P window linecount 1;
#P comment 177 573 179 196618
#P newex 164 546 56 196618 r mydials;
#N vpatcher 10 59 653 609;
#P window setfont "Sans Serif" 10.;
#P comment 314 399 191 196618 The zmap objects convert the 0-127 MIDI values to the range that VST parameters use (0.-1.0);
#P outlet 538 474 15 0;
#P comment 339 29 140 196618 MIDI controller messages;
#B color 12;
#P comment 44 474 245 196618 VST parameter messages for the vst~ object;
#B color 12;
#P outlet 23 474 15 0;
#P inlet 339 59 15 0;
#P inlet 252 59 15 0;
#P inlet 176 59 15 0;
#P inlet 100 59 15 0;
#P inlet 23 59 15 0;
#P newex 252 375 33 196618 + 1;
#P newex 252 401 52 196618 pak 0 0.;
#P newex 293 375 94 196618 zmap 0 127 0. 1.;
#P newex 176 327 33 196618 + 1;
#P newex 176 353 52 196618 pak 0 0.;
#P newex 218 327 94 196618 zmap 0 127 0. 1.;
#P newex 100 279 33 196618 + 1;
#P newex 100 305 52 196618 pak 0 0.;
#P newex 142 279 94 196618 zmap 0 127 0. 1.;
#P newex 23 231 33 196618 + 1;
#P newex 23 257 52 196618 pak 0 0.;
#P comment 22 29 245 196618 VST parameter numbers from the ubumenus Since ubumenu numbers from 0 , we add 1....;
#B color 12;
#P newex 65 231 94 196618 zmap 0 127 0. 1.;
#P number 293 355 35 10 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 218 307 35 10 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 142 259 35 10 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 65 212 35 10 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 339 133 213 196618 route 74 71 76 77;
#P comment 351 90 229 196618 The route object chooses only the controller numbers I want for my dials , and sends everything else out the right outlet;
#P connect 19 0 9 0;
#P connect 9 0 8 0;
#P connect 17 0 24 0;
#P connect 14 0 24 0;
#P connect 11 0 24 0;
#P connect 8 0 24 0;
#P connect 1 0 2 0;
#P connect 2 0 6 0;
#P connect 6 0 8 1;
#P connect 20 0 12 0;
#P connect 12 0 11 0;
#P connect 1 1 3 0;
#P connect 3 0 10 0;
#P connect 10 0 11 1;
#P connect 21 0 15 0;
#P connect 15 0 14 0;
#P connect 1 2 4 0;
#P connect 4 0 13 0;
#P connect 13 0 14 1;
#P connect 22 0 18 0;
#P connect 18 0 17 0;
#P connect 1 3 5 0;
#P connect 5 0 16 0;
#P connect 16 0 17 1;
#P connect 23 0 1 0;
#P connect 1 4 27 0;
#P pop;
#P newobj 100 573 77 196618 p dialhandler;
#P newex 44 249 56 196618 r vstdials;
#P newex 100 600 55 196618 s vstdials;
#P window linecount 3;
#P comment 405 90 277 196618 The trigger and deferlow objects are used to delay loading the ubumenu with a list of plug-in parameters until the VST plug-in finishes loading.;
#P window linecount 1;
#P comment 405 66 277 196618 The plug message is used to load a VST plug-in.;
#B color 12;
#P message 323 180 56 196618 params;
#B color 13;
#P newex 323 204 79 196618 trigger l clear;
#P user ezdac~ 24 465 68 498 0;
#P user gain~ 46 330 22 100 158 0 1.071519 7.94321 60.;
#P user gain~ 24 330 22 100 158 0 1.071519 7.94321 10.;
#P newex 323 116 67 196618 deferlow;
#P newex 323 90 75 196618 trigger b l;
#P message 323 66 44 196618 plug;
#B color 12;
#P window linecount 3;
#P comment 405 263 233 196618 You can see the plug-in's edit window by using the open message or double-clicking on the vst~ object;
#B color 14;
#P window linecount 2;
#P comment 405 180 277 196618 The params message loads the four ubumenus with a listing of the plug-in parameters;
#B color 13;
#P window linecount 1;
#P message 322 263 68 196618 open;
#B color 14;
#P newex 104 317 90 196618 prepend append;
#P user ubumenu 155 372 233 196618 0 0 1 0;
#X setrgb 255 255 255 153 102 187 153 102 187 4 4 4 141 141 141 112 112 112;
#X add Gain;
#X prefix_set 0 0  0;
#N vst~ loaduniqueid 0;
#P newobj 24 294 212 196618 vst~;
#P newex 90 89 52 196618 s mydials;
#P newex 24 145 210 196618 qs.vstizer;
#B color 5;
#P newex 90 123 44 196618 r other;
#P newex 167 600 43 196618 s other;
#P window linecount 2;
#P comment 167 621 146 196618 send all other controller messages back to the vstizer;
#B color 12;
#P window linecount 1;
#P newex 24 39 46 196618 midiin;
#P newex 24 66 210 196618 midiparse;
#B color 5;
#P comment 72 40 295 196618
#P connect 2 0 1 0;
#P connect 1 0 6 0;
#P fasten 11 0 8 0 327 285 29 285;
#P fasten 15 1 8 0 393 172 29 172;
#P fasten 20 0 8 0 328 231 29 231;
#P connect 6 0 8 0;
#P fasten 6 1 8 0 129 172 29 172;
#P fasten 25 0 8 0 49 276 29 276;
#P connect 8 0 17 0;
#P connect 17 0 19 0;
#P fasten 8 1 18 0 69 321 51 321;
#P hidden connect 17 1 18 0;
#P connect 1 1 6 1;
#P fasten 18 0 19 1 51 459 63 459;
#P connect 1 2 7 0;
#P connect 5 0 6 2;
#P fasten 9 0 26 0 160 395 105 395;
#P connect 26 0 24 0;
#P connect 8 2 10 0;
#P fasten 30 0 26 1 160 428 121 428;
#P connect 1 3 6 3;
#P fasten 31 0 26 2 160 461 137 461;
#P fasten 32 0 26 3 160 492 153 492;
#P fasten 20 1 9 0 397 344 160 344;
#P fasten 10 0 9 0 109 364 160 364;
#P fasten 20 1 30 0 397 344 160 344;
#P fasten 10 0 30 0 109 364 160 364;
#P fasten 20 1 31 0 397 344 160 344;
#P fasten 10 0 31 0 109 364 160 364;
#P fasten 20 1 32 0 397 344 160 344;
#P fasten 10 0 32 0 109 364 160 364;
#P connect 1 4 6 4;
#P connect 27 0 26 4;
#P connect 26 1 4 0;
#P connect 1 5 6 5;
#P connect 1 6 6 6;
#P connect 14 0 15 0;
#P connect 15 0 16 0;
#P connect 16 0 21 0;
#P connect 21 0 20 0;
#P pop;
Cheers


Quote: hans.mittendorf@free.fr wrote on Sat, 26 May 2007 09:24

> look at this patch. I was made by Gregory Taylor and is for vst,

> but that's the way to do it, I believe.

Yes, for the vst object. [au~] only prints out the info in the Max window :-(

Quote: hans.mittendorf@free.fr wrote on Sat, 26 May 2007 09:24
----------------------------------------------------
> look at this patch. I was made by Gregory Taylor and is for vst,
> but that's the way to do it, I believe.
----------------------------------------------------

I just received a new version of the au object from Micheal. He has added a fourth output. Maybe he has it on his website already.

http://www.michaelnorris.info/software.html

I just received a new version of the au object from Micheal. He has added a fourth output. Maybe he has it on his website already.
http://www.michaelnorris.info/software.html


Quote: hans.mittendorf@free.fr wrote on Sat, 26 May 2007 10:04

> I just received a new version of the au object from Micheal. 

> He has added a fourth output. Maybe he has it on his website

Quote: hans.mittendorf@free.fr wrote on Sat, 26 May 2007 10:04
----------------------------------------------------
> I just received a new version of the au object from Micheal. 
> He has added a fourth output. Maybe he has it on his website
> already.
> http://www.michaelnorris.info/software.html
----------------------------------------------------

Great, the new 'plug ' message makes the whole scripting thing redundant

- unfortunately, creating an instance of the newest version (b.03) crashes

Anyone else finding this ? Did the b.02 version accept the 'plug' message,

and if so, could someone send me a copy ?

Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000007

0 com.cycling74.MaxMSP46 0x000680f9 freeobject + 23

1 com.cycling74.MaxAPI 0x0180991d freeobject + 30

2 info.michaelnorris.au~ 0x0e07e6b4 au_closewindow + 75

3 info.michaelnorris.au~ 0x0e07e79e open_au + 97

4 info.michaelnorris.au~ 0x0e07ecd2 au_new + 121

5 com.cycling74.MaxMSP46 0x0003091d typedmess_fun + 1943

6 com.cycling74.MaxMSP46 0x0011d7e0 object_new_typed + 166

7 com.cycling74.MaxMSP46 0x00023d32 auxtable_search + 154

8 com.cycling74.MaxMSP46 0x000263c4 extload + 374

9 com.cycling74.MaxMSP46 0x00026703 newload_internal + 665

10 com.cycling74.MaxMSP46 0x00026807 newload + 47

11 com.cycling74.MaxMSP46 0x0003023f typedmess_fun + 185

12 com.cycling74.MaxMSP46 0x00030c96 typedmess + 80

13 com.cycling74.MaxMSP46 0x000316f4 aeval + 1242

14 com.cycling74.MaxMSP46 0x00009750 atombuf_eval + 204

15 com.cycling74.MaxMSP46 0x000b96d5 patcher_vnewex + 165

16 com.cycling74.MaxMSP46 0x00030286 typedmess_fun + 256

17 com.cycling74.MaxMSP46 0x00030c96 typedmess + 80

18 com.cycling74.MaxMSP46 0x00031d25 eval + 1331

19 com.cycling74.MaxMSP46 0x0000adb7 binbuf_loadeval + 133

20 com.cycling74.MaxMSP46 0x0013f6f1 clipboard_newfrom + 105

On 26/5/07 09:24, "Philippe Gruchet" wrote:

> Quote: hans.mittendorf@free.fr wrote on Sat, 26 May 2007 10:04

> ----------------------------------------------------

>> I just received a new version of the au object from Micheal.

>> He has added a fourth output. Maybe he has it on his website

Great, the new 'plug ' message makes the whole scripting thing redundant
- unfortunately, creating an instance of the newest version (b.03) crashes
Max instantly :-(
 Anyone else finding this ? Did the b.02 version accept the 'plug' message,
and if so, could someone send me a copy ?
 Crashlog snippet below,
Cheers
Roger

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000007

Thread 0 Crashed:
0   com.cycling74.MaxMSP46             0x000680f9 freeobject + 23
(utilities.c:408)
1   com.cycling74.MaxAPI               0x0180991d freeobject + 30
2   info.michaelnorris.au~             0x0e07e6b4 au_closewindow + 75
3   info.michaelnorris.au~             0x0e07e79e open_au + 97
4   info.michaelnorris.au~             0x0e07ecd2 au_new + 121
5   com.cycling74.MaxMSP46             0x0003091d typedmess_fun + 1943
(message.c:678)
6   com.cycling74.MaxMSP46             0x0011d7e0 object_new_typed + 166
(obex.c:664)
7   com.cycling74.MaxMSP46             0x00023d32 auxtable_search + 154
(install.c:367)
8   com.cycling74.MaxMSP46             0x000263c4 extload + 374
(loader.c:542)
9   com.cycling74.MaxMSP46             0x00026703 newload_internal + 665
(loader.c:622)
10  com.cycling74.MaxMSP46             0x00026807 newload + 47
(loader.c:564)
11  com.cycling74.MaxMSP46             0x0003023f typedmess_fun + 185
(message.c:488)
12  com.cycling74.MaxMSP46             0x00030c96 typedmess + 80
(message.c:399)
13  com.cycling74.MaxMSP46             0x000316f4 aeval + 1242
(message.c:1061)
14  com.cycling74.MaxMSP46             0x00009750 atombuf_eval + 204
(atombuf.c:234)
15  com.cycling74.MaxMSP46             0x000b96d5 patcher_vnewex + 165
(vnewobj.c:486)
16  com.cycling74.MaxMSP46             0x00030286 typedmess_fun + 256
(message.c:492)
17  com.cycling74.MaxMSP46             0x00030c96 typedmess + 80
(message.c:399)
18  com.cycling74.MaxMSP46             0x00031d25 eval + 1331
(message.c:1316)
19  com.cycling74.MaxMSP46             0x0000adb7 binbuf_loadeval + 133
(binbuf.c:350)
20  com.cycling74.MaxMSP46             0x0013f6f1 clipboard_newfrom + 105
(clipboard.c:19)

On 26/5/07 09:24, "Philippe Gruchet"  wrote:

>
> Quote: hans.mittendorf@free.fr wrote on Sat, 26 May 2007 10:04
> ----------------------------------------------------
>> I just received a new version of the au object from Micheal.
>> He has added a fourth output. Maybe he has it on his website
>> already.
>> http://www.michaelnorris.info/software.html
> ----------------------------------------------------
>
> Yes, thanks!
>
>

Quote: roger.carruthers wrote on Sat, 26 May 2007 14:48

> Great, the new 'plug ' message makes the whole scripting

> - unfortunately, creating an instance of the newest version

> (b.03) crashes Max instantly :-( Anyone else finding this ?

No crash here. Does it crash with this patch?:

> Did the b.02 version accept the 'plug' message

> and if so, could someone send me a copy ?

Quote: roger.carruthers wrote on Sat, 26 May 2007 14:48
----------------------------------------------------
> Great, the new 'plug ' message makes the whole scripting
> thing redundant
> - unfortunately, creating an instance of the newest version
> (b.03) crashes Max instantly :-( Anyone else finding this ? 

I can confirm the crash Roger mentions under MAX.msp 4.6.2, with the 

au~ beta .3. MB Pro Intel Core Duo, 2.16 GHz.

This patch crashed 3 times in succession. To be specific, attempting 

to open it via 'New from Clip Board' crashed 3 times in a row. 

Further, any attempt to substantiate the au~ (beta .3) object in a 

clean patcher crashes the program. When I say crash, I mean it 

immediately closes the program, no hanging, etc.

On May 26, 2007, at 5:02 PM, Philippe Gruchet wrote:

> Quote: roger.carruthers wrote on Sat, 26 May 2007 14:48

>> Great, the new 'plug ' message makes the whole scripting

>> - unfortunately, creating an instance of the newest version

>> (b.03) crashes Max instantly :-( Anyone else finding this ?

> No crash here. Does it crash with this patch?:

"Sound still remains to be deciphered, hence the idea of an 

introduction to the sound object to train the ear to listen in a new 

way: this requires that the conventional listening habits imparted by 

::Pierre Schaeffer, Solfege de l'objet Sonore (1966)

I can confirm the crash Roger mentions under MAX.msp 4.6.2, with the  
au~ beta .3.  MB Pro Intel Core Duo, 2.16 GHz.

This patch crashed 3 times in succession.  To be specific, attempting  
to open it via 'New from Clip Board' crashed 3 times in a row.   
Further, any attempt to substantiate the au~ (beta .3) object in a  
clean patcher crashes the program.  When I say crash, I mean it  
immediately closes the program, no hanging, etc.

> Quote: roger.carruthers wrote on Sat, 26 May 2007 14:48
> ----------------------------------------------------
>> Great, the new 'plug ' message makes the whole scripting
>> thing redundant
>> - unfortunately, creating an instance of the newest version
>> (b.03) crashes Max instantly :-( Anyone else finding this ?
>
> No crash here. Does it crash with this patch?:
>
> 

"Sound still remains to be deciphered, hence the idea of an  
introduction to the sound object to train the ear to listen in a new  
way: this requires that the conventional listening habits imparted by  
education first be unlearned."

> Do you know how to extract any info displayed in the Max window from

Please bang cycling for this feature request, I made several proposals 

I think it would be so useful that its essential (lets see what Max 5 

Philippe Gruchet schrieb:
> Do you know how to extract any info displayed in the Max window from
> the Max window?

Please bang cycling for this feature request, I made several proposals 
already over the years...
I think it would be so useful that its essential (lets see what Max 5 
will give us...)

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


It is annoying not to be able to copy it;

yeah, I second it!!
It is annoying not to be able to copy it;


when the window opens you will have your text and you can copy with the copy function from the menu

you click on the Max window
you chose save as from the menue
you save it to the desktop
then you chose
open as text file from the menue
when the window opens you will have your text and you can copy with the copy function from the menu
have fun


On 28 mai 07, at 12:00, Hans Mittendorf wrote:

> when the window opens you will have your text and you can copy with 

- activate the Max window (make sure it's the frontmost window)

> Oh, one way to do it is:
>
> you click on the Max window
> you chose save as from the menue
> you save it to the desktop
> then you chose
> open as text file from the menue
> when the window opens you will have your text and you can copy with  
> the copy function from the menu
> have fun

For me:
- activate the Max window (make sure it's the frontmost window)
- copy from edit menu

o.k. that's better, but you can't extract before you paste....

On 28 mai 07, at 12:20, Hans Mittendorf wrote:

> o.k. that's better, but you can't extract before you paste....

You can if it's an error message (with the error object). For au~ 

object, it would make sense that the Audio Unit list comes out one 

You can if it's an error message (with the error object). For au~  
object, it would make sense that the Audio Unit list comes out one  
au~'s outlet.

I recommend to go to Micheal's website and download the latest au~object.

I recommend to go to Micheal's website and download the latest au~object.
Things have changed a lot.


Do you know if the crash issue reported by Roger and Jason solved? Sorry 

> I recommend to go to Micheal's website and download the latest au~object.

Do you know if the crash issue reported by Roger and Jason solved? Sorry 
for being lazy... ;-)

Hans Mittendorf wrote:
> I recommend to go to Micheal's website and download the latest au~object.
> Things have changed a lot.


So far, to the best of my knowledge the au object is limited for the moment to the plug ins Micheal has provided. I will mention this problem.

What has been done is parameter control. That's really nice!!!

So far, to the best of my knowledge the au object is limited for the moment to the plug ins Micheal has provided. I will mention this problem.
What has been done is parameter control. That's really nice!!!


Quote: hans.mittendorf@free.fr wrote on Mon, 28 May 2007 13:35

> I recommend to go to Micheal's website and download the latest 

That's always the b3 version. Works fine on G5 machines!

Quote: hans.mittendorf@free.fr wrote on Mon, 28 May 2007 13:35
----------------------------------------------------
> I recommend to go to Micheal's website and download the latest 
> au~object. Things have changed a lot.
----------------------------------------------------

That's always the b3 version. Works fine on G5 machines!


Quote: hans.mittendorf@free.fr wrote on Mon, 28 May 2007 12:00

> when the window opens you will have your text and you can copy

Quote: hans.mittendorf@free.fr wrote on Mon, 28 May 2007 12:00
----------------------------------------------------
> you click on the Max window
> you chose save as from the menu
> you save it to the desktop
> then you chose
> open as text file from the menue
> when the window opens you will have your text and you can copy
> with the copy function from the menu
----------------------------------------------------

I get an eerror message
error shell no such object

I put the shell objects into place but running the script does nothing.

I put the shell objects into place but running the script does nothing.
What was to expect from the patch?


What version of Max are you using? Version 4.6.3 fixes a problem (on 

Intel macs) which affected the shell object.

Am 29.05.2007 um 14:23 schrieb Hans Mittendorf:

Au~ scripting