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

DSMC2 Beta Build v6.4.23

Yes, I confirmed that, it seems to happen with full height at any resolution that you cannot run R3D and ProRes even ProRes LT. At all resoultions at 2:1 or WS it is not an issue, not sure why.

On further testing can only run at speed using ProRes 422, it will run 444 at 23.98 but if I use 6k resolution 2:1 and try to run 60 fps (59.96) at 444 it either says it is recording but the file is corrupt, or, it gets this funny part in the upper left corner of every frame. Also, noticing a lot of lockups requiring removing power and reboot. The menus seem to get confused it you go too fast through them. But the good news is at 422 ProRes I was able to record with LUT applied down to 4k and 2k with corresponding maximum fps.
 
Last edited:
Fans kick up in adaptive quiet, I see that they will if target temp is above 39 C. Will auto calibration force the target temp above 39 C?
 
I still can't figure out how to bake in the settings in this build, running prores only, doesn't bake in Ipp2
 
Chris McKechnie said:
I'm no longer even seeing DC voltage with my AB mount batteries. Clean contact points on Standard IO. Using WC cable less AB mount. When I plug AC power in, gives me voltage.
Click to expand...

Yeah me either. But this was the case with the previous Beta too.
 
Wow so ipp2 3D LUTs can now be burned into prores? That will save my ass on some smaller fast turnaround projects where I can't be involved in post.
 
Jon Dishler said:
Earlier comment I made on this thread:

I did find one glitch which is when I tried 8k full combining both R3D and ProRes, the record button locked up yellow and required a reboot. With 8k 2:1 it works fine and anything smaller.
Click to expand...

Hi Jon,

The Technical Support team at RED would like to help you resolve this issue.

Please submit a Technical Support ticket on support.red.com with a log file and detailed instructions on how to reproduce this error. We will get this information over to our Engineers ASAP.
 
Scott C said:
Had this same issue on the most recent release firmware, jfyi. Shooting 6k/2k ProRes simultaneously.
Click to expand...

Hi Jon,

The Technical Support team at RED would like to help you resolve this issue as well.

Please submit a Technical Support ticket on support.red.com with a log file and detailed instructions on how to reproduce this error. We will get this information over to our Engineers ASAP.
 
Done. I unfortunately do not have a log file as I did a secure format after all the nonsense, and went back to R3D only. I did leave a detailed description and can be contacted at the number I left for questions.
 
Jon Dishler said:
Done. I unfortunately do not have a log file as I did a secure format after all the nonsense, and went back to R3D only. I did leave a detailed description and can be contacted at the number I left for questions.
Click to expand...

You can still get us a log file with the required information. The camera stores log data internally that persists across upgrades and multiple boots.
 
Understood, and I just sent it. Also was having some additional issues with booting so they should be on the log file as well. Thanks for the help.
 
Brad Harris said:
Hi Jon,

The Technical Support team at RED would like to help you resolve this issue as well.

Please submit a Technical Support ticket on support.red.com with a log file and detailed instructions on how to reproduce this error. We will get this information over to our Engineers ASAP.
Click to expand...

Brad,

I've actually got a ticket open for this (and another issue) currently. The most recent suggestion was that it was a glitch in that release firmware that has since been fixed in betas. I haven't had an opportunity to test this one yet but it sounds like maybe there's something still there. I plan to test this week and update with new log files.
 
So anything but full hight works with burned in proxies at the moment? I´m in my hotell room weighting the option of installing it for this little shoot tomorrow or not.

Should I go for it? Worst case I just shoot no proxies. But would love to be able to have graded proxies straight of the bat so i´m thinking I could just shoot wide screen and get it and then crop in for the 16:9.
 
I don't think you can actually burn in IPP2 with this build. I've asked several times in this thread and on the Epic W thread on FB but no one can tell me definitively that it works. Has anyone actually gotten it to work? If so, HOW? Please, I really really really really want to be able to use it but I've tried every combo imaginable in settings and none work.
 
Jason Crittenden said:
I don't think you can actually burn in IPP2 with this build. I've asked several times in this thread and on the Epic W thread on FB but no one can tell me definitively that it works. Has anyone actually gotten it to work? If so, HOW? Please, I really really really really want to be able to use it but I've tried every combo imaginable in settings and none work.
Click to expand...


UPDATE: Upon the suggestion of another EW owner, I reinstalled the new build and THAT fixed it. Works now. :) Yay!
 
You must log in or register to reply here.
Back
Top