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

:jacked:

WRONG Itunes, iPod, iPhone is why Apple is forever.

Let's face it JC, we live in a world where MAC's and PC's and even the Redheaded Linux have to play together all the time.

A used MAC Mini is SUPER CHEAP and since REDCINE-X is FREE, I agree with other posters that a MAc is a worthwhile investment for you to support your PC workflow.

The thread is not hijacked : I think having the choice of platform is important when you're dealing with r3d files. Itunes,iPod, iPhone, etc... have a great success because you can use them with a PC too. Nobody would buy an iPod if you have to buy a Mac to use it (by the way the European Community often suits companies like Microsoft/Apple which don't understand that you can't force customers to buy their other products to use their primary product...)

Back to topic regarding Redcine-X : a Mac Mini isn't useable with it and isn't supercheap : you have to look at the specs, it's expensive for what it offers compared to an entry-level PC. If you want to use a Mac in a Redcine postproduction workflow, you have to buy the Mac Pro which is, as far as I know, the only Mac which allows to add several cards, and especially an eSata card (that you'll have to buy, even the most expensive Mac doesn't feature eSata). Don't forget that when you're using Redcine, you have your R3D dailies somewhere, and you have to access quickly to this data.

I'm editing a feature right now, and everything is backup up on RAID setups, connected by eSata (sorry but it's a standard, I'm not interested in USB or Firewire). All my dailies are backuped on LTO tapes. And connecting a LTO device is a breeze on PC, I helped a friend with a Mac, it's just a nightmare. Not to mention the gamma difference, the formatting compatibility, NTFS vs HFS. Mixing PC and Mac is a source of problems, it's great if it can be avoided.

But I hope that soon Redcine for Windows will solve all that, despite all my grief, I'm a huge Red fan, I love what they're doing. :driving: (don't know what this smiley means, but I love it)

PS : by the way, I own a Macmini and an iPod...
 
Last edited:
FYI, Jean, I believe Tim's "hijack" was in reference to his own own thread and not to anyone else's. I'd also agree with most of the points you brought up as well, although i use macs exclusively so it's difficult for me to get too passionate about it :)
 
abour RedCine-X vs. RocketCine-X...
I have an idea... Lets just wait a while until RedCine-X is out, THEN we will for sure know what app is best for any situation.
If you like both for diferent stuff... Keep both, they are free!

Probably the old apps will disaper but they can still be used. Like RedAlert is very quick an easy if you just need to grab a dpx from one frame of a shot.
(just because I have Photoshop doesn't mean I don't use Preview.


Only time will show us the trouth
 
As I said my experience at this time is limited when talking about editing tools, both, hardware and software based, but that was my understanding of what Jim said, and what RRCX vs. RCX represent, anything is possible with RED, we know that, so will have to wait and see what will happen with both applications, but I was mostly referring to the Hardware of RR, sure will be great when RCX is out and taking full advantage of RR.

ciao
 
abour RedCine-X vs. RocketCine-X...
I have an idea... Lets just wait a while until RedCine-X is out, THEN we will for sure know what app is best for any situation.

That's probably the best way to look at it...
 
I have an idea... Lets just wait a while until XYZ is out, THEN we will for sure know

Ha! If everyone followed that advice, we'd have about 8 posts a day around here. :-)
 
Any news on the REDCINE X launch?

alot of the bigger bugs have been worked out.. Snow Leopard came along mid-flight though and brought along a few compatibility issues. New target is Friday for the Alpha release before we do the big code merge.
 
Hey Jarred,

Is it possible we will see an R3D trim/export tool in RedcineX? I know this is a tool many of us have waited for a long time. Would be great to have in many instances especially for stock footage submissions. Pretty please:-)
 
Last edited:
Hey Jarred,

Is it possible we will see an R3D trim/export tool in RedcineX? I know this is a tool many of us have waited for a long time. Would be great to have in many instances especially for stock footage submissions. Pretty please:-)

5th time this has come up. It is on our list.

Jim
 
5th time this has come up. It is on our list.

Jim

Jim,

Just spent the last month filming a major doc with our R1 and while I would prefer not to hijack the thread, this does seem the appropriate place to respond.

