mitchellb16

This is what it says on the Cycling74 website about the limitations in Jitter:

When authorized only via Live, the visual display of the jit.window and jit.pwindow objects are crippled. This limitation does not exist inside Live itself, or when Max and Jitter are authorized.

This is fairly ominous and vague. As someone who has not used Jitter much but am quite experienced in Max, would someone please describe what this means? I am looking to integrate visuals into my live performance with Ableton and am wondering if basic Jitter functions withing Max for Live will do the trick.

Jitter Limitations
When authorized only via Live, the visual display of the jit.window and jit.pwindow objects are crippled. This limitation does not exist inside Live itself, or when Max and Jitter are authorized.

jitter-limitations-in-max-for-live

You can patch fine with Jitter in the MFL editor, you just get the output of jit.pwindow and the like interrupted every now and then. And all Jitter patching works fine in MFL devices in Live.

If you already own MaxMSP and Jitter , there is no such interruption.

Thanks. But what does "interrupted every now and then" mean? I do not own a license to Max/MSP or Jitter anymore and will buy a Max for Live license if Jitter is stable enough for my live show. I am emphasizing live performance now and do not want to have Jitter needing to be babysat during my performance. Is this a bug or is it something that is necessary?

The output of Jitter into display windows is temporarily interrupted every now and then only while you are editing. It is not interrupted while you are running in an MFL device. This basically means you get Jitter for free, but its behaviour while running in the editor is not the same as if you had spent several hundred dollars on a full MaxMSP/Jitter license.

Ok, thanks for the info. I have purchased my M4L license and have downloaded the demo version of Max/MSP/Jitter. I have been playing with the jitter patches in live and can get it working in the Max editor while the preview is on. However, when I switch back to Live, my video is gone. This is the problem with jit.window as a standalone window, as well as jit.pwindow when I put it in the presentation mode.

According to the Limitations of Max for Live page, there should be no interruption when I am running Max in demo mode. Am I doing something wrong with my code?

Ok, thanks for the info. I have purchased my M4L license and have downloaded the demo version of Max/MSP/Jitter. I have been playing with the jitter patches in live and can get it working in the Max editor while the preview is on. However, when I switch back to Live, my video is gone. This is the problem with jit.window as a standalone window, as well as jit.pwindow when I put it in the presentation mode. 

Hard to know what you might be doing wrong without seeing your device.

Also, I think we need to know your workflow, for example, when you post your device tell us exactly what you did to get to the point where you get stuck

Also, I think  we need to know your workflow, for example, when you post your device tell us exactly what you did to get to the point where you get stuck

do you have your jit.window @floating 1, turn it to 0

Did you ever figure this out? This is the same problem I am having?

I see the jit.window in patching mode, but back in Live, nothing.

Did you ever figure this out?  This is the same problem I am having?  

I see the jit.window in patching mode, but back in Live, nothing.


I am working with Jitter in M4L from a while (see project V-Module, in the forum on: 

https://cycling74.com/forums/ableton-m4l-and-jitter-a-modular-system-for-real-time-video-synthesis-and-music

 - you can download my devices there) and it is a perfectly workable combination. And I do not own Max, exactly as you, I understand.

As everybody says: while you are editing, jit.window and jit.pwindow are crippled (intermittent), once you save your patch, output to windows works unrestricted, dot.

If your window disappear.... well.... it either a bug or maybe something simpler such position on another screen or behind something else.

Anyway, if you are not affected by a bug, it should work as described.

I am working with Jitter in M4L from a while (see project V-Module, in the forum on: https://cycling74.com/forums/ableton-m4l-and-jitter-a-modular-system-for-real-time-video-synthesis-and-music - you can download my devices there) and it is a perfectly workable combination. And I do not own Max, exactly as you, I understand.

As everybody says: while you are editing, jit.window and jit.pwindow are crippled (intermittent), once you save your patch, output to windows works unrestricted, dot. 

If your window disappear.... well.... it either a bug or maybe something simpler such position on another screen or behind something else. 

one question is jitter included if i buy max4live? i guess i need the matrix stuff, and wonder if i have to think about it when i buy max4live?

Yeah Jitter is included in Max for Live, as described above. If you have Max 6, Jitter is a default part of that as well.

I have a problem exporting the video in ableton live, I get a message "an error occurred while rendering the video ableton" somebody help me?

Jitter Limitations in Max for Live