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

Release Camera Build 3.2.16

If I'm not seeing the phantom power option does that mean I need some kind of hardware upgrade? I'm Epic #334.
 
Hi all.
My Scarlet upgraded fine.
We're having a problem with our Epic.

Sidehandle isn't recognized anymore. Force upgraded camera following correct procedure. But It looks like sidehandle upgrade went bad. Now, whenever booting up the camera the "upgrading attached peripherals" message pop up for a couple of seconds and then sidehandle stop communicating like it isn't there. Camera works fine with touch lcd.
The bigger problem is that it is behaving this way also after reflashing of same or previous builds.
The owner opened a ticket but maybe there is a know issue.
Anyone?
Thanks for helping
 
Hmmm.... odd, using an epic right now, just perfomed upgrade. When i change resolutions, the camera shuts down.

Happened twice. gonna test more. will report back.



Edit: Has not happened again. :)
 
When I tried to update my Redmote to 3.1.8, the RNDIS/...Gadget didn't appear in the network: "Unable to connect to the attached Device". This had never happened to me before and figured maybe it was because I recently installed OS Lion on my desktop system. I got it to update with no problem using my laptop with Snow Leopard. Has anybody else had a problem updating their Redmote on Lion?
 
RED confirms 1080p 24 Hz on Scarleet is not working

RED confirms 1080p 24 Hz on Scarleet is not working

FYI - for anyone having trouble getting 1080p 24 Hz HDMI to work on the Scarlet ... RED just told me that it doesn't work yet, but they are working on it.

Still a great feature list in this build!!!

I'm very much looking forward to having my camera get better and better with each build (which is exactly the opposite of owning a Canon/etc., where they just get more and more out of date).

EDIT - I was just told that the RED representative's reply in my service ticket was incorrect. 24 Hz IS supposed to work in Scarlet.

It just doesn't work in the 2012 Samsung LED LCD I just purchased (that Samsung's level 2 techs told me will work with 60 Hz and anything below, including 24 Hz) - or my other older Samsung monitors.

EDIT - it may not work after all. A very nice fellow at RED is looking into this, and I'll wait to add another edit until I know what's going on for sure.
 
Last edited:
I'm actually having trouble downloading the firmware. this happened last year to me too. anyone care to try to email it to me or just upload it to their server?
 
Jason Comparetto said:
I'm actually having trouble downloading the firmware. this happened last year to me too. anyone care to try to email it to me or just upload it to their server?
Click to expand...

Ya i will email it :)

Edit

SENT
 
Last edited:
Leo Ticheli said:
A few more tests this morning; unfortunately, I got the split screen and a solid white screen a couple of times on booting up. Disconnecting/reconnecting the LCD cleared the problem, but just adding more stress on the cable & connector.

Also, I can't figure out how to receive a stereo signal to the headphones; phantom power working fine, but we'd like to monitor with both ears. Any help appreciated.

Good shooting and best regards,

Leo
Click to expand...

I was able to get rid of the split screen by pressing the bottom button on the 5" Touchscreen.
 
Thanks for the tip, Andrae, unfortunately, this did not work for me. I'm having other problems as well, ISO not responding to changes and color disappearing from the LCD. Reboot doesn't fix these but system restore does. I've reported my problems to Red; hopefully they have a fix.

Good shooting and best regards,

Leo
 
I been getting a lot of improper shut downs today? Been using the firmware since the release and now some how today I keep getting the improper shutdown.
 
Bug on playback

Bug on playback

Love the new build. But having one little issue crop up:

The camera doesn't like to play-back the first time you enter playback after a boot up. Its weird...

I record, and when I go into playback the play button does not 'light up' and I can't playback. If i restart playback works fine on those clips, as well as if I record new clips at that point.


Tried it again the next day and had the same issue.

(on EPIC)
 
Les C. said:
FYI - for anyone having trouble getting 1080p 24 Hz HDMI to work on the Scarlet ... RED just told me that it doesn't work yet, but they are working on it.

Still a great feature list in this build!!!

I'm very much looking forward to having my camera get better and better with each build (which is exactly the opposite of owning a Canon/etc., where they just get more and more out of date).

EDIT - I was just told that the RED representative's reply in my service ticket was incorrect. 24 Hz IS supposed to work in Scarlet.

It just doesn't work in the 2012 Samsung LED LCD I just purchased (that Samsung's level 2 techs told me will work with 60 Hz and anything below, including 24 Hz) - or my other older Samsung monitors.

