Resolume Forum

Hi
Seems like quicktime h264 has problem with autopilot.
If next video does not start from beginning, On trigger blink first frame of video.

With dxv codec it looks ok.

Yes, for some reason the external decoder returns the first frame in every case when Resolume requests the frame from a certain position.

Also in these cases a clip's start frame is probably not a keyframe, so you'll see a longer than expected launch time or high CPU load for these clips, because the frame - and all frames before to a keyframe - needs to be decoded from the last keyframe position.

Please use DXV for the best performance.

If that's not an option you can set a small transition time for the layer to hide the flash.

I'm having a similar problem however I am using dxv encoded media.

it doesn't happen when I manually trigger columns, only on autopilot... any thoughts?

More details on the problem mentioned by euprunner:

When going from one DXV clip to another using autopilot, the incoming file displays some arbitrary frame from the middle of the clip before displaying the actual first frame. This does not happen with all clips; those which fade in from black or have some other transition appear fine. Those which have active content on the first frame show this issue. It's quite consistent.

endquote wrote: Sat Jul 14, 2018 18:08 When going from one DXV clip to another using autopilot, the incoming file displays some arbitrary frame from the middle of the clip before displaying the actual first frame.

We fixed this a while back, looks like it's indeed broken again. We'll look into it.

has anyone found a fix for the frame blink yet?

I'm having the same issue - 30second DXV3 video sometimes blinks a random frame of the clip just before auto pilot transition to black clip.

most frustrating as I'm about to do a high end show and really wanting to use resolume for the whole thing

We're still working on this.
Try setting a Layer transition time of 0.1 seconds in the meantime.