Beta REDCINE-X (Build 221) & REDLINE (Build 194)

[Rob Lohman]

* Beta REDCINE-X, Build 221 for Mac OSX : http://red.cachefly.net/redcinex/REDCINE-X_build_221_mac.zip

* Beta REDLINE, Build 194 for Mac OSX : http://red.cachefly.net/redcinex/REDline_build_194_mac.zip

Windows build follows later this week.

Please see release notes and/or readme files for further details.

ALWAYS READ ALL INSTRUCTIONS CONTAINED IN THE DOWNLOADED INSTALLATION FILES BEFORE PROCEEDING.

WARNING: AS THESE ARE BETA BUILDS, THEY ARE RECOMMENDED FOR PREVIEW AND TESTING PURPOSES ONLY. THEY ARE NOT RECOMMENDED FOR USE ON COMMERCIAL PRODUCTIONS.

Change list:

New Features:
- Redesigned User Interface
- Frame Store added. Recall saved images with keys 1,2,3 Save images to the Frame Store with Option+1, Option+2, Option+3
- Enable crop for a clip and a resizable crop box will appear in the video window.
- Clip Settings Panel added
- Look Presets, Look, LGG, Curve, Framing Tool, and Framing Presets can now all be found in the clip settings panel.
- Snapshots can now use export presets
- Browser/Bin/Export have been combined and completely collapsable.
- Manual Audio Sync Tool has been added.
- BWF Audio syncing improvements
- Batch Export list has been reordered for better usability.
- Euphonix MC Color support added for Mac.
- RGB Curves added
- Ability to select a single channel R,G,B for viewing in histogram added.
- QuickTime reference file (re)generation with all image processing settings (requires new REDCODE QuickTime codec v4.1 BETA which can be downloaded here : http://reduser.net/forum/showthread.php?p=584169#post584169)

Bug Fixes:
- Avid Exports to case sensitive drives fixed
- Avid ALE now respects clip in/out points.
- Speed improvements.
- RMD saving improved.
- Project saving/loading improved.
- Exporting of large timelines has been fixed.
- Video playback lockup bugs fixed.
- Delayed/Jerky start on playback fixed.
- Tangent Wave panel jog now moves video player scrub bar.

Edit: added the new QuickTime reference file creation feature and link to the REDCODE QuickTime codec 4.1 beta release

[Sterling Wescott]

SWEET!
EDIT: The UI is incredible.

[Nathan Pena]

Awesome thanks! What do I need to do to get the new Redline working? No txt file with the download.

[Noah Richoz]

Thanks! Many welcome features that are going to make my life easier!

[Mikael Lubtchansky]

Thanks much for those !!

[Rob Lohman]

Awesome thanks! What do I need to do to get the new Redline working? No txt file with the download.

If you just want to test you can put it in any folder and navigate to there in your shell and run it from there. If you want to upgrade your REDLINE or make it available all the time from any shell window do this:

1) go to finder

2) go to the 'Go' menu and then select 'Go To Folder' and enter /usr/sbin

3) copy the file there (Finder will ask for your permission to do this)

redline is now available from your shell.

[brandon thomas]

If you just want to test you can put it in any folder and navigate to there in your shell and run it from there. If you want to upgrade your REDLINE or make it available all the time from any shell window do this:

1) go to finder

2) go to the 'Go' menu and then select 'Go To Folder' and enter /usr/sbin

3) copy the file there (Finder will ask for your permission to do this)

redline is now available from your shell.

nice, thanks!

[Nook Kim]

Awesome..

[Nathan Pena]

Great thanks!

[David Battistella]

I like that the r3d and the render are a close match. What codec did you render too. What happens if you render to a dvcpro HD codec?

David

[Nathan Pena]

Thank you!!!!! New Redline is fantastic! Finally back to speedy half debayers for us poor souls without a Redrocket.

[jimhare]

This is great! When will we get more information on the Magic Bullet plug in?

Thanks Rob,

Jim

[Justin Barham]

- Manual Audio Sync Tool has been added.


As an assistant editor, that alone makes my day. Also loving the UI changes.

[Rob Lohman]

jimhare: soon!

[Joseph Hutson]

This is great! When will we get more information on the Magic Bullet plug in?

Thanks Rob,

Jim

I heard today, somewhere.

[Lars Steenhoff]

Fantastic !!!! Thanks for making this available.

I hope this will become the best RAW/R3D converter on the market.

One thing to ask for is to separate the RGB curves into 4 different windows for faster access to the individual colors.

[Chris Parker]

this is awesome.

will the ale that is exported contain metadata from the BWF file (sound TC, soundroll, sound filename)??

GREAT work guys. this is the new beginning.

[Emyr R. E. Pugh]

The automatic audio sync tool is fantastic - works a treat with our external audio.

One little gripe, though... the adjustment sliders, Shadow, Flut, Kelvin and so forth can no longer be adjusted via the scroll wheel on the mouse as this is now scrolling the entire dialogue - is this intentional or just an oversight in this early build?

[Mikael Lubtchansky]

some REDLINE questions/comments... I imagine more patience is needed as this is just a first (great) beta...

