Transcoding R3D files results in image ghosting

[Quinn Pfitzner]

I have recently shot a project on a Red One and have tried to transcode the R3D files to Apple Prores 422 (HQ) for an offline edit. Most of the footage was shot in 4K while some was shot high speed in 2K.

I initially used my white macbook 2.4 GHz Intel Core 2 Duo (2Gb Ram) to transcode the files using Red Rushes with the following settings:

Render settings:
Debayer quality - Full Res
Timecode - External/TOD
Look Source - Camera
Color Space - Redspace
Gamma Space - Redlog

Resize settings:
Crop: (not used)
Scale: 1920 x 1080, Fit Width, CatmulRom (sharp)

Output settings:
Quicktime Movie, Apple ProRes 422 (HQ)

Half of the Apple ProRes file (approximately 40 of the 100) have very noticeable ghosting. By ghosting I mean that the clapperboard may have two right edges and two bottom edges, one of the edges is slightly more opaque than the other. This can been seem through out the entire take on most of the objects in the scene that have reasonably strong edges.

I then asked another editor who own a 4 core Powermac to transcode the files for me with the same setting and exactly the same file appeared with the ghosting effect.

I then transcoded one of the R3D files that had this ghosting problem, except this time I converted it to 1920x1080 Blackmagic 10bit RGB 4:4:4. The same problem occured.

All of the original R3D files appear without any ghosting or any other issues.

I am have a Dp 2.3 GHz Powermac with a blackmagic capture card, HD monitoring and a raid. I know that this machine has been left behind due to the R3D codec not being made available to it, but I am set up to uncompressed 2K editing and grading so that does not bother me. I am just having a lot of trouble converting the R3D files to something that I can work with.

Am I using the wrong settings? or could this be a software or operating system issue. I'm using red rushes 3.60 (1) and my OS and final cut are up to date.

I am hoping that someone has a solution to this problem. Can anyone point me in the right direction.

 

[jake blackstone]

I have recently shot a project on a Red One and have tried to transcode the R3D files to Apple Prores 422 (HQ) for an offline edit. Most of the footage was shot in 4K while some was shot high speed in 2K.

I initially used my white macbook 2.4 GHz Intel Core 2 Duo (2Gb Ram) to transcode the files using Red Rushes with the following settings:

Render settings:
Debayer quality - Full Res
Timecode - External/TOD
Look Source - Camera
Color Space - Redspace
Gamma Space - Redlog

Resize settings:
Crop: (not used)
Scale: 1920 x 1080, Fit Width, CatmulRom (sharp)

Output settings:
Quicktime Movie, Apple ProRes 422 (HQ)

Half of the Apple ProRes file (approximately 40 of the 100) have very noticeable ghosting. By ghosting I mean that the clapperboard may have two right edges and two bottom edges, one of the edges is slightly more opaque than the other. This can been seem through out the entire take on most of the objects in the scene that have reasonably strong edges.

I then asked another editor who own a 4 core Powermac to transcode the files for me with the same setting and exactly the same file appeared with the ghosting effect.

I then transcoded one of the R3D files that had this ghosting problem, except this time I converted it to 1920x1080 Blackmagic 10bit RGB 4:4:4. The same problem occured.

All of the original R3D files appear without any ghosting or any other issues.

I am have a Dp 2.3 GHz Powermac with a blackmagic capture card, HD monitoring and a raid. I know that this machine has been left behind due to the R3D codec not being made available to it, but I am set up to uncompressed 2K editing and grading so that does not bother me. I am just having a lot of trouble converting the R3D files to something that I can work with.

Am I using the wrong settings? or could this be a software or operating system issue. I'm using red rushes 3.60 (1) and my OS and final cut are up to date.

I am hoping that someone has a solution to this problem. Can anyone point me in the right direction.

What's the frame rate?

 

[Deanan]

I have recently shot a project on a Red One and have tried to transcode the R3D files to Apple Prores 422 (HQ) for an offline edit. Most of the footage was shot in 4K while some was shot high speed in 2K.

Can you try rendering out from redalert and see if you get the same thing?

 

[Quinn Pfitzner]

The frame rate is 25fps

 

[jake blackstone]

The frame rate is 25fps

The reason I'd asked about the frame rate is that it looks like a cadence problem, but it's all progressive, so I guess it doesn't apply. Nevertheless, as I see there is not many other suggestions, was it shot at 25 fps? Are you transcoding at the same frame rate? I'm sorry I'm just guessing... Could you post one of the problem r3d files so we could check it out?

 

[Quinn Pfitzner]

The original r3d files have 'ghosting' problem

The original r3d files have 'ghosting' problem

I'm sorry I have mislead you all by stating that the original R3D files were fine, they are not fine. THE ORIGINAL R3D FILES HAVE THE 'GHOSTING' PROBLEM - no wonder it does not go away when transcoding.

I have a small original R3D file that shows the problem at its very worst, I guess due to the dark subject and light background (very similar to the image in my original post in this thread)

If someone can give me a tip on how to make the original 17Mb R3D file available to you all, that would be greatly appreciated. Otherwise I could post my email address, for people to email me directly so I can send it directly to them. Is posting of email addresses allowed?

Thanks again

 

[mirakovski]

Hi,
Use www.sendspace to upload the file. After uploading paste the link here on the forum, and we will se what we can do. I think I know what is the problem, but I need to see first.

 

[Guy]

I've seen this before. I think it must be caused by reflection from the OLPF/IR filter in the camera. Could also be from filters in front of the lens but I've seen it happen when no filters are used. Most obvious on bright white objects against a darker background.

 

[Quinn Pfitzner]

The answer to my problem was filter stacking. Light leaked in between the stacked ND filters and caused a 'mirror' effect. This gave the image a sort of 'double exposure' look that was mainly obvious along edges of extreme shadow and extreme highlight. Unfortunately I was unable to pick this up on location while viewing the directors monitor. The DP and 1st AC did not notice either.