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

Any idea what would cause this...?

I had a similar problem with some footage from B camera in a recent shoot. We were running build 9 (I believe) and in FCP/Compressor, it'll crash when dealing with those specific frames. One frame is good, the next will be badly messed up. I figure I can cut around those frames in the actual edit, but right now it's just the matter of rendering the shots out into a useable format that won't crash the system.

Later tonight I'm going to try running the shots through RedCine. Perhaps I can render out new proxies or at least a TIFF sequence that can be rendered out to prores without a crash.
 
Brook Willard said:
Were there any HMIs in play? I'm sure that's not the cause here, but I've seen some pretty funny things from angry HMIs.
Click to expand...

HMI's causing interference with the Red? How so? Magnetic or electronic ballast?

Sounds like important info. Thanks.
 
um3k said:
A Red in Ohio? Where?! I must see it!
Click to expand...
We're in Dayton, but tonight is the last night of the shoot. Email me if you want more details.
Still trying to figure out the problem. We switched camera bodies and last night's shoot went off without a hitch.
 
I'm working with precinct13 on the same film. Now that we're getting closer to a rough cut of the feature, I'd like to get our "problem" clips straightened out.

Has there been a solution to this problem yet? I see from previous posts that this is possibly a decode problem, but until it is solved I figure anything is possible.

I downloaded the latest version of RedAlert (1.5.4) and ran one of our problem clips through it. The QuickTimes still had the bad frames.

Here is what it looks like:

BadFrame.png
 
Just jumping in here and may be way out of my realm of understanding but I got a disc or 4 from Silverado to get up to speed on REDCINE with a while back and noticed that some of the r3d. clips had a similar pattern in them. I also noticed that when I shuttled the clip across the pattern it usually made REDCINE crash or blue screen. Those clips were shot back in Sept. so Im sure they had a very old build on their camera. Maybe its a old build vs. new REDCINE build?????
Also just downloaded a clip from Redrelay.net of some girl in a wine celler and noticed that all the QT clips all had the same half frame electriczebra print.
For what its worth.
 
Russ Fill said:
Just jumping in here and may be way out of my realm of understanding but I got a disc or 4 from Silverado to get up to speed on REDCINE with a while back and noticed that some of the r3d. clips had a similar pattern in them. I also noticed that when I shuttled the clip across the pattern it usually made REDCINE crash or blue screen. Those clips were shot back in Sept. so Im sure they had a very old build on their camera. Maybe its a old build vs. new REDCINE build????.
Click to expand...

Russ,

Most likely due to us shooting on older firmware or running an older version of REDCINE.

We'll have a "sampler" project released in about two weeks that will blow your mind in terms of size and scope. First of its kind--ever.

Torrey
-----------------------------------------------
Torrey Loomis
President & CEO - Silverado Systems, Inc.
Outfitter to the World's Foremost Apple Professionals
2600 East Bidwell Street, Suite 280
Folsom, CA 95630
(916) 760-0032 • FAX (916) 404-5258
tloomis@silverado.cc
http://www.Silverado.cc

Check out our Insider blog at http://silveradosys.blogspot.com
 
You must log in or register to reply here.
Back
Top