jit.gl.render problem

    Bruno Zamborlin
    May 24 2006 | 1:45 pm
    Dear all, I have a problem with jit.gl.render. I'm using MaxMSP 4.5.5. and Jitter 1.5.2. (demo mode) on Windows XP.
    If I link a jit.noise (or something else) to a jit.pwindow everything is ok, but if I link jit.noise to a "jit.gl.render name" and I create a pwindow "name", it doesn't work.
    That's the patch that explain the problem:
    Where I am mistaking?
    Regards, Bruno
    • vade
      May 24 2006 | 3:34 pm
      Your patch works here, on OS X 10.4.6. Check the jitter list archives for Joshua Kit Claytons recommendation for PC drivers. I believe he recommends the latest ATI Catalyst drivers.
      v a d e //
      www.vade.info abstrakt.vade.info
    • Bruno Zamborlin
      May 24 2006 | 9:03 pm
      Thank you Vade. But I can't find anything about ATI drivers. I try to install ATI Catalyst from here:
      http://download.freenet.de/archiv_a/ati_catalyst_treibe r_w2k-xp_5566.html without success.
      I'm using a Dell Latitude laptop with a Mobility Radeon X300... is this of aid?
      Thx :)
    • Bruno Zamborlin
      May 25 2006 | 9:25 am
      I have noticed that the example patch "jitter-examples/render/jit.gl.render-over-movie.pat" also doesn't work. I can view the rendering (from jit.slide) and I can heard the audio from the .avi that I imported. But I can see it.
      No error in the Max Window.
      Is it maybe a Windows Jitter bug? Or is it just a problem of my video card maybe?
      Regards, Bruno
    • vade
      May 25 2006 | 2:11 pm
      Honestly, I dont know - I dont own a PC so I dont deal with conflicting/odd driver issues. Maybe *search* the forums, or email support@cycling74.com for help.
      v a d e //
      www.vade.info abstrakt.vade.info
    • Bruno Zamborlin
      May 25 2006 | 9:49 pm
      Andrew B. from Cycling74 told me this is a bug, and that he will try to fix it on the next version of Jitter.
    • Joshua Kit Clayton
      May 25 2006 | 9:55 pm
      Yes, thanks for the report. I believe it arises from a similar problem as Peter Nyboer's recent glreadpixels problem. A workaround for this problem would be to render a videoplane instead of using the draw_pixels method.
      -Joshua