Eryck Abecassis

I just found a kind of conflict between pluggo 

(in vst~) and the presence of a led object in the patch

in such a case Max says "unable to find picture 20100"

I just found a kind of conflict between pluggo 
(in vst~) and the presence of a led object in the patch

in such a case Max says "unable to find picture 20100"
and "unable to find picture 20101"
and of course led don't shine anymore

pluggo-354-and-the-led

I had the same error, but was not aware that

the vst object could be the reason. (OS 10.9.3)

anyway, after building a new custom led, everything worked fine.

I had the same error, but was not aware that
the vst object could be the reason. (OS 10.9.3)

>I had the same error, but was not aware that

the vst object could be the reason. (OS 10.9.3)<

not the vst~, but the pluggo, could be !?

the error appears here on both OS 10.3.9 and 10.4.6

hmmm, a custom led, with java script I suppose

>I had the same error, but was not aware that
the vst object could be the reason. (OS 10.9.3)<

hmmm, a custom led, with java script I suppose
but I 'm not yet a javaman !
later....

I built the led just with the picture based control: pctctrl.

no not java script.
I built the led just with the picture based control: pctctrl.
easy to do it that way.

>I just found a kind of conflict between pluggo 

>(in vst~) and the presence of a led object in the patch

>in such a case Max says "unable to find picture 20100"

I've had the same problem. didn't realize that pluggo was to blame. i

>I just found a kind of conflict between pluggo 
>(in vst~) and the presence of a led object in the patch
>
>in such a case Max says "unable to find picture 20100"
>and "unable to find picture 20101"
>and of course led don't shine anymore

I've had the same problem. didn't realize that pluggo was to blame. i
replaced my led with toggle.

> I just found a kind of conflict between pluggo 

> (in vst~) and the presence of a led object in the patch

> in such a case Max says "unable to find picture 20100"

Its not pluggo related, I had this bug in a big performance patch as 

well. The led was inside a bpatcher. Seems to be worse on Dual G5 

computers, I guess its some internal message ordering bug...

Eryck Abecassis wrote:
> I just found a kind of conflict between pluggo 
> (in vst~) and the presence of a led object in the patch
>
> in such a case Max says "unable to find picture 20100"
> and "unable to find picture 20101"
> and of course led don't shine anymore
>
> well, not a horrible bug, but...

Its not pluggo related, I had this bug in a big performance patch as 
well. The led was inside a bpatcher. Seems to be worse on Dual G5 
computers, I guess its some internal message ordering bug...

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


no problem with empty vst~or a GRM tools inside it

bug when vst~ contains a pluggo, like swish or comber for exemple

What makes me say it is the pluggo:
an experience with a blank patch
just with a led and a vst~ :

 no problem with empty vst~or a GRM tools inside it

 bug when vst~ contains a pluggo, like swish or comber for exemple

Bugs which shows up in Max most likely shows up as well in Pluggo...

Its just a pointer to the friendly bugfixers at cycling which also read

Eryck Abecassis wrote:
> is it a proof ? maybe not ...

Bugs which shows up in Max most likely shows up as well in Pluggo...
Its just a pointer to the friendly bugfixers at cycling which also read
this list...

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

pluggo 354 and the led