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.
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.
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!
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.
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.
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.
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?
|« Previous Thread | Next Thread »|