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

The pre build 16 wish-list, please - only users post to this thread...

Gunleik Groven

Gunleik Groven

REDuser Sponsor
Joined
Dec 28, 2006
Messages
13,465
Reaction score
5
Points
38
Location
Norway
Website
quine.no
I'm a spoiled brat. I have a ONE :)

Still, after some extensive use over a couple of weeks I have a wish list (I told Jim...)

1. 1080 or 1:1 monitoring. Could be B&W un de-bayered, doesn't matter. I know Jarred said: Won't happen. I still want it...
2. Lower compression rates. Same as above. But I'll get an EPIC eventually...
3. ROCK SOLID info from the cam if a frame drops. I have had this only once, but still...
4. Exposure controlls before metadata implementation
5. RAW workflow opened.
6. IR filters and a recomended filter range for different light situations.
7. This is a strange one, but some way to controll individual channels. Don't know if it's even doable... Just an idea...
8. 16 GB FLASh, or getting the solid-state box out
9. Release builds that are free of known bugs when they're named release. I actually don't mind the bugs too much, but it is confusing customer base (not as in: RED customers, but as in: my customers....)
10. The base production pack should include top rods and I'd have prefered the Carbon rods, seeing that the price is the same....
11. RETHINK THE CABLE DESIGN! (sorry for screaming). The cables should lay as flat to the body as possible. Now they're all over the place, and I really fear that they'll break the cam, if something bumps into them.
12. The promised list of certified CF cards. I know the RED cards are very affordable, but I don't live in California, so I can't just drop by when the needs exceeds my projected needs. I haven't tried any non-RED cards, but if it is true that they're locked out in software, that contradicts an earlier statement (due to change at any time, I know...) and it would be good to know @ least... Even when I wouldn't agree on such a policy.
13 dove tail locking...
14. Audio on the preview playback...
15. Sleep mode...

For post:
1. RC bugs too much. Get it out of beta and let us render our RC projects in redline. RC is not very good for rendering. RedLine Rocks for that purpose.
2. individual channel controll in RC/RA
3. RAW workflow solutions. I really LOVE working with the DPXs, but I'm already a spoiled brat.... The power is in RAW, RAW is what we're recording. Find a way to cash in on that.
4. a button for a foolproof dpx naming scheeme, so that the exported DPXs would import into anything eating dpx. (OK, this slightly contradicts #3, but not really, as I have to deliver files to others than my humble self...)
5. Red Ray looks like (to me) a potentially very good post tool, too... :) But we'll need screens.

Just the ordinaire disclaimer:
This cam rocks. (In Jarred-lingo). I really enjoy it. But these are my main issues.

The surprises in 16 are obviously NOT covered here...

Keep it up. You're doing a fantastic job!
 
The one feature I would dearly love is a standby mode.

For nature docs the 1hr battery life, and long powerup time is killing me.

That's about it, everything else has been excellent.
 
Audio

Audio

1. Fix the audio problems. I still can't just plug a mic in (with adapter) and get anywhere near a decent signal. What is going on with that phantom power problem.

2. Now that the Log and Transfer is enabled in FCP which is the baddest of all bad ass. I need red alert to let me do secondary color correction or better channel correction so that i can import those looks and really speed things up and process it perfectly right out the raw gate.

3. Standby mode.
 
We're still having booting issues that started with the betas of build 15. About one time in four the camera freezes early in the boot cycle and needs to be reset. Would be nice to have a fix for that.

Other than that (and raw monitoring, and other stuff that has been discussed extensively), the big stuff is workflow-related. What we'd ideally like is a way to be able to cut proxies (or QT files generated from them) in FCP, and then grade only the used shots, in order they appear on the FCP timetime, in a RedCine-like environment, preferably with sound, after which grade settings and a list of shots to render could be passed off to RedLine for background and/or distributed processing.
 
