phiol

I have problems with jit.movie @engine avf (bluescreen on videoload)

and @engine qt (video stops on load until manual (stop-start))

as well as @automatic 1 not working on [jit.gl.pix @gen xfade]

All explanations are included in this example patch.

THE GOAL: xfade 2 videos/ stopping the one not playing to save CPU.

ps. this is not for my curiosity, it for work.

I have problems with jit.movie @engine avf (bluescreen on videoload)
and @engine qt (video stops on load until manual (stop-start))
as well as @automatic 1 not working on [jit.gl.pix @gen xfade] 

All explanations are included in this example patch. 

THE GOAL: xfade 2 videos/ stopping the one not playing to save CPU. 

ps. this is not for my curiosity, it for work.
Hence the urgent part


urgent-jit-movie-gl-pix-automatic-1-problems

Regarding the bluescreen: you can delay the start of the crossfade for a frame or two, so the blue frames won't be noticed.

While for the jit.gl.pix: you can put a [t b l] between the second jit.movie and the right inlet, so you'll bang the [jit.gl.pix] only when the second video is playing.

I would would I go about doing your 1st suggestion ?

using a counter with the bang from the qmetro ?

Thing is, the blue screen duration length is not even, sometimes longer than others

I would would I go about doing your 1st suggestion ?
using a counter with the bang from the qmetro ?
Thing is, the blue screen duration length is not even, sometimes longer than others

even with a delay of 100ms. I believe it's because even if any of the 2 Player is getting a blue screen , [gl.pix @gen xfade] passes it through.

I tried using a speedlim and a qlim (
even with a delay of 100ms. I believe it's because even if any of the 2 Player is getting a blue screen , [gl.pix @gen xfade] passes it through. 

No, I meant by putting a [delay] before triggering the [line].

I put a 3 frame (180 ms) delay, and it seems a little better, although some occasional blue frame still appears.

Thanks Lska, I tried that and am still getting blue screens once in while but definitively much better.

I really hope to hear from Rob Ramirez or any C74 Jitter creators,

Thanks Lska, I tried that and am still getting blue screens once in while but definitively much better.
Thanks 

I really hope to hear from Rob Ramirez or any C74 Jitter creators,
why I'm getting a blue screen. 

the blue frame is a known issue that we are looking into.

i would try modifying your workaround to count a certain number of frames, rather than using delay, before the crossfade starts.

but really, i would use jit.movie in a poly~, with the content preloaded and initialized.

i would try modifying your workaround to count a certain number of frames, rather than using delay, before the crossfade starts. 

but really, i would use jit.movie in a poly~, with the content preloaded and initialized.


>>i would try modifying your workaround to count a certain number of frames, rather than using delay, before the crossfade starts.

how do I delay frames? that was my question to LSKA. The only delaying methods I know are

counter / pipe/ delay / speedlim/ qlim/ and maybe deferlow.

As for the poly~ approach, I was gonna take this approach if I could of, but

this is for an installation where the artist is constantly changing content from distance, in DropBox.

SO i'm constanstly updating a container/(umenu) using [filewatch path]  and [folder path].

So I can't really do the fill up the poly~ voices with folder dump.

hope to hear about the frame delay method.

>>i would try modifying your workaround to count a certain number of frames, rather than using delay, before the crossfade starts. 

how do I delay frames? that was my question to LSKA. The only delaying methods I know are
counter / pipe/ delay / speedlim/ qlim/ and maybe deferlow. 

Poly~:
As for the poly~ approach, I was gonna take this approach if I could of, but
this is for an installation where the artist is constantly changing content from distance, in DropBox.
SO i'm constanstly updating a container/(umenu) using [filewatch path]  and [folder path].
So I can't really do the fill up the poly~ voices with folder dump.

hope to hear about the frame delay method. 

Hi Phiol. I think Rob suggested to delay the moment the crossfade happens, not the video.

Anyway, responding to your question, I've used jit.matrixset before to delay video. As a downside, you lose the direct to gpu optimizations...

Hi Phiol. I think Rob suggested to delay the moment the crossfade happens, not the video.
Anyway, responding to your question, I've used jit.matrixset before to delay video. As a downside, you lose the direct to gpu optimizations...

Thanks for the tip. there is just way to much in this patch to not try and stay on the GPU side as much as possible. I'll already had to create multiple standalone apps to take somewhat advantage of the 6 core Mac Pro.

Thanks a lot for any tips. I'm learning :0)

Thanks a lot for the fast reply Pedro,
Is there a way to delay a texture ?
Of course I'm gonna ask ;-) 

Thanks for the tip. there is just way to much in this patch to not try and stay on the GPU side as much as possible. I'll already had to create multiple standalone apps to take somewhat advantage of the 6 core Mac Pro. 

Thanks a lot for any tips. I'm learning :0) 

https://cycling74.com/forums/time-delayed-textures-3d-texture-buffers/

https://cycling74.com/forums/time-delayed-textures-3d-texture-buffers/
Good luck!


I tried Wesley's texture delay , but you were right , Rob meant count frames.

Thanks to all you guys, no more blue screens

Below is my final version implemented what I got from Rob's suggestion.

@LSKA: Just for clarification sake, 3 frames would not be 180ms delay , it would be approx 50ms.

@c74 team: hope the time-chance-magic will be on your side

Thanks a lot Pedros for the nice link.
I tried Wesley's texture delay , but you were right , Rob meant count frames.

Thanks to all you guys, no more blue screens
Below is my final version implemented what I got from Rob's suggestion.

@LSKA: Just for clarification sake, 3 frames would not be 180ms delay , it would be approx 50ms.
Cause my fps == 60Hz 

Thanks again to all of you.
@c74 team: hope the time-chance-magic will be on your side
to rid the blue screen :-) soon


You're right... these are the symtoms of too much work!

Good for you man :-)! I Hope it's mostly Jitter work.

[URGENT] jit.movie & gl.pix (@automatic 1) problems