For some reason with this version and the previous the getpluginnames button in the audiounit~ help does not work – it doesn’t generate a list of available plugins. I trashed the Max prefs but that didn’t help. Suggestions?

I suspect that maybe Max had been quit (or crashed) or something in the middle of doing the scan. If so then the database of plug-ins created by the scan would have been in a bad state. So then re-scanning fixed the problem.

If you do find something else going on, please let me know, and thanks for the report!
Tim

hey,
i’d like to report a bug. I think it’s the right place, it’s rather straightforward.
So…
Max freezes if :
audiounit~ has loaded a plug in without a custom gui (includes all Apple default plugs) ; then
user makes the plugin gui appear ; then
closes the max patcher in wich is the audiounit~ host.
You need to force Max to close then.

btw thanks for audiounit~, it’s great job even with that :) and i have a feature request as well : would it be possible to have a way to display a plugin gui appear inside a patch, not in a floating window, like if inside a bpatcher ? same question for vst~ btw…

minor niggle with the helpfile: in the subpatch "midi", the audiounit doesn´t load because of the first argument (i think). if one replaces the 0 by 2, all is fine.
seems audiounit~ doesn´t like to be without input.
(max 517, mac 10.6.7.)

i got message error windows with a little terminal icon, about plugins for example " native saying memory is getting low" and then its impossible to close the error windows, the weirdest thing is that even if i close max i got the window is staying,even relaucnhing the finder doesn’t help, only solution then is to logg off.

on my computer (mac10.6.8., max 5.1.8) when using the octogris au (http://www.iact.umontreal.ca/site/?page_id=1091&lang=en) even in the simple 2X2 configuration, opening and operating the pluginwindow works fine, but sending a wclose message crashes max.
would be nice to have these spatialisation plugins supported in max!

today, I wanted to connect an Absynth 5 audiounits plug in to the object.

Under recall presets, I get "disabled". I asked Brian Clevinger the designer of Absynth what to do. He instructed me to chose program and click on.

I did it but there are no presets listed. When I click clear inside preset communication the menu is cleared, when I click recall preset $1 I get nothing back.
Does anybody know what to do to get presets listed from Absynth?

I always like progress but I have just ported some patches from Max4 to 5 regarding the new audiounit object. Now, it has already changed again and when I look at the new vst/au object, it does not tell me more. I tried the Absynth plug in and try to load the presets but it could not do it.
Maybe it is still the same problem like I found under Max5, but in any case I have to learn about this object again…….Maybe it is for the better though…

A major drawback of the vst/au "unification" seems to be that parameter values are restricted to the range 0-1.
Also, from some quick tests I’ve got the impression that parameter names are not handled correctly.

In the Max6 version AUPitch seems to work correctly insofar as pitch actually corresponds to pitch.
But the problem is that it accepts only values in the range 0-1 (which doesn’t conform to the AU standard).

I HOPE that you still consider the au object of Max5 worth updating?!!!
As I said earlier, I had a problem with chosing program preset from an Absynth 5 plug in.
I can only say, regarding from what I saw the new object is like under 6, that it should have the same structure like au under 5. A list of programs, a list of plug ins, a list of parameters, hopefully inside an ubu menu. That was very elegant and easy to use.

I tried the vst. The prg names are there and I can switch between them. Unfortunately, the sound does not change. I tried the stand alone Absynth 5 and it is just like that too. I wrote to Brian and I hope he will tell me what the problem is.
But yes, vst does the prg changes.

I still need to use Max5 for some production work. Where can I find the very latest (last) version of the audiounit~ …. I found several beta versions mentioned in various forum posts but it was never clear which one was the most recent.

Would you be open to releasing the source for this external? I’ve tried using ~vst in Max 6 but have found ~audiounit to be much more stable, and I prefer it’s api. There are also some enhancements related to parameter processing that I’d like to bake into it, to avoid the messaging overhead.

I don’t really care about maintaining the source in a public repo, so if you’d prefer to just send it to me privately, I would be most grateful.

I would also love to get access to the source of this external. I’m desperately trying to switch to Max6 but I am still having problems with the [vst~] component sometimes causing Max to crash when a VST is freed. I’ve been contemplating writing my own VST wrapper but it’s a lot of work and I’d love to have an existing external from which to start (or just use).

I think the integration of VST and AU in [vst~] of Max6 is inherently problematic as both standards are using different parameter handling.
Keeping a separate [audiounit~] object in Max6 would be cleaner IMO.

in the last two years, I’ve began to developing several plugins and instruments which are ported as dll and vst to win (xp,w7) as osx (10.5.8, 10.6.8)

now is the ver.6 of Max on my machines (the difficult design is another point – I prefer more the outfit by Max 4.6.3 a kind of "constructivism")
and the ugly mistake in Max ver 5, 6 is the unavailability by these choices

If somebody has a practicable solution to available the export of my developed stuff as vst etc please let me this know
I’ve (and not myself) also interest for some howtos manuals or short guides about this tpoic (and others from the MaxMsp-world)
in german (sure I understand english, but sometimes is it more useful to read and recapitrulate the readings in native language)
thanks and regards