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

DSMC2 Release Candidate v7.0.0rc3

BrendanLeahy said:
Which is a perfect example as to why you don't use beta firmware on shoots...
Click to expand...

Release firmware...bug which still seems to exist. I never install beta. Last release firmware also killed the red thc with redlink (DSMC1). 18-35 got also killed some firmwares ago.
 
I still get the random dismount of ssd in beta. It happens less than without beta. Good to know if this properly kills the random dismount of ssd bug. It's ruined a couple shoots as the camera can sometime not mount for 30 to 60 mins.
 
Manfred Baulig said:
Release firmware...bug which still seems to exist. I never install beta. Last release firmware also killed the red thc with redlink (DSMC1). 18-35 got also killed some firmwares ago.
Click to expand...

Scott C said:
I just had an audio buffer overflow error yesterday on a "stable" RELEASE firmware, not a beta. And lost part of an interview. This is not a new bug, it just looks like it hasn't been fixed.
Click to expand...

Sorry guys, was referring to this initial post you were replying to, so was under the impression you meant it was something happening with this release candidate firmware only:

Michael Tiemann said:
7.0rc3 failed to record 8K HD 8:1 + 2K ProRes HQ proxy at 23.98fps: audio buffer overflow. Submitting log file via red.com.
Click to expand...

Good to know it's an issue even on 6.23 :/
 
When I tried to select different blackshade calibration map the change doesn't reflect immediately but I need to press back and reopen the page to see the updated calibration map setting. Minor bug.
 
When I switch from a crop/smaller resolution back to the bigger ones sometimes there is a glitch on the screen that look like a mirror effect at the edge of the frame as if the sensor reading is not centered. I will try to replicate this and post a R3D to make it clear.

Another one, although I'm not sure if this is a bug. I was experimenting with extremely high ISOs and I set the FLUT to +8 and found out that the recorded image playback is way brighter (almost white) than what I saw on the preview screen during recording.
 
It works great with my Weapon CF 8K but I have issues with my Epic-W.
The message Auto-Calibration pops up anytime for no reason and more annoying, all scrolling menu on the first page are locked.
If I want to change frame rates, ISO, shutter speed or white balance, I have to manually enter the numbers, scrolling is like deactivated.
For that camera, I will roll down to the previous firmware.
 
vincent kardasik said:
It works great with my Weapon CF 8K but I have issues with my Epic-W.
The message Auto-Calibration pops up anytime for no reason and more annoying, all scrolling menu on the first page are locked.
If I want to change frame rates, ISO, shutter speed or white balance, I have to manually enter the numbers, scrolling is like deactivated.
For that camera, I will roll down to the previous firmware.
Click to expand...

I believe the auto-calibration text was to let users know that as heat changes within the camera - the calibration map for the auto black shade is being changed. This was to offset tech support inquiries for people assuming something was wrong with their camera when the auto-calibration would make it look like the video feed was locking up or freezing for a second or two.
 
as noted earlier -> no battery info with the WoodenCamera V-Mount plate w/RED Bricks... kinda hard to shoot when you have no idea on your battery status (without hitting the battery onboard display LED)
 
I got a few "proxy record errors" yesterday while recording 7K 2:1+2K Prores 422LT. Interesting because it happened on two separate Epic Ws both after working fine for a few hours. It recorded R3D only without incident. I would very much like the battery percentage back as well for my Wooden AB batter plate, or even just the official Red AB plate.
 
I just recorded for 10+ hours on three cameras using 8K 2:1 + ProRes 422 LT with two audio channels. All cameras did fine and all media seemed to behave. There was one glitch at the end: when I went to shut down one of the cameras (using Shutdown commands from 7" RED TOUCH), the fans turned on at high speed for a good minute (with the screen blank) and then I noticed that the camera had not turned off. I then held down the power button again, and it did shutdown. Other cameras shut down normally.

For me, the audio buffer overflow is connected directly to 4 channel audio and works fine with 2 channel audio.
 
Evin Grant said:
I got a few "proxy record errors" yesterday while recording 7K 2:1+2K Prores 422LT. Interesting because it happened on two separate Epic Ws both after working fine for a few hours. It recorded R3D only without incident. I would very much like the battery percentage back as well for my Wooden AB batter plate, or even just the official Red AB plate.
Click to expand...

I have had the Proxy Record Error pop up on a Scarlet-W on the current non-beta release as well. Running 5K + ProRes.
 
Anthony Berenato Jr said:
I believe the auto-calibration text was to let users know that as heat changes within the camera - the calibration map for the auto black shade is being changed. This was to offset tech support inquiries for people assuming something was wrong with their camera when the auto-calibration would make it look like the video feed was locking up or freezing for a second or two.
Click to expand...

Ok, got that.
Weird it does it only on my Epic-W and not on the Weapon CF.
 
I really want to test the RC, but I'm honestly frightened to see if my WC plate might have voltage readout issues as well. I'm not looking forward to replacing it if there are issues. Whether it gets fixed or not, I hope someone can explain a bit of what's going on to calm the worry.

Excited for full IPP2 implementation, going to be a bummer if some of us are going to have to wait longer.
 
Last edited:
You must log in or register to reply here.
Back
Top