Bug report: jit.gl.slab not able to change context

Aug 11, 2007 at 3:36pm

Bug report: jit.gl.slab not able to change context

Summary:

jit.gl.slab do not seem able to change to another context than what it
was instantiated with.

Steps to Reproduce:

1) Open the patch below.
2) Start qmetro.

Result:
You get a white jit.window. Not surprising really, as jit.gl.slab is set
to draw to another context (“bar”) than the one that is rendered (“fa”).

4) Change drawinf context for jit.gl.slab by clicking the “drawto fa”
message box.

Expected result:
jit.gl.slab should now draw to the proper context, and images be seen.

Actual result:
The window remains white.

5) Try reloading the slab by clicking the “read co.additive.jxs” message
box.

Result:
Nothing

6) Click the “getparamlist” message box

Result:
Nothing is reported to the Max window.

7) Recreate the jit.gl.slab object by changing the “bar” argument for “fa”.

Result: Only now the slab start working.

Regression:
Max 4.6.3, Jitter 1.6.3.
Max OSX 10.4.10
2.33 GHz Intel Core 2 Duo MacBookPro

Am I missing something, or is there a problem here?

Thanks,
Trond

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P newex 158 59 32 196617 sel 1;
#P message 158 86 102 196617 read countdown.mov;
#P message 317 86 82 196617 read dishes.mov;
#P message 27 196 100 196617 read co.additive.jxs;
#P message 37 215 54 196617 drawto fa;
#P newex 317 127 144 196617 jit.qt.movie 320 240;
#P flonum 239 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P message 239 182 57 196617 amount $1;
#P newex 238 200 76 196617 prepend param;
#P newex 342 276 32 196617 print;
#P message 168 202 67 196617 getparamlist;
#P newex 21 145 70 196617 jit.window fa;
#P newex 158 276 182 196617 jit.gl.videoplane fa @scale 1.333 1. 1.;
#P newex 21 123 121 196617 jit.gl.render fa @ortho 2;
#P newex 21 79 58 196617 t b b erase;
#P newex 158 249 169 196617 jit.gl.slab bar @file co.additive.jxs;
#P toggle 21 37 15 0;
#P newex 21 58 51 196617 qmetro 2;
#P newex 158 127 144 196617 jit.qt.movie 320 240;
#P comment 177 161 62 196617 mix amount;
#P connect 3 0 2 0;
#P connect 2 0 5 0;
#P connect 5 0 6 0;
#P fasten 5 2 6 0 74 105 26 105;
#P fasten 3 0 19 0 26 55 163 55;
#P connect 19 0 18 0;
#P connect 18 0 1 0;
#P fasten 5 1 1 0 50 117 163 117;
#P fasten 11 0 4 0 243 223 163 223;
#P connect 1 0 4 0;
#P fasten 9 0 4 0 173 223 163 223;
#P fasten 15 0 4 0 42 239 163 239;
#P fasten 16 0 4 0 32 239 163 239;
#P connect 4 0 7 0;
#P connect 12 0 11 0;
#P connect 13 0 12 0;
#P connect 14 0 4 1;
#P fasten 19 0 17 0 163 81 322 81;
#P connect 17 0 14 0;
#P fasten 5 1 14 0 50 117 322 117;
#P fasten 4 1 10 0 322 271 347 271;
#P window clipboard copycount 20;

#33215
Aug 11, 2007 at 6:06pm

Hm. If you control/option click, it *says* its drawing to ‘fa’, so it
might be a different issue, but either way it isnt working.

:)

On Aug 11, 2007, at 11:36 AM, Trond Lossius wrote:

