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 PRO X 15 release / 16 Beta

Thanks guys for the patience. It appears to be an initialization issue we didn't run across in testing. We'll get it fixed.

Thanks!
David
 
Mike,

I figured out the issue you're running up against. Turns out the sensitivity on those three controls was way too low. We have it fixed in house. If you need a fix ASAP, shoot me an email at redcinex at red and I'll get you sorted out.

Thanks Grant. I'm happy to wait until the next release, unless you want someone to test it for you, but I figure you guys got it covered there.
 
So you have 1 secondary monitor on your system in addition to the primary screen on which you run RCX correct? So when you go to second monitor it should be popping out onto that screen. Can you confirm?

Thanks,
David

Having the same issue, v14 worked fine, v15 not, simply does not show a "2" in the preferences, uninstalling and going back to v14.
 
Having the same issue, v14 worked fine, v15 not, simply does not show a "2" in the preferences, uninstalling and going back to v14.

Shaun,

There's a fairly simple workaround for this issue. Open up preferences, then click 'OK'. The second monitor will work then.

The dropdown shows the number of additional monitors other than the primary, not the total number of monitors connected to the system.
 
Last edited:
Mike,

It's definitely not intended to fail like that. If you could, please enable verbose logging, and recreate the crash and send the logs in to redcinex at red dot com and we'll get the issue sorted out. Also remember to disable verbose logging again once you're done.

Thanks

Check your mail.

Post sending the email I had a thought: autosave? What does RCX do if attempting to autosave something to a volume mounted read only? Something less than graceful?

Mike
 
Shaun,

There's a fairly simple workaround for this issue. Open up preferences, then click 'OK'. The second monitor will work then.

The dropdown shows the number of additional monitors other than the primary, not the total number of monitors connected to the system.

Hi Grant, I did try that initially too, it still didn't work for some reason. I just reinstalled v15 again and without needing to do anything it's working now. Many thanks.
 
I found a bug that I've been able to reproduce multiple times. If I have a folder structure of R3D's, such as multiple days compiled together in folders Day_1, Day_2, and so on and select one of those folders in the Browser tree with Scan Depth higher than 1 (I usually use 3), RCXP will include one or more clips from the other folders in the Project section. For example, I click on Day_1, but I'll see a clip from Day_8. I have a collection of R3D's from various sources organized in folders, and it will even include random clips from folders higher up in the tree.

I noticed this a few times with Build 14, but it's happening even more with Build 16. I fix it by clicking onto a different folder and then back onto the folder I want so it refreshes the scan.

EDIT: I should probably give info about my system. 2 different Retina MBP's, one running both Lion and Mountain Lion and the other running only Mountain Lion. R3D's are on an external OWC Qx2 RAID connected via eSATA using a LaCie TB eSATA hub.
 
Two tiny changes I'd really love to see:

1.) Clicking the slider for a setting should "bring focus" to it, allowing arrow key adjustment. Currently this only happens if you click the numerical value.

2.) Clicking the slider OR numerical value for a setting should highlight its numerical value, allowing it to be replaced with the number pad. Currently you have to TRIPLE click the numerical value to do this (double click only gives you the digits before or after a decimal).

Related bug: Neither number pad nor arrow key entry work for ISO.
 
v15 can't output MXF files correctly as it can't output all the selected files and only outputs a random amount. It also puts them into separate folders which is a nightmare workflow wise.

v14 is also very buggy at output all the clips in the bin to MXF and I have to go through manually selecting the clips it forgot to output. I thought this issue was because I was using RedLine (which is freaking great) but its not.

Stuck in transcoding hell at the moment with something that should be automatic taking up a lot of my time behind the machine trying to babysit it.
 
FYI
I had a problem in v16 beta: the drop down menus for normal/anamorphic | resolution | Fit (size) and 2D/3D were greyed out so I could not change any of these options. I went to v15 to render out the file I am working with. v15 seemed more responsive all round and those options were available..
thanks for the updates!

peter
 
I love the dynamic subfolder feature for exports, but it's not working for me at all. I have tried a few different metadata options, as well as variations on a simple name:
clips
/clips
clips/
/clips/
/clips/|date|
/exports/|reel ID|
No matter what I choose here, the exported clips all go to the base output folder. No subfolders are created. Anyone else notice this?
 
BurnIns

BurnIns

The majority of the metdata still does not work in the burn in, its available in the drop down, but does not display on output - pretty much anything which does not display an example below the drop down - Lens, focal distance, aperture, etc.
 
Christopher: The metadata you mention, Lens, Focal Distance, and Aperture require the lens to be able to communicate that data to the camera. Not all lenses are able to do this. If the field is blank when viewing the metadata on the clip itself, the burnin will also be blank for that field.
 
I was exporting some Tiff snapshots from RCX Pro 15 this morning. After several good ones, I had a situation where the stills weren't showing up in the folder I had selected in Preferences. Thinking that RCX was sending them someplace else, I did a search and found that they hadn't been saved anywhere. When I tried to quit RCX, I got a dialog asking if I wanted to cancel the export. I clicked no and let it sit for about an hour, in case it really was still trying to export my stills. No luck there, so I turned on verbose logging and saved a log. Quitting and restarting RCX seemed to fix the problem. Everything else was operating normally within RCX, even the shutter-click sound effect when I saved a snapshot.

If you're interested, I'll send in the log–just let me know.
 
Back
Top