Trippy pwindows
how those jit.pwindow inside bpatcher are behaving these days
It happens only with textures (same if you connect a texture to a jit.pwindow) and it has been like this for me since jit.pwindow can show textures efficiently (without an internal readback to a regular matrix), since Max 8.* I can't remember.
if you want to avoid that, send jitter matrices to a pwindow, so in your case, switch from [jit.pworld] to [jit.world @visible 0 @capture 1] + [jit.gl.asyncread] + [jit.pwindow] and maybe add a [speedlim] before the asyncread to lower the preview framerate. And also lowering the texture dimension after speedlim might help reducing the performance hit.
Not as convenient as a single pworld, but that's what I came up with to avoid what we see in your video.
I already have jit.world module
these are simple bpatcher module for playing movies
not sure I can handle any performance hits for this particular project
when make a lot of copies
I can live with weird scrolling - was just wondering about it
ultimately when rendering video I do make world invisible (send to OBS) and smallify the patch to increase frame rate
//
maybe when module is finished - lose the pwindow completely