Welcome to our community

Be a part of something great, join today!

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

REDCINE-X Build 340...

I still can´t get the white balance color picker to work.
I thought that the Kelvin 1700 problem were solved but
I have seen this issue through the last many versions
of Redcine X.
Any hints around??

Best

Please enable verbose logging and send a RCX log file of a 1700 click to redcinex at red dot com. I have not been able to reproduce this issue.
 
All my renders ended before reach 100% with the error mesage "Finished with Error" "Error applying crop or scale:frame: xxx" I am not cropping the shots.

Any ideas?
Thanks

What build are you using? What crop settings are applied? Please enable verbose logging and send your log files to redcinex at red dot com.

Cheers,
David
 
Hey guys... any help with the extra frame bug when importing from an EDL? Also tried emailing and got no response.
 
Hey guys... any help with the extra frame bug when importing from an EDL? Also tried emailing and got no response.

I'm going to be looking into it. Didn't get a chance today. Just to rule out the obvious, are you importing using the correct FPS and Timecode settings?
 
Thanks for the bug report, I was able to reproduce and fix this.

Cool THX.
That's very good!

Any thoughts on these questions:

1. Histogram while monitoring SDI
2. Proxy update of computer preview, at least when NOT in motion, so that one can measure parts of the image?
3. DRX (yes I know, but still...) Actually a software cluster costing in the ballpark of a Mac with a Rocket can do the full debayer 1080 rendering with DRX at the same price...
4. Some way to assign a good folder-naming when exporting multiple clips for a vfx-shot?
5. Loading shots. I really need RCX to be pointed at a top-level folder with MANY magazines (think: a feature or a TV series) and also some quicktimes and other media and load ALL r3d's in the underlying directories for batch operations like re-creating QT-proxies etc...

As to the GUI, I would have loved to easily get rid of all the other stuff BUT the viewer the histogram and the controlls. The control strip (the far-right) should be detachable, and the curve tool should be stretchable, like in Clipfinder, to make it more easy to make precice small adjustments.

Now a lot of mostly un-needed controlls are cluttering up the workspace all the time. while the important ones are easily hidden. There's some kind of wrong priority going on here. Even when working on dual monitors.

I also need all presets that are saved to hang in there, even after crashes. Now they often get lost.
As I am often setting up workflows for others who don't neccesarily know how to make adjustments, this is a must.

RedlogFilm is fantastic. We've run a couple of things through online now, and it works great. BUT

It seems to be calibrated for 800+ ISO, which makes sense. I still see that some highlights are thrown away already at 800, and have setup 320, sometimes 250 + a curve in the bottom as the default developing setting for online. This works great, but I would have loved to see a better calibrated 320 version of that LUT.

I won't go into a discussion about wether the data in some way "actually" is there in the highlights at 800, I just see that we don't get them fully out without stepping back to 320/250. And that we've been testing this quite a lot lately.

On a chart, it looks good. With hair and skin it does not. Typically images like the Kodak Cineon girl in the hair and stuff with silly-low WB - like 3200... -:)

To make these good-for-grade, I need to lift the blacks/lowlights quite a bit with the curve. Maybe it would be an idea to look at the calibration of RLF @ 320?

Redline installation is not ideal either in large environments as you have to be localadmin and the RCX needs to be in the Application folder. Simply because you need to update it frequently as the development goes forewards, and one doesn't really want any DIT to be the super-user on larger network operations... Can this be simplified? It is a simple copy operation, isn't it. Maybe give a manual way to install it?

Ah... and we need redlogFilm in the SDK for Clipfinder and other applications...
It works with Redline, but not when adjusting the clips.

Just a couple of cents worth of feedback...
 
Just a very small thing:

Just discovered a folder in RCX's browser that seemed not to be there in Finder.

Turned out that having a space as the first character in the folders name (I do that to send it to the top of the list) has no effect in RCX.

Cheers,

Jochen
 
Hi Matthew

I have now send you a LOG at red.com Support site.
I got the 1700 K issue with a lot of clips in the timeline and not with one single.
It comes and goes random sometimes I have tried to colorcorrect without the picker at all
because after a few times use I got the 1700 K issue everytime.

Best

Steen
 
Hi Matthew

I have now send you a LOG at red.com Support site.
I got the 1700 K issue with a lot of clips in the timeline and not with one single.
It comes and goes random sometimes I have tried to colorcorrect without the picker at all
because after a few times use I got the 1700 K issue everytime.

