Max Doe

I play an organ with an upper and lower manual transmitting midi on CH1 (upper) and CH2 (lower) note and velocity.

I want to use the midi values to colour 2 shapes (

.gridshape) - 1 shape for left hand and 1 shape for the right hand. That works fine.

However - I want to combine this with some beautiful point lights like in the  "point light" example from GL3-launch.

I managed to route the shader to my shapes but I had to duplicate 

 in order to make it work......but this also duplicated the shapes. :-( and also the jit.gl.gridshape "plane" receives now midi values and gets coloured what I do not want. 

midi-reactive-jitglcamera

Midi reactive / jit.gl.camera

Nicholas Hobson

I'm struggling to understand how to use rotatexyz on a 3d object. I'm not sure if there is a bug, or it is just my limited understanding of how rotatexyz works.

I have an object I'd like to rotate around it's own axes. If I only rotate on an individual axis (x, y or z) it works as I would expect. However, when I start combining different rotations in multiple axes, the results are not what I would expect.

In the attached patch, for example, once I have rotated in z by 90 degrees, rotating in either x or y produce the exact same result. It looks like it's rotating around the world's y-axis, rather than the object's y-axis.

In fact, no matter what rotations are applied, the y-axis rotation always appears to be relative to the world's y-axis rather than object's. Is this a bug?

x-axis rotation appears to work as I would expect. No matter the orientation, rotating around x rotates the object perfectly around its x-axis.

I feel like I'm missing something. I want to apply rotations to the object relative to its own axes.

On a side note, for some reason, if I save and re-load the patch without closing Max, the axes don't automatically appear unless I fully close max and then re-open the patch. Is there a way to ensure the axes are visible every time the patch loads?

I'm struggling to understand how to use rotatexyz on a 3d object.  I'm not sure if there is a bug, or it is just my limited understanding of how rotatexyz works.

I have an object I'd like to rotate around it's own axes.  If I only rotate on an individual axis (x, y or z) it works as I would expect.  However, when I start combining different rotations in multiple axes, the results are not what I would expect.

In the attached patch, for example, once I have rotated in z by 90 degrees, rotating in either x or y produce the exact same result.  It looks like it's rotating around the world's y-axis, rather than the object's y-axis.

In fact, no matter what rotations are applied, the y-axis rotation always appears to be relative to the world's y-axis rather than object's.  Is this a bug?

x-axis rotation appears to work as I would expect.  No matter the orientation, rotating around x rotates the object perfectly around its x-axis.

I feel like I'm missing something.  I want to apply rotations to the object relative to its own axes.

On a side note, for some reason, if I save and re-load the patch without closing Max, the axes don't automatically appear unless I fully close max and then re-open the patch.  Is there a way to ensure the axes are visible every time the patch loads?


I'm struggling to understand how to use rotatexyz on a 3d object. 

jitglplato-rotatexyz-bug

It's just gimbal lock, switching to using jit.anim.node and using rotate with @turnmode local did the trick.

jit.gl rotatexyz bug?

soundyi

I stumbled upon a mighty issue (aka bug) where the output dimension of a texture is reduced to 512 x 512, using the @adapt 0 attribute in the patcher box of a JIT.GL.PIX.

The reason why I want to use adapt 0 : I use a second texture as a parameter for a JIT.GL.PIX patch, in this case a color - hence the dimensions of the second texture is 1x1 ... and an adaption would be a waste of memory.

The attached patcher demonstrates this - drag and drop the Shapes.png file on the dropfile object "target area" and you will notice that jit.fpsgui states "dim = 512x512", but it should be 1920x1080 (if you use the attached shapes.png file, which has this resolution - its shapes are white and the background is transparent, so don' let the "all white" preview fool you ;-) ... where 512x512 seems to be the default size for an empty texture.

Using @apdapt 0 with JIT.GEN I experienced no reduction of the matrices dimensions ... does the adapt attribute work differently in the matrix (CPU) & texture (GPU) domain?

Pix adapt issue.maxpat

Shapes.png

Hi there,
I stumbled upon a mighty issue (aka bug) where the output dimension of a texture is reduced to 512 x 512, using the @adapt 0 attribute in the patcher box of a JIT.GL.PIX.

The reason why I want to use adapt 0 : I use a second texture as a parameter for a JIT.GL.PIX patch, in this case a color - hence the dimensions of the second texture is 1x1  ... and an adaption would be a waste of memory.

Hi there,
I stumbled upon a mighty issue (aka bug) where the output dimension of a texture is reduced to 512 x 512, using the @adapt 0 ... 

jitglpix-with-adapt-0-reduced-the-output-texture-dimension-to-512-x-512

well... it's not a bug. The @adapt 0 attribute lets jit.gl.pix ignore the input dimensions, no matter what inlet you use. So if you don't specify the @dim attribute directly in the jit.gl.pix object, it will resize every texture to 512x512.
Otherwise, if you use @adapt 1, it will adapt to the leftmost inlet resolution, but it will still resize all other textures. 
If you want to set a color without using a texture, you could set a param (see patch below)


Hi LSKA,

thanks for your info and the elegant solution for the "memory saving" ... using a parameter for a color instead of 1x1 texture is for sure the better solution.

And with your input I found out what fooled me ... names are just names and even if they are identical they may refer to different concepts ;-)

And for others who may stumble upon this :

In the case of jit.gl.pix, adapt is "native object" attribute : https://docs.cycling74.com/max8/refpages/jit.gl.pix#adapt.

In the case of jit.gen, adpat is (common) "MOP" attribute : https://docs.cycling74.com/max8/refpages/jit.gen#Matrix_Operator 

So, techniques that worked out for matrices really have to be revisted for textures ... got it ;-).

