Rendering problem with REDCINE-X build 221

[Dominique Grenier]

I've got some rendering problems using the latest version of Redcine-X. I had those same problems for a short period using the build 194 but they didn't last.

Basically, when I render any clip I get what's pictured in the attached image, that is, random noise for what seems the be the upper 3/4 of the clip and a black bar at the bottom. This is for the duration of the clip.

Any ideas?

[James Rayburn]

what are you rendering to? detail your full settings.
also, detail your source footage.

[Paul Komadina]

I just had the same problem.

Source footage is 4096 x 2304 25fps.

I first converted to Quicktime 1080p ProRes 422 (HQ) and everything was fine. I just tried Quicktime 4096 x 2304 ProRes 4444 and I got exactly what Dominique describes: 3/4 noise and a black bar along the bottom.

[Dominique Grenier]

what are you rendering to? detail your full settings.
also, detail your source footage.

Sorry, had an unexpected job.

My source footage was 4096 x 2048 at 23,976. I, too, was rendering in full 4K. I didn't tried rendering in 1080p first, I'll try that tomorrow and report here. But when I think about it, I did a job a couple weeks ago where I rendered in 1080 and didn't have a problem. It wasn't on build 221 though.

[Sam Winzar]

I don't believe the current Quicktime architecture supports 4K resolution. Not sure if that could be part of the issue but it would definitely be an issue once you try to work with the footage.

[Dominique Grenier]

I don't believe the current Quicktime architecture supports 4K resolution. Not sure if that could be part of the issue but it would definitely be an issue once you try to work with the footage.

Well, I've rendered in After Effects much bigger formats than 4K! We've already rendered a 26,000 x 8000px clip, so I don't think this is the problem.

[Sam Winzar]

Well, I've render in After Effects much bigger formats than 4K! We've already rendered a 26,000 x 8000px clip, so I don't think this is the problem.

I'll admit I live in Final Cut world and FCP craps itself with anything over 4000

[Dominique Grenier]

I'll admit I live in Final Cut world and FCP craps itself with anything over 4000

LOL, I'm not saying we had fun rendering that big of a clip, but at this point this is more a memory issue rather than QuickTime.:sifone:

[Paul Komadina]

I just tried a 4K at ProRes HQ 422 and same issue.

I've done 4K quicktimes in the past without issues. Oh, and FCP can now handle 4K quicktimes. It's not elegant, but it works.

Hi Sam!

[Sam Winzar]

Hey Paul,

Oh well, good to know Quicktime + 4K is not the issue. I'll stop spreading false rumours.

[PHactor]

Had same issue on a clip that was the first one after installing Build 30. When it displays in the player window you get a thin red-lined border around the frame of the image. 4HD clip at 29.97 and taking to Prores SQ. After transcoding at 1/2 premium debayer, had the random noise upper, black lower result. Sound was present.

So, I trimmed the head a few frames and it transcoded with a soft image but with an overall beige tint. A second pass after double-checking settings (redcolor, redgamma, look settings)and re-pasting grade this time to Prores HQ, it worked out the grade I had made. Redcine-x 221, QT4Beta, MBP 2.66, 4GB, G-Drive, Esata, bottle of Moose Drool...

Paul Hickey

[Johnny Friday]

I'm having problems rendering out to prores444 or for that matter any format. In that the QT Component does not seem to be passing the new color science info on to QT. So colors are unsaturated and washed out and don't look ANYTHING like what i saw while color correcting. I am wondering (based on your problems) if the Beta Redcode QT component and build 221 are not yet functioning as they should and require a "tuneup". Speculation on my part, but after three days of testing that's all I come up with since Redcine build 20 was outputting everything perfectly for me and now the new Redcine-x builds along with new color science do not produce same results.

RED?

[Paul Komadina]

I did a 3K ProRes 4444 and that worked fine.

[Dominique Grenier]

I can confirm on my side too. I rendered a clip in 4K 16:9, and it had the noise and black bar. I rendered the very same clip in 1080p, and it was all good.

In my case, this is footage shot last July. I'm gonna try footage shot on build 30 later today, if I can.

[David Battistella]

May I just raise the question of why you need to render the QT files in 4K?

David

[Dominique Grenier]

May I just raise the question of why you need to render the QT files in 4K?

David

Selling stock footage. There shouldn't be a reason why anyway, since 4K originated footage should be able to be rendered in 4K, right?

It is obviously a bug, which mean it can be fixed...

[Julio Quintana]

I'm getting the same thing trying to render out 3K footage to 1080p ProRes HQ.

[James Page]

Has there been any answer to this? I'm having the exact same problem with all flavours of 4k pro res footage. its a big problem for me!

[Dominique Grenier]

I contacted Deanan via email directly, and he asked me to send him a log, which I didn't had time to do yet, but I'm gonna do it probably today or tomorrow.

[James Page]

I contacted Deanan via email directly, and he asked me to send him a log, which I didn't had time to do yet, but I'm gonna do it probably today or tomorrow.

Any update?

[Dominique Grenier]

