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

RCX PRO Build 11 Beta and Epic/ Scarlet Camera build 3.0 (release)

Has anyone had problems transcoding longer clips to quicktime? 3 minutes seems to be the longest clip I can successfully process (approx a 10GB R3D file). Any longer clip will not open, with an error message reading "The movie could not be opened. The file is not a movie file". Curiously all of these corrupt quicktime files are exactly 4.29 GB.

The only solution I can find is to cut each long R3D into bit size pieces, under 3 minutes. I'm using RCX Pro Build 11 + Red Rocket Card to transcode to QuickTime 1080p Pro Res 422 HQ.

Any advice out there? Thanks
 
I usually don't gush, but RC3/RG3 + Alchemy are like a drug.. I am going back in my raw archives and yanking out shots that I thought were unusable. Amazing!

My epic arrives tomorrow.. all this goodness at once.. I may explode.

The only down shot is I gotta get some work done, but I can't stop messing with old footage :-)
 
Last edited:
Peter Stelzhammer said:
just some (feature?)request for RCX 11:
is it possible to only write a specific Proxy-type, e.g. P(review) only?
there is a dropdown-arrow in the export-options but it's not active as it seems -> I can only export all Proxy-versions together (F, H, M, P).
in general it works fine - would just be for a cleaner workflow if I only need one type from the Proxy-versions.
Click to expand...


++ 1 (and thanks for all the fish!)
 
Christian Felder said:
Hello!

...everything looking great - but:

Audiorecording has permanent klicks and constant hicks - not useable!

...was working with the last version.

Any ideas?

Thank you....
Click to expand...


Same problem !
+1
 
great Update, just one thing:

I have crashes after some menu jumping on the touchscreen.
It freezes and i have to hold down the start button to shut it down.

anybody experience the same?

Thanks.
 
Alex Boothby said:
Has anyone had problems transcoding longer clips to quicktime? 3 minutes seems to be the longest clip I can successfully process (approx a 10GB R3D file). Any longer clip will not open, with an error message reading "The movie could not be opened. The file is not a movie file". Curiously all of these corrupt quicktime files are exactly 4.29 GB.

The only solution I can find is to cut each long R3D into bit size pieces, under 3 minutes. I'm using RCX Pro Build 11 + Red Rocket Card to transcode to QuickTime 1080p Pro Res 422 HQ.

Any advice out there? Thanks
Click to expand...

How is the target volume formatted? Sounds like its FAT32, which has a filesize limit. Try rendering to a different location, or reformatting the drive to HFS+ if its clear to do so.
 
Merish Claren said:
great Update, just one thing:

I have crashes after some menu jumping on the touchscreen.
It freezes and i have to hold down the start button to shut it down.

anybody experience the same?

Thanks.
Click to expand...

This has happened to me twice, and I am still on the previous build.
 
Jeffrey Loewe said:
RG3 appears to create more noise in my .r3d's then using RG2 did in the past.
Click to expand...

That's not possible as that selection has no influence on how data gets recorded. However, if you use the histogram to expose then you may be changing the amount of light (f-stop / shutter speed / lights themselves) you give the sensor since the curve is different, or the curve is bringing out more of the noise and you were always under exposing. What happens in RCX when you go back to RC2/RG2 on a clip that looks noisy to you in RC3/RG3?
 
Alex Boothby said:
Has anyone had problems transcoding longer clips to quicktime? 3 minutes seems to be the longest clip I can successfully process (approx a 10GB R3D file). Any longer clip will not open, with an error message reading "The movie could not be opened. The file is not a movie file". Curiously all of these corrupt quicktime files are exactly 4.29 GB.

The only solution I can find is to cut each long R3D into bit size pieces, under 3 minutes. I'm using RCX Pro Build 11 + Red Rocket Card to transcode to QuickTime 1080p Pro Res 422 HQ.

Any advice out there? Thanks
Click to expand...