- REDline doesn't have a --FLUT™ parameter yet ?
- the --noMatrix parameter seems to be broken here (no difference in my tests here)
- does the RSX option supports ROCKETCINE formated .RSX files (with new color science) or do we need to wait for REDLine to fully support .RMD files ?
- in REDLine help the ranges for ISO, Kelvin, gain and exposure do not match the ones in REDCINE-X.

I noticed the new REDfilm gamma space, any specific info on this ?

Access to RCX's presets, MX and ROCKET support are great and working fine, clobbering option will be very useful too !!!


----
If REDCINE-X had a "view RAW" button on the histogram panel it would be very useful to quickly compare graded/RAW histograms.

THANKS a LOT for those new tools !

[jimhare]

jimhare: soon!

Heh, Excellent, can't wait! :beer:

[Joe Taylor]

Having problems opening R3D files into a bin. Then the entire platform froze up and would not force quit. I rebooted and tried to download #221 again but still will not open any R3D files. Build 183 still works fine as a backup, however. Are my problems unique?

[Gustavo Penna]

It might sound really stupid.. but i'm a total CS (computer stupid)

But whats the difference between build 221 and 194. and i also saw at red-day that now you can do your rushes here? where r the instructions if they r any?

CS gus

[jimhare]

Build 221 is the first version of Red Cine X - The Next Generation! More features and refined user interface. So much nicer than 194, and when plug ins start happening, this is going to get really powerful, really fast!

[Mike Prevette]

The new Redcine-x is an AMAZING improovment. The UI is so much better, finally usable on a 15" MBP! Just so much cleaner.

My hat is off!

[Mike Prevette]

Bug report:


on a non rocket system (MBP 15") the debayer quality setting (at the top of the main window) doesn't display it's drop down properly after going into full screen mode and after.

[Kaku Ito]

First of all, I like the version 2 so much better.

I can't seem to find the make quick time menu.

[Paul Lee]

It's like Xmas morning...

[Yang Liu]

A stupid question: How to use REDLINE？

[Chris Kenny]

Coming along really nicely, guys. We've switched from Clipfinder to RCX as our primary on-light grading tool. But there are a couple of things that still drive me nuts. In no particular order:

1) It would be really, really nice to have a keyboard shortcut to jump the viewer to the next clip in the current bin.

2) Relinking. Right now, if you're doing anything that requires actually saving important data in the RCX project file, you're basically screwed if you have to move footage, as far as I can tell. This kind of makes most of the timeline related features of the app useless, because anything you do that can't be preserved entirely in the RMD file (like setting in/out points on the timeline or putting multiple instances of a clip on the timeline with different grades) will inevitably be lost when you move footage to another drive, etc. and the RCX project can't be relinked.

3) There are now visible boundaries between clips in the timeline, which is excellent. But they could be more visible. And it would also be really nice to have simple vertical lines in the scrubber in the viewer window showing clip boundaries there as well.

4) Undo, but I'm sure you're on that.

5) Basic system integration stuff. Having RCX launch and load projects when they're double-clicked, maybe open R3D files when double-clicked. Maybe even get really fancy and allow clips to be dragged into bins or onto the timeline directly from the Finder. Allowing multiple selection in the 'Open Clip' file selection dialog would also be nice.

6) An estimated time on the competition of the entire batch would be really, really nice. We get calls from impatient clients, you know?

7) A way to export/import RCX projects as XML. Would enable all kinds of useful workflow integration possibilities.

Anyway, keep up the good work. The pace of development you're maintaining its nuts.

[Jody Neckles]

* Beta REDCINE-X, Build 221 for Mac OSX :
- Manual Audio Sync Tool has been added.
- BWF Audio syncing improvements


Great stuff RED team!

Anyone know if there is a manual for this?

Also has anyone figured out the steps to manually link an audio file? I have a R3D that needs to link to a external audio file and the sound TC is way off.

[Hans von Sonntag]

The automatic audio sync tool is fantastic - works a treat with our external audio.



Yes! A great time safer. Thanks for that,

Hans

[Robert Horwell]

MC color and Redcine-X, it's working a dream. Massive time saver, thank you.

[TimWitte]

I really like the new UI, much cleaner now. I do have two things with the Viewer window.
First if I switch the viewer from normal to anamorphic and i use my scrollwheel (or two finger swipe on the trackpad to scroll) on the Clipsettings window
with the Viewer still as active window it switches between those modes when i scroll up or down (the scroll in the Clip Settings window works normal).
And second, if I have switched the viewer to fullscreen (CMD-F) and back, the viewer sits on top of everything, even the menu (see attached image).

[Martin Ubilluz]

I made a quick time wrapper through the new redcine and when I import it to final cut it reads my grade but when I send to color it reads the meta data not my grade is that right?

[Robert Horwell]

If you just want to test you can put it in any folder and navigate to there in your shell and run it from there. If you want to upgrade your REDLINE or make it available all the time from any shell window do this:

1) go to finder

2) go to the 'Go' menu and then select 'Go To Folder' and enter /usr/sbin

3) copy the file there (Finder will ask for your permission to do this)