Best

Steen

Fixed, thanks for the feedback!
 
Redline installation is not ideal either in large environments as you have to be localadmin and the RCX needs to be in the Application folder... Can this be simplified? It is a simple copy operation, isn't it. Maybe give a manual way to install it?
Just to clarify, RCX does not have to be in the Application folder to install REDline. You don't need to be localadmin, either (just install to a folder you have permissions to). Also, the installer does not do a copy, it creates a symbolic link to the REDline executable inside the REDCINE-X.app bundle.

To manually install REDline to a folder that's in your path, like /home/bin, enter the following from the command line (assuming REDCINE-X.app is in /path/to):

ln -s /path/to/REDCINE-X.app/Contents/MacOS/REDline /home/bin

Alternatively, you can add /path/to/REDCINE-X.app/Contents/MacOS to your path.
 
5. Loading shots. I really need RCX to be pointed at a top-level folder with MANY magazines (think: a feature or a TV series) and also some quicktimes and other media and load ALL r3d's in the underlying directories for batch operations like re-creating QT-proxies etc...

Try right-clicking on a folder or device in the browser and selecting "Open in New Bin Tab (include subfolders)". This will load all R3D's in that folder and its subfolders, up to ten levels deep.
 
Just to clarify, RCX does not have to be in the Application folder to install REDline. You don't need to be localadmin, either (just install to a folder you have permissions to). Also, the installer does not do a copy, it creates a symbolic link to the REDline executable inside the REDCINE-X.app bundle.

To manually install REDline to a folder that's in your path, like /home/bin, enter the following from the command line (assuming REDCINE-X.app is in /path/to):

ln -s /path/to/REDCINE-X.app/Contents/MacOS/REDline /home/bin

Alternatively, you can add /path/to/REDCINE-X.app/Contents/MacOS to your path.

Thanks. That's funny, because when we tried to install it with Redcine-X folder anywhere else but in directly in the app folder, it wouldn't install, and when any user but the localadmin tried to do it, it wouldn't install.

I am not the networking guy who sets up the accounts, but I know my user had admin rights and had a "local" account, still not possible, but with localadmin it worked.

On my private computer none of these things were issues.

Both 10.6.4 with Rocket installed....

Funny!
 
Try right-clicking on a folder or device in the browser and selecting "Open in New Bin Tab (include subfolders)". This will load all R3D's in that folder and its subfolders, up to ten levels deep.

Cool, will try immediately.
Will it also NOT make problems if there are other files than r3d's down that path?

Cheers

G
 
That's funny, because when we tried to install it with Redcine-X folder anywhere else but in directly in the app folder, it wouldn't install, and when any user but the localadmin tried to do it, it wouldn't install.
There was a bug with the installer where it would fail if the REDCINE-X.app bundle was in a path with spaces, or the path it was installing to had spaces in it (that's now fixed and will be in the next version after 340). That would explain having to put the app in the /Applications folder.

You'll need admin access if you're installing to a folder with admin permissions, like the default install folder /usr/sbin. A non-admin user should be able install to somewhere in their home folder, for example ~/bin.
 
ah... that explains it, I guess.

As I use it with Clipfinder, I need it to be in the /usr/sbin/ folder...

But I guess I can do it manually the way you explained.... ?

Thanks for the response.

Any thought son the other questions?

Currently we'll be using RC-X as a backup solution when we need to look at 10-bit images to make a decission, but will mainly stick to Clipfinder for offline work...

For online renders, I need to visit RCX because of the redlogFilm + curve options.

I have a pretty specific EXPORT FOR VFX naming scheme in place now where one could give the top directory a manual name and all the subsequent folders in a VFX sequence could be generated from a combination of FCP XML data, metadata-settings, ecport settings and the name of the top folder. I could mail it to you if that was ok...

Cheers and thanks!

G
 
As I use it with Clipfinder, I need it to be in the /usr/sbin/ folder...

But I guess I can do it manually the way you explained.... ?

You'll need admin permissions to install to /usr/sbin, so sudo is necessary:

sudo ln -s /path/to/REDCINE-X.app/Contents/MacOS/REDline /usr/sbin

Feel free to mail us your export naming scheme at redcinex at red dot com. We're currently looking into a more flexible naming scheme for exports.
 
Back
Top