Apple Color REDCODE plugin 4.0 beta

[Ian Laurie]

Final cut keeps crashing due to the RED QT plugin. What can fix this?

 

[Ian Laurie]

Never mind. All I needed to do was reinstall the QT plugin and all is fine

 

[Rob Lohman]

Okay, I figured out WHAT the issue is, but not sure why Color is doing this. I have a MacPro with two monitors hooked up to an ATI 2600. If I have both monitors plugged in, it gives me crap in the output at anything over 10bit. If I have just one monitor plugged in, all depths render correctly. I'm not sure if it's more of a Color issue, or if it's something to do with the RED plugin. I haven't had this happen with any other footage (non red), so it's got to deal with how color deals with RED footage through the plugin.

Matthew

That sounds like a GPU issue (color renders through that). There was another thread in this forum about the different pixel formats supported on the ati and nvidia cards

 

[Bing Bailey]

That sounds like a GPU issue (color renders through that). There was another thread in this forum about the different pixel formats supported on the ati and nvidia cards

I think it is GPU related because a lot of my plugins won't work when I have a second monitor plugged in. you need a card with at least 512mb for that to fly right

 

[Omar Saad]

Thank you so much Rob and rest of the Red team! This could not have come at a better time for me. Looking forward to trying it out tomorrow!

best,

Omar

 

[Chris Armstrong]

The plugin seems to struggle with clips that have had their speed changed.

Anytime I try to pass a sequence or group of clips that include one with a speed change color crashes.

 

[Chris Armstrong]

Do you want an email of the Color crash report?

I'm getting lots of crashes. Seems to be tied to speed changes, redcode 42, and maybe other issues.

Footage is 4KHD. Shot on build 21.
Some sequences are redcode 36, some 42, and a couple 28.

It's strange, some will go into Color, others just crash it.

 

[Luca Immesi]

Do you want an email of the Color crash report?

I'm getting lots of crashes. Seems to be tied to speed changes, redcode 42, and maybe other issues.

Footage is 4KHD. Shot on build 21.
Some sequences are redcode 36, some 42, and a couple 28.

It's strange, so will go into Color, others just crash it.

I'm not sure but I read somewhere it's not indicated to send to Color the effects with R3D files.
For other codec is ok but for the R3Ds is better to send them to Color without effects.
Can someone confirm?

 

[Luca Immesi]

I have a bad news and a good one: the bad is the spanned r3d bug persists, the good one is the amazing clipfinder can fix it :smile:

 

[Kaku Ito]

I have a bad news and a good one: the bad is the spanned r3d bug persists, the good one is the amazing clipfinder can fix it :smile:

Probably the spanned R3D but is coming from the REDCODE version and the Color plugin just handles the color process?

 

[Luca Immesi]

Probably the spanned R3D but is coming from the REDCODE version and the Color plugin just handles the color process?

mmm...it could be, we'll see when the new red plugin for quicktime comes out.

 

[Rob Lohman]

Need more information guys

On the crashing: yes, please email me the crash log (rob at red). It would also be great if you could put a sample file with issue up for me to download somewhere.

Spanned R3D's: what exactly is the problem? It should absolutely load clips that span multiple files properly. Please let me know *HOW* you're loading the clips that are giving you issues!

 

[Paul Lee]

we've never had luck with sending RED footage with speed changes. Got to be 100%. Seen problems with other codecs as well. Will try on this new plugin.

 

[Nick Shaw]

Spanned R3D's: what exactly is the problem? It should absolutely load clips that span multiple files properly. Please let me know *HOW* you're loading the clips that are giving you issues!

It's the same issue there has always been. Loading spanned R3Ds works, but doing a 'send to Color' with proxies that refer to spanned R3Ds gives a freeze frame. Of course sending proxies to Color is not an officially endorsed workflow, but it is a useful one.

The Clipfinder fix (based on a process I developed) modifies a Color project to point it at the R3Ds instead of the proxies.

 

[Ian Andolina]

You will need to re-send from FCP, you cannot load a previously sent sequence that failed (I think Color caches which plugin / codec to load for a project, which would be why your old stuff worked Ben)

First off, lots of :beer: to you and da' boys!!! Secondly, if I have a saved sequence already in Color using the 2.9 plugin, does this Color-caches-plugin-version thing also affect it? I've deleted the 2.9 plugin, and its telling me V4beta 2 in the Red tab, but just in case something weird was going on...

Apple have to add in the controls for that. All we do is, as Rob says, pass them the image decoded as per the settings they set.

Hoping there are some strings / :single-malt: bottle you can pull to get Apple to speed up... :cheers2:

 

[Rob Lohman]

It's the same issue there has always been. Loading spanned R3Ds works, but doing a 'send to Color' with proxies that refer to spanned R3Ds gives a freeze frame.

I've identified the issue in the code. Will get cracking on a fix. Thanks for the info!

if I have a saved sequence already in Color using the 2.9 plugin, does this Color-caches-plugin-version thing also affect it?

It should not. I think you're fine.

 

[David Battistella]

I've identified the issue in the code. Will get cracking on a fix. Thanks for the info!



It should not. I think you're fine.

The spanned R3d thing has been around for a while. Clipfinder and other software has a tool to fix this problem with freeze frames. It has something to do with the XML export from color.

It's a typical problem when using clips from the same master clip in a sequence.

David

 

[Laurent AZEMA]

Someone could tell us how the new plug in perfoms?
Did you got the same results as with the lastest Red Softwares?
Good to know
I have no r3d at home yet to test it by myself

 

[Kaku Ito]

Someone could tell us how the new plug in perfoms?
Did you got the same results as with the lastest Red Softwares?
Good to know
I have no r3d at home yet to test it by myself

The REDgamma and REDcolor selection seem to be working, but FLUT or Shadow adjustments don't show up in RED tab due to Apple Color needing to be updated.

 

[Ben Brainerd]

It could just be me being really tired, but it seems like everything's coming in a LOT darker. Like stuff that was looking nice at 320 has to be jacked up to 500+ to get the same levels...

I'll try again after a nap. My eyes have been kinda off all day, so I wouldn't read too much into it until I double check against the scopes.