redline is now available from your shell.

I'm lost with all this?

[Michael LAGERWEY]

Wow, good job guys,
Just in time for our last production...

[jimhare]

That makes perfect sense because in FCP you are looking at the wrapped QT, in Color it goes all the way back to the R3D so it would make sense the original MetaData is what would come through here.


I made a quick time wrapper through the new redcine and when I import it to final cut it reads my grade but when I send to color it reads the meta data not my grade is that right?

[Emyr R. E. Pugh]

That makes perfect sense because in FCP you are looking at the wrapped QT, in Color it goes all the way back to the R3D so it would make sense the original MetaData is what would come through here.

That's what's always happened, but it would be just great if Color could read the .RMD interpretation of the RAW data and you could then color that but still have the access to the RAW data. Clipfinder allows you to send a Red Alert .rsx (?) file with the RAW date to Color so that it loads up just some of your one-light corrections done in RED Alert - doesn't it? What would be ideal though is for all of your .RMD changes to be accessible all the qay down the line to Color - and it seems we're getting closer and closer to the day that will be a reality, though it does depend also on Apple pulling their weight and updating the RED control panel in Color itself.

[Mitch Martinez]

the new UI is awesome. thanks!

[CJ Roy]

So, love the new UI. But rendering w/ rocket is still twice as slow as RocketCine.

Any reasons for the speed decrease?

[Deanan]

So, love the new UI. But rendering w/ rocket is still twice as slow as RocketCine.

Any reasons for the speed decrease?

Looking into it. It seems to happen only on some machines with some formats.

[CJ Roy]

3.2 8core 14GB Ram.

Still on Leopard on this one. Could that be hindering it?

[Deanan]

3.2 8core 14GB Ram.

Still on Leopard on this one. Could that be hindering it?

Not sure yet. Can you email the logs to redcinex at red . com?
Maybe a also a brief description of format source, dest, burn in, codec, etc.

[CJ Roy]

Sent

[Jesse Korosi]

What are the chances in future builds of RedcineX having Sound Meta Data (.Wav Filename, Roll and Sound TC) being put into the ALE generated when exporting MXF/AAF files from RedcineX after syncing?

Cheers,

[Luca Immesi]

Could we have a shortcut to generate proxies? Like a voice "make quicktime proxies" in the menu? Going to the export etc. it takes time.
Thanks.

[Kaku Ito]

Could we have a shortcut to generate proxies? Like a voice "make quicktime proxies" in the menu? Going to the export etc. it takes time.
Thanks.

That's where it was.

[Luca Immesi]

That's where it was.
But now there isn't...

[Luis Otero]

Now all my projects, created with current version, or with past RCX versions, does not show the timeline time-ruler.

Also, to move the position line, I need to drag it from its current location to the new desired location. So, clicking in "where-the-ruler-used-to-be" in other place do not make the line to move, as it used to (well, also I can move it pressing the FWD or REV buttons from the Tangent Wave).

Note: is there an estimated timeline to get the modules capability, like Magic Bullet and others?

[Nick Shaw]

I have tried making an export preset to make QuickTime wrappers, and chosen "Output with clip filename to clip folder". However when I try to use it, I get asked for a destination folder. So I can't get it to re-make proxies a whole bin of clips in one go. Has anybody else got this to work?

[Khan Bui]

Deanan, do we have window version of this new redcine-x v2 yet?

[Hrvoje Simic]

Some thoughts about the new UI solution.


The good thing is that it’s more clear and organized.


The thing is that this solution has a price of negative influence on other factors.
Please don’t take this the wrong way, I’ll try to explain. First the negative factors then the suggestion for the solution without the issues.


There are many times when you want to get the perspective of the all the settings, which one influences what, think about what is happening with the picture, re-check the settings, go back and fine tune, compare...etc etc...

With new UI logic this is more restricted. Much more clicks will be needed to do the same job because of:


redundant opening and closing windows
unnecessary effect on user’s visual memory of all the settings
complication when applying looks and comparing them



Essentially, with this you are stacking a large bunch of creative controls into a small space whereas you want to have the largest controllable space (and perception) you can, especially considering that you're dealing with users who in general have enough screen estate.
For watching and changing one parameter you have to close the other one - not good.

The advantage hardware controller gives to grading is multiple controls available at the same time.
With this new UI solution you cannot even see multiple controls at the same time.

If you guys really really like this version please allow fully independent UI setups for individual customization.



This scheme could be very useful for a laptop use, for example, but on a large screen estate doesn’t use the full potential of the software.

New vertical placement of RGB wheels is more confusing, lift and gain are upside down, more space is used for them (wasted space on the sides) and they are generally too small, IMO, same as sliders under them. All the sliders are too short (as with previous versions).

The huge advantage of 12 bit space and great fine tuning abilities is extremely limited with tiny adjustment space on the screen.

It is great that you guys are constantly developing and trying different things, and the speed of development is amazing.
I suggest not to stop here.




Solution suggestions


Designing picture settings in proportions which allow better combinations on the screen. Also individual settings scaling. What could also help is if user could arrange settings windows and in "preferences" - or by a small check box on the main bar - turn on “glue window groups” and/or “lock all windows position”, so that with further work one can’t accidentally move a window.