And by the way there is also a hint in the Gen docs "In jit.gl.pix , inputs can have different sizes." - so there is no need to use a "MOP adapt alike attribute" for jit.gl.pix in the first place, if one really needs to use another texture with different dimensions than the "primary / left most" texture.

See https://docs.cycling74.com/max8/vignettes/gen_overview at the bottom of the page - in the last paragraph.

JIT.GL.PIX with @adapt 0 reduced the output texture dimension to 512 x 512

Tate Storey

Hello everyone! I am here to ask if anyone has experienced the jit.gl.spoutsender object not working with the new update to Ableton? I usually tag the jit.gl.spoutsender object onto the end of my Jitter patches to get OBS to record them but my patch that did previously work is no longer working with 11.3.2. OBS is seeing that there is in fact a Spout object to be recorded but no video output appears. I've tried the Vizzie objects to record but find the recorded video gets corrupted. I would like to get this resolved as soon as possible as I need to record some of my patches soon for an upcoming music release and want some visual accompaniment.

Hello everyone! I am here to ask if anyone has experienced the jit.gl.spoutsender object not working with the new update to Ableton? I ... 

jit-gl-spoutsender-not-working-with-ableton-11-3-2

make sure you've updated your spout package to the latest version and refrozen your device or you can set your gfxengine Max preference back to gl2

Awesome! It seems I already had the latest spout package 2.0.73 but changing the graphics engine to gl2 fixed it :) Thank you for the quick response Rob!

jit.gl.spoutsender not working with Ableton 11.3.2

Sabina Grisi

This may sound studipily easy to solve, but I spent HOURS trying to come up with something and I just can't figure it out. Please help :'v

Hello everyone:
This may sound studipily easy to solve, but I spent HOURS trying to come up with something and I just can't figure it out. 

how-to-change-the-jit-matrix-predeterined-name-"export"-to-another-pretedermined-one-when-exporting-a-picture-using-"exportimage"


even that it states name, meant is full path, otherwise
file gets exported to ... who knows, depends on several factors.
I guess you expected to add name and see it in export dialog.
That is not working so.
you can make own export dialog

How to change the jit.matrix predeterined name "export" to another pretedermined one when exporting a picture using "exportimage"

John J.A. Jannone

I'm receiving base64 PNG files from an http request - I'd like to convert these to Jitter matrices, presumably in node.js. I'm currently saving them as files (see 

https://cycling74.com/forums/saving-large-base64-images-with-node-js

I'm receiving base64 PNG files from an http request - I'd like to convert these to Jitter matrices, presumably in node.js. I'm currently saving them as files (see https://cycling74.com/forums/saving-large-base64-images-with-node-js). Anybody tried this?

I'm receiving base64 PNG files from an http request - I'd like to convert these to Jitter matrices, presumably in node.js. 

output-base64-images-as-jitter-matrix

Hey John! 

There are surely lots of node modules to convert from base64 to rgb numbers or image files. 
I've found this one for example: 
https://www.npmjs.com/package/base64-img 

I don't think Node in Max has any idea what a jitter matrix is, so you either output the image as a list of rgb numbers, or you let node save the image into your hard drive and then read it back with a jitter matrix

>I don't think Node in Max has any idea what a jitter matrix is,

Indeed. It would be nice to see more of the Max js API  available in node.js

>you let node save the image into your hard drive and then read it back with a jitter matrix

Yes, that's what I'm doing - it works, I just find the temp files inelegant :)

output base64 images as Jitter matrix

n_angel