Any update?

Nope. I sent a log to Deanan, but didn't hear anything else. I guess it is being investigated...

[Michael Lofquist]

I'm having the same problem for 2K footage.

Has this got anything to do with the REDCODE QUICKTIME CODEC installed on my MAC BOOK?

I've got the v3.9.0 off the support page installed

-->>> no luck -- I tried with the v4.1 build and same result

[Deanan]

I'm having the same problem for 2K footage.

Has this got anything to do with the REDCODE QUICKTIME CODEC installed on my MAC BOOK?

I've got the v3.9.0 off the support page installed

-->>> no luck -- I tried with the v4.1 build and same result

It's related to the framing and export settings. We're looking into it.

[Dominique Grenier]

It's related to the framing and export settings. We're looking into it.

I didn't had time to do further tests, but is it just with the latest build or the problem is within other builds as well?

Thx,

[JasperJ]

hi All,

I had exactly the same problem as TS with build 221, noise and black while exporting to ProRes 422HQ or 444.

After returning to build 194 and having other problems, I found a 'workaround' for this bug. In my case the source is 4k, 3K or 2K (125fps) for a 2048 x 1024 end resolution.
If I change (in build 221) the export resolution to 2048 x 1080 (thus creating black bands above/below) I have no problems at all. Every single clip or bin is exporting just ok.

I must say it is a very annoying bug, literally hours and hours of wasted render time...

Hope this can help anyone getting their deadlines.

Best from Belgium,

Jasper

[Deanan]

hi All,

I had exactly the same problem as TS with build 221, noise and black while exporting to ProRes 422HQ or 444.

After returning to build 194 and having other problems, I found a 'workaround' for this bug. In my case the source is 4k, 3K or 2K (125fps) for a 2048 x 1024 end resolution.
If I change (in build 221) the export resolution to 2048 x 1080 (thus creating black bands above/below) I have no problems at all. Every single clip or bin is exporting just ok.

I must say it is a very annoying bug, literally hours and hours of wasted render time...

Hope this can help anyone getting their deadlines.

Best from Belgium,

Jasper

Can you email redcinex@red screenshots of your export and framing setup for the clips that render that way? What res and aspect ratio is your source footage?

[Sam Crutsinger]

I've got a 4.5K feature I'm working on right now.
When I rendered with the debayer at 1/2 Good, I got static.
When I render with the debayer set for 1/2 Premium, I get normal video.

2240x960 Pro Res 4:2:2 Proxy output.

[Deanan]

I've got a 4.5K feature I'm working on right now.
When I rendered with the debayer at 1/2 Good, I got static.
When I render with the debayer set for 1/2 Premium, I get normal video.

2240x960 Pro Res 4:2:2 Proxy output.

I can't recreate that here. Can you email your settings windows screenshots for export and framing to redcinex@red so we're trying the same things you are?

[Sam Crutsinger]

I can't recreate that here. Can you email your settings windows screenshots for export and framing to redcinex@red so we're trying the same things you are?

I'm actually on 194, not 221.

I'm on location without web access except for the cell. I'll send screen shots when I can

[Michael Lofquist]

Deanan

Any chance of a release soon that deals with these issues ?

cheers

Michael

[Luis Otero]

I had EXACTLY the same problem, and the only way Deanan was able recreate and force its rendering appropriately was by using 1920 X 1080P.

[Dominique Grenier]

I had EXACTLY the same problem, and the only way Deanan was able recreate and force its rendering appropriately was by using 1920 X 1080P.

Same thing here, if I render in 1080, no problem, the problem is when I render in 4K.

[Deanan]

Deanan

Any chance of a release soon that deals with these issues ?

cheers

Michael

Probably monday/tuesday.

[Matthew Rogers]

Deanan, I am having problems rendering out footage shot on pre build 30 builds. Just rendered out a whole bunch of footage today that I shot Wednesday and it went great. But if I render out stuff I shot last summer, half the clips have this error, "Error processing image for frame: xxxx"

Clips are being rendered into regular ProRes with a full debayer at 1080p.

Matthew

[Deanan]

Deanan, I am having problems rendering out footage shot on pre build 30 builds. Just rendered out a whole bunch of footage today that I shot Wednesday and it went great. But if I render out stuff I shot last summer, half the clips have this error, "Error processing image for frame: xxxx"

Clips are being rendered into regular ProRes with a full debayer at 1080p.

Matthew

Can you email me the logs from the app?
userfolder/library/application support/red/redcinex/logs
deanan at red

[Michael Lofquist]

Probably monday/tuesday.

brilliant !

Thanks for getting on top of this so fast

michael

[Dominique Grenier]

Probably monday/tuesday.

Any news as of yet?

[Ryan E. Walters]

I just tried using build 211 today and I am having the same issues- I cannot render out 4.5k material shot on pre build 30 Red One in 4.5k. I'm not adding anything fancy- just a basic white balance and then export out at 4.5k ProResHQ - 23.98 - quicktime. When I export out a still frame it all looks fine. I've attached my log files to this post.