> Summary:
>
> jit.gl.slab do not seem able to change to another context than what
> it was instantiated with.
>
> Steps to Reproduce:
>
> 1) Open the patch below.
> 2) Start qmetro.
>
> Result:
> You get a white jit.window. Not surprising really, as jit.gl.slab
> is set to draw to another context (“bar”) than the one that is
> rendered (“fa”).
>
> 4) Change drawinf context for jit.gl.slab by clicking the “drawto
> fa” message box.
>
> Expected result:
> jit.gl.slab should now draw to the proper context, and images be seen.
>
> Actual result:
> The window remains white.
>
> 5) Try reloading the slab by clicking the “read co.additive.jxs”
> message box.
>
> Result:
> Nothing
>
> 6) Click the “getparamlist” message box
>
> Result:
> Nothing is reported to the Max window.
>
> 7) Recreate the jit.gl.slab object by changing the “bar” argument
> for “fa”.
>
> Result: Only now the slab start working.
>
>
> Regression:
> Max 4.6.3, Jitter 1.6.3.
> Max OSX 10.4.10
> 2.33 GHz Intel Core 2 Duo MacBookPro
>
>
> Am I missing something, or is there a problem here?
>
> Thanks,
> Trond
>
>
>
>
>
> #P window setfont “Sans Serif” 9.;
> #P window linecount 1;
> #P newex 158 59 32 196617 sel 1;
> #P message 158 86 102 196617 read countdown.mov;
> #P message 317 86 82 196617 read dishes.mov;
> #P message 27 196 100 196617 read co.additive.jxs;
> #P message 37 215 54 196617 drawto fa;
> #P newex 317 127 144 196617 jit.qt.movie 320 240;
> #P flonum 239 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 239 182 57 196617 amount $1;
> #P newex 238 200 76 196617 prepend param;
> #P newex 342 276 32 196617 print;
> #P message 168 202 67 196617 getparamlist;
> #P newex 21 145 70 196617 jit.window fa;
> #P newex 158 276 182 196617 jit.gl.videoplane fa @scale 1.333 1. 1.;
> #P newex 21 123 121 196617 jit.gl.render fa @ortho 2;
> #P newex 21 79 58 196617 t b b erase;
> #P newex 158 249 169 196617 jit.gl.slab bar @file co.additive.jxs;
> #P toggle 21 37 15 0;
> #P newex 21 58 51 196617 qmetro 2;
> #P newex 158 127 144 196617 jit.qt.movie 320 240;
> #P comment 177 161 62 196617 mix amount;
> #P connect 3 0 2 0;
> #P connect 2 0 5 0;
> #P connect 5 0 6 0;
> #P fasten 5 2 6 0 74 105 26 105;
> #P fasten 3 0 19 0 26 55 163 55;
> #P connect 19 0 18 0;
> #P connect 18 0 1 0;
> #P fasten 5 1 1 0 50 117 163 117;
> #P fasten 11 0 4 0 243 223 163 223;
> #P connect 1 0 4 0;
> #P fasten 9 0 4 0 173 223 163 223;
> #P fasten 15 0 4 0 42 239 163 239;
> #P fasten 16 0 4 0 32 239 163 239;
> #P connect 4 0 7 0;
> #P connect 12 0 11 0;
> #P connect 13 0 12 0;
> #P connect 14 0 4 1;
> #P fasten 19 0 17 0 163 81 322 81;
> #P connect 17 0 14 0;
> #P fasten 5 1 14 0 50 117 322 117;
> #P fasten 4 1 10 0 322 271 347 271;
> #P window clipboard copycount 20;
>

v a d e //

http://www.vade.info
abstrakt.vade.info

#110357
Aug 12, 2007 at 6:37pm

Thanks for this report. I can reproduce.

wes

#110358
Aug 12, 2007 at 7:31pm

#110359
Aug 13, 2007 at 1:30am

#110360
Aug 13, 2007 at 1:40am

I don’t think this problem has anything to do with shader files but
instead with the offscreen context generated by jit.gl.texture
internal to jit.gl.slab for processing input textures. Clearly
something is not being initialized or destructed appropriately and is
throwing errors to the Max window. I’ve noticed this behavior as
well. If anyone has any simple patches that generate these errors
consistently, please post ‘em.

thanks,
wes

#110361
Aug 13, 2007 at 2:07am

Hi Wes-
Did you see my post before posting this? There is an example patch in
there. Or is it that you not get the same errors on this patch/shader
combo?
BTW here are my machine specs if that helps:

Hardware Overview:

Model Name: MacBook Pro 15″
Model Identifier: MacBookPro2,2
Processor Name: Intel Core 2 Duo
Processor Speed: 2.33 GHz
Memory: 2 GB
ATI Radeon X1600
VRAM (Total): 256 MB

-md

On Aug 12, 2007, at 6:40 PM, Wesley Smith wrote:

> I don’t think this problem has anything to do with shader files but
> instead with the offscreen context generated by jit.gl.texture
> internal to jit.gl.slab for processing input textures. Clearly
> something is not being initialized or destructed appropriately and is
> throwing errors to the Max window. I’ve noticed this behavior as
> well. If anyone has any simple patches that generate these errors
> consistently, please post ‘em.
>
> thanks,
> wes
>
>

#110362
Aug 13, 2007 at 2:25am

Hmm. I’m unable to reproduce on either an intel imac with almost the
same config as yours or on my mac book pro with an nvidia 8600. I’m
using the latest Jitter. What are you using?

