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

Beta Camera Build 3.2.8

ok, works fine now. All it needed was indeed a factory reset. No need to go production version first.

I had the same thing here, upgraded, no side handle.



Mike 'Fireman' Ross said:
Updated EPIC-X #2229 from last 3.x build... oooops

attachment.php


Support ticket time. Log saved. Anyone else seen anything weird? This update was done as per the book, no side handle. Going to try rollback to production build.

Mike
Click to expand...
 
is there a way to reset the gyro data, when i turn it on in display mode the pitch angle is fine but the roll angle is about 5° off

nice to have the gyrodata, VFX will love it :)
 
Really like the optional 'Time remaining' readout for the batteries; seems to calculate / recalculate quickly between standby and rolling.
 
Manuel Wenger said:
is there a way to reset the gyro data, when i turn it on in display mode the pitch angle is fine but the roll angle is about 5° off

nice to have the gyrodata, VFX will love it :)
Click to expand...

Curious if gyro will be sensitive enough for match moving? If so, this is another game changer.
 
Steve Marshall said:
Whereabouts is the Target REDCode setting?
Click to expand...

It is not a separate setting - it is automatic. When you change the REDCODE from the menu you are actually setting the TARGET REDCODE. If you change your frame rate up real high you will see the REDCODE automatically change to the best setting and be colored yellow if it does not match the target. When you change your frame rate back your REDCODE will change back.
 
Trent Lillehaugen said:
It is not a separate setting - it is automatic. When you change the REDCODE from the menu you are actually setting the TARGET REDCODE. If you change your frame rate up real high you will see the REDCODE automatically change to the best setting and be colored yellow if it does not match the target. When you change your frame rate back your REDCODE will change back.
Click to expand...

Fantastic, thanks Trent
 
I had a bumpy journey until Epic and RedMote were back to work.

After installing the new firmware the LCD turned half white, half camera picture. After a reboot I reckoned that the RedMote's firmware had to upgraded as well. Detached the RM. After a re-boot the LCD was now white. Bummer. Switched off the camera and connected the EVF. Re-booted Epic. Now I saw the checker board which fortunately tuned quickly in a proper camera picture. Connected the cable to the LCD. Now the LCD showed a normal picture. Changed the system settings to Factory Default and upgraded the RedMote. From then on all is working as usual.

If I would not had had an EVF, I probably have been stuck with the white LCD. I guess multiple re-boots may help. The installing process of this beta might need some re-work.

Either way thanks for the convenient HD formats, very handy!

Hans
 
I have updated my Scarlet to the beta twice and every time when trying to record the camera crashes and I have to shutdown. That happens at every resolution / framerates. The SSD is also format post firmeware update per the instructions. When the camera crashes it asks me to save a log. How do we do that when you have no other option but to shutdown? Anybody with this issue?
 
Not sure why some people are having trouble with the Beta upgrade - could be multiple issues and different for everyone; but. I read the install instructions for this one (strangely) and they were different than the last time.
You need to have the camera on and then install the REDMag and instruct the camera to update - unlike the other updates where the REDMag is in the camera and then you turn it on. Could this be what's hanging some cameras?

G.
 
Robino_J said:
I have updated my Scarlet to the beta twice and every time when trying to record the camera crashes and I have to shutdown. That happens at every resolution / framerates. The SSD is also format post firmeware update per the instructions. When the camera crashes it asks me to save a log. How do we do that when you have no other option but to shutdown? Anybody with this issue?
Click to expand...

The cam will automatically save a log on shutdown anyway; it will be on the Mag (as a .log file)
 
You must log in or register to reply here.
Back
Top