Welcome to our community

Be a part of something great, join today!

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

REDCINE-X Build 158...

R3D Data said:
Answer:



So no detail adjustment yet with a rocket installed. I think the options should be grayed out if they are not available.
Click to expand...

OK---was driving me nuts as well that i could not move anything within the detail window. Now i understand---i'll get rid of my rocket card in that case. not!
 
AAAHHhhh I see. at least I don't feel stupid anymore. Must say though that exporting a 1080p from the 4K is a pretty great Denoise on its own. and doing it at nearly realtime is so worth it.
 
•*Now have the RR card. However, I like the way you could see the frames being processed in Red Rushes in order get an idea of the time to process frames. Can you do that with RocketCine-X?

• When I press the Export button, I can't tell whether it's actually engaged my request until I go to the partition where I sent the file. Is this correct?
 
BajaProductions said:
OK---was driving me nuts as well that i could not move anything within the detail window. Now i understand---i'll get rid of my rocket card in that case. not!
Click to expand...

I actually did pull the rocket card. I was doing a still shoot, and the subject needed just a bit of extra help, and of course we had a look in RCX that would be hard to replicate in RA. So, off to extra-slow rendering TIFFS I went.
 
David Collard said:
•*Now have the RR card. However, I like the way you could see the frames being processed in Red Rushes in order get an idea of the time to process frames. Can you do that with RocketCine-X?

• When I press the Export button, I can't tell whether it's actually engaged my request until I go to the partition where I sent the file. Is this correct?
Click to expand...

Switch to the batch tab on the lower left to see the status.
 
My Redcine X 158 crashes all the time when trying to export a 1080 h264 out of some 3K slow mo I shot. Am I doing something wrong? I tried clip finder and the same problem. Starts the render but then crashes soon after. Now trying to export out of proxies in compressor. It seems to be working out of compressor.

Please help.
 
Last edited:
Jean-Charles Wolfarth said:
Deanan,

Any news about the release of the build 158 for Windows ? The saving function is desperately needed... The scripting interface too, by the way :yesnod:

Thanks !
Click to expand...

We're still working on fixing issues that came up with 158. Hopefully in a few days.
 
Ivan Cortazar said:
My Redcine X 158 crashes all the time when trying to export a 1080 h264 out of some 3K slow mo I shot. Am I doing something wrong? I tried clip finder and the same problem. Starts the render but then crashes soon after. Now trying to export out of proxies in compressor. It seems to be working out of compressor.

Please help.
Click to expand...

It's because quicktime likes to use alot of frames cached to make the h.264 and it tries to grab too much memory. Try reducing the keyframes to a lower number and turning off multipass.

We're rewriting the QT export and pulling it out of RCX so they both can use more memory.

Quicktime is a huge royal pain in the ass...
 
Thanks Deanan,

Also please add:

If encounter a corrupted frame verify/write black/white etc and continue with next frame, then report to log file?

right now it would just crash RCX.

Thanks

Michael T.
 
Apple told me that if you can write a working quicktime codec then you are a "programming man with balls". Deanan isn't strictly right with "huge royal pain in the ass" because it's actually a "right royal pain in the ass" :)

Graeme
 
QuickTime, and the fact that is is a "right royal pain in the arse", is the best reason for considering the purchase of Smoke for Mac. Being able to keep QuickTime out of the equation and work with frame sequences (in real time) would be a huge boon.
 
Nick Shaw said:
QuickTime, and the fact that is is a "right royal pain in the arse", is the best reason for considering the purchase of Smoke for Mac. Being able to keep QuickTime out of the equation and work with frame sequences (in real time) would be a huge boon.
Click to expand...
May I humbly point out Adobe's CS4 or upcoming, 64bit native CS5 suites, both of which are cross platform? Not trying to derail the thread, just sayin' :wink5: No Quicktime shenanigans to speak of....

Cheers!

Paul
 
It seems everyone is someway affected by Quicktime. Apple needs to do something.
 
gbalaji said:
It seems everyone is someway affected by Quicktime. Apple needs to do something.
Click to expand...

Yes.
At least for the last 8 years... (that' when I started to use it for anything work-related...)

One can make wishlists
Not all dreams come true...
 
Paul Leeming said:
May I humbly point out Adobe's CS4 or upcoming, 64bit native CS5 suites, both of which are cross platform? Not trying to derail the thread, just sayin' :wink5: No Quicktime shenanigans to speak of....

Cheers!

Paul
Click to expand...

I have CS4 Production Premium, but don't really use it. As far as I am aware, and correct me if I'm wrong, Premiere cannot handle DPX sequences, or any other frame sequences using time-code meta-data. So a DPX conform is not possible. And on Mac at least, Premiere is still quite tied to Quicktime.
 
Deanan said:
It's because quicktime likes to use alot of frames cached to make the h.264 and it tries to grab too much memory. Try reducing the keyframes to a lower number and turning off multipass.

We're rewriting the QT export and pulling it out of RCX so they both can use more memory.

Quicktime is a huge royal pain in the ass...
Click to expand...

It's probably because the of the Quicktime APIs. There's a million different ways to create a movie in Quicktime and not all of them work. I've struggled with this for 7 years and I still run into issues. Quicktime needs a serious overhaul. That said I would not try to create an a H.264 movie from Red Cine X. It's not Red Cine X that I blame for the problem, it's Quicktime. It's far better to convert to Pro-Res then convert the Pro-Res to H.264. Do it in two steps!
 
BradWright said:
It's probably because the of the Quicktime APIs. There's a million different ways to create a movie in Quicktime and not all of them work. I've struggled with this for 7 years and I still run into issues. Quicktime needs a serious overhaul. That said I would not try to create an a H.264 movie from Red Cine X. It's not Red Cine X that I blame for the problem, it's Quicktime. It's far better to convert to Pro-Res then convert the Pro-Res to H.264. Do it in two steps!
Click to expand...

Interesting way to do it....I've had MIXED results going from redcine-x to h.264---mostly not so good. Now i'm using a similar approach by going from prores via matrox mxo2 to h.264 using matrox compressor plugin and having really good results...but only because Matrox has made the steps easy by making the setup simple by selecting the size file you want at the end of the transcode process. But only discovered this workflow recently as i've been hoping and trying to make it work direct from redcine-x. Hope it gets better to eliminate a two part process.
 
You must log in or register to reply here.
Back
Top