Welcome to our community

Be a part of something great, join today!

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

REDLine error - segmentation fault

M

Michael MK Siu

Well-known member
Joined
Jan 30, 2007
Messages
90
Reaction score
0
Points
0
Location
Montreal, QC; Toronto, On; HKG
Dear all,

I am using REDLine to transcode to ProRes 2K and receive the following error:

segmentation fault

I have never seen this before and would like to know if there's a solution to this problem.

We are shooting 4K 2:1 on CF cards, we are on build 16 3.2.4 and RedAlert 3.3.8, and RedCine 3.1.2.

This specific card contains four clips. When encoding the second and last clip on the card, it would process some frames (366 frames on clip 2 , and 34 frames on clip 4) and once those next frames hit, the segmentation fault error appears and encoding stops. This occurs on both of our 2 MacPro, as well as MacBook Pros.

Clip 1 and clip 3 both rendered out without a glitch.

I tried opening this clip in REDALert and REDCine. Both software will open the clip and scrubbing through the clip I can see the footage. However, upon rendering out from both programs, it crashes the software. Sometimes playing back in REDCine will result in a crash as well.

If any one had any results or advice on this situation, it'd be greatly appreciated.

Of note, we have successfully shot at least 8 8GB CF card with this build and this error had not appeared with other cards (or footage form build 15). There is however, another incident of card corruption - which we think is the card's fault rather than camera.

Thank you.
Michael
---
[www.dvshortfilms.com]
[www.mksiu.com]
 
Follow up:

Here's the redline command we are using:

redline -i <.R3D dir> -w 11 -R 2 --useEC --QTcodec 0 --outdir <output dir> -G 14 -c 11

It did not matter where the .R3D dir, or the output dir is - internal, or external drive. The same error arise consistently.

I tried stripping off some of the parameters, ie -G 14, -c 11 etc. but that did not help.

I tried outputting to other formats, ie TIFF, and had received strange results. It either stops at exactly the same frame as did the QT transcode, or continue to render til the end of the clip. However, upon checking the exported clips, frame 366 onwards (for clip 2), is exactly the same frame all the way til the end.

Any suggestions?

Michael
---
[www.dvshortfilms.com]
[www.mksiu.com]
 
You might have a bad frame in there which is crashing redline. try starting redline by skipping over frame where it crashes (-s framenumber).
 
Deanan,

Thank you once again for the quick and helpful reply. You have saved the day once again!

I skipped over the frames and segmented my encoding into different parts and the rendered QT file plays fine now. Although there looks to be ALOT of bad frames and one clip is segmented into five parts already! We just have to cut around the "missing" frames.

I are wondering what might be the course of these bad frames - is this a build 16 anonymity, potentially cause by something else? I know that this specific card was "shoot out" until the out of memory error came up on the camera just before auto shut down. Would this be a cause of bad frames? But it seems odd that it will corrupt not only the last clip but clip that was ahead of it.

Once again, thank you. We are actually still on set in a national park with limited phone / internet access. But because of your prompt reply and help - we were able to "fix" this problem and now I am able to show dailies of (almost) all the clips to the DP / Director tonight, which is really short of a miracle!

My deepest thanks.

Yours,
Michael
---
[www.dvshortfilms.com]
[www.mksiu.com]
 
Can you please contact support about this?
 
Please email brent and myself and we'll track it on our end.
 
You must log in or register to reply here.
Back
Top