matrix resizing problem

Jan 30, 2008 at 12:11am

matrix resizing problem

hi all,
I am building an application in Jitter, and have come across this possibly very simple, yet baffling problem. My matrices keep switching planecount on me?!?

Now, this is absolutely user error at the root, but surely @adapt 0 should prevent this from ever happening? I need a jit.matrix 1 char 16 16, and it keeps screwing up for me. I have attached a small picture of the infected area for your perusal in lieue of a readable patch to give you.

Cheers for any insights… this is driving me nuts, to be honest.

#35569
Jan 30, 2008 at 12:18am

On 30 janv. 08, at 01:11, Andreas Wetterberg wrote:

> hi all,
> I am building an application in Jitter, and have come across this
> possibly very simple, yet baffling problem. My matrices keep
> switching planecount on me?!?
>
> Now, this is absolutely user error at the root, but surely @adapt 0
> should prevent this from ever happening? I need a jit.matrix 1 char
> 16 16, and it keeps screwing up for me. I have attached a small
> picture of the infected area for your perusal in lieue of a readable
> patch to give you.
>
> Cheers for any insights… this is driving me nuts, to be honest.

You’re right, @adapt 0 force the matrix to not adapt to the
characteristic of the input matrix, but in [jit.rubix] support only 4
planes (and @type char). So no matter what you do, [jit.rubix] will
output a 4 planes matrix. You probably need a [jit.unpack] if you want
to extract only one plane.

HTH,
ej

#121371
Jan 30, 2008 at 12:36am

On Jan 29, 2008, at 4:11 PM, Andreas Wetterberg wrote:

> hi all,
> I am building an application in Jitter, and have come across this
> possibly very simple, yet baffling problem. My matrices keep
> switching planecount on me?!?
>
> Now, this is absolutely user error at the root, but surely @adapt 0
> should prevent this from ever happening? I need a jit.matrix 1 char
> 16 16, and it keeps screwing up for me. I have attached a small
> picture of the infected area for your perusal in lieue of a
> readable patch to give you.
>
> Cheers for any insights… this is driving me nuts, to be
> honest.

Look at jit.rubix.help and/or the html reference page. This object
only accepts 4 plane char matrices. So your attempt to change this is
being overridden by the behavior of the object.

You’ll have to find either another solution or work with 4 plane
matrices and ignore the other planes.

-Joshua

#121372
Jan 30, 2008 at 1:40am

Yeah, the problem did also appear to occur with regular jit.matrix’es,
though… I figured that as long as I had adapt 0 on both the problem
shouldn’t be permeating the sytem like it did… hm. Thanks for your
help, Joshua and EJ.

Andreas.

Joshua Kit Clayton skrev:
>
> On Jan 29, 2008, at 4:11 PM, Andreas Wetterberg wrote:
>
>> hi all,
>> I am building an application in Jitter, and have come across this
>> possibly very simple, yet baffling problem. My matrices keep
>> switching planecount on me?!?
>>
>> Now, this is absolutely user error at the root, but surely @adapt 0
>> should prevent this from ever happening? I need a jit.matrix 1 char
>> 16 16, and it keeps screwing up for me. I have attached a small
>> picture of the infected area for your perusal in lieue of a readable
>> patch to give you.
>>
>> Cheers for any insights… this is driving me nuts, to be
>> honest.
>
>
> Look at jit.rubix.help and/or the html reference page. This object
> only accepts 4 plane char matrices. So your attempt to change this is
> being overridden by the behavior of the object.
>
> You’ll have to find either another solution or work with 4 plane
> matrices and ignore the other planes.
>
> -Joshua
>
> .
>

#121373
Jan 30, 2008 at 11:41am

On 30 janv. 08, at 02:40, Andreas Wetterberg wrote:

> Yeah, the problem did also appear to occur with regular
> jit.matrix’es, though…

Really? I can’t reproduce that.

ej

#P window setfont “Sans Serif” 9.;
#P user jit.fpsgui 188 207 60 196617 3;
#P user jit.fpsgui 122 207 60 196617 4;
#P user jit.fpsgui 189 124 60 196617 3;
#P user jit.fpsgui 123 124 60 196617 4;
#P button 103 64 15 0;
#P user jit.pwindow 102 252 82 62 0 1 0 0 1 0;
#P window linecount 1;
#P newex 103 169 173 196617 jit.matrix 1 char 320 240 @adapt 0;
#P newex 103 85 121 196617 jit.noise 4 char 320 240;
#P connect 1 0 2 0;
#P connect 1 0 6 0;
#P connect 1 0 7 0;
#P connect 0 0 1 0;
#P connect 0 0 4 0;
#P connect 0 0 5 0;
#P connect 3 0 0 0;
#P window clipboard copycount 8;

#121374

You must be logged in to reply to this topic.