That way all the tools on the “table” user has arranged become fixed and one can concentrate fully on work. User could also move the whole group in the other side of the screen without fiddling with the redundant stuff and each individual window.

The simplest solution for more precise lift-gamma-gain control would be adding a stripe for precise tuning above each slider. Moving across it would move the main slider in smaller increments (affecting numerical value also, of course).
For the rest of the sliders, the simplest general feature implementation, which would release more of Redcine’s potential is in enabling larger control paths - more detailed movements - more precise visual feedback (or just fully independent scaling) - goes for curves also.

Combining browser/bin/export and ablity to slide the mutual bar is very good.
I suggest adding a horizontal switch option if it’s not a problem.


On 100+ shot projects any miniscule redundant action is multiplied and in the end greatly slows down the whole process. GUI optimization shouldn’t be to hard to iron out (guesswork) and can give a great benefit.

[Adam Clark]

any idea when sound might be available for the pc like it was in redcine?

[Carl Dieker]

Hi,

Great update. But I think I am having a bug here. RCX exports 4K 16:9 to ProRes HQ 2K 16:9 without a problem. But when I am trying to export 2K 16:9 100p/25p slowmo-files to 2K 16:9 ProResHQ I get nothing but split screen frames with noise in the upper 2/3 and black below.

I tried trashing all of my QT- and RCX-preferences plus deleted the red-folder in App Supp but to no help.

Otherwise the QT-wrappers/proxies/refencefiles open up without a problem in FCP and they display the right colors, which is awesome.

Deanan, should I email you Verbose files or is it enough with the RCX log-files?

Best of luck,

Calle

[Deanan]

Hi,

Great update. But I think I am having a bug here. RCX exports 4K 16:9 to ProRes HQ 2K 16:9 without a problem. But when I am trying to export 2K 16:9 100p/25p slowmo-files to 2K 16:9 ProResHQ I get nothing but split screen frames with noise in the upper 2/3 and black below.

I tried trashing all of my QT- and RCX-preferences plus deleted the red-folder in App Supp but to no help.

Otherwise the QT-wrappers/proxies/refencefiles open up without a problem in FCP and they display the right colors, which is awesome.

Deanan, should I email you Verbose files or is it enough with the RCX log-files?

Best of luck,

Calle

Verbose please.
Send them to redcinex at red . com

Can you also email a screengrab of what the bad frame looks like?

[Daniel Crooks]

... I get nothing but split screen frames with noise in the upper 2/3 and black below.


I've just experienced the same thing. Exporting 2K 16:9 (2048*1152) unscaled to ProRes 4444 I get the upper 3/4 noise and lower 1/4 black. But exporting to 1920x1080 works a treat.

[Emmanuel Cambier]

Bug report:


on a non rocket system (MBP 15") the debayer quality setting (at the top of the main window) doesn't display it's drop down properly after going into full screen mode and after.

Same thing here, the drop down menu won't work after the first change.

[Michael Lindsay]

Sorry if this is already been covered:

Will this latest Redline update allow tools like Monkey extractor to render using a recently created RSX (one with a Flut tweak)..

thanks

Michael L

PS Are we any closer to Redline empowered tools driving the Rocket?

[Deanan]

I've just experienced the same thing. Exporting 2K 16:9 (2048*1152) unscaled to ProRes 4444 I get the upper 3/4 noise and lower 1/4 black. But exporting to 1920x1080 works a treat.

Can you email the logs to redcinex at red.com?

[Deanan]

PS Are we any closer to Redline empowered tools driving the Rocket?

The new one does support rocket.

[Michael Lindsay]

The new one does support rocket.

fantastic!

Michael L

[Deanan]

am i supposed to do something with the new redline i just downloaded. i dont think i ever downloaded redline in the past i just downloaded rocketcine or redrushes etc and just opened them up and used them. does the new redcineX v2 need me to do some other kind of install with that redline zip for it to work properly?

This version was a preview release. The release version will have an installer.

[Jeff Kilgroe]

Finally getting back to playing here. Took REDCINE-X 221 for it's maiden flight. It seemed to be working great. Then it locked up (no beachball mouse cursor) and wouldn't respond after I attempted to copy a look to all the clips in the bin for the second time. I had to force quit.

No log files were written that I can find. But I'll keep playing with it.

[Drew Ingram]

Any update on the Windows release?

[Deanan]

Any update on the Windows release?

Sometime next week. We've got some good feedback on 221 and need to work on a few things before we do another release.

[Drew Ingram]

Sometime next week. We've got some good feedback on 221 and need to work on a few things before we do another release.

Thanks, Deanan. We're a bit excited over here, just took possession of our first RED One.

[Jeremy_Sawatzky]

ok ive been playing with the new redcine x on my new i7 system :) but im trying to export a small 10 second clip. i set up all my settings in the export block and click export. it says running but nothing is happening. my cpu sits at 0% load. i try to pause it, stop it, anything and it crashes. Im exporting to 4k quicktime files. This is my first time using this program. sorry if im just being stupid lol.

