Max 8.2 Jitter Tools package

    Aug 24 2021 | 6:48 pm
    Jitter fam!
    The Max 8.2 beta release comes packed with tons of new features, including a new package for all you pixel pushers called Jitter Tools. The package contains abstractions, source code, help files and ref pages for a handful of Jitter related tools, intended to grow over time.
    Currently the package contains the following projects:
    • - An incredibly cool object from the mind of Federico Foderaro, meshwarp is a customizable grid of points to deform a mesh and associated texture via mouse interaction. While the main use case is video mapping, the possibilities abound.
    • jit.polymovie and - Inspired by polybuffer~, the 2 polymovie objects allow for easy loading and fast switching of groups of movie files. Additionally the object supports multi-head playback from a single source for added video madness.
    • - Well used by many a Jitter head, we've revamped the existing textureset example into a full fledged object. jit.matrixset type image store and recall capabilities, but for ultra-fast GPU based textures.
    Each of these are demonstrated in the Jitter Tools launcher patch (Extras --> Jitter Tools Launch) and help files, so please take a look and let us know what you think!

    • Aug 25 2021 | 5:54 am
      That wonderfull!
    • Aug 25 2021 | 9:41 pm
    • Oct 24 2021 | 11:05 pm
      I would like to report an jitter-related issue I found when I tried to migrate some of my patches to Max 8.2. The attached patch gives a demonstration of the issue.
      If you toggle the hidden property on an object (like the empty message object in the patch), the jit rendered graphics flicker annoyingly. This can be very distracting if such toggling is done rapidly  (i.e. through qmtero as is the case in some of my patches, and the attached patch).  Note that, strangely, the issue occurs ONLY if there is an object beyond the borders of  the patching area. If you drag the dummy object, located above the top border, below that border the flickering stops. if you put it beyond any of the borders of the patching area, the flickering starts again.  I verified that this behavior does not occur for Max 8.1.11 or previous versions.  I hope this can be easily fixed.  Thank you for looking into this. 
    • Oct 25 2021 | 3:55 pm
      hi Adam. This issue has nothing to do with the Jitter Tools package, so please submit this to support -
    • Dec 04 2021 | 12:52 pm
      This is great. For me when I open the Jitter Tools Launch, the @vol 0 of the is not working. I definitely hear the sound of
    • Dec 06 2021 | 10:38 am is amazing and very useful, thanks !
      One small issue : when sending it a message show_ui 0 : UI disappears, but if I click on the mesh in the jit.window, it comes back. There is no way to disable UI mouse interaction completely. It makes incompatible with any other piece of patch that use mouse interaction ( @ui_listen 1 —> ,, …) Too bad ! I would expect show_ui 0 to completely disable GUI in jit.window. Or please add another attribute : enable_ui
      Thanks for considering :-) Mathieu
    • Dec 07 2021 | 4:20 pm
      Thanks much MIB and Mathieu for the feedback! We will create issues for these requests on the respective githubs (meshwarp and polymovie)
      In fact, it looks like the issue MIB is reporting is already ticketed. Please let me know if that doesn't sound like what you are experiencing.
      Thanks again!
    • Dec 08 2021 | 3:43 am
      @MIB, actually I'm unable to reproduce this volume issue, and I believe the github issue was already fixed. Could you please let me know what OS, what Max version and which video engine you are currently running?
    • Dec 11 2021 | 12:43 pm
      Hi, I get this when ever I open
      • js: mesh.js loaded meshwarp.js: Javascript ReferenceError: Mesh is not defined, line 94 js: Set_Attributes_Functions: Javascript TypeError: gMesh is undefined, line 204 js: error calling function getPosition [meshwarp.js] js: Set_Attributes_Functions: Javascript TypeError: gMesh is undefined, line 192 js: error calling function getScale [meshwarp.js]
    • Dec 14 2021 | 4:09 pm
      for the archives, the issue Roger reported has been fixed and is available in the Package Manager, see this thread for more info -
    • May 05 2022 | 4:23 pm
      Hello, will there be an mc~ version? Would be awesome!