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

RELEASED: REDCINE BETA (v3.1.8)

Awesome news, guys. Post any and all feedback here for our developers...

BC
 
I just witnessed my first RED CINE crash. I can't ever remember the previous version doing that. I was simply playing files.
 
Ivan G said:
I just witnessed my first RED CINE crash. I can't ever remember the previous version doing that. I was simply playing files.
Click to expand...

Ivan, let's go to Las Vegas and clean them out; you are the luckiest person I've ever heard of!

I've never had a RedCine session that failed to fall over at least once.

Good shooting and best regards,

Leo
 
LOL! That's what I said! It's never ever happened but with the new update it did. I'm in no way complaining, just thought I'd let the developers be aware.

I'M ALL IN!:tongue:
 
No audio from REDCine Build 3.1.8 OSX

No audio from REDCine Build 3.1.8 OSX

In REDCine 3.1.8 on Mac OSX 10.5.6 with QT 7.6 Pro I tried rendering a couple of R3D clips out to 1280 X 640 QT H.264. These clips have 3 channels of sound. When playing the rendered clips in QT Pro, I see the little sound level bars in the lower right of the QT Player, but there is no sound.

I can play and export the sound out of the QT Proxies, so I know audio is there in the original R3D.

Maybe I'm not exporting correctly?

Attached is a log file.

Thank you, John
 
This is the first time I've seen this. Doing a 1fps Varispeed timelapse with open shutter. When I imported into REDCINE I got this frame attached below. Also, as you can see, when I scroll through the clip every so often I get a RED clip name and timecode which I've always assumed was dropped frames, however, no drops were present when shooting.
Also, the strange part was that when I kick the Quality level up to Full Res High the artifacts in the image goes away yet I still get the RED timecode while playing. Then, I took the clips into REDRUSHES to do a transcode to make sure they were okay and they transcoded just fine, no crazy pixels as seen below. REDALERT had the same crazy pixel madness as well.
I'm wondering if this is a camera bug rather than a software bug when recording with these settings rather than a software bug?

My Camera settings were Build 18 BETA, 29.97fps, 4K 16:9, REDCODE 28, 1fps 360' shutter.
 
Wow. Is the crazy pixel thing those sparkles? It actually looks kind of cool, like water reflections and stars. I thought there were weird issues when you wen that slow on shutter speed. I gues the really weird thing is that it was OK in redrushes. Were any settings different?

Also, has anyone been able to run the new redcine and export files with sound without any issues?
 
SF Geek said:
Wow. Is the crazy pixel thing those sparkles? It actually looks kind of cool, like water reflections and stars. I thought there were weird issues when you wen that slow on shutter speed. I gues the really weird thing is that it was OK in redrushes. Were any settings different?

Also, has anyone been able to run the new redcine and export files with sound without any issues?
Click to expand...

Yes those sparkles are the crazy pixels. Trust me, when its in motion it is not cool :-) REDRUSHES makes everything okay as does Full Res High Setting in REDCINE. All the other debayer levels show the pixel dancing thingy.

At least the end result it okay and their is no sign of the dancing pixels in the QT Proxies either. Weird!
 
I had those artifacts (purple ones) in a project I was transcoding back last March or so. That was the last time I used Redcine. It's depressing that the problem's still there. Time's up for this software. It's a great shame.
 
You must log in or register to reply here.
Back
Top