Pages: 1 2 [3]   Go Down

Author Topic: RED WORKFLOW  (Read 19457 times)

fredjeang

  • Guest
Re: RED WORKFLOW
« Reply #40 on: April 10, 2012, 08:14:26 am »

 ;D

Coot is in shape !

This morning (I live near a concert hall), there was a line of trucks, possibly for concert live recording. I could count at least 8 HD cameras and there were still unloading.

There were Grass Valley Thomson. I talked to a guy and he told me that they use Edius too. I've heard very good things about those Thomson HD cameras, they use a system with 3 colors layers and it seems that the quality is stunning.
Logged

bcooter

  • Guest
Re: RED WORKFLOW
« Reply #41 on: April 10, 2012, 03:47:33 pm »

;D

Coot is in shape !

This morning (I live near a concert hall), there was a line of trucks, possibly for concert live recording. I could count at least 8 HD cameras and there were still unloading.

There were Grass Valley Thomson. I talked to a guy and he told me that they use Edius too. I've heard very good things about those Thomson HD cameras, they use a system with 3 colors layers and it seems that the quality is stunning.


Since I've been on so many time zones lately, I sleep 4 hours feel great can't get back to sleep, then somewhere during the day hit a wall, hit 5 expressos, which keeps me up until 2 am, then rinse and repeat.

That's why I had time to do the Red Team Van.

IMO

BC

Logged

fredjeang

  • Guest
Re: RED WORKFLOW
« Reply #42 on: April 10, 2012, 05:08:29 pm »

I liked the Red Team Van. (but where are the horny Redgirls in high-heels in charge on the detox?)


Something escapes to my understanding about the recent posts on the Red workflow.

James and Von are both saying that Redrocket is the way. I'm ready to beleive that knowing the both sources are serious when they don't draw GM wild vans.

But there is still a transcoding involved, init?

Why not using the proxy that comes with the camera to cut
then re-link to R3D
and grade primary in the time line with no third-party app using the raw panel?

The implementation of AMA was precisely to avoid the import. But it makes very little sense IMO to trancode to a low DNxHD for editing when there is the possibility to not doing it.

It seems to me that the workflow you're talking about (if I understand it) is very effective but also very brutal in the sense that it needs lots of power.
You use the rocket to go, I imagine, Prores 4:2:2 and stick with it.
Or I'm missing a point there.

« Last Edit: April 10, 2012, 05:19:24 pm by fredjeang »
Logged

bcooter

  • Guest
Re: RED WORKFLOW
« Reply #43 on: April 10, 2012, 11:57:35 pm »

I liked the Red Team Van. (but where are the horny Redgirls in high-heels in charge on the detox?)


Something escapes to my understanding about the recent posts on the Red workflow.

James and Von are both saying that Redrocket is the way. I'm ready to beleive that knowing the both sources are serious when they don't draw GM wild vans.

But there is still a transcoding involved, init?

Why not using the proxy that comes with the camera to cut
then re-link to R3D
and grade primary in the time line with no third-party app using the raw panel?


The implementation of AMA was precisely to avoid the import. But it makes very little sense IMO to trancode to a low DNxHD for editing when there is the possibility to not doing it.

It seems to me that the workflow you're talking about (if I understand it) is very effective but also very brutal in the sense that it needs lots of power.
You use the rocket to go, I imagine, Prores 4:2:2 and stick with it.
Or I'm missing a point there.




Fred, Fred, Fred.

Do yourself a favor.  Get an idea and go shoot a 30 second video on your panasonic (good camera) a Sony or Canon, (good cameras) and find some rental house in Spain that'll loan you a full RED system.  They'll do it, because the film industry cuts more deals than the still rental companies.

Then also borrow a RED Rocket and quickly color your one light dailies in Cine-x, then color your other files in whatever your latest tools are  . . . Edius, Premier, whatever, run a stopwatch and see which one is faster and gives a better first showing result.

Remember, you can put out anything for a proxy and YOU know the difference between the video and finish out, but does your client?  Does your client's, client's client's wife know the difference? 

You never want that phone call that asks, "why are these video's so dark, or grainy or blue, or red or green or choppy or smooth or  . . .
IMO

BC
Logged

fredjeang

  • Guest
Re: RED WORKFLOW
« Reply #44 on: April 11, 2012, 04:37:10 am »


Remember, you can put out anything for a proxy and YOU know the difference between the video and finish out, but does your client?  Does your client's, client's client's wife know the difference? 

You never want that phone call that asks, "why are these video's so dark, or grainy or blue, or red or green or choppy or smooth or  . . .


That's correct.

So far I never edited Red files with the client's pressure behind. That's the reason why others workflows that are also working well seemed to me so appropriate but you're right.

If we do our indy films with Red, we have a choice of workflows and possibilities are open, but in commercial config the Red Rocket is the more logical way to go. Agree, I see it.
Logged
Pages: 1 2 [3]   Go Up