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

Build 15: Stuttering image problem & False Color Focus meter

PaulClements

PaulClements

Well-known member
Joined
Dec 28, 2006
Messages
1,995
Reaction score
0
Points
36
Age
47
Website
www.pclements.co.uk
Testing out Build 15.

First of all, I've noticed that when there is motion infront of the camera the bottom of the screen is stuttering or flickering as if having issues playing back the motion. It seems to occur for about 12 or 13 seconds, stop for 12 or 13 seconds and then resume again and so on and so forth.

Anyone else have this and any idea why? Anyone resolved the issue in any way?

Also where is the False Color Focus meter? For the life of me I cannot find it. I'd presumed it would be with the other assists but it doesn't appear to be on my version.

Cheers
Paul
 
PaulClements said:
Also where is the False Color Focus meter? For the life of me I cannot find it. I'd presumed it would be with the other assists but it doesn't appear to be on my version.

Cheers
Paul
Click to expand...


Video button --> viewfinder menu --> joystick left to color checkbox --> click and it's next to false color. Tell me what you see... I've got no lens here.
 
We are also seeing the stuttering at the bottom of the frame on the LCD. Have done black shading on build 15.
 
Red over monochrome was cool, but then got the footage into Red Cine and all of my footage was monochrome!!!! Why should a "viewfinder" color choice make it's way to Red Cine? Has anyone else experienced this?

I was honestly a bit rushed and didn't have a chance to go back, but it seems to me that is exactly what happened.
 
Keith Neff said:
We are also seeing the stuttering at the bottom of the frame on the LCD. Have done black shading on build 15.
Click to expand...

I, too, did the black shading and I was experiencing more of a rip/stutter at the bottom of my screen. I didn't see if it made it's way to the actual record, but it was definately there. 36 was likely selected and I've heard of problems there--so that may be it.

I only had a small window to play, and I'm AFC (away from camera) all day today so I can't really shake down all of the options, but it would be good to hear what others experience.

Does it make it's way to the footage? Does it matter 24 vs 36?
 
I black - shaded twice on Build 15 and still got those stutters.. Sounds like a few bugs made its way into this build.. Multiple outputs is as good as getting a new camera though
 
has anyone else gotten the "Media is Too Slow" message?

After updating to build 15 none of the RED CF cards are saying they are fast enough to record 4K @ 23.98.

time to reinstall the upgrade again....
 
Thom said:
Red over monochrome was cool, but then got the footage into Red Cine and all of my footage was monochrome!!!! Why should a "viewfinder" color choice make it's way to Red Cine? Has anyone else experienced this?

I was honestly a bit rushed and didn't have a chance to go back, but it seems to me that is exactly what happened.
Click to expand...

Just tried this myself. Yep, it comes into REDCINE monochrome. But don't freak... if you take a look at the color tab, saturation is at 0. Change it to 1, and all is well.

Same for REDAlert.

My guess is that the saturation of 0 is getting passed to REDCINE/RedAlert/Proxies along with the ASA setting and the like in the metadata.

Just a minor bug, no worries. It's beta, after all. :construction:

W
 
I was getting the monochrome with saturation set to zero until I reset the project and/or reformatted the flash card. Then everything was happy again.
 
Monochrome

Monochrome

It definitely should not be setting Saturation to 0 just because you set the COLOR parameter in VIEWFINDER to MONOCHROME or EDGE HIGHLIGHT. But if it is, then that is the reason why REDALERT or REDCINE react that way. We'll have to recheck our code to see if we can understand how that could happen. It is a good idea to re-format CF cards after an upgrade as there may be an aspect of file format / metadata differences between builds.
 
I had most of the problems described here and more (the Black shading crashed a few times), but I went through all the menus and selected RESET (to factory defaults) for everything I could find. Then I reinstalled Build 15 and haven't had an issue since then.

I also made sure I used a CF that had been formatted by the camera, and untouched, other than by adding the Upgrade file. I get the distinct feeling that if you do anything else (such as manually deleting old files from the CF) you run into problems.
 
gary adcock said:
has anyone else gotten the "Media is Too Slow" message?

After updating to build 15 none of the RED CF cards are saying they are fast enough to record 4K @ 23.98.

time to reinstall the upgrade again....
Click to expand...

Yes, this happened to us.
Had to go down to 3K before it would record.
Any suggestions?

ps. Love the active monitor outputs.
 
You must log in or register to reply here.
Back
Top