Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Video glitches (Scarlet & Premiere Pro)

Navin Ramaswaran

Navin Ramaswaran

Well-known member
Joined
Apr 8, 2013
Messages
121
Reaction score
0
Points
0
Location
Toronto, ON
Hi all,

I recently completed a feature shot on the Scarlet and have encountered 2 issues while in post :

1. When "warp stabilizer" is applied to a clip it plays back just fine on the Premiere Pro timeline. But upon rendering/exporting the following glitch appears - https://vimeo.com/110733530 [PASSWORD = files]

2. I have noticed this glitch on 2 clips so far, on both our master and backup drives. This 1 frame glitch is present when viewing in Redcine-X and Premiere Pro - https://vimeo.com/110733589 [PASSWORD = files]

Using the latest version of Adobe Suite CC (ver 8.1)
Camera firmware 5.2.9

Anyone else experiencing similar issues?

Thanks.
 
Wow, rave party on the stabilisation! Have you tired converting the clip to ProRes or DNxHD or something and stabilising after that, does that help?

The second one does look like a data integrity issue. How are you offloading your clips? I've had issues like this with certain combinations of eSATA cards, operating systems and drivers. Ideally, your data wrangling workflow should include doing a checksum to make sure the files have been copied correctly.
 
Not sure if it's related, but I used to have flickering issues in PP when applying PP's Ultra Key on green screen footage from my BMCC's CinemaDNG files. My solution was to just re-export because it was unpredictable. It happened on maybe 1 out of every 3 exports.
 
Are you working on a mac? I've got many glitches in fcpx and resolve since i went from mavericks to yosemite.
 
Hey Andew,

I haven't tried converting to ProRes, etc. yet. I'll give it a shot - might be a good workaround for now.
Thanks!

Andrew Gentle said:
Wow, rave party on the stabilisation! Have you tired converting the clip to ProRes or DNxHD or something and stabilising after that, does that help?

The second one does look like a data integrity issue. How are you offloading your clips? I've had issues like this with certain combinations of eSATA cards, operating systems and drivers. Ideally, your data wrangling workflow should include doing a checksum to make sure the files have been copied correctly.
Click to expand...
 
Hey Navin,

Quick question -- was the data copied to each drive independently from the source/REDmag, or was it copied to driveA and then driveA was duplicated onto driveB? Did you use data management software to verify the integrity of the transfer (like R3D Data Manager)?

If the source files are actually glitchy, and RED doesn't find anything in the log files, it was probably something that happened in the transfer (slight power surge, hdd write-glitch, etc... basically beyond your control). If you have no other takes, the 1 frame glitch should be easy enough to fix (remove the bad frame, use something like pixel motion to fill in the gap), but the blinking one might be a little more difficult.
 
Hey Mike!

Data was copied onto each drive independently. No data management software was used - just direct transfer from REDmag to Drives.

I agree - I think the 1 frame glitch can be fixed for the most part (although I'd like to get to the bottom of this to avoid this issue in the future). The blinking one only happens when Wrap Stabilizer is applied to the clip. I'm going to try and transcode the specific R3D file to ProRes4444 and see if it reacts the same way after Wrap Stabilizer is applied.


Mike P. said:
Hey Navin,

Quick question -- was the data copied to each drive independently from the source/REDmag, or was it copied to driveA and then driveA was duplicated onto driveB? Did you use data management software to verify the integrity of the transfer (like R3D Data Manager)?

If the source files are actually glitchy, and RED doesn't find anything in the log files, it was probably something that happened in the transfer (slight power surge, hdd write-glitch, etc... basically beyond your control). If you have no other takes, the 1 frame glitch should be easy enough to fix (remove the bad frame, use something like pixel motion to fill in the gap), but the blinking one might be a little more difficult.
Click to expand...
 
Did you try rendering on - SOFTWARE ONLY - instead of CUD or OPENCL (GPU). This normally fixes glitch issues on Premiere for me.
But could be something different because you see it in RCX to.
 
If you still have the data on the cards you should also see if you see the glitch in the original files to further narrow down the issue. I had some similar issues and switching from Cuda to software worked as was mentioned before.
 
Yep this worked (for the warp stabilizer issue). I did more reading online and this seems to be a known issue. Hopefully Adobe rectifies it soon.

The digital glitch issues I am still experiencing randomly. Sometimes the glitch shows up on the Master drive but not on the Backup, but sometimes it's on both. Maybe the DMT transferred from card to master hard drive AND card to backup drive some times (the way it should be done); and just card to master hard drive and then master to backup at other times. So far I've been able to work around this issue by cutting out a frame or reframing, but there is 1 shot we're actually re-shooting (because we do have the opportunity to do so). Scary issue, I'll be keeping tabs on this.



Dimitri Boschma said:
Did you try rendering on - SOFTWARE ONLY - instead of CUD or OPENCL (GPU). This normally fixes glitch issues on Premiere for me.
But could be something different because you see it in RCX to.
Click to expand...
 
Cards have been wiped unfortunately. But the warp stabilizer render issue is fixed after switching from Cuda to Software only. Thanks!

Dustin Dooley said:
If you still have the data on the cards you should also see if you see the glitch in the original files to further narrow down the issue. I had some similar issues and switching from Cuda to software worked as was mentioned before.
Click to expand...
 
You must log in or register to reply here.
Back
Top