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 feedback..

Doh.. 2k = 1/2 res
4k = 1/4 res

Sorry.. stupid. me.. to giddy swiping all over the place :D

Just played back 1k in realtime while changing the grade.. r3d files pulled over gigE :D

So if you can just enable EDL conform and let it read DPX seq also :)

Playing on a macpro running a boggy 7600gt gfx card.. monitor DELL 24 wf whatever I get masses of tearing if it's running more than 5fps upto 23fps

realtime is fine though. :-/ refresh issue?

did someone mention a LUT load option ?

Cheers

Si
 
BUG - REDCine in Leopard

BUG - REDCine in Leopard

This is great! Thanks for letting us play around with this even before our cameras ship...

A big one though: Everything works fine until I try to play back at full-res, or export anything (to any format). Instantly my screen gets completely garbled and I can't get out of REDCine without force-quitting. The files export, but they're completely black. No image. Makes REDCine kinda useless at the moment...

I'm running a MacBook Pro 2.16Ghz with Leopard. I know it's posted that REDCine isn't Leopard compatible yet, but thought I might as well let you know what I'm getting.
 
Image of redcine in XP. Looks like this... although if I mess around with the white balance it goes to the correct image.

550_1195139887.jpg
 
It seems that I have missed something, but I can't get my output from redcine right. I took R3D file, played with it in redcine and then I set output to photo jpeg quicktime movie - I get only 1st frame in a movie, (no moving images, just 1st frame.) although it seems to render every frame...

My problem with getting only the first frame has been resolved by updating to Quicktime 7.3 (together with the full FCS update).
 
My problem with getting only the first frame has been resolved by updating to Quicktime 7.3 (together with the full FCS update).

I'm up to date with everything (quicktime and FCS) but no go here...
although it is still beta so I do understand :)
no hurry here.
and to add: interface I like a lot!

cheers
 
My problem with getting only the first frame has been resolved by updating to Quicktime 7.3 (together with the full FCS update).
Hi Nick
I have been using quicktime 7.2 on a macbook pro without that problem so maybe it's the fcs update.
 
I'm having the same problem as Zuvis - All up to date (Quicktime, FCS) macbook Pro, but only getting the 1st frame... ???

ho hum.
 
After download of all Apple's recent pro apps updates RedCine is running OK now in Mac OS X Leopard 10.5.1.

RedCine 4K project playback on 8 core MacPro (9 GB memory, 2 ATI Radeon ATI Radeon X1900 XT cards) almost or about 98% realtime!!!

Enjoying to watch Jim's 4K footage in realtime 24 fps reverse playback.

And of course all that only when it shows 1/2 resolution High.

RedCine 4K project playback on MacBook Pro a bit slower for 1/2 resolution High but is very good and almost realtime for laptop computer at 1/4 resolution Medium.
 
after update to 10.5.1 is the same single frame in quicktime renders...
no changes. and if I try to export jpeg picture sequence my mac book pro 2.4 crashes...
 
Very excited! I download the Redcine. It's here, on my desktop. And then I click on it, and I get "sorry you're not running the correct architecture". And I realize that in order to run this, I've got to spend some more money on a new computer, even though I've got a whip fast dual g5 processor with all kinds of ram! And it gets me thinking....thinking about the Apple approach to things. Thinking about a conversation I had with a retail friend of mine who told me that Apple's main goal is selling hardware, in this case, duo Intel based computers.
And so I'm thinking why redcine was designed to work with intel processors only. It wasn't necessary to do that, so why do it Jim?
That in conjunction with only being able to edit in FCP makes me think that Apple and Red have more than an aquaintance relationship. And that makes me unhappy, because I don't like exclusionary policies, since those kind of platforms invariably mean that the consumer pays extra for admission! And I'm thinking that it's starting to look like that's really whats happening here. And I know I'm going to get fifty responses saying, dude, Red technology is so cheap, you should shut up, but I'm feeling that this Redcine only on Intel processor business is nothing more than a squeeze.
Armour on!
 
... And I realize that in order to run this, I've got to spend some more money on a new computer, even though I've got a whip fast dual g5 processor with all kinds of ram! And it gets me thinking....thinking about the Apple approach to things. Thinking about a conversation I had with a retail friend of mine who told me that Apple's main goal is selling hardware, in this case, duo Intel based computers.
And so I'm thinking why redcine was designed to work with intel processors only. It wasn't necessary to do that, so why do it Jim? ...

If you had an Intel-based Mac, you'd know why he did it... :biggrin:
 
And so I'm thinking why redcine was designed to work with intel processors only. It wasn't necessary to do that, so why do it Jim?

I read that Redcine would be intel-only here at least 6 months ago as I recall, so it wasn't a recent decision. It's unfortunate if you've invested in other hardware, but I wouldn't go too far into conspiracy theories. More architectures = more development time. Red is a super-small company and to be very honest it seems to me they have their hands full getting it working well on even one platform. (For all I know, maybe it was actually coded at Assimilate but I think they're pretty small also.)
 
I am so fucking happy about RedCine. Not only is it amazing and well appointed software, but it's also helping me procrastinate on an edit I really should be working on.

Cheers guys! Great work!
_mike
 
I read that Redcine would be intel-only here at least 6 months ago as I recall, so it wasn't a recent decision. It's unfortunate if you've invested in other hardware, but I wouldn't go too far into conspiracy theories. More architectures = more development time. Red is a super-small company and to be very honest it seems to me they have their hands full getting it working well on even one platform. (For all I know, maybe it was actually coded at Assimilate but I think they're pretty small also.)

I invested in the hardware awhile ago, thats not my point. Conspiracy (or as I like to call them, an "alternative" possibility) theory notwithstanding, IntelMacs are relatively new on the market, and so I guess my observation is that making Redcine only compliant on Intel based macs was not necessary for any development issues, but rather the result of agreement between Red and Apple.
Making software has more to do with integration along operating systems than it does about hardware upgrades, and most programs that run on pre-intel machines also run on intels, right? So I don't think that development time is really the reason for this, although it's not an unreasonable comment.
The whole low budget filmmaker strategy takes another hit when you've got to dump another 10-15% of budget into a new computer.:greedy:
 
Back
Top