[Jeremy_Sawatzky]

k good news i just tryed some other settings and it rendering. but another question. its only using about 30% of my cpu and 2.5gb of 6gb of ram. Is this normal? i would expect it to be using around 85% and 4.5gb.

[Jeremy_Sawatzky]

uh oh i just experienced the same problem as the other guys. Fuzz with a large black bar at the bottom. time to try for 1080p

[nigelsmith]

Same thing here, the drop down menu won't work after the first change.
I had the same problem after going fullscreen - the thing is it DOES work, but you have to guess where the setting you want is and click on it. The drop down menu is invisible but still active!
This bug was also in v194.
But still a massive improvement and a nice piece of software.
Well done Red guys :thumbsup:

[Brandon Kraemer]

Can anyone comment on where things stand with XML or EDL support, for creating cut-downs of full .R3D files prior to transcoding... or loading "telecine" XML lists generated by Crimson. I recall Red was going to add support for this a month or so ago, but leaving it up to 3rd party developers? Can any one inform further?

[jamie parry]

http://www.youtube.com/watch?v=EBVvM1ThGoU

(just me and my iMac after the kids had gone to bed!)
it's available fer nuthin
it is ugly and terminal/cmd centric but it seems to work for me.

it's all done at 25 fps but i can change all the 25's to 24 for you cross atlantic folk!
all the source scripts will be available so if you make it better post it back yeah?
have fun

there are other (mac only) solutions
http://www.reduser.net/forum/showthread.php?t=42478
and
clipfinder

I think there's another one as well somewhere...

mine you can mess with.
j

[Brandon Kraemer]

http://www.youtube.com/watch?v=EBVvM1ThGoU

(just me and my iMac after the kids had gone to bed!)
it's available fer nuthin
it is ugly and terminal/cmd centric but it seems to work for me.

it's all done at 25 fps but i can change all the 25's to 24 for you cross atlantic folk!
all the source scripts will be available so if you make it better post it back yeah?
have fun

there are other (mac only) solutions
http://www.reduser.net/forum/showthread.php?t=42478
and
clipfinder

I think there's another one as well somewhere...

mine you can mess with.
j

Thanks for the links... did you post the source scripts someplace? Have you tried this with FCP by chance? The source scripts are preset to work in 25 fps, yes? How easy is that to change, on a per project basis?

[jamie parry]

the stuff is all open there
they are .command files which are basically a double clickable script
if you drag it onto textedit it will open up
just copy it and change the 25 to 24 then use that when you need to! Easy peasy.

the windows one is just a .bat file and the xsl it uses is just a text file. all doable by someone who knows what they are doing (or me.)

one thing of note you HAVE to use redcine-x and relink to the ale it makes to get your rushes done or the xml won't have the required information in it.
and if you're on the beta of MC version 5 and messing about you need to change TapeID to TapeName in the script as that has changed in filmscribe (thanks avid!)

I've not done anything with FCP. Clipfinder works for that no?
this stuff is just or avid.
cheers
j

[Chris_Stacy]

Thanks for the info. Do you know anything about the Redcine X for windows? Your post said later this week. Is it out and if so where I can down load it? thanks.

[Johnny Friday]

PROBLEM - Viewer does not play the full clip length. (build 221)

playback with redrocket card and output to external monitor via HD-SDI thru AJA converter and input via HDMI dreamcolor monitor:

ISSUE: when loading clips and playing them back, they do not play all the way till the end. The play head will show that it is at the end of the clip in the viewer, but the clip has not played to the end. If i then drag the playhead slightly to the left, i'll see part of the shot that is way ahead of where the clip stopped. So, playhead basically is not showing current location or viewer does not play the full clip.

[Chris Vincze]

An updated version of RedLine is what I've been waiting for!

I can't seem to get it to write QT wrappers -- using -w 10 seems to start to render full res quickTimes & doesn't do the wrappers. Is this a bug, or is the documentation wrong?

Thanks

Chris

[Nick Shaw]

It would appear to be a bug. -w 10 worked fine in the last REDline, but doesn't in the new one. Have you reported this to Red?

[Chris Vincze]

No -- anyone know the right channel to report bugs?

[Nick Shaw]

No -- anyone know the right channel to report bugs?

I emailed Deanan. They are already aware of it.

[Alex MacLean]

this is awesome! thank you so much!

[Johnny Friday]

