Gary Lee Nelson

Jeremy Bernstein just updated my seedable random number generators for Max 6/7.

I will be posting these on the forum (when I figure out how). .zip attached.

I will be posting these on the forum (when I figure out how).  .zip attached.

Cheers
Gary Lee Nelson
TIMARA Department
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson


third-party-objects-that-run-in-the-new-max

Litter Power is working... although it has been a lot of work to make it happen.

I sent out an announcement to registered Litter Pros just an hour ago.

Litter Bundle for Jitter is in testing and should be out Real Soon Now.

A new version of the Litter Starter Pack will be out shortly after the LBJ release.

Most of the objects from 1.7 actually run unchanged and provide their core functionality. However, there are a number of cosmetic error messages listed in the Max window, Assistance disappears, and the previous response to the Get Info menu command is no longer supported. On top of that, Max 5 is happier if Litter Power makes a lot of other changes. Since we want Max 5 to be happy, the changes are being made.

Litter Power is working... although it has been a lot of work to make it happen. 

As I also mentioned in some other thread, the Tap.Tools 3 beta 

(available from electrotap.com) works in Max 5.

Tap.Tools 2 doesn't function whatsoever. As with Peter, it's been a 

tremendous amount of work getting a large package like this up and 

running. And the work isn't done -- which is why TT3 is called a beta 

As I also mentioned in some other thread, the Tap.Tools 3 beta  
(available from electrotap.com) works in Max 5.

Tap.Tools 2 doesn't function whatsoever.  As with Peter, it's been a  
tremendous amount of work getting a large package like this up and  
running.  And the work isn't done -- which is why TT3 is called a beta  
for the moment.

best,
   Tim
_________________
Tap.Tools / Teabox / Hipno / Hemisphere
http://electrotap.com


Just tried Peter Elsea's list package. I did test everything but 

Just tried Peter Elsea's list package.  I did test everything but  
there were no complaints from Max 5.

Cheers
Gary Lee Nelson
TIMARA Department
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson

I did NOT test every object in Elsea's group but the ones I tested 

On Apr 24, 2008, at 12:31 PM, Gary Lee Nelson wrote:

> Just tried Peter Elsea's list package. I did test everything but 

I did NOT test every object in Elsea's group but the ones I tested  
worked perfectly.
Cheers
Gary Lee Nelson
TIMARA Department
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson

> Just tried Peter Elsea's list package.  I did test everything but  
> there were no complaints from Max 5.
>
> Cheers
> Gary Lee Nelson
> TIMARA Department
> Oberlin College
> www.timara.oberlin.edu/GaryLeeNelson
>
>


i went through my collection of objects and found only two externals 

(out of 109) that aren't working in Max 5 and will need to be fixed:

    mutual exclusive switching across the entire max-domain: this 

external traverses all patchers     and looks at each object's class, 

then sends the ones that are a mtx a typedmess.

    also runs through the patcher hierarchy and reports various fields of 

    scripting name, position etc. this has always been working on the 

    territory and might not make it across to the new API.

some objects have been superseded (read: copied) such as streamlist, 

which now has a zl cousin called (sic!) zl stream, changelist (you 

guessed it!) is zl change, sumlist gets zl sum, duplist gets zl thin.

the all time favorite "_" (underscore) is still there, is a little bit 

less useful with the advent of the right inlet to the message box and 

is much less elegant to look at in the shiny new environment.

i still advise everyone to update to the latest build 0.4.1 since 

there have been a number of bugfixes and slight improvements since 

that's all i have to report about the jasch_objects, which are 

i went through my collection of objects and found only two externals  
(out of 109) that aren't working in Max 5 and will need to be fixed:

- mtx:
	mutual exclusive switching across the entire max-domain: this  
external traverses all patchers 	and looks at each object's class,  
then sends the ones that are a mtx a typedmess.

- posit:
	also runs through the patcher hierarchy and reports various fields of  
an object, such as class,
	scripting name, position etc. this has always been working on the  
edge of undocumented 	
	territory and might not make it across to the new API.

some objects have been superseded (read: copied) such as streamlist,  
which now has a zl cousin called (sic!) zl stream, changelist (you  
guessed it!) is zl change, sumlist gets zl sum, duplist gets zl thin.

the all time favorite "_" (underscore) is still there, is a little bit  
less useful with the advent of the right inlet to the message box and  
is much less elegant to look at in the shiny new environment.

i still advise everyone to update to the latest build 0.4.1 since  
there have been a number of bugfixes and slight improvements since  
last year's release.

that's all i have to report about the jasch_objects, which are  
available as usual from here:

Quote: jasch wrote on Thu, 24 April 2008 19:29

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

> this external traverses all patchers....

Yeah, lp.argus and lp.mrsnorris were burnt by this, too. Sometimes it's nice to know one's not alone.

Quote: jasch wrote on Thu, 24 April 2008 19:29
----------------------------------------------------
> - mtx:
> this external traverses all patchers....
----------------------------------------------------

