The more things change the more they stay the same.

[Deanan]

Deanan, I have a couple of upcoming projects that could so much give a good use to that plug in. I know you are working hard and all but could you give us an estimate on when could the plug in be available? :waaa:

It's really hard to say as there are some big changes to it being made under the hood. There's always risk with that but we are hoping for week after next.

[I Bloom]

So I have been away for a bit but 3 things seem to consistantly remain the same.

1. The Red One produces amazing images.

2. A post solution that does not make the editor wish to commit harakiri is just around the corner.

3. The birger mount is shipping next week.

Please feel free to correct me on any of these as I may have missed some important new announcements.

Cheers All

Daren

4. Finner still thinks bitching is a good way to solve problems.

[Dominic Cochran]

IDK Ian, seemed pretty accurate to me. Of course it depends on the editor, but if you have to ship the footage to someone else, chances are they don't know what's going on. Luckily we don't have that problem(we're full-service), but I can certainly empathize with those who do.

[I Bloom]

IDK Ian, seemed pretty accurate to me. Of course it depends on the editor, but if you have to ship the footage to someone else, chances are they don't know what's going on. Luckily we don't have that problem(we're full-service), but I can certainly empathize with those who do.

4K origination and finishing did not exist before the Red camera other than in tiny extremely high end and basically experimental pockets of the film industry. They created a new industry essentially that has only been truly in motion for less than a year.

The problem is not that it can't be done, I have clients finishing Red productions on laptops, it is that there is a learning curve that people don't want to deal with. There are guys working tirelessly, trying to reduce that learning curve and expand the reach of this new industry. But the problems are truly complex and the solutions are going to take time. Bemoaning this reality will not make it go away any faster.

IBloom

[Dominic Cochran]

Ah, if only 4K finishing were the only problem. But somehow, I doubt that's what Finner is "bitching" about. But yes, I do agree with you for the most part. Problem is, most people just want a way to edit and finish this stuff at 2K or(much) less.

Personally, we've figured it out because we've been here from the beginning and spent a lot of time here, others who are expected to be able to deal with RED post aren't so lucky. I just hope the guys you mention ARE working very hard, because it's in all of our interests to see RED not only understood, but welcomed universally.

And of course, your personal contribution is much appreciated, and even more when the Avid component gets finished!

[Bruce Allen]

Currently the most popular workflows we're seeing is transcoding to ProRes or DNxHD (via compressor, RR, RC, RL, or via the wrappers into Media Composer).

Really?

RedCine currently gives me (and everyone else, I thought) noise when I go to DNxHD.

EDIT: and all the other acronyms you use don't exist for PC.

And how do you get audio in a non-convoluted way on a PC running Media Composer?

How is this a current, popular workflow if it's not possible yet?

From what I've tried, we still have to go through immediate steps. The arrow on the red.com workflow page that points from RedCine to Avid in a single step is misleading.

Bruce Allen
www.boacinema.com

[Deanan]

The QT ref files is the best way to get into MC directly (on the mac).

We're waiting for Avid to release a new version of the DNxHD for all our tools. It's a change on the AVID side end that needs to happen to get around the noise problem. The unreleased version works well for transcoding but I'm sure they have their own QC process that they have to go through.

Audio support is in underway at the moment for RC and the SDK.

It's been always clear that we're a mac based company and mac support would be ahead of PC support. All development work happens first on the mac and then it takes time to port everything 'reliably' while at the same time supporting constant camera and codec changes.

Really?

RedCine currently gives me (and everyone else, I thought) noise when I go to DNxHD.

EDIT: and all the other acronyms you use don't exist for PC.

And how do you get audio in a non-convoluted way on a PC running Media Composer?

How is this a current, popular workflow if it's not possible yet?

From what I've tried, we still have to go through immediate steps. The arrow on the red.com workflow page that points from RedCine to Avid in a single step is misleading.

Bruce Allen
www.boacinema.com

[Jay A. Kelley]

Sounds like a good time for an update. Things have been moving very quickly behind the scenes on many different fronts. There are alot of things happening with partners that we aren't abl to talk about yet.

Currently the most popular workflows we're seeing is transcoding to ProRes or DNxHD (via compressor, RR, RC, RL, or via the wrappers into Media Composer). At the moment, editing in the native editor codecs gives you the best editing workflow (because they're native, rgb, lower res, less space).
Transcode times for an 8 core mac are about 3:1 for 2k (from 4k) and greater than realtime for 1k (from 4k).

There's be a new release of the QT codec week that fixes a bunch of things and enables more control over the 2k decode speed/quality. This release will also work better with compressor, etc.

The first version Adobe plugin is currently being tuned and will provide a good base to grow the workflow as we continue to work with Adobe on improving the workflow. It's a tremendous amount of work to get it right but we're very excited about where we're going here.

I'll let Michael speak about the Avid future when they're ready to. We're looking forward to what they have planned because it will really make R3D/Avid very smooth.

There is also very cool stuff happening with RED support from Adobe/Assimilate, Quantel, Digital Vision, DVS, etc. There are more announcements planned for IBC from other companies but I don't know which ones I can talk about yet.

We're working on a number of fixes for the SDK which should be released next week. There are a ton of very cool tools planned from various people who signed up for the sdk.

We have a HUGE todo list and mostly everything is a high priority.

I am looking forward to Avid's announcement as well. I'm sure they are working very hard to make things wonderful for us.

:)

Jay

[Evin Grant]

Denan,
What's up with Apple? I see news from everyone else but. I'm very excited about the Premier stuff but I was really hoping to have native support for Color by now. Has apple really given up on Pro Apps? I know you can't answer this but it sure feels like it.

[Bruce Allen]

The QT ref files is the best way to get into MC directly (on the mac).

We're waiting for Avid to release a new version of the DNxHD for all our tools. It's a change on the AVID side end that needs to happen to get around the noise problem. The unreleased version works well for transcoding but I'm sure they have their own QC process that they have to go through.

Audio support is in underway at the moment for RC and the SDK.

It's been always clear that we're a mac based company and mac support would be ahead of PC support. All development work happens first on the mac and then it takes time to port everything 'reliably' while at the same time supporting constant camera and codec changes.

Very much understood.

I was simply disputing your "current popular workflows" rebuttal, which included RedCine -> Avid DNxHD.

That workflow is not current and popular because it doesn't work yet.

But you advertise it on your web page.

Just want you to understand that if it did work, we really would be complaining a lot less. Avid seems pretty low on your to-do list or else you would have had DNxHD exports from RedCine working a year ago. Glad to hear you plan to fix it, or course.

So I think Finner is right for now.

We all hope for him to be wrong ASAP ;)

BTW, last time I asked about Quicktime PC support (a month or two ago?), you guys said "real soon now".

Can't someone just write a wrapper using your SDK? Eg, a temp quicktime codec that simply calls the SDK functions for the decode. Doesn't need to be realtime. Seems pretty simple to me. Then suddenly we'd be able to import on Avid on the PC.

Can I write it?

Bruce Allen
www.boacinema.com