Metafuze 2.1.1 transcode colour space/gamme space?

[Jamie Havill]

Hi,

I've transcoded our offline media out of Metafuze 2.1.1, and I just want to know what gamma space/colour space this version of Metafuze defaults to? Will it have used whatever was set in the metadata (meaning Redspace/Redspace), or does it default to something else?

Thanks,
Jamie.

 

[Job ter Burg]

It defaults to camera metadata, unless you manually change the ISO, or if you add an RLX file.

Also note that the 2.1.1 release of MetaFuze does not (properly) support the MX chip's color science.

 

[Jamie Havill]

Thanks Job. I still have a conundrum though, maybe you can help.

I transcoded these specific R3D's to DNxHD36 offline files a few months back. As far as I can remember we shot on build 21, and definitely transcoded using version 2.1.1 of Metafuze. I didn't add an RLX file or change any metadata at all.

If you look at the picture attached, you can see my problem. The colour varies between each screencap. I didn't touch any settings related to colour in Metafuze, so presume it used Redspace/Redspace for transcoding. I then set Redspace/Redspace in Redcine-X and saw a big difference in colour. It's the same in PDPlayer, and when I open the R3D's in Avid using AMA on MC5 and leave the metadata untouched (Redspace/Redspace) and the same with Premiere Pro CS5. Why am I seeing this difference in colour? What is Metafuze doing with the files?

The major problem is I REALLY like what Metafuze did, it naturally created a a beautiful tone and palette that I desperately want to replicate in the grade. Our colourist renders out at his end to DNxHD 185x using his own workflow from our R3D's ready to be graded (on a Da Vinci 2K), but I'd like to start on the same colours as I've got here with the offline files created with Metafuze, as I think it would be a really great place to begin, and the images would take very minimal work to get where I want them to be, saving us a lot of time.

If anyone could shed some light as to whats going on, I'd be really grateful.

Thanks,
Jamie.

 

[Job ter Burg]

Well, RedCine-X build 252 was released last week, so I guess there were some changes in the color science between the SDK of January and the Red tools of June. Do you have MC5 available to you? You could check the result with AMA and compare.

 

[Jamie Havill]

Hi Job,

I think it is the changes in how the newer Red tools interpret colour. I just fired up Redcine v20.0.0 and the results were the same as Metafuze when set to Redspace & Redspace. It seems for this project the older way of dealing with colour is more pleasing, so I'll try and figure out a way of getting the files trasncoded in an older app with our colourist.

Thanks for all the help Job. Also, I said in my initial post I'd tried MC5 - it must use the newer SDK as the colour was the same as the new Redcine-X.

 

[MichaelP]

...and the next version of MetaFuze will be using the latest SDK which will have the latest color science, sensor stuff, etc...

Michael