Deanan:
How can we color correct if we are using the Rocket card and monitor out of the rocket? If i choose the monitor setup for the Rocket, i of course get signal out of the rocket card and picture. Then if i want to do a pick white balance (that's the only thing i can think of) i then have to deselect the monitor and do a pick white balance from the viewer on my other monitor. Then choose the rocket out monitor to go back to viewing on my rocket monitor out.

Is this much of a concern or has it been brought up? I'm constantly doing pick white balances so would seem that it would be necessary to play simotaneously on both the rocket monitor out as well as within the viewer of the redcine-x software......unless i am missing something??

At the very least, wanted to bring this to your attention unless it has already been mentioned.

[Nick Shaw]

Deanan:
How can we color correct if we are using the Rocket card and monitor out of the rocket? If i choose the monitor setup for the Rocket, i of course get signal out of the rocket card and picture. Then if i want to do a pick white balance (that's the only thing i can think of) i then have to deselect the monitor and do a pick white balance from the viewer on my other monitor. Then choose the rocket out monitor to go back to viewing on my rocket monitor out.

I suspect it may be quite difficult, if not impossible, to run the Rocket SDI output and computer monitor entirely in parallel. However what about the possibility of using a software decode to drive the computer monitor in pause mode, for colour picking and driving the histogram while adjusting parameters?

[Deanan]

I suspect it may be quite difficult, if not impossible, to run the Rocket SDI output and computer monitor entirely in parallel. However what about the possibility of using a software decode to drive the computer monitor in pause mode, for colour picking and driving the histogram while adjusting parameters?

It's not possible due to some restrictions in the architecture but it's something we are working towards.

[Rainer Fritz]

an active histogram on hd-sdi output would be great...

Deanan, wanted to ask you for a pointer in the histogram as in the old redalert that we can set the black point same in every shot more in detail....

as in the past, thx for your work deanan... redcine-x is a badass app....

[Johnny Friday]

an active histogram on hd-sdi output would be great...

Deanan, wanted to ask you for a pointer in the histogram as in the old redalert that we can set the black point same in every shot more in detail....

as in the past, thx for your work deanan... redcine-x is a badass app....

....that brings up a point. Yes, i could not find the histogram anywhere on my monitor when i was driving through the redrocket card to my cc monitor. I have not tried to find it with rocket monitoring off. Are we somehow locked out of using the histogram if driving through the rocket monitoring?

[gbalaji]

Did Build 221 have export option or not and if yes under which tab ?

[severin schultze]

Hi all,

is it possible to get more then 3 bins in RCX? It would be great for on set work for a feature with lots of location changes to separate each scene in one bin to do first lights and transcodings.

Thanks

- severin

[Johnny Friday]

Did Build 221 have export option or not and if yes under which tab ?

Yes, exporting in on the far right tab or workspace along the left side of it towards the bottom. in fact if i recall there are: BIN, EXPORT and another tab all with arrows pointing horizontal. click on the arrow and it will open. the tab to the right

[Gino Varisano]

any word on that windows release? been looking for it all week... keep up the great work!

[Petri Teittinen]

any word on that windows release?
Seconded. Builds 183 and 194 no longer work properly on my Win7 64-bit (equipped with Red Rocket). Loading a clip in the player and clicking anywhere on the clip timeline puts RC-X in "Not responding" mode. I wish RED would publish a list of requirements, such as what services RC-X relies on, do I need .NET or Java etc.

[Jay A. Kelley]

Agreed, also waiting for windows release

Jay

[Deanan]

Agreed, also waiting for windows release

Jay

We're working on getting audio and other features/bugs.

[Petri Teittinen]

Deanan, any chance of an option to output 24bit TIFFs instead of 48bit ones in a future Windows version of RC-X?

[Deanan]

Deanan, any chance of an option to output 24bit TIFFs instead of 48bit ones in a future Windows version of RC-X?

It's on the todo list.

[Michael Epple]

I noticed a bug when I went to full screen playback. The debayer scaling (1/2, 1/4) as well as the fit scaling (100%, fit both, etc) drop-down menus become invisible.

[guanyi]

thanks! when get the Windows build.

[Johnny Friday]

Deanan:
Are we close to a new build? one that has new/improved QT Components (built in)? I've been getting poor results from QT transcodes when it comes to color saturation etc...

Thanks for the overtime!

[PHactor]

Deanan:
Noticed a bug when applying a look to clips in bin or timeline just increasing sharpness only, say to "3", the look defaults to "0" sharpness upon application. "Copy grade" works in "paste" mode in timeline, but not in "look preset". Repeated attempts to save "sharpness" setting in individual look presets, then applying to bin or timeline resulted in sharpness resetting to "0".
Mac Book Pro 2.6Ghz 4GB, Redcine-X 221, QT beta

Thanks for all your HARD WORK!
Paul Hickey
RED#901

[nigelsmith]

I found another bug, that means I have to force quit the program. when you click on debayer settings in the export pane, often the window that opens is invisible. And because you can't see it to select a setting, you can't cancel out of the export settings window. :(

[Rainer Fritz]

Sometimes it seems that the histogram is not uptodate... when i changing a setting eg. curve it shows actual values... often after playback...

[roryhinds]

Does this new REDCine X (221) cancel out RocketCine?
So they are one in the same now? Or are we waiting on RocketCine to be released?

[Deanan]

Does this new REDCine X (221) cancel out RocketCine?
So they are one in the same now? Or are we waiting on RocketCine to be released?

No new Rocketcine is planned.

[roryhinds]

so is REDCineX now RocketCineX?
So you would just use REDCineX with your RR card and not the old RocketCineX?

[Deanan]

so is REDCineX now RocketCineX?
So you would just use REDCineX with your RR card and not the old RocketCineX?

Correct. Although no one is stopping you from using rocketcine.

[roryhinds]

what are the differences between the two, with regard to Rocket performance?

[Deanan]

what are the differences between the two, with regard to Rocket performance?

REDcinex is faster in some cases but about the same in others.
We're doing some speed testing this week to see where things are.

REDcineX also has alot more bug fixes in it and alot more flexibility/features.

[Michael Epple]

I found another bug that creates a mirror drive that shows up in the browser if you accidentally hit export with a preset that has an output path to a drive that is not currently mounted. The drive that is preset in the export sequence pops up in the browser and I can not get rid of it. If I connect that drive and open up rcx the drive has a -1 after the name because there already is the ghost mirror drive always mounted in the rcx browser.

[Deanan]

I found another bug that creates a mirror drive that shows up in the browser if you accidentally hit export with a preset that has an output path to a drive that is not currently mounted. The drive that is preset in the export sequence pops up in the browser and I can not get rid of it. If I connect that drive and open up rcx the drive has a -1 after the name because there already is the ghost mirror drive always mounted in the rcx browser.

That's not really a bug. OSX mounts the volume under a normal unix path and the export preset is using a normal unix path. There's no concept of a mounted drive with unix paths so when you go to export and the drive is not there, the path is still relevant and the directories get populated as needed.

[Michael Epple]

Yes, but that drive shows up now in the browser window regardless if it is actually connected or not. You're saying that's not a bug?

[Conrad Hunziker]

It shows up in the browser because its in the path. With the drive disconnected, in finder, select Go > Go to folder, then enter "/Volumes/" without quotes. Move the folder with your drive name to somewhere else. Now the browser window will be as you expect it, and the drives wont mount with "-1" appended.

[Deanan]

Yes, but that drive shows up now in the browser window regardless if it is actually connected or not. You're saying that's not a bug?

Correct. You can mount drives anywhere but OSX mounts them under /Volumes by default. You can make your own folders there also since it's a regular path.

One option is to detect if the folder is actually the same as a mounted volume or not but we make assumptions that may not work for other people (such as some facilities that link to san volumes manually under /Volumes).

[Chris Bouchard]

Build 221 crashes frequently during renders on Snow Leopard 10.6.3
It's pretty stable on Leopard 10.5.8

[nigelsmith]

Build 221 crashes frequently during renders on Snow Leopard 10.6.3
It's pretty stable on Leopard 10.5.8
It's not crashing here on 10.6.2
HTH

[sbilodeau]

Build 221 crashes frequently during renders on Snow Leopard 10.6.3
It's pretty stable on Leopard 10.5.8

I've had the same issue, but under both Leopard and Snow Leopard. I'm able to process between 40-60GB of R3D footage before the application quits and needs to be restarted. This happens if I submit it all at once, or in multiple batches over the course of a day.

I've also noticed that the REDCINE-X 221 processes our slow-motion 2K clips in two or three times the time it takes to render a 4.5K clip of the same final duration. Am I the only one noticing this?

I don't know if this is a bug or by design, but a burn in always has two lines, even if both fields in one line are selected as "None".

A couple of features that I would wish for:
- A separate grading viewer than the timeline, i.e. the ability to open and grade a file from the bin, rather than needing to pull it into the timeline first
- Custom field for Burn-Ins
- Ability to simultaneously burn in at the top and bottom of the clip
- A magazine rename tool that would fix a formatting error by renumber in the Roll number in the file structure and each clip's metadata, then regenerate the QT Reference files in each folder. Currently I can do this manually or using NameMangler and Clipfinder (or REDRushes), but I can't rename the roll on the metadata, though this is less important to my since our workflow relies wholly on the file names themselves.
- Copy a look directly from one clip to another without having to save a look preset

Other than that the program is working fine here and really accelerating our on-set workflow. Great job RED team and keep it coming!

[Luis Otero]

Deanan,

Is there any plan to move this to 64-bit structure? I think that being able to use more than 4 GB of RAM will help us a lot. I have 16 GB installed, and it is a shame it is not using more...

Also, is it CPU centric, or is it taking advantage of the GPU. I recently installed GTX 285 (Mac) with CUDA activated to take advantage of the PP CS5 Mercury Engine (I love it!!!) and I think it will be great if such power is unleashed...

Regards,

[John Marchant]

- A separate grading viewer than the timeline, i.e. the ability to open and grade a file from the bin, rather than needing to pull it into the timeline first


Unless I've misunderstood you, this has been possible for some time. Just drag a clip from the bin to the viewer, grade away, happy days :)

This build has been pretty stable for me, except when saving TIFF stills- it seems to crash about every fourth or fifth image. Saves the file OK, but the app freezes.

[Drew Ingram]

Any update on the windows release?

[Dave Beard]

Can anyone help me understand exactly what RedLine is, and what it does for me. Also, I'm wondering if this along with the new Recode QT codec is going to help along programs such as Clipfinder and Red Rushes to have the new RedColor and RedGamma

[Nick Vernon]

Is there any Monkey Extract like GUI that supports the new REDline?

[Yusuf Thakur]

where is the windows build 221, I have been waiting and waiting and.........
Yusuf Thakur
VFX,Dubai

[Deanan]

where is the windows build 221, I have been waiting and waiting and.........
Yusuf Thakur
VFX,Dubai

Almost ready. Doing QC on it now.

[AlvisZ]

Since FCP->Crimson->Redcine->Whatever is discontinued, is there any chance to see XML import option in REDCINE-X one day?

[Casey Green]

Hi Deanan,

Nice seeing you at RED Studios last week. And as always, let me know if you find a way to work in the Zoom / Scroll Timeline navigation.

You guys are brilliant, I'm sure you'll find away!

Rock on,

~ Casey

[Chris Vincze]

Is there any Monkey Extract like GUI that supports the new REDline?

I think this depends on how the new redline is coming along. Any news on this? New Build 30 Monkey would be fantastic.

[Brandon Kraemer]

I think this depends on how the new redline is coming along. Any news on this? New Build 30 Monkey would be fantastic.

Monkey has been working on these builds for a couple weeks now (see their thread in workflow). Things hopefully should catch up soon.

[Dave Beard]

A new clipfinder would be great as well. Unfortunately Hans said there is some problems with the new redline.

[Chris Vincze]

Yes, there's a few bugs with the new RedLine (I found one with the wrapper creation). A working build 30 would help loads, not just with a new Monkey but lots of other processes. I'm surprised getting a working redline out hasn't been more of a priority (or that more people haven't been nagging!) I know that RED are extremely busy, but this would really help.

[Uli Plank]

Hans-Georg seems to be working on a script to get from Clipfinder to RCX, and since he can read XMLs…

[Conrad Hunziker]

Is there any Monkey Extract like GUI that supports the new REDline?

The new version (v6.1) of R3D Data Manager supports the beta REDline. You'll need to install it in /usr/sbin/

http://www.reduser.net/forum/showthread.php?t=45249

[Petri Teittinen]

Deanan, this is somewhat offtopic, but do you think it could be possible to have a list of software requirements/dependencies for RCX on Windows?

I'm no programmer, but I'm certain RCX hooks on to some Windows resources/services/APIs/whathaveyous or it wouldn't work at all.

For example, does the Windows need to have .NET or Java installed, and if yes, which version does RED recommend? How about display drivers, which version do you remommend for Nvidia/ATI? (I remember some version of RCX crashing constantly on my Win7 64-bit until I updated drivers for my Nvidia GTX 260.) Are there some specific services RCX needs to run? What about DirectX?

With such a list available users could do a small part of debugging themselves if they're having problems with RCX. For example, checking whether they're using the recommended display drivers etc.

[Drew Ingram]

Any windows update?

[Deanan]

Any windows update?

We were close to a release but had to clear up a few bugs.
I'm hoping we can get a build out very soon.

[nigelsmith]

A couple of features that I would wish for:
- A separate grading viewer than the timeline, i.e. the ability to open and grade a file from the bin, rather than needing to pull it into the timeline first

You can already do that - just drag the clip to the player window.



- Copy a look directly from one clip to another without having to save a look preset


You can already do that too - use copy [command + "c"] and paste [command = "v"]

HTH.

[nigelsmith]

The v221 timeline bug, where zooming the view causes it to vanish, even on project versions saved earlier, is proving a real killer for me. I've been using Jamie Parry's XMLua tool to get picture locked sequences from Avid into Redcine-x for conforms, but one false move on the timeline zoom , and the whole project is ruined.
Ok so I know not to touch it, but students...... :(

[danibam]

no windows update yet, right? ... I keep looking here on this thread but I am not really sure if it will be posted here or not

Daniel Perez

[roryhinds]

can we please have a dedicated place where we can get the latest version of RED software. Just getting a pain to search the forum hunting for the latest updates

thanks

[Jeff Kilgroe]

can we please have a dedicated place where we can get the latest version of RED software. Just getting a pain to search the forum hunting for the latest updates

RED.COM/SUPPORT ???

It's all there, except for the Redcine-X 221, which is linked to in the first post of the announcement thread, this thread as well as duplicated in Crucial Ordnance. No searching really required.

[Petri Teittinen]

May I suggest an RCX updates thread where only Deanan and other members of the RED team can post in? Users can then enable automatic email notifying by subscribing to the thread. The board software should email a notice to all subscribed members whenever there's a new post in that thread. It's working fine on a couple of other forums I frequent.

[Milan Spasic]

Hello RED team,

Loving the new Redcine-X 221. Bugs were not massive or at least not big enough to spoil the enjoyment ......until today!
Both build 221 and 194 are crashing inexplicably every time I try to render to ProRes.

The app is very stable on my MacBook Pro, but on a MacPro with the Redrocket it's refusing to spit out the clips regardless of what I tried (re-installed QT component, repair permissions etc...)
I tried both RCX builds as well as ProRess422 and ProRes4444 and the result is the same, it briefly lists the clips in the batch monitor and then crashes.

HELP! :(

[Luis Otero]

I had crashing problems with ProRes 222 & 4 X 4, until I rendered 1080p. The 2K or 4K is a no-go over here...

[danibam]

Windows ??? .... did that ever happen ??