Known EPIC issues/faults

[Jens Jakob Thorsen]

2) High frame rate footage likes a LOT of light

Why do you recommend this, it has been known since the beginning of cinema?(joke, but about common knowlegde)

 

[jimhare]

I've run R1s this way for 3 years, and haven't had an issue for the last 2. Cutting isn't really an option, has to be the whole show, just like an O/B. The good thing is we can leave the fans on during the take. Doesn't bother anyone is a 2,000 seat auditorium! ;-)

Hmm, never done one that long.. Honestly don't think I would risk it.. I'd cut when possible, give the fan at least a few seconds to let the little baby breath.. You would be quite sad if there was an issue with a 70 min take.. Good question though..

Also if sound is not an issue, I'd have that baby cranking while rolling!

 

[Justin Marx]

Hmmm,

Good thread idea.
No gotcha's to report at all my end though.

Been shooting the EPIC-X out of the box since Sept.
The first day felt, looked and worked as if the darn thing had been beamed in from the future.
And a very distant one at that


My RED adventure began with build number 12? on Gibby's #8 R1 in Aug '07.
Required a few tweaks to adapt the early builds to our applications.
Such as our re-useable underwater cooling system that also made a great snack after shooting several hours.

I will POST any challenges I encounter in the field as well as solutions as EPIC-X begins to travel with me around the planet underwater and in the air.

We'll see...

I can't believe that dog just sits there with the prop wash and noise!

 

[Stephen Williams]

The good thing is a 12 second startup is a get out of jail free card. When the R1 used to stop during a take (hasn't happened for two years but in the early days was an issue) it would kill 2 minutes + from that angle, which caused problems back then.

There is something wrong with your camera mine boots in 8 seconds, always has over the last 3 firmwares.

 

[jimhare]

There is something wrong with your camera mine boots in 8 seconds, always has over the last 3 firmwares.

Heh, my Epic arrives tomorrow and I'll be checking my boot time. Checked a friend's last week and it booted in about 10-11 seconds. 8 would be great.

 

[Randall Brown]

1. There is no audio in the HDSDI output. This is HUGE is you plan to capture sound in camera and record proxy to a teradek, aja kpro, PIX 240, etc.
2. Occasionally get a split line on the monitor or EVF, where the image "breaks" and needs a restart to clear it.
3. Range on Redmote is tricky
4. No Phantom Power on Audio Jacks... yet?

All that said. LOVE this thing,

 

[jimhare]

Okay, got my Epic this morning and cannot get it to hiccup at all. Every boot successful (10
Second average) did a series of long takes, each between 60 and 100 minutes with 100% success, and a series of HDR and high speed tests.

Again, not a single fault to report, this thing is solid and the kinks worked out.

In fact I only noticed two things:

1 the touchscreen isn't always responsive, but I have felt that way about every touchscreen ever, including my iPhone and iPad.

2. I don't get a time remaining when using Red Bricks with the belt pack, but this appears to be the case with many users so maybe it's not supposed to yet. Will try again tomorrow using the Red Cradle.

Extremely impressed with how robust it is. Absolute joy!

 

[Stephen Smith]

I had an issue today where the camera would freeze. Timecode wouldn't roll and the tally turned yellow. We were shooting 23.976, 5K, 2.4.1 Aspect. Anyone ever had this happen? I must admit we are on a version old firmware... I cleared the camera settings and that seemed to do the trick. I am hoping everything is okay with my camera.

 

[Jeremy Torrie]

This has happened with us a few times...all we did was a force quit/power down and up again and it went away. Completely arbitrary. There has been a LCD screen freeze issue but that was addressed in the last firmware upgrade.

 

[Stephen Smith]

I think that is the issue. I just need to upgrade that when it comes back in.

 

[Deanan]

I had an issue today where the camera would freeze. Timecode wouldn't roll and the tally turned yellow. We were shooting 23.976, 5K, 2.4.1 Aspect. Anyone ever had this happen? I must admit we are on a version old firmware... I cleared the camera settings and that seemed to do the trick. I am hoping everything is okay with my camera.

This one is a the half press preset that is tied to the wrong function.
The latest build fixes that or you can unset the half press.

 

[James Milner-Smyth]

James we now have 4 Epics (Ms and Xs) and I have to report the following gotchas:

1. Shooting home movies at 5K uses a lot more data than a Canon 5D. But the images will be ready for our future home viewing of 4K...

2. The Epics do not yet have dishwasher loading capability. I'm not sure any future firmware upgrade will achieve this but I've begged Deanan to put it on the feature wishlist.

3. The cameras last a really long time on a single V-lock which can only be a bad thing for battery manufacturers.

4. Being very compact in a stripped down configuration can lead to you not being taken seriously as a shooter. You can be filming high speed 5K images in a very public place and no-one will try and arrest you.

OK in all seriousness I'd love for playback to be enabled asap as looking back at slo-mo in camera would be really useful. And maybe once in a while if you really messed up with your playing around of settings you might have to turn it off and turn it back on again (not a trial at these boot speeds). Also now people can shoot 300fps I'd wish they'd remember to cut the camera occasionally as processing clips that last hours can be a pain.

But boy do those images make that worthwhile.