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

New Build 16 v3.2.1

Did everyone go on vacation or is anyone still trying to break it?
 
I did get codecerrors yesterday (or rather: my cam with my new photographer...) running through grass and flipping up to the sky.

And yep, the shot was meant to be, not only a break the codec rehearsal.

RC 28 4k 2:1 @ 30 fps

Unfortunately I don't have the log, as this thing just had to be finished quickly and be sent off...
 
REDdrive or CF?
Can you email me the log when you get the camera back?
Just put in a card and then eject it and it'll write the log.
Still frames from the shot and the clip name would also be
useful.
 
gunleik, which build were you using?
 
Latest

Shot for 7 hours today without other issues than the occational weird LCD/HD-SDI output. No crashes, no nothing. Already sent on TV, and that's the issue Deanan with the crashes. Just had to format everything and run into another shoot. Will the LOG still be right?

Played around with the RAW preview. Looks informative...

30 fps: Disk.
25 fps: CF (RED CF cards, just to take away any confusion...)


Gunleik
 
Deanan said:
Did everyone go on vacation or is anyone still trying to break it?
Click to expand...

Deanan,

I'm patiently waiting for someone to tell me which version of Quicktime I should install for Redcine 3.1.2 on a Windows XP Pro 32 bit system.

As soon as someone (preferably from Red) tells me, I can start my batch render.

Then I will go out and try to break the mutha...

-Thor
 
Just shot day one of a commercial using this build. I'm not amazed by the image quality gains with build 16... but the added features are phenomenal. This is the first big step I've felt the camera take since simultaneous outputs.

RAW view + false color assigned to two buttons on the EVF is the BEST.FEATURE.EVER.

Thanks, guys.
 
I've had some playback codec errors. Still haven't had a codec error recording. I haven't done much RC28 though.

The playback errors suck because they kick you out of playback mode even if you're just trying to skip by that clip. If that error is thrown then we should be kicked to the clip before or after the clip giving the error depending on the direction you were scrolling when the error happened. Another short term remedy is to let us scroll past the final clip and loop back to the 1st clip.

Seems like it should be really easy for you guys to have a click right joystick on the last clip cycle to clip 1 instead of just stopping on the last clip. If current clip >= last clip then current clip = 1 else current clip++ ;

Also add cycling from 1 to last clip via a left joystick click. That would help a lot until a full clip viewing feature is added to the camera.

Also need a play all and play forward from here. Like 2 play presses within a half second triggers play all clips forward from here. With the 1080P playback you kinda want to sit there and watch this stuff. :-)
 
What Joelnet said.

-Thor
 
Do the log files show issues during playback if we were to forward them to RED?

I haven't experienced playback codec errors, but then again, I only tried playback from the camera once, just to check out the 1080p HDMI. Looks amazing on a 71" 1080p Samsung DLP, BTW. :)
 
So this is it so far? No other issues with the new build?
 
Some significant issues recording to CF with the latest build yesterday. Shot the day before with no problems but ended up with the first 4 cards of yesterday's shoot being basically being unuseable. Switched to Red Drive eventually which worked fine with no issues.
Shot was a steadicam 360degree spin around talent in a grass field at sunrise. Not sure if RF interference was at play as we were running a Preston FIZZ wireless FF, Modulus video transmitter, and AJA downconverter at the same time.
More information here:
http://www.reduser.net/forum/showthread.php?t=16322
 
release notes for the build

release notes for the build

Just curious in the release build notes it says

"Addressed residual Codec Errrors in high contrast 4K scenes"

Just curious if all of this much appreciated codec troubleshooting applies only to 4K footage, as I know that I have gotten codec errors at 3K as well.

Should the improves apply no matter what resolution you are shooting at?

EDIT: Nevermind I should have read further down and saw this "Addressed Codec Errrors in high frame rate 2K and 3K scenes" (although the codec errors I got ,in the previous build, were not at high frame rates, just 29.97 at 3K)
 
Deanan said:
Did everyone go on vacation or is anyone still trying to break it?
Click to expand...

Deanan,

I did not get the codec error message, BUT... here's what did happen:

I shot some 2k 2:1 Redcode 36 at 100 fps, B16 3.2.1.

When I played the footage back, right in the middle of the shot, the camera suddenly showed the "Initializing" screen. ???

The LCD went blue... like the R and G channels had completely disappeared.

The camera went competely through the "Initializing" stage with only the blue LCDS active. When the camera was up and ready to shoot, it still only had the blue channel showing.

So, I restarted the camera. This time it came up like it normally does. So I tried playing the clip again. It did exactly the same thing at exactly the same point in exactly the same clip. The screen went blue and gave me the "Intializing" message again. When the camera came up, the screen was still blue.

Broke the codec? Not exactly, but something is broken.

I'd be glad to send you the folder. You could load the clip on a camera and see if does the same thing. Where do you want me to email the log file? To Stuart again?

-Thor
 
Please email it to Stuart and myself.
Does the clip render fine in RA or RC?
I'll send you upload instructions when I get your email.

Thanks.
 
Deanan,

The log file is uploading right now to you and to Stuart in the form of an email attachment.

I'll see if I can get it to render in RC. FYI, I'm on a PC.

-Thor Wixom
Red 137

EDIT: I'm going to do this in the morning. I need some sleep. I'm not a vampyre like you guys!
 
Shot some 2k 120FPS today and got playback errors... rocket io I believe. I don't have the drive with me now but when I get it back I'll see if I can get the log file off it and send it in. After powering on/off and trying a few times to get it to playback it finally started working for no apparent reason. Very weird.
 
Please send the log if you can. You don't need the drive that was causing the problems as the log can be written to any drive/card by ejecting.
 
You must log in or register to reply here.
Back
Top