yaniki

I want to use the great [jit.playlist] object introduced in Max 7 (I'm working on Yosemite and 64 bit Max) for some of my upcoming projects, but I discovered a strange behaviour (or maybe I'm doing something in wrong way?).

I'm using [jit.playlist] with @output_texture attribute set to "1", @drawto and @texture_name - to connect texture produced by the object to my rendering context. The texture produced by the object I'm using in other parts of my patch.

So, everything is fine when I fire up first video, but when I'm changing video to another one, object ceases to generate texture. But when I click the first video again object is working again... In other words: "output_texture" is working with first played video only.

jit-playlist-output_texture-issue

please post a simple patch demonstrating this issue.

MacBook Pro (17-inch, Early 2011), Yosemite, 2,2 GHz Intel Core i7, 16 GB 1333 MHz DDR3, AMD Radeon HD 6750M 1024 MB

hi yaniki. i understand now what you're trying to do. jit.playlist does not support this technique, instead try this:

Shouldn't the jit.gl.videoplane have a @transform_reset 2 attribute ?

> Shouldn’t the jit.gl.videoplane have a @transform_reset 2 attribute ?

Depends, what you want to create ;-). In this particular case my patch is just a illustration of the problem - my whole structure is more complicated, but I prepare this simple example for our discussion.

@Rob: thank you! So: with "output_texture 1" attribute [jit.playlist] is producing a texture, and we are still on GPU side, even, if the scheme of the connector (between the [jit.playlist] and the [jit.gl.texture]) looks like matrix-handling?

Yes, this is a thing I noticed too. You can check by connecting a message box to jit.playlist output:

@LSKA: thank you very much! Now I completely understand all things I need. Cool!

jit.playlist + @output_texture = issue?