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 :)

Can't get a clean render at all

Spike Baumann

Spike Baumann

Well-known member
Joined
Mar 1, 2007
Messages
529
Reaction score
0
Points
0
I have tried REDalert, clipfinder, REDrushes, quicktime...they all give me these fucked up frames that look like the image has been cut and pasted all over itself. I tried all different settings, resolutions and both pro rezs. WTF. REDcine keeps crashing the MBP with the second monitor because of some out of range shit. The R3D file is fine and the proxies are all fine but I keep getting these frames in random places. I tried exporting DPX and Tiffs and I get the same shit.
The edit out of FCP will render fine but I need to bring a few clips into After Effects to do some compositing so I'm trying to just bring those clips in from the original files. I'm about to beat the dog right about now.

Oh...another thing. The fucked up frame looks different in each program, in AE it looks like it has been cut and pasted in little slices. In FCP it looks like its sliced into big interlacing. In quicktime it looks like the video is cut into 4 slices and every other slice has been moved over a bit.
 
"Fucked up" is the format Redcine is best at transcoding into. No offence to anyone..

Redrushes and Red Alert seem to do much better.
 
And the version numbers of the program. Please make sure you have the latest version of all programs since something like this was a known bug in some older versions. If the proxies do not exhibit the problem then it's likely the other programs are older versions.
 
1203_1230442544.jpg


This is what happens out of almost all of the programs. I haven't been able to try REDcine because it crashes the laptop giving me an out of range error on the extra monitor.
I just tried another clip finder tiff render and half the files were unreadable.

In final cut I was able to render out a rough edit a few days ago and that was fine but now that I'm trying to do the composites all the renders are messed up. Also on top of that... none of my files open anymore. I get a file too new or unreadable error with every copy I had saved to be safe.
:angry03: I have the biggest headache right now. I have to have this done by the 12th.

Final cut is at 605
REDalert is at 360
REDrushes is 360(1)
quicktime is at 755(249.13)
clipfinder is at 215(100)
OSX is at 10.5.5
2.16ghz core2 MBP
3 gigs ram
 
It sounds like your problems are somewhat changing. That screenshot looks like nothing I've ever seen before. Would it be possible to put the original R3D up for us to download somewhere (please zip it first so we know we get it properly)? If so shoot me an email with the link (my email is rob at red dot com)

It's very weird that you're having problems in certain apps but not in all or in all situations. Are you sure your harddisk and everything is okay?
 
Yeah I get hits like that all over randomly. I unplugged the other monitor to see if it was that maybe just in case since it was about around the time I started having problems. I have yet to try another export since because I had to double time to re-edit what I lost on the corrupt FCP project.
I will compress the file I was using for the composite later today when I get a little more of the edit done.
 
Sooooo. check this...I unplug my second monitor and guess what, I have successfully exported 2 prorez quicktimes. Weird, isn't it. I hope I didn't just jinx myself.
 
Spike said:
Sooooo. check this...I unplug my second monitor and guess what, I have successfully exported 2 prorez quicktimes. Weird, isn't it. I hope I didn't just jinx myself.
Click to expand...

It makes as much sense as anything. Something is definitely wrong somewhere. Some applications might use the GPU to accelerate certain tasks, maybe that has something to do with it.

Michael Morlan said:
Interesting. One of my clients was having issues on only one of their RedCine WinXP machines with the lower half of the frame blanked. I'll recommend this thread to them.
Click to expand...

This is one of the problems I was talking about before. This sounds like they might be running older versions of the software, a problem like this was fixed recently (if I remember correctly it only occurred on 4K HD footage).

In case you're using the QuickTime codec remember to update to the latest, which is currently in the RED Final Cut Studio 2 Installer (we'll be updating the separate RED QuickTime Codec soon as well).
 
I thought I was in the clear but coming back from vacation and opening everything I see I have screwed up frames again. I don't get it. Last night I rendered a few files from REDalert and they were fine then this morning I start to work on them and they have the broken frames again. The weird thing is that if I scrub through really slow frame by frame the messed up frame will have a green tear through it. If i scrub through almost frame by frame speed, just a little faster, I get what looks like a part of the image moved over 50 pixels at the same spot I saw the green tear during the frame by frame step through.
 
I give up and going to wipe the MBP clean and install everything from scratch. The thing I thought that might be causing this was I'm using NTFS file systems on my drives but I edited a bunch of P2 MXF music videos and reels on them with no hitch. I think maybe quicktime may be the culprit here.
 
what's your graphic board ?

I had the same problem on two computers.
with an Ati x550 (agp). And extremly constrasted black and white with an Ati x850 (pci)...
(i may have switched both :) don't remember)

I changed one for a nvidia 9600 gtx (pci express), and it's is gone. I can finally render my r3d.

Maybe it's just a matter of graphic port ? i mean when the buffer has exceeded, it just copy what's already rendered ? don't know...
 
its a ATY, RadeonX1600 ...(thought it was ATI)

is this something I can change out?

Thanks for replying. I'm going to wipe the computer today just in case but will get a Nvidia.
 
So i went to my partners place and tried to open all the files on his mac pro and they wouldn't open. I got the "this file is too new for this version of Fina Cut" error I was getting. I was ready to edit this thing a 3rd time but we found an XML I exported just in case for some reason and it worked and opened the last edit I had. WOOOHOOOO!!!
Now I know to always make an XML back up file so I can at least get an edit back. I rendered a small clip of it and it also worked like a charm so I'm going to try to wipe the MBP clean and see if that works. He also has an ATI card so I'm hoping that it was some OS error. Fingers crossed.
 
You must log in or register to reply here.
Back
Top