I've been on Max for about a month now and have had success with a few experiments. I now want to create my first artwork, which is comprised of 70 video clips that are about 7 seconds in length each (680MB total). The end product will randomize the playback across three projection screens over which subtitles (also written and randomized in jitter) will play. This project is meant for a non-music related video installation to be run off a single computer connected to three projectors in a gallery setting.

I first tried creating the patcher using jit.playlist but had trouble loading all the files at once whenever reopening the patcher. I now want to try using jit.movie @output_texture to be more efficient and to experiment with lists to call up the clips by name. My question is, however, given the size of the project will jitter be able to handle all that I'm throwing at it?

I read that jitter will slow down while playing multiple clips simultaneously. Timing is critical because I need for the lengths of each video channel's timeline to vary and for all three timelines to end at exactly the same time.

I'm currently using a MacBook Air M1, but I wonder if I should invest in something more powerful. If so, what sort of specs for hardware should I consider? I'm not above building my own PC if necessary.

I first tried creating the patcher using jit.playlist but had trouble loading all the files at once whenever reopening the patcher. I now want to try using jit.movie @output_texture to be more efficient and to experiment with lists to call up the clips by name. My question is, however, given the size of the project will jitter be able to handle all that I'm throwing at it? 

Hello all,
I've been on Max for about a month now and have had success with a few experiments. 

jitter-playback-limitations

I think it should have no trouble. I'm on an M1 MacBook Pro. Here's six HD 30fps movies playing and being layered (adding and multiplying the images alternately in the jit.gen) - it turns the fan on for sure, but it maintains 30fps - and with @output_texture it should be much more efficient than this.

I tried it on the GPU - runs at 65-70 fps.


Thanks for the reply! I'll look into your idea of switching between GPU and CPU more. I remember years ago (15) in art school my film professor shooting down my idea of overlaying text through a chroma-keyed background onto my video. I was scared the text done in jitter might be too intensive on top of everything else, but I'll run my own tests.

Jitter can easyly handle that. The files will not be "loaded" they will be played on the fly from your ssd, no matter how much files you've "loaded" (actually linked) in your patch. 
The most important is the files itself.  Don't use h264 or any other hi compressed video files. Use mjpeg as codec. High compressed codecs as h264 will drag your CPU. The more compressd your file is, the more CPU is needet to encode (re-decode) the video file. IMHO Mjpeg is the best for fast and non CPU draging video playback. 

And yes, [ @output_texture 1 ] is your friend

Thanks, Herr. I exported everything to h264 so I'll take you up on the advice.

I could not drag and drop all 70 of the clips at a time onto the patcher. I instead dropped ten clips at a time onto the playlist. Whenever I quit and reopened the patcher I got the pinwheel and had to force quit—unless I moved all the clips into a different folder, reopened the patcher and then moved the clips back into the original folder.

Jitter Playback Limitations

Jasmine Ly

problem: jit.gl.model does not load the .obj unless I reintantiate the maxobject by directly editing the maxobject.

expected behaviour: I load my patcher, turn on jit.world, and the model appears in the world.

I have attached the .obj file and in the patch please see the green-coloured jit.gl.model object for what I'm referring to

Amiga-Days_MarioStar.zip

problem: jit.gl.model does not load the .obj unless I reintantiate the maxobject by directly editing the maxobject.
expected behaviour: I ... 

jit-gl-model-not-loading-model-s-upon-start

if I save this patch, download the attachment model file, unzip, place the patch in the unzipped folder and then open the patch it finds the model file fine. My guess is you are having a path issue. The model file attribute needs a full path, or the file needs to be in the search path.

I tried to follow your steps, on a different machine, too, but the models still won't load by just the toggle alone.  For me, they only appear after I click on the jit.gl.model maxobject, retype any value, like a '0', and then hit enter.  I'll try for a solution with a full path, thank you!

I misread your issue, so please ignore the comments about file paths. this sounds like a depth or layer issue. I'll have to look again at your patch when I'm on a computer

Seems like you are targeting "ashape" with jit.gl.multiple, while the model is called "amodel". 
If I change the target everything works correctly 

Thanks so much!  Can't believe I missed that tiny mistake.  I'll mark this forum as resolved.

Marking this forum as solved; had targetname on 'ashape' instead of 'amodel'.  

Jit.gl.model not loading model(s) upon start

Paul 

Patch image/video attached, using glitch mp4 video to effect the text

How can i make the glitch effect respond to audio input playlist?

Patch image/video attached, using glitch mp4 video to effect the text
How can i make the glitch effect respond to audio input playlist?
thanks!
Paul

