grimepoch

I've been using jit.xfade for years to mix between two videos. Recently I was starting to use some old code and found that it does not work the same anymore.

Previously, if I had 2 video inputs going in, and the left video stopped, iit.xfade would continue to play the video coming in the right inlet.

Now, if the left inlet video stops, the outlet stopped showing any changes in video.

I tried this with 08jSimpleMixing tutorial patch and observed the same behavior (I removed the stop message for video 2 so it would stop video 1).

Is there some other way I should be handling this now? I use this as a part of a VJ setup I created so I need the right inlet video to continue when the left stops.

I've been using jit.xfade for years to mix between two videos.  Recently I was starting to use some old code and found that it does not work the same anymore.

Is there some other way I should be handling this now?  I use this as a part of a VJ setup I created so I need the right inlet video to continue when the left stops.


jit-xfade-behavior-changed

It wouldn't surprise me if this has something to do with the "unique" setting that only outputs frames when they change. The behavior of the left inlet being the trigger is expected, so maybe you had previously been using unique "o," which would output frames on each bang of the movie object even if the movie itself was stopped, as opposed to unique "1" which would only output frames when they change... so no output if the movie is stopped.

It wouldn't surprise me if this has something to do with the "unique" setting that only outputs frames when they change.   The behavior of the left inlet being the trigger is expected, so maybe you had previously been using unique "o," which would output frames on each bang of the movie object even if the movie itself was stopped, as opposed to unique "1" which would only output frames when they change... so no output if the movie is stopped.


Interesting enough, I went from I think 7.1.2 to 7.1.3 and it started working properly again (or, at least, how it's worked for the past 5 years).

That said, before I do another gig with this setup, I will keep pushing it to make sure that it works properly still in all cases.

Phiol, I will definitely give that a try just as a precaution.

I was doing a show with it when it stopped working so just to get through the show I tied the outputs together which means they basically flicker while they are both active just to get something going :)

That said, before I do another gig with this setup,  I will keep pushing it to make sure that it works properly still in all cases.

Phiol, I will definitely give that a try just as a precaution.  

I was doing a show with it when it stopped working so just to get through the show I tied the outputs together which means they basically flicker while they are both active just to get something going :)


jit.xfade behavior changed