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

Build 17 issues?

Shawn Booth said:
The EVF does have odd behaviors from time to time doesn't it? Cable switching doesn't help, power cycling usually does but I've found the best solution for certain issues (whole camera system) is:

Acceptance.

And I move forward and keep shooting... while grumbling under my breath of course. Some problems are just there like visiting in-laws...
Click to expand...

this started two weeks ago...here.
switching cables didnt help-
 
Acceptance is growing old....

How does a release build suck more than the beta build? I really don't want to go back to B16 or beta B17 - love the features with RB17 but WTF...

Never had a power problem until RB17 - now the camera powers off whenever all the time... I have 6 bricks, all numbered. #'s 4-6 can't keep the camera powered, the pins appear fine. I do think though that it is the cradle rather than the build. I just never had these issues with ANY other build...

Boot hangs - every time I turn the camera on. I push the black button, quickly hit it again to power cycle off and quickly cycle it back on. Boots fine and appears to be a little faster than 90 seconds...

And B18 doesn't offer any help...

New question. Will Epic/Scarlet also rely on builds and their updates? If so, I feel like the whole community is going to suffer for a time while RED figures out how to keep up with their own growth.

Epic/Scarlet are great, I really want a DSMC Scarlet myself but until they're shipping I can only focus on the R1 and working with it. Which was always great and fun until RB17 issues began cropping up and growing and persisting...

Save the renders, save the announcements - fix RB17.
 
Has anyone else experienced an odd re-frame on playback? We just shot B17 for the first time this weekend and along with all of the other issues stated in this thread, we also noticed that during playback, we got a re-framed image.

It was re-framed/zoomed in about 25% and only on the Red ProLCD - The actual HD-SDI out client monitor was tinted awful neon green!
 
christiansprenger said:
It was re-framed/zoomed in about 25% and only on the Red ProLCD - The actual HD-SDI out client monitor was tinted awful neon green!
Click to expand...

Sounds like you have playback set to 1080 and a non dual-link monitor connected to one half of a dual link signal.

1080p playback only shows the full frame on an external HDSDI monitor - cropping on the LCD is an accepted side effect. The PVW out is single link, but the other two are dual link. If you have a ET break-out-box the PVW output is labelled 720p, but this is not correct if you have chosen 1080 in the menu.
 
Green issues

Green issues

On a shoot today we had some very strange issues and the clients got all concerned. All the outputs were saturated and certain colors had a greenish cast to them. (Places where there shouldn't be highly visible green, like skin tones)

The clips when opened up in Redcine or Redalert looked fine. But I was able to recreate what we were seeing in the monitors by changing the colorspace from Redspace and (gamma) Redspace to Rec 709 and (gamma) Redspace.

If If used the Rec 709 and Redspace combo, it was like what was coming out of the monitors. Note the green around the mouth and eyes.

A system restore SEEMED to solve the issue, but won't find out for sure till tomorrow morning on set. Is is possible the Camera matrix is getting stuck/confused? Any ideas on what is going on?
 
It looks like the green cast is from bounce off of those green walls. Remember that the monitor preview is far more saturated than the image opened in Redcine/Red Alert.
 
We've had Build 17 for about eight hours now and we're already thinking of rolling back to 16, which would unfortunately force us to shelve our new 16GB CF Cards as well.

Our Red always had some minor boot hang issues but Build 17 really dropped the hammer on us. I would estimate 50% of our power-ups now hang at the Booting... stage. This is indoors, at room temperature. Unplugging the monitor and power cables really helps, but it's time consuming and worrisome to constantly deal with this.

Someone here mentioned a hot swap power solution, I would love to know what they use.
 
Still on B16.
Found that if I wait 60 seconds (which feels a tremendous amount of time, so you have to tell a joke meanwhile) after powering off and before switching on, the booting time is reasonable.
I try to tell them it is like the reload of a film magazine on an old Mitchell camera which almost no one has the idea of what I am talking.
Yes I must be old. Not too old.
 
burnie said:
We've had Build 17 for about eight hours now and we're already thinking of rolling back to 16, which would unfortunately force us to shelve our new 16GB CF Cards as well.

Our Red always had some minor boot hang issues but Build 17 really dropped the hammer on us. I would estimate 50% of our power-ups now hang at the Booting... stage. This is indoors, at room temperature. Unplugging the monitor and power cables really helps, but it's time consuming and worrisome to constantly deal with this.

Someone here mentioned a hot swap power solution, I would love to know what they use.
Click to expand...

Here is what I use...

http://switronix.com/product_details.php?cmd=info&id=214
 
Monteiro said:
I have found that rebooting with the LCD Monitor unplugged almost always works.
Click to expand...

I also find it works, so well that I would say it works everytime. It certainly feels that way.

My problem is that I have now reached the point where I need to unplug the monitor for each boot. I am more likely to get a boot hang than not if I leave it in.
 
Can't record Audio at all on build 17

Can't record Audio at all on build 17

Although, it meters fine and appears to record, we always get the audio fault error on playback of any clip with audio. (Video alone records fine) Roll back to build 16 and it records just fine.

We have tried different channel inputs, different connectors, different mics, different drives, same result. On playback we always get audio fault codec errors.
 
You should be able to record audio fine with B17. It's just that you'll get the playback error when you try to do playback.
 
On Set Issues

On Set Issues

RB17, 2K2:1, 29.97fps, RC28, 180 shutter, RED Drive

Locked off camera, greenscreen, lav mic- 1 channel plugged in to camera.

Every so often the camera stops recording and gives either:

RECORD ERROR - Audio Error

or

ROCKET IO - Audio Error

We're able to start up again after the error clears. I would like to know what the issue is: Is it operator related? Camera malfunction?

Will send log files to Deanan and Stuart as soon as drive is swapped. Just wanted to share and see if anyone knows/familiar while we continue shooting.

Maybe it's just 17 audio issues?
 
Shawn Booth said:
The EVF does have odd behaviors from time to time doesn't it? Cable switching doesn't help, power cycling usually does but I've found the best solution for certain issues (whole camera system) is:

Acceptance.

And I move forward and keep shooting... while grumbling under my breath of course. Some problems are just there like visiting in-laws...
Click to expand...

a divorce can solve that problem....hahahah
 
You must log in or register to reply here.
Back
Top