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 Beta Build 16 (v3.1.6) available for test

S

Stuart English

Red Team
Joined
Dec 30, 2006
Messages
3,643
Reaction score
0
Points
0
Location
Irvine, Ca
Thanks to the camera .LOG files from those of you who experienced codec errors, we have been able to create an updated Beta Build 16 (v3.1.6.)

But we'd like to field test this before going to a broader Beta test release.

So, especially if you have seen codec errors, please P.M me to get a copy of this updated beta build.

Please tell us if you see resolution of your codec issue, or if it does not resolve it, we'd like your camera .LOG file please so we can dig deeper into that.

Its been great to have your detailed feedback on this.
 
Please make the next updated Beta Build version so when installing, all the user customized presets are kept without resetting to default settings.

thanks in advance
 
Presets

Presets

Please make the next updated Beta Build version so when installing, all the user customized presets are kept without resetting to default settings.
Click to expand...

Sorry can't do that at this stage. We need to add a save USER file type first.
 
new beta build for test (v3.1.6)

new beta build for test (v3.1.6)

bump-

Thanks to the camera .LOG files from those of you who experienced codec errors, we have been able to create an updated Beta Build 16 (v3.1.6.)

But we'd like to field test this before going to a broader Beta test release.

So, especially if you have seen codec errors, please P.M me to get a copy of this updated beta build.

Please tell us if you see resolution of your codec issue, or if it does not resolve it, we'd like your camera .LOG file please so we can dig deeper into that.

Its been great to have your detailed feedback on this.
__________________
 
Stuart, if you wish for someone to test it on daylight exterior hi-con dense foliage scenarios, I'd be willing to do that for you, as I plan to shoot that kind of stuff this weekend for my own tests (weather permitting).

Right now I'm on B16-3.15 and loving it, thank you all. But if you think it'd be worth the while, I'll bump it up to B16-3.16. No problem.

Lemmeknobro...

:weight_lift:
 
I started using the new upgrade yesterday after having codec errors everyday on 3.1.5, and usng two reds on a low loader carshoot (both upgraded to 3.1.6) all errors were gone ! however I had one rocket I/O error yesterday which could have been a bumpy ride with the 320GB drive. After putting the drive in my jacket and later securing it on a cinekinetic tiny saddle no problems reoccured. Well done Stuart and team. Hope most of the codec errors are gone now .

Mick van Rossum NSC
 
Very encouraging! I'm amazed at Red team's reactivity. Well done!
Can't wait to do some of my own testing on tricky subjects such as moving water this week-end.
 
So, I tested the B16 3.1.6 today on greenscreen with a LOT of hard backlight in 2K 120P, 3K 50P and 4K 25-30P. We used it on two REDs at the same time. It worked perfect and smoothly. No problems at all, no codec errors. I have to say, that I shoot always 2:1. Tried 16:9 on a greenscreen and had the feeling, that there were more artefacts this way.

There was a strange issue I figured out today while using a wireless focus. When we used it, it produced dropframes on 4K 25P. Woodoo? We took the power from the REDbattery. When we disconnect it from the battery, there were no more dropframes. I don't think, that it has to do with the built, could be a sort of frequence problem, don't know. Any body else noticed something similar?
 
Daniel Reichenbach said:
So, I tested the B16 3.1.6 today on greenscreen with a LOT of hard backlight in 2K 120P, 3K 50P and 4K 25-30P. We used it on two REDs at the same time. It worked perfect and smoothly. No problems at all, no codec errors. I have to say, that I shoot always 2:1. Tried 16:9 on a greenscreen and had the feeling, that there were more artefacts this way.
Click to expand...

Why would there be more artifacts? If REDCODE was a fixed data rate codec then I would expect that. However, I believe that it's not, so the same scene at 16:9 should have a bigger final data rate per second. In fact, I am positive about this. My Red Drive went back to RED because it was too slow to handle 4k 16:9, but could do 4k 2:1 with no problems.

Matthew
 
i would like to try this on some SPECIAL FEATURES i am shooting in CHINA well lit...for horror. can you send me the link ASAP i am having lots of rocketio_error problems with my build 16 as it is> NOMADCINEMA@yahoo.com
 
You must log in or register to reply here.
Back
Top