As suggested above you want to make sure you're rendering to a volume that can support bigger than 4GB files (FAT[32] does NOT!). If you are rendering over the network then you may want to use our QuickTime Exp exporter to write bigger files
 
Rob Lohman said:
That's not possible as that selection has no influence on how data gets recorded. However, if you use the histogram to expose then you may be changing the amount of light (f-stop / shutter speed / lights themselves) you give the sensor since the curve is different, or the curve is bringing out more of the noise and you were always under exposing. What happens in RCX when you go back to RC2/RG2 on a clip that looks noisy to you in RC3/RG3?
Click to expand...

It gets noisier. I actually switched back to RG2 in camera and was experiencing the same problems. I shot two nights before without the update, same lighting, same situations...no noise at all.
 
Jeffrey Loewe said:
It gets noisier. I actually switched back to RG2 in camera and was experiencing the same problems. I shot two nights before without the update, same lighting, same situations...no noise at all.
Click to expand...

Did you re-run the black shading after the install? Or re-set the active calibration map to your previous user setting?
 
TheBied said:
Did you re-run the black shading after the install? Or re-set the active calibration map to your previous user setting?
Click to expand...

I did blackshade after the install. And before each time I've gone out to shoot trying to fix whatever is happening. I've just never seen the meter on the left that watches the blacks clip so much. Even in well lit situations.
 
I've been reviewing clips I shot over the weekend in Moab, and I have to admit that I'm seeing the same thing, noise even in very well-lit shots, in any areas mid-tones and darker. Eyeing the histogram as I was shooting, I was worried that I was over-exposing a bit, as we had some fast glass out on a sunny day. Nothing clipped in the high end, but I am surprised at the fuzz in the mids and lows.

I black shaded when I did the upgrade, I don't have time or the battery power to do one each time out in the field, I'm moving fast and gunning it as things happen.

It's gotta be something I'm doing (or not doing), but I am seeing what you're seeing, apparently.

Jeffrey Loewe said:
I did blackshade after the install. And before each time I've gone out to shoot trying to fix whatever is happening. I've just never seen the meter on the left that watches the blacks clip so much. Even in well lit situations.
Click to expand...
 
Jeffrey Loewe said:
It gets noisier. I actually switched back to RG2 in camera and was experiencing the same problems. I shot two nights before without the update, same lighting, same situations...no noise at all.
Click to expand...

Would love to see examples if you have time.
 
Rob Lohman said:
As suggested above you want to make sure you're rendering to a volume that can support bigger than 4GB files (FAT[32] does NOT!). If you are rendering over the network then you may want to use our QuickTime Exp exporter to write bigger files
Click to expand...

Thanks again Rob & John Marchant. Looks like it was the destination drives after all. Cheers!
 
Jared VanLeuven said:
I've been reviewing clips I shot over the weekend in Moab, and I have to admit that I'm seeing the same thing, noise even in very well-lit shots, in any areas mid-tones and darker. Eyeing the histogram as I was shooting, I was worried that I was over-exposing a bit, as we had some fast glass out on a sunny day. Nothing clipped in the high end, but I am surprised at the fuzz in the mids and lows.

I black shaded when I did the upgrade, I don't have time or the battery power to do one each time out in the field, I'm moving fast and gunning it as things happen.

It's gotta be something I'm doing (or not doing), but I am seeing what you're seeing, apparently.
Click to expand...

If there are this many similar situations happening something has to be going on. Not upset or knocking RED but it is definitely noticeable and is unusually more apparent now than in the past. And I'm not the only one seeing it.

And it sure does. I wish I knew what it was. Most of my work right now is shooting concerts. Having a noisy image even when something is lit properly isn't ideal. I guess for me it's things that are Mid's are even having grain and noise patterns appearing. Which I didn't see before, even in pure daylight. Could it be my sensor rather than the upgrade? I'd love to know whats going on, but I guess everything has to run through NeatVideo for the time being which isn't optimal, and wasn't having to be done before...
 
You must log in or register to reply here.
Back
Top