We have nearly 6TB of footage and there were literally times when we had unexpected things happen on set when I would just radio my AC to roll the camera and I would run over and grab it, shoulder it and run to get try and get a few seconds for a shot that I would never have otherwise gotten.

I did this because I knew those magical seconds were all I was going to get and they were never coming back. If I was lucky I could get a few brief moments the editor could use on a 30 second take.

When this happens there is generally a few of me setting the exposure (with the new and vastly improved false color meter which is my new best friend) and then my focus puller getting sorted. That means on a 20 second take I may have 16 seconds of crap I never want the editor to get his hands on (zooming, etc.).

Other times we had to take the 'sit and wait' approach and just roll on things till they happened. I have one such 13 minute shot just for a few seconds of action that we could not predict.

It's not just that there's a lot of footage that's unusable, it's more the case that the editor (who may be on another coast and never call me after I've wrapped) may never find these gems because the ratio of good to bad footage is so high on these takes. That's why I can't tell you how important this is to get into the SDK so we can make tools to trim the source files.

When shooting features this is rarely the case, the conditions are more controlled and hopefully you've done a good job of blocking and staging so this sort of nonsense is not an issue.

But, and it's a big but, doing docs you just have to do these unsavory things sometimes to get the shot. Getting this from "on the list" to "on the high priority list" would go a long way towards helping some of us improve our final product with the camera.

As far as I can determine this is the only format that does not allow us to trim the source footage. It's not a gratuitous request for those of us shooting non-fiction content and any pressure you can bring to get this feature either into the tools (and the SDK) is much appreciated.

Thanks again,

:J
 
Jim,

Just spent the last month filming a major doc with our R1 and while I would prefer not to hijack the thread, this does seem the appropriate place to respond.

We have nearly 6TB of footage and there were literally times when we had unexpected things happen on set when I would just radio my AC to roll the camera and I would run over and grab it, shoulder it and run to get try and get a few seconds for a shot that I would never have otherwise gotten.

I did this because I knew those magical seconds were all I was going to get and they were never coming back. If I was lucky I could get a few brief moments the editor could use on a 30 second take.

When this happens there is generally a few of me setting the exposure (with the new and vastly improved false color meter which is my new best friend) and then my focus puller getting sorted. That means on a 20 second take I may have 16 seconds of crap I never want the editor to get his hands on (zooming, etc.).

Other times we had to take the 'sit and wait' approach and just roll on things till they happened. I have one such 13 minute shot just for a few seconds of action that we could not predict.

It's not just that there's a lot of footage that's unusable, it's more the case that the editor (who may be on another coast and never call me after I've wrapped) may never find these gems because the ratio of good to bad footage is so high on these takes. That's why I can't tell you how important this is to get into the SDK so we can make tools to trim the source files.

When shooting features this is rarely the case, the conditions are more controlled and hopefully you've done a good job of blocking and staging so this sort of nonsense is not an issue.

But, and it's a big but, doing docs you just have to do these unsavory things sometimes to get the shot. Getting this from "on the list" to "on the high priority list" would go a long way towards helping some of us improve our final product with the camera.

As far as I can determine this is the only format that does not allow us to trim the source footage. It's not a gratuitous request for those of us shooting non-fiction content and any pressure you can bring to get this feature either into the tools (and the SDK) is much appreciated.

Thanks again,

:J

We all want this feature. It is important. It will get done. We won't forget. I promise.

Now... can we not bring this up ever again? :-)

Jim
 
We all want this feature. It is important. It will get done. We won't forget. I promise.

Now... can we not bring this up ever again? :-)

Jim

If you can get it into the (linux) SDK I'll never mention it ever again, promise ;)

:J

PS - 20.1.x was a big success for us in a VERY high risk environment. Using 17 would have been impossible in my opinion so much thanks on the recent improvements to camera stability.
 
Jonathan, while you're waiting for a beta of REDCINE-X, you might be able to make use of a command-line tool I wrote for this purpose (Windows and Linux compatible).

The original thread was here, but the attachment has since disappeared.

Jim/Jarred - was this intentionally removed? If not, I'll upload again for those who don't mind using an unsupported, 'at-your-own-risk' tool.
 
Back
Top