EPIC-BASIC FEATURES STILL NEEDED

[Greg M]

- Full Raster 4K HD
- 5K HD
- Focus confirmation w/ Manual focus lenses (Canon Mount)

 

[Mike Harrington]

1. Ability to delete clips in camera. (would be a great benefit for filmmakers in remote areas where transferring loads of footage and carrying multiple hard drives is not feasible). Add a few layers of protection for others who don't like this feature, such as, "do you want to delete this clip?" And if that's not enough, "do you really want to delete this clip?" Perhaps the delete clips in camera setting could be turned on and off.

I like that...+1

 

[Greg M]

With the MX camera, quicktime proxies are generated. These are convenient.

They may have been eliminated from the Epic camera for sensible reasons. It appears some savvy "data" guys were throwing
away the R3Ds and just keeping the proxies.
However, not having the quicktime proxies forces the user to employ RedCineX software which in turn produces superior customized proxies.

Remember proxies are not stand alone file. Useful, but not a replacement for RedCineX and rendering ProRes or MXF files.

 

[Jon B.]

Also, I noticed the headphone volume/audio output is very low.
Kevin

So is this the case with monitoring for Epic at the moment? I can't hear well monitoring audio and want to make sure there's not something I missed.

 

[Max M.]

I would to darken the image outside my frameguide, like
in RCX does, that would be nice to have that on the EVF and touch screen, shouldnt be to
difficult...

 

[D Fuller]

Proxies are not currently created in camera. So you cannot just put the card in a laptop and open up a QT proxy to view a take immediately...must use RC-X.

This takes about a second per clip in RCX. What's the problem? By not doing it in-camera, the camera is ready for the next shot faster. i prefer that.

 

[Kevin Wild]

D Fuller... there are instances where proxies make things convenient. We have a SAN based facility with 5 edit suites. Not all have RCX. It's nice to be able to open the proxies on any computer to view the files without opening them in RCX.

Not sure how long it takes for the camera to create proxies. I might agree with you if the time it took was long, but proxies are nice to have.

Kevin

 

[D Fuller]

With the MX camera, quicktime proxies are generated. These are convenient.

They may have been eliminated from the Epic camera for sensible reasons. It appears some savvy "data" guys were throwing
away the R3Ds and just keeping the proxies.
However, not having the quicktime proxies forces the user to employ RedCineX software which in turn produces superior customized proxies.

Ummm... If they threw away the R3D, the proxy would not work at all. It's just a pointer.

You're talking about two different things. Proxies (as produced by the R1) are just QT pointer files. RCX can produce these (it's the QT wrapper settin gin export) but they are not customized or superior, they're just pointers like the R1 files, and they take about a second per file to produce. The customized and superior stuff that you render out of RCX is not the same thing at all. Thos files are more in the line of video dailies.

 

[D Fuller]

D Fuller... there are instances where proxies make things convenient. We have a SAN based facility with 5 edit suites. Not all have RCX. It's nice to be able to open the proxies on any computer to view the files without opening them in RCX.

Not sure how long it takes for the camera to create proxies. I might agree with you if the time it took was long, but proxies are nice to have.

Kevin

What i'm saying is that if you need that capability, you can generate those proxies from one of your suites that does have RCX in about two minutes per mag. They can end up in the same place as if the camera generated them. They can be made by your DIT, if you like, or by the assistant who transfers the data to the SAN. It seems like a better place to be doing that sort of thing. (Just my opinion, of course.)

 

[Gunleik Groven]

The in-cam proxy generation was an unneccesary bugpit.

Glad it is not there.

Haven't really tried cam proxies from the Epic... Do they even work? In FCP/Color etc?

That said:
Greg
What do you mean by fullraster 4khd?
Isn't it?

 

[Tom Gleeson]

How about
1/ 5K 16:9 (this omission just seems insane)
2/ Clean output 16:9 with no black borders
3/ 1080p r3d record

 

[Gunleik Groven]

as to #3, that would need to be a crop...

And I am not sure I want that at all. Or... I see no need for that.

But a 444 fullraster 1080 redlogFilm RGB 1080 signal out the SDI could have many uses...

 

[frazer]

I was just shooting a doc in the middle of nowhere in Ethiopia, and I was very happy to hand off drives to the director every night so he could watch the QT proxies. I don't want to come back from 14 hours of shooting that started at 5am and make QT proxies in RedCine, no matter how quick and easy it is. I just want to go to sleep. I rarely use the proxies, but when I need them, I'm very grateful to have them.

Frazer

 

[Pawel Achtel]

I was just shooting a doc in the middle of nowhere in Ethiopia, and I was very happy to hand off drives to the director every night so he could watch the QT proxies. I don't want to come back from 14 hours of shooting that started at 5am and make QT proxies in RedCine, no matter how quick and easy it is. I just want to go to sleep. I rarely use the proxies, but when I need them, I'm very grateful to have them.

Frazer

Sound Devices Pix 240 is your proxy module....solved.

 

[Tom Gleeson]

1080P R3D

1080P R3D

as to #3, that would need to be a crop...

And I am not sure I want that at all. Or... I see no need for that.

But a 444 fullraster 1080 redlogFilm RGB 1080 signal out the SDI could have many uses...

Gunleik,

I agree with the SDI output but full sensor 1080P R3D which was on Reds roadmap at one stage would seem to be the perfect compromise for clients who do not require the ultimate image quality. As a commercial DOP I need to serve my clients needs and the more options and flexibility I can offer them the more work it will create for me.

 

[Denis Buhot]

prerec mode !!

prerec mode !!

prerecord, asap !! I can't figure myself without a prerec mode... Wildlife shooting makes it an absolute must, and so do other efp/eng applications.

 

[Joe Bruncsak]

+1 for Pre-Record and 5K 16:9

 

[Mark Toia]

I'm more than happy now that I have playback... ))
And to be honest, if they didnt add anymore to the camera I could live with it happily ever after...

But have to second a few things.

*16:9 - 5k would be great. (but 2:1 is my choice of shooting format)
*REDMOTE to get proper range, it will then become very very useable.
*Louder Audio records.
*Deeper richer blacks for the Bomb EVF
*Anti glare / SUN BRIGHT coatings for the 5inche touch screen
*Dual monitoring EVF and touch screen

Other than that... Would not care if these requests don't resolved as the camera way exceeds my expectations anyway...

Did I ever mention I LOVE THE PLAY BACK Function build, love it, love it, love it, love it !!!!

 

[Denis Buhot]

Ah...4K and 5 K 1:9...

Ah...4K and 5 K 1:9...

... too. 4K 16:9 is on the specs sheet right here... Anyway, I understand that one can set his own user's frame already, and shoot inside a 16:9 frame guide at 5K, or inside a 16:9 frame guide at 4K. Am I right ? If yes, that can wait...

 

[Björn Benckert]

What i'm saying is that if you need that capability, you can generate those proxies from one of your suites that does have RCX in about two minutes per mag. They can end up in the same place as if the camera generated them. They can be made by your DIT, if you like, or by the assistant who transfers the data to the SAN. It seems like a better place to be doing that sort of thing. (Just my opinion, of course.)

I think a lot of people does not realize that you can make wrappers (R1 kind of offline files in RCX) so many people go on and try to render out Proress files, and when not having a red rocket that is quite time consuming. So if it was not a big deal then I think a on board "create proxies before eject" would be nice than you can have a "less educated DIT" / production assistant copying and looking trough the files etc. This person does not need schooling in RCX etc.