ComfortableInClouds

Hello, I just recently downloaded monolake's PX-18 drum sequencer patch from the userpages, which looks incredible, like the drum sequencer to end all drum sequencers. problem is, it doesn't seem to be running properly. I get several errors in the Max window upon loading it. they are as follows

So, even if you don't know this patch, i was wondering whether you knew where i could find an 'igate' object. also, how might it be possible to locate the specific 'tempo' and 'table' object the max window is talking about?

Hello, I just recently downloaded monolake's PX-18 drum sequencer patch from the userpages, which looks incredible, like the drum sequencer to end all drum sequencers. problem is, it doesn't seem to be running properly. I get several errors in the Max window upon loading it. they are as follows 

-igate: No such object; 
-tempo doesn't understand  "float"; 
-table doesn't understand "set".

px-18-trouble-missing-object-locating-errors

On 18 juin 08, at 19:10, Kyle Kaplan wrote:

igate is a third party object. You probably could replace it by a gate 

This has already been fixed for the next incremental release.

It works for me, which version do you have? Could you provide a patch?

igate is a third party object. You probably could replace it by a gate  
object.

I have what appeared to be the latest version from the userpages. I've attached the patch.

Also, even if igate can be replaced by 'gate', how do i locate the igate object in such a large patch? Is there any sort of object path in Max? like you can ask for an object's location in the patch in terms of subpatches and connections?

> I get several errors in the Max window upon

just duplicate the external gate, and rename it igate. It was an 

optimized gate in the old days where the speed of an 68000 processor was 

1 MHz. (at least 5000 times slower than an actual processor)

You could try to open it in Max 5. Its easier to locate the object 

there... (double click on the error message...)

Kyle Kaplan schrieb:
> I get several errors in the Max window upon
> loading it. they are as follows
>
> -igate: No such object;

just duplicate the external gate, and rename it igate. It was an 
optimized gate in the old days where the speed of an 68000 processor was 
1 MHz. (at least 5000 times slower than an actual processor)
Not an issue nowadays...

> -tempo doesn't understand "float";
> -table doesn't understand "set".

You could try to open it in Max 5. Its easier to locate the object 
there... (double click on  the error message...)

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


Ah, never knew that bit about the double-clicking in the max window! What a good thing to know. Much thanks.

Has no one else who uses this patch gotten these errors before? Why does one suppose that it's not working for me? also, i looked for the gate external, but only found gate~. I tried replacing the igate objects with a gate object and now when i load the patch it freezes Max everytime. I do hope I can get this patch working because it looks amazingly useful.

> Has no one else who uses this patch gotten these errors before? Why

> does one suppose that it's not working for me? also, i looked for the

> gate external, but only found gate~. I tried replacing the igate

> objects with a gate object and now when i load the patch it freezes

> Max everytime. I do hope I can get this patch working because it

I guess gate is a standard object since its first incarnation almost 20 

years ago... Maybe you have another object called gate in your search path?

Its funny that this patch is utilising igate, because in the same 

subpatcher he is placing a bunch of buttons. To replace these with [b] 

would be magnitudes more effective than replacing gate with igate... 

(Back then, but even today I'd replace the buttons...)

Kyle Kaplan schrieb:
> Has no one else who uses this patch gotten these errors before? Why
> does one suppose that it's not working for me? also, i looked for the
> gate external, but only found gate~. I tried replacing the igate
> objects with a gate object and now when i load the patch it freezes
> Max everytime. I do hope I can get this patch working because it
> looks amazingly useful. -- -k. 

I guess gate is a standard object since its first incarnation almost 20 
years ago... Maybe you have another object called gate in your search path?
Its funny that this patch is utilising igate, because in the same 
subpatcher he is placing a bunch of buttons. To replace these with [b] 
would be magnitudes more effective than replacing gate with igate... 
(Back then, but even today I'd replace the buttons...)

PX-18 Trouble - Missing Object + Locating Errors