Patch image/video attached, using glitch mp4 video to effect the text
How can i make the glitch effect respond to audio input ... 

working-with-audio-jitter-newbie

Working with Audio [Jitter newbie]

Yonathan Zenebe

I am using a jit.world to make a particle system and am following Federico's Amazing Max Stuff tutorial.

Currently, my particles are contained in a cube shape. Can you help me figure out how to contain them within a sphere shape instead?

Particle_example_forum_post.maxpat

I am using a jit.world to make a particle system and am following Federico's Amazing Max Stuff tutorial.
Currently, my particles are contained in a cube shape. Can you help me figure out how to contain them within a sphere shape instead?

Hello friendly coders!
I am using a jit.world to make a particle system and am following Federico's Amazing Max Stuff tutorial.
Currently, ... 

help-with-particle-system-shape

Hey hey, 

they are a cube because they are initially placed using random numbers evenly spaced between -1 and 1. 
You could normalise their initial position vector to get a position placed always at 1 unit from the centre. 
Then you could use a random number to randomise it and so get it inside the sphere. 

Here's the patch 


And adding [sqrt] in the jit.gen just after [in 1] will generate an even distribution of particles. See https://programming.guide/random-point-within-circle.html for an explanation of why

Help With Particle System Shape

Rob Ramirez

Happy post RNBO day everyone, I've got some details and context on what the Jitter team has cooked up for the 8.5 update.

Top of the list, GLCore (or glcore) and what it's all about. With 8.5 we've done 2 things:

The reason for the renaming is to better reflect the reality that most graphics cards will support OpenGL versions beyond version 3. The engine provides support for modern core profile OpenGL at whatever version your graphics card supports.

For existing gl3 users not much has changed in functionality (other than the new juicy bits described below). However the consequences extend beyond the technology. We now have a solid foundation for continuing our engine modernization and growth, and can fully document the new behavior and features. To that end there are a handful of new examples to check out in the glcore Examples Extras patch.

For gl2 users this is a significant but hopefully seamless change. We will publish more details on how best to utilize modern graphics engines and other ins and outs, and we strongly encourage 

 with any issues. However if you wish to revert back to gl2 simply change your 

 back to gl2. You first might want to check out the afore mentioned glcore Examples patch to see what you're forgoing.

glcore-extras.png

A new entry to our Jitter Tools suite is the 

 object, which allows for manipulating letters and words of text using a 

 like interface and highly efficient mesh rendering. As an added bonus for text lovers we’ve removed the 1024 character limit on 

textmult.png

Also included with 8.5 are some lovely new 

 effect adds global fog and atmospheric scattering to any 3D scene with ease, and for experimenting with global illumination check out the 

fog-fx.png

Speaking of global illumination, the new 

object handles the loading and sharing of environment map resources for image based lighting (IBL), cubemap, and skybox rendering for supported objects. This currently includes 

, where if a context has an environment attached, the supported objects will use it for rendering.

, giving much better results when rendering these model files. In the video below we see non-PBR rendering on the left, and PBR rendering on the right.

For links to the example patches mentioned (and loads more) check out the 

Renamed the formerly beta gl3 engine to glcore

Transitioned our default graphics engine from the legacy gl2 to the modern glcore.

The reason for the renaming is to better reflect the reality that most graphics cards will support OpenGL versions beyond version 3. The engine provides support for modern core profile OpenGL at whatever version your graphics card supports.


For gl2 users this is a significant but hopefully seamless change. We will publish more details on how best to utilize modern graphics engines and other ins and outs, and we strongly encourage contacting support with any issues. However if you wish to revert back to gl2 simply change your Graphics Engine (gfxengine) preference back to gl2. You first might want to check out the afore mentioned glcore Examples patch to see what you're forgoing.


A new entry to our Jitter Tools suite is the jit.gl.textmult object, which allows for manipulating letters and words of text using a jit.gl.multiple like interface and highly efficient mesh rendering. As an added bonus for text lovers we’ve removed the 1024 character limit on jit.gl.text input strings.

Also included with 8.5 are some lovely new jit.gl.pass post processing effects. The atmospheric effect adds global fog and atmospheric scattering to any 3D scene with ease, and for experimenting with global illumination check out the temporal screen-space ambient occlusion (tssao-gi) and screen-space reflections (tssao-gi-ssr and ssr) effects.

Speaking of global illumination, the new jit.gl.environment object handles the loading and sharing of environment map resources for image based lighting (IBL), cubemap, and skybox rendering for supported objects. This currently includes jit.gl.pbr, jit.gl.material, and jit.gl.skybox. The object functions like jit.gl.light, where if a context has an environment attached, the supported objects will use it for rendering.