EDIT - it may not work after all. A very nice fellow at RED is looking into this, and I'll wait to add another edit until I know what's going on for sure.
Click to expand...

This is a confirmed bug that affects both Scarlet and EPIC in 3.2.x. We will have a fix rolled into the next release which should be coming shortly.
 
Can't record

Can't record

Hi, i've been using this release on a production 2 days ago. And right from the start, everybody was in position i had a very unpleasant Moment and had to tell the whole crew that we needed 5min, because the camera wouldn't record. The fan went down to recording levels, but nothing else happened. So finally after 10min i found out that the RedCode was set to high for 4KHD. Normally there would be a message prompting me to lower the redcode if i would want to start recording. but that message never came. So i was left there wondering what could be wrong with our camera, with no clue... PLEASE FIX THAT ASAP!
 
Daniel Kunz said:
Hi, i've been using this release on a production 2 days ago. And right from the start, everybody was in position i had a very unpleasant Moment and had to tell the whole crew that we needed 5min, because the camera wouldn't record. The fan went down to recording levels, but nothing else happened. So finally after 10min i found out that the RedCode was set to high for 4KHD. Normally there would be a message prompting me to lower the redcode if i would want to start recording. but that message never came. So i was left there wondering what could be wrong with our camera, with no clue... PLEASE FIX THAT ASAP!
Click to expand...
There's no message anymore, it should just drop the compression automatically to a level you can record at.
 
I notice a great many views on this thread, but relatively few posts. Is 3.2.16 working fine for almost everyone, but problematic for only a few of us?

My Epic rarely boots without either a solid white or black & white split screen, requiring disconnecting/reconnecting the LCD. Sometimes the ISO will get stuck; the number can be changed, but there is no effect on the LCD; no I do not have RAW mode selected. Also, a few times the LCD has gone black, requiring a reboot.

I've installed the software a few times and am growing tired of the process. I've written to Red, but have yet to receive a reply; I'm sure their hands are full with more pressing concerns.

Unless the problems are unique to a small number of users, I have to say that 3.2.16 is unacceptable for production work and should not be called a release build. I've got a shoot tomorrow; should I go back a rev?

Any advice most gratefully received.

Good shooting and best regards,

Leo
 
Leo Ticheli said:
I notice a great many views on this thread, but relatively few posts. Is 3.2.16 working fine for almost everyone, but problematic for only a few of us?

My Epic rarely boots without either a solid white or black & white split screen, requiring disconnecting/reconnecting the LCD. Sometimes the ISO will get stuck; the number can be changed, but there is no effect on the LCD; no I do not have RAW mode selected. Also, a few times the LCD has gone black, requiring a reboot.

I've installed the software a few times and am growing tired of the process. I've written to Red, but have yet to receive a reply; I'm sure their hands are full with more pressing concerns.

Unless the problems are unique to a small number of users, I have to say that 3.2.16 is unacceptable for production work and should not be called a release build. I've got a shoot tomorrow; should I go back a rev?

Any advice most gratefully received.

Good shooting and best regards,

Leo
Click to expand...


Leo,
Same, iso not change on the LCD, and at 5 ws 90/96/120 fps with user blackshading have a horizontal line ( put the iso at 12800 for see), and , does not always play the clip works.
i have rollback to 3.0.7 is better for me in this moment.
Phantom does not have the audio and some things, but much more stable.

Luigi
 
Leo Ticheli said:
I notice a great many views on this thread, but relatively few posts. Is 3.2.16 working fine for almost everyone, but problematic for only a few of us?

My Epic rarely boots without either a solid white or black & white split screen, requiring disconnecting/reconnecting the LCD. Sometimes the ISO will get stuck; the number can be changed, but there is no effect on the LCD; no I do not have RAW mode selected. Also, a few times the LCD has gone black, requiring a reboot.

I've installed the software a few times and am growing tired of the process. I've written to Red, but have yet to receive a reply; I'm sure their hands are full with more pressing concerns.

Unless the problems are unique to a small number of users, I have to say that 3.2.16 is unacceptable for production work and should not be called a release build. I've got a shoot tomorrow; should I go back a rev?

Any advice most gratefully received.

Good shooting and best regards,

Leo
Click to expand...

Re-installing the firmware will not fix the problem you are having. Unfortunately there is a bug that is causing some people to experience a problem with the LCD monitor at start up. If this is the case (and you don't like any of the work-arounds), please roll back to 3.0.x until we have a fix.
 
Only issue I have really had is that the low voltage warning doesn't always come on when the battery is low but it will instead just cut out the camera.
 
You must log in or register to reply here.
Back
Top