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

Top 3 Features - Wishlist

I want to edit my Red material on a Steenbeck. WHY CAN'T I?! The Red team needs to do something about this obviously overlooked workflow. The customers are waiting.

(Or could it be that Red is simply a new way of doing things...?)
 
top 3 wish list

top 3 wish list

I mirror the first post ...

[0. shadow noise improvement(s) ... keeping fingers crossed for build 16]

1. Cache, minimum 4 seconds
2. Sleep-mode / ability to power the camera up quickly (say < 2 secs)
3. Magnified display (pixel for pixel or larger) for critical focusing

Cheers

EDIT : not a complaint ... it's great piece of kit :usd:
 
Workflow

Workflow

aquafox said:
I want to edit my Red material on a Steenbeck. WHY CAN'T I?! The Red team needs to do something about this obviously overlooked workflow. The customers are waiting.

(Or could it be that Red is simply a new way of doing things...?)
Click to expand...

We are on it ! :shiftyph34r:
 
camera
1) user assignable buttons
2) 1:1 zoom
3) sleep mode
4) upload LUT's to the camera
5) histograms based on RAW file instead of preview
6) overview of all clips as icons in playback mode


RedCine
1) less flat preview to start with in RedCine, more like the quicktimes are
2) ability to make QT previews with the settings in RedCine
3) ability to delete clips from hard disk from within RedCine
4) copy color settings to all clips
5) better way of setting in and out points of clips and move them to another position in the timeline
6) integrate Crimson in RedCine
 
It's the age old problem, of customers wanting to not have to adjust their way of doing things while they get outstripped by nimbler production companies. Power and connections can only get you so far when one commercial production company says I can do it for this price and another says I can do it for this. I've had the privilege of working around some truly talented editors lately, and I can tell you safely they aren't that demanding, you just have to make it work for them in their artistic environment. While only a few have really figured it out and are now blackboxing it in facility its not that hard (which I say as I support a highend uncompressed DPX workflow thats cutting on an unsupported avid meridien natively file based).
 
1. Sleep mode

2. possibility to zoom into the viewfinder picture (to get rid of vignetting while shooting 3K with S16 lens)

3. False Colour on user assignable buttons

Camera is working great. Done my third commercial with RED in the last 3 weeks and the only thing that I find can be better is DR/noise. I'm interested how build 16 will improve this.

Workflow is cumbersome. In traditional commercial land every single frame has to be converted to UC PAL and then dumped to DigitalBetacam. From there the common workflow (Avid, FFF, Quantel) is working. From this perspective shooting 35mm is not that much more costly. Using RED is still an artistic decision and not driven by economics. This will change in the future when reconforming, versioning, archiving etc... are working with r3d.

I'm not sure how an open SDK will solve this fast. It will take another 1 or 2 years until AVID, Discreet and Quantel will implement R3D RAW in their solutions and posthouses will embrace this in their pipeline.

Until then a fast rendering app./ with render-nodes/hardware plus HDSI/SDI out is needed. This can solve the problem fast and people can still use their trusted tape workflow.

Please note that FCP/Crimson(thanks Ian)/REDCine is a working pipeline for many (also me) but not for commercial land.


Hans
 
laguun said:
the customers dont want to change their workflow, and they dont want being consulted, neither by you, neither by us, they simply want to use working solutions.
Click to expand...

I have clients that feel this way, but... Like I tell them, "new tools. new workflow." Evolve or die.
 
Evin Grant said:
Back on topic:
1: RED LOG applied before compression. (Should solve the noise, 3200K and sensitivity issues)
2: Customizable button assignments (I really want false color on button #1)
3: LUT uploads for looks in camera.
Click to expand...

1) Do whatever it takes to make the camera perform better under Tungsten lighting. Hopefully that's what build 16 is about because daylight already looked terrific.