We've also added glTF PBR material support to jit.gl.model, giving much better results when rendering these model files. In the video below we see non-PBR rendering on the left, and PBR rendering on the right.

For links to the example patches mentioned (and loads more) check out the glcore Examples and Jitter Tools Extras patches, and the jit.gl.pass reference page.

Happy post RNBO day everyone, I've got some details and context on what the Jitter team has cooked up for the 8.5 update.
Top of the list, ... 

jitter-8-5-and-glcore

Hey everyone, we've got an update for glcore included in the Jitter Tools 1.0.6 version now live in the Package Manager. This update addresses a handful of reports we've received since the release of 8.5 and is recommended for all 8.5.x glcore users.

fix move texture output when skybox enabled in same context

jit.gl.mesh - fix crash on certain adjacency draw modes

jit.gl.path - evalout equals zero drawing fix

jit.gl.text2d - fix screenmode 0 rendering with high dpi display

jit.gl.environment - reflection map edge length attribute

jit.gl.meshwarp - external input matrix for initial mesh geometry via mesh_matrix message

jit.gl.meshwarp - output_mesh_matrix message to output the mesh vertex data

Rob, congrats to you and c74 on glcore. I get the effort your team put into it. :-)
Are there C/++ examples for the updated interfacing possible HOST to/from GPU for textures, buffers, mapping between max,opencl,opengl, etc.

Unfortunately I don't have a great answer for you. The SDK has not been updated with examples for developing for glcore, and given the current state of flux in our backend graphics engine work, I don't have a good estimate for when that might change. 

That being said, both Syphon and Spout are open source and demonstrate how an external can support both legacy gl2 and modern glcore using some wrapper functions we expose in the jit.gl.draw.h header file. If you're only concerned with core profile support you can ignore these wrappers and link to the gl3 library headers instead (which may be easiest by defining GL3_VERSION=1 in your project preprocessor definitions). Additionally, the basic principles of jit.gl external development outlined in our SDK documentation still hold true.

I'm also more than happy to provide whatever insight I can for any brave explorers in this space.

Fantastic, thank you Rob and the team!

Do you have do you have any idea when TXAA / TAA is coming to Jitter!? Ref here at 16m20s https://youtu.be/S7xPbjICNsw 

I just posted the TAA pass fx here:
https://cycling74.com/forums/sharing-temporal-anti-aliasing-taa-fx-for-jit-gl-pass 

At the moment, it's quite complex to make it available as a built-in tool, but if you're interested in it, check out the patches at the link above

Thanks for the response; will check out the patches!

I am excited about the great jitter upgrade!

I'm working on some samples, so check out my twitter as well. 

https://twitter.com/mirrorboy/status/1662831859439644674?s=20
https://twitter.com/mirrorboy/status/1662699971462979585?s=20

I have a few questions as I use it.

Will the pbr in jit.gl.model be reflected without jit.gl.pbr connected? (I loaded the glTF and it seems to reflect the pbr textures without specifically connecting jit.gl.pbr or jit.gl.material). and, I could not change pbr parameter on jit.gl.model.

Also, if the texture loaded in jit.gl.model references a multi-texture by albedo, can I use the multi-texture in jit.gl.pbr when drawing with matrixoutput or jit.gl.mesh?

Jitter's material has many inheritance relations and parameters, and jit.gl.model is very difficult due to some invisible parts, so it would be great to have contents like 1st step.

Cycling '74 Forums

I am excited about the great jitter upgrade! I'm working on some samples, so check out my twitter as...

could solve all my questions. Have fun playing some colourful music :) Note: Don't miss to set a saturation/velocity value b4

It's just gimbal lock, switching to using jit.anim.node and using rotate with @turnmode local did the trick.

Hi LSKA, thanks for your info and the elegant solution for the "memory saving" ... using a parameter for a color instead of 1x1 texture is...

Awesome! It seems I already had the latest spout package 2.0.73 but changing the graphics engine to gl2 fixed it :) Thank you for the quick...

You're a life saver, @SourceAudio !

Hi Federico! >I don't think Node in Max has any idea what a jitter matrix is, Indeed. It would be nice to see more of the Max js API...

Thanks, Herr. I exported everything to h264 so I'll take you up on the advice. I could not drag and drop all 70 of the clips at a time...

Marking this forum as solved; had targetname on 'ashape' instead of 'amodel'.

Patch image/video attached, using glitch mp4 video to effect the text How can i make the glitch effect respond to audio input ...

And adding [sqrt] in the jit.gen just after [in 1] will generate an even distribution of particles. See...