Yeah, lp.argus and lp.mrsnorris were burnt by this, too. Sometimes it's nice to know one's not alone. 

would it be possible to get some source code for some of your objects?

specifically, the bcf one. i have a bcr, and i imagine that with slight modification, i could adapt the bcf object into an equivalent bcr object...

would it be possible to get some source code for some of your objects?
specifically, the bcf one. i have a bcr, and i imagine that with slight modification, i could adapt the bcf object into an equivalent bcr object...


On 2008 Apr 24, at 12:46 PM, Peter Castine wrote:

> Quote: jasch wrote on Thu, 24 April 2008 19:29

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

>> this external traverses all patchers....

> Yeah, lp.argus and lp.mrsnorris were burnt by this, too. Sometimes 

Yep. Jamoma too. But, at least with Jamoma, we were well aware it 

would all break -- we just didn't know how long until it broke. I 

anticipate that Jamoma will be in good shape for Max 5 by the end of 

On 2008 Apr 24, at 12:46 PM, Peter Castine wrote:
>
> Quote: jasch wrote on Thu, 24 April 2008 19:29
> ----------------------------------------------------
>> - mtx:
>> this external traverses all patchers....
> ----------------------------------------------------
>
> Yeah, lp.argus and lp.mrsnorris were burnt by this, too. Sometimes  
> it's nice to know one's not alone.

Yep.  Jamoma too.  But, at least with Jamoma, we were well aware it  
would all break -- we just didn't know how long until it broke.  I  
anticipate that Jamoma will be in good shape for Max 5 by the end of  
June.

For some reason the Lobjects doesnt work on my macbook pro, I get a weird error message: Larray: not available for PowerPC. I get this for any Lobject. I have looked in my search path and havent found anything which would suggest a name conflict.

I`v been trying out the Tap.tools 3 for Max 5 and tap.limit~ does not seem to work for some reason. Anyone else have this problem?

On 2008 Apr 25, at 5:50 PM, Richardo del Pozo wrote:

> I`v been trying out the Tap.tools 3 for Max 5 and tap.limit~ does 

> not seem to work for some reason. Anyone else have this problem?

By tap.limit~, do you mean tap.limi~? On the Mac it should be okay. 

On Windows it is currently crashing, but I think we've got it fixed 

and will hopefully be able to push a fixed version to the software 

If you are on a Mac, could you possibly send details about your system 

On 2008 Apr 25, at 5:50 PM, Richardo del Pozo wrote:
>
> I`v been trying out the Tap.tools 3 for Max 5 and tap.limit~ does  
> not seem to work for some reason. Anyone else have this problem?

By tap.limit~, do you mean tap.limi~?  On the Mac it should be okay.   
On Windows it is currently crashing, but I think we've got it fixed  
and will hopefully be able to push a fixed version to the software  
update this weekend.

If you are on a Mac, could you possibly send details about your system  
to support@electrotap.com?  Thanks!
    Tim
_________________
Tap.Tools / Teabox / Hipno / Hemisphere
http://electrotap.com


Hi. Yes i meant tap.limi. Ill send you the details of whats wrong. R


The tap.5comb~.maxhelp complains about bad arguments for tap.lp-comb~... 

Richardo del Pozo schrieb:
> Anyone else have this problem? 

The tap.5comb~.maxhelp complains about bad arguments for tap.lp-comb~... 
(as expected 5 times...)

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

never mind my comment on the lobjects. I was a bit confused by the Lobjects website which links to an osx version which is old, the newest one is only available via ftp.

Thanks for pointing out the broken link- it is now fixed.

Lmap, Lgrid will not run because of the so far undocumented changes to display methods.

Larray, Ldumpster, file functions do not work. I don't know why, but presumably the new API will reveal all.

I am currently converting help files to be readable. I should be done sometime in July. Documentation in the new scheme may appear by Christmas.

(Another indignity to growing old, in addition to the AARP cards and automatically getting the senior discount in restaurants:

Setting my Max Default Fontsize to 12 point.)

(Another indignity to  growing old, in addition to the AARP cards and automatically getting the senior discount in restaurants:
Setting my Max Default Fontsize to 12 point.)

On 2008 May 22, at 3:30 PM, Peter Elsea wrote:

> Larray, Ldumpster, file functions do not work. I don't know why, but 

> presumably the new API will reveal all.

Are you using FSSpecs at all? Any FSSpec-related functions are no 

longer with us in Max 5. If you use the existing sysfile_* API as 

documented for Max 4 then you should be okay in Max 5. Not much has 

changed to the public interface for these file routines.

> Larray, Ldumpster, file functions do not work. I don't know why, but  
> presumably the new API will reveal all.

Are you using FSSpecs at all?  Any FSSpec-related functions are no  
longer with us in Max 5.  If you use the existing sysfile_* API as  
documented for Max 4 then you should be okay in Max 5.  Not much has  
changed to the public interface for these file routines.

Third party objects that run in Max 6/7?