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

REDCINE tip...

Status
Not open for further replies.
Rob's work on REDCode and the Quicktime codec has been superb. I was once told by someone who really knew about programming, that if you can work with the Quicktime API and write code with it that works, that you're a "real programming man, with balls".

Graeme
 
Yeah, there is a reason for the new QTkit API...for the girly-men (like me)
Doesnt help you writing a wrapped codec though.
 
Graeme Nattress said:
if you can work with the Quicktime API and write code with it that works, that you're a "real programming man, with balls".
Click to expand...

I met one of the Shake developers and he went off on how bad quicktime was to deal with in comparison to the Windows video APIs. In fact, he discovered Quicktime was working at 8 bit when Apple was claiming it was working at a higher bit depth. He recoded it to fix that issue before it ever made the news. That's all years ago of course. No harm, no foul.
 
joelnet said:
I met one of the Shake developers and he went off on how bad quicktime was to deal with in comparison to the Windows video APIs. In fact, he discovered Quicktime was working at 8 bit when Apple was claiming it was working at a higher bit depth. He recoded it to fix that issue before it ever made the news. That's all years ago of course. No harm, no foul.
Click to expand...

QuickTime was the first serious multimedia framework implemented on the desktop. It has a lot of history, and by now it's very "deep".

And dark.

Like a cave.

It wouldn't surprise me at all to learn that not even Apple knows everything that goes on down there.
 
The more I learn about QuickTime the less I am interested in continuing to use it. I work mostly in the audio field and comparatively, its a breeze. Despite having too many file formats and number redundant compression schemes, at least they are all fairly well documented and easy enough to make your way through.

QuickTime seems like it might have had a structure in the beginning, but as time passed it lost it and wandered off in many different directions with no single authority keeping track of further developments. Not that the we need yet another video format, but really, QuickTime seems to be a mess.
 
shout out to deanan, ted, kelly, brent and of course big bad john...they are the air cover in my world of army crawling on the front lines.

oh yeah , zach too for chucking in that shim...awesome dude, it made those s4's cook(e)
 
Yes.

One Big fat shout out to the entire RED team and to JIM for assembling such a great talent base!

David
 
This could take forever to credit everyone. Can't someone do a clip of RED Team screen credits?:love:
 
Back on subject - after doing my first red mini-test yesterday (on Eiriks cam. Thanks a million Eirik!!!!)

It seems like the iso (over 320) and exposure controlls are there just in case you really need them.

Setting the iso down (when appliceable) and just using curves (and possibly some brightnes/contrast for final touch up), give you a nice and noisefree image all the way to your editing suite.

Now I just have to set up that 11x8-core cluster, a SAN solution & FCP server to get realtime-performance and a nice way to script it.... :)

(And scripting is NOT me...)

Thanks a million for fantastic tools to work with!

I'm so looking foreward to get my Red in a month or so!

(NOW, what's up with that native EDL/pull list function in RedCine... :) ? Not there? )

Gunleik
 
I'm quite sure it won't...
but would like to be proved wrong.

iBlooms xml hack is interesting, though. (Haven't tested it yet.)

Gunleik
 
iBlooms hack did not function for me correctly, unfortunately i haven't the luxury of time to figure out why.

I may bug him to take a look at it soon because i have a lot of RED projects coming up, that all depends how quickly they are able to ship off #659

Lets hope for no errors in the batch that just went out.
 
gunleik said:
Back on subject - after doing my first red mini-test yesterday (on Eiriks cam. Thanks a million Eirik!!!!)

It seems like the iso (over 320) and exposure controlls are there just in case you really need them.

Setting the iso down (when appliceable) and just using curves (and possibly some brightnes/contrast for final touch up), give you a nice and noisefree image all the way to your editing suite.

Now I just have to set up that 11x8-core cluster, a SAN solution & FCP server to get realtime-performance and a nice way to script it.... :)

(And scripting is NOT me...)

Thanks a million for fantastic tools to work with!

I'm so looking foreward to get my Red in a month or so!

(NOW, what's up with that native EDL/pull list function in RedCine... :) ? Not there? )

Gunleik
Click to expand...


Hi Gunleik

How fast did your system render files out of redcine?
 
pablokorona said:
iBlooms hack did not function for me correctly, unfortunately i haven't the luxury of time to figure out why.

I may bug him to take a look at it soon because i have a lot of RED projects coming up, that all depends how quickly they are able to ship off #659

Lets hope for no errors in the batch that just went out.
Click to expand...
We've got it working on Mac with FCP, and have successfully pulled shots in RedCine on both Mac & PC, across a network. In the interim of a Red (or others) tools release it works now.
It does take some fiddling of the resulting Redcine.XML, in particular path naming conventions have to be modifed (eg our Mac & PC's look at network filers with different upper pathing levels, and / & \ slashes needed correcting), and also the "resolution" needs to be modified to the desired Redcine Project size (eg, FCP edit at 1k qts, Redcine 2k Project from 4k R3D files).... but its a great start at least.
Chris
 
Hei Helge

On one easy standard config box, around 18x realtime for Prores HQ.

Waiting for new faster disks and much more RAM, so I'm a bit reluctant to answer what I figure one machine will accomodate especially since the GPU issue is not resolved yet, but I guess my workflow wil tip towards DPX's rather than ProRes (doing a lot of keying/comp'ing) and I guess furthermore I will have to set up one mother of a cluster with three XRAIDS to accomodate a rational workflowspeed.

That said, I'll experiment and build some more, while the jury is out.

I will test this on Xserves in a san with RAIDS, too, but because of the GPU thingy, my bet is on MacPros.

Good thing is that this will speed up Shake workflow a bit as well...

Gunleik
 
In a later version of REDCINE, eventually, could we get a feature where we could expand the size of the 'curves' view panel for more detailed tweaking? Maybe with keyboard arrow control over individual selected curve handles as well.

Just an idea.
 
Status
Not open for further replies.
Back
Top