In RedCine, secondary colour correction would make it the dream app for me (by secondaries I only mean each colour channel has the full six colour adjustment available to it, like Photoshop's "Selective Colour" function). I know, there's Scratch to protect, but with the Looks files coming down the pipeline there needs to be more control over it than a one light.

Cheers Red, I know you guys are flat out!

Paul
 
Build 16 :
Hope to have
a) Passwords protection to avoid the wrong person to steal to run it.
b) I hate to rotate the tiny knob to go from 24 to 120 FPS, it's Slow. Why not have 50 / 100 / 120 "fast jump" with the joystick function?
c) Battery Alarm with a beep sound when battery goes nearly empty.
e) Black & White mode on the LCD ( Easy Focusing )
f) Viewing angle adjustment on memu status display.

Thanks.

Stewart
d)
 
Windows build of Redline..... I have 50-8proc machines eager to chew up some
r3ds. into dpx...

Camera Wise: It would be nice if the camera could speed test unknown memory types, and tell you
so and so card, only good for x-fps.... could be handy for 2k ect, in a pinch.
 
gunleik said:
You sort of just described CrimsonWorkflow, without the rendering :), and this is why I want RC to send renders to RL..
Click to expand...

Yeah, CrimsonWorkflow is about 70% of the way there. The sound and the rendering are an issue, though.

The rendering issue is obvious, so, to expand a little more on the sound isue.... When you're working on a narrative project, it can be a bit hard to figure out exactly what's going on without sound at times. Knowing what's going on influences color grading decisions.

Also, the fact that RedCine doesn't pass sound through from R3D files into QT output files is a fairly big workflow hassle. If you've cut from proxies and you re-link only your video files to QT files exported from RedCine, you still have the sound that referenced the proxies, and things line up, but you have to keep all the R3D files online just to have sound! Using Compressor to pull sound from proxies out into separate AIFF files seems like it should be a solution to this issue, but the problem with that is that Compressor doesn't offer an option to pass the channels through to AIFF files while keeping them separate. QuickTime Player does, but doesn't have built-in batch processing.
 
Ahh... I see. I have deliberately stayed out of sound till now, just working on the image workflows. Sound is next and this was very good info to have.

One thing I really start to miss from FCP (if it isn't there and I only don't know) is the "render to separate folders" option in RC (although rendering in RC sucks even worse than FCP renders... And crashes quite a bit...)

If one had such a solution, or to render to separate files pr cut, could one use the cam proxies to cut with, export the audio (I know you can achieve separate files with tons of in- and outpoints, but that's besides the issue), crimson to RL and back. relink the FCP sequence and use the new audio files and send that off for CC?

Just a thought before I get my hands wet.

Gunleik
 
cf card test

cf card test

great idea, i've often thought about 2k and best buy possibly having to collide


Camera Wise: It would be nice if the camera could speed test unknown memory types, and tell you
so and so card, only good for x-fps.... could be handy for 2k ect, in a pinch.[/QUOTE]
 
Chris Kenny said:
Yeah, CrimsonWorkflow is about 70% of the way there. The sound and the rendering are an issue, though. (...)
Click to expand...

If you look through the Crimson Workflow tutorial, he has audio functioning througout...


Gunleik
 
Chris Kenny said:
If you've cut from proxies and you re-link only your video files to QT files exported from RedCine, you still have the sound that referenced the proxies, and things line up, but you have to keep all the R3D files online just to have sound!
Click to expand...
Why not just do a quick one-pass render of the audio only from your FCP timeline? Then you can bring that back in and ditch all the proxy audio. You can't really use Crimson until you have a picture lock, so at that point the audio (at least from the RED source) should pretty much be set as well. It won't help with audio during grading in REDCine, but at least you don't have to keep all those R3Ds around...
 
1a.) Definetely the 1:1 Monitoring!
1b.) And 1080 monitoring would be an addition (but not a replacement to 1:1).
...
16.) Custom resolution mode: Allow us to set whatever custom resolution we want within the given constraints. See here for some details: http://www.reduser.net/forum/showthread.php?t=10333
17.) Open up drive SATA port for custom designs, ie. we need a wiring description.
18.) Profiling of non-RED media on any of the connection ports.

Axel
 
You must log in or register to reply here.
Back
Top