wes

On 8/12/07, MarkDavid Hosale wrote:
> Hi Wes-
> Did you see my post before posting this? There is an example patch in
> there. Or is it that you not get the same errors on this patch/shader
> combo?
> BTW here are my machine specs if that helps:
>
> Hardware Overview:
>
> Model Name: MacBook Pro 15″
> Model Identifier: MacBookPro2,2
> Processor Name: Intel Core 2 Duo
> Processor Speed: 2.33 GHz
> Memory: 2 GB
> ATI Radeon X1600
> VRAM (Total): 256 MB
>
> -md
>
>
>
> On Aug 12, 2007, at 6:40 PM, Wesley Smith wrote:
>
> > I don’t think this problem has anything to do with shader files but
> > instead with the offscreen context generated by jit.gl.texture
> > internal to jit.gl.slab for processing input textures. Clearly
> > something is not being initialized or destructed appropriately and is
> > throwing errors to the Max window. I’ve noticed this behavior as
> > well. If anyone has any simple patches that generate these errors
> > consistently, please post ‘em.
> >
> > thanks,
> > wes
> >
> >
>
>

#110363
Aug 13, 2007 at 2:32am

Here’s what I got:

Jitter 1.6.3 installed
MXJ System CLASSPATH:
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/jitter.jar
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/jode-1.1.2-pre-
embedded.jar
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/max.jar
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/mysql-connector-
java#10E70A.jar
MXJClassloader CLASSPATH:
/Applications/MaxMSP 4.6/Cycling ’74/java/classes/
/Users/markdavid_laptop/MarkDavidLaptopDocs/CURRENT PROJECTS/
MD_Max_java_files/
Jitter Java support installed

Maybe I should get me a hoodoo charm, or a rabbit’s foot?

Anyway, could be worse… Is anyone else able to reproduce…
-md

On Aug 12, 2007, at 7:25 PM, Wesley Smith wrote:

> Hmm. I’m unable to reproduce on either an intel imac with almost the
> same config as yours or on my mac book pro with an nvidia 8600. I’m
> using the latest Jitter. What are you using?
>
> wes
>
> On 8/12/07, MarkDavid Hosale wrote:
>> Hi Wes-
>> Did you see my post before posting this? There is an example patch in
>> there. Or is it that you not get the same errors on this patch/shader
>> combo?
>> BTW here are my machine specs if that helps:
>>
>> Hardware Overview:
>>
>> Model Name: MacBook Pro 15″
>> Model Identifier: MacBookPro2,2
>> Processor Name: Intel Core 2 Duo
>> Processor Speed: 2.33 GHz
>> Memory: 2 GB
>> ATI Radeon X1600
>> VRAM (Total): 256 MB
>>
>> -md
>>
>>
>>
>> On Aug 12, 2007, at 6:40 PM, Wesley Smith wrote:
>>
>>> I don’t think this problem has anything to do with shader files but
>>> instead with the offscreen context generated by jit.gl.texture
>>> internal to jit.gl.slab for processing input textures. Clearly
>>> something is not being initialized or destructed appropriately
>>> and is
>>> throwing errors to the Max window. I’ve noticed this behavior as
>>> well. If anyone has any simple patches that generate these errors
>>> consistently, please post ‘em.
>>>
>>> thanks,
>>> wes
>>>
>>>
>>
>>
>
>

#110364
Sep 3, 2007 at 6:42pm

Coming in late on this one again, as I have kept working on slab-based
patches and seen some more patterns that might be worth reporting.

I am not able to find any consistent steps that will produce the errors.
However, when the error appears, it starts immediately as soon as I
start rendering to a new context (e.g. first time after opening the
patch and starting to bang jit.gl.render et al.). And I have found a
simple workaround that seems to consistently solve the problem without
having to close the patch or restart Max: If I use a rect message to
jit.window to resize/move it somewhere else, and then move it back where
I want it to be, the errors are gone and rendering and slabs work as
supposed to. I don’t know if this might provide some additional clues to
tracking down what causes it.

Best,
Trond

Wesley Smith wrote:
> I don’t think this problem has anything to do with shader files but
> instead with the offscreen context generated by jit.gl.texture
> internal to jit.gl.slab for processing input textures. Clearly
> something is not being initialized or destructed appropriately and is
> throwing errors to the Max window. I’ve noticed this behavior as
> well. If anyone has any simple patches that generate these errors
> consistently, please post ‘em.
>
> thanks,
> wes
>

#110365

You must be logged in to reply to this topic.