2) I want the phantom power to work. Right now it doesn't work at all on any input. That's not what I would call a feature request or bug. That's what I would call a broken camera - it should be on the front burner. As in hey, my phantom power is not working do I need to send it in for repair or what? Specs may change. But not that one.

3) You should be able to see audio levels at the same time you're adjusting the gain.

4) Audio with QT proxies.

5) Totally Customizable UI, ideally. I should be able to configure every camera, evf and lcd button.

In the meantime, I should be able to toggle between False Color, Edge Focus Assist On/OFF on the same button. It's pain right now to go to the menu to do that.

6) R3D support in Color ideally via a proxy edit.

7) oh - sleep mode everyone is talking about sounds good too.
 
Jim,

would it be possible to get a split screen mode where you can see the new look on the right with the regular feed on the left. I think this would be great for quick comparisons on set on camera to the live outputs.

Cheers

Bing
 
Man, so many good and important feature ideas here...

So Jim, how much you paying us for all this IP??!

Just kidding, it's great to have such a hands-on input into the tool you use - that's probably the most "revolutionary" thing about this camera/company, imho...
 
>99% of all important 3hrd party VFX/CGI products (max, maya, xsi, combustion, nuke, fusion, ae) cant work with redcode raw (or only with the low-quality QT proxies).
Click to expand...
Not to steer this back OT but I just wanted to say that NOBODY in the VFX world uses quicktimes, avi, redcode, or any other movie wrappers with those apps. We all use image sequences like DPX's... but in software we always use reduced quality/size tif's, tga's or jpg's (or whatever small file you want).

I'm sure in the future compositing apps like nuke and fusion will support it. Until then you always have image sequences.

... game on
 
Jeff Kilgroe said:
I have clients that feel this way, but... Like I tell them, "new tools. new workflow." Evolve or die.
Click to expand...

Many clients (broadcaster especially) will not go red, but only have it as an alternative to their xxx or yyyy XDCAM HDs, P2, HDCAM (SR), maybe even EDITCams etc. They wont die.

Avid, discreet and quantel basing houses are by far the huge majority of upper-class postproduction houses. To them, Red is an alternative to 35mm/HDCAM. They also wont die.

We want to win them over to red, not competete with all of them. That would be nonsense. The houses ARD & ZDF have ~26.000 employees. But, marc and i both agreed & recommended to not go offtopic in this thread - lets better focus on the wishlist.
 
Gene Crucean said:
Not to steer this back OT but I just wanted to say that NOBODY in the VFX world uses quicktimes, avi, redcode, or any other movie wrappers with those apps. We all use image sequences like DPX's... but in software we always use reduced quality/size tif's, tga's or jpg's (or whatever small file you want).

... game on
Click to expand...

thousands of houses use 10/12 bit QT (blackmagic/aja), AVI (blackmagic/AJA) and their DPX wrappers. Lets go back to topic (and/or start another thread in 4K workflow or ot)
 
you know the pissing match of who knows more is so beyond interesting. lets leave that where it belongs with the dinosaurs on cml. this forum should be about good ideas and ways we can get this system to what we want rather than my daddy is bigger than your daddy style stuff
 
1. 1-1 pixel Focus Assist
2. Sleep Mode
3. Recording Cache (yep, 4 secs would do it)
4a. Longer interval choices in timelapse (5 sec, 10, etc)
4b. Longer exposure times for those intervals

Oh, and that whole dovetail thing *ducks, runs*
 
The most important things have already been mentioned, so I'll go for the less important specialty things...

1. 'Varicam' flags on the User Bits in the VITC on the HD-SDI out.
2. Flexible sync input (auto sensing input, be able to sync to whatever comes out of the RED camera standing next to it with a single cable between....)
 
1) Standby/sleep mode with quick startup.

2) Longer timelapse intervals and full range of shutter speeds for those intervals (currently limited to 1/24sec)

3) and again Standby/sleep mode with quick startup !
 
You must log in or register to reply here.
Back
Top