Cineform changing colors?

markblasco

markblasco

Well-known member
I picked up cineform Neoscene to make AVCHD editing easier on my PC. I have noticed on some of the footage captured from my HFS100 that the deeper colors don't look quite as deep after running neoscene. Is this something I am doing wrong, or is this normal?
 
I don't use neoscene myself, though is almost definitely a gamma shift from 0-255 (full range luma) to 16-235(TV level luma). This is essentially the same as the whole 7.5-100 IRE measurement if I'm not mistaken.

If you have the option, try to use PC Levels (it may be called Rec. 709, BT. 709, Full Range, etc). Someone else may be able to assist you more accurately.
 
It's possible that you weren't viewing the source material correctly. Cineform takes color space conversions accurately.

Unless your blacks and white are being crushed, I wouldn't worry about it. More than likely you are doing some extra finishing at the end, and that's what you should worry about when you output your deliverable.
 
Cineform might do the YV12=>YUY2 conversion correctly, but the other editing software might not do the YUY2=>RGB conversion correctly .

Most editors work in sRGB 16-235 so that sometimes explains colors & levels shifts

Perhaps markblasco could list the editor being used , also , how are you comparing the footage (software player? which one, PC monitor, HDTV etc...) The method of comparison , decoder used , renderer used can make the exact same footage look entirely different.
 
same here.. i'm noticing my colors shifting in final cut after using neoscene to convert my videos.
 
I experienced this during my trial run, as well. I want to buy it ASAP but am afraid to until this issue is explained.
 
I'm using Premiere CS4, taking AVCHD video from a Canon HFS100. To compare, I am viewing the video from the camera directly in Premiere, and then viewing the exact same video after converting it with cineform. I am putting them both side by side, and the color difference in more saturated colors is noticeable.
 
markblasco said:
I'm using Premiere CS4, taking AVCHD video from a Canon HFS100. To compare, I am viewing the video from the camera directly in Premiere, and then viewing the exact same video after converting it with cineform. I am putting them both side by side, and the color difference in more saturated colors is noticeable.
Click to expand...

I would write a bug report to Cineform and ask them what's going on. It's possible that a metadata bit in the cineform file is being set wrong.
 
PP clamps all footage (except v210) to sRGB 16-235 if it doesn't have a preset for it (so you may lose some highlights, shadow detail). It has a preset for AVCHD, so levels are passed through correctly

Even "lossless" formats like lagarith in RGB mode, or even uncompressed 8-bit YUV or RGB , aren't treated as truely lossless because of this levels behaviour.

I don't use cineform anymore, but that was the behaviour a while back with PP. Others have commented that this issue with PP was fixed
 
Hi, i am having the same problem with color shifting when transcoding to Cineform, I have a prores file captured from tape, then i use rhozet to transcode the file to Cineform but the output it's always different from the source file, i have used the scopes built in final cut pro to view the changes and there is always a big difference between source and output files. I tried to create an AVI Cineform file and it is still different than the source, a bit better than the QT file but not the same as source, can someone help with this, or anyone can suggest ways to troubleshoot or tips to try to fix this, thank you
 
PDR said:
PP clamps all footage (except v210) to sRGB 16-235 if it doesn't have a preset for it (so you may lose some highlights, shadow detail). It has a preset for AVCHD, so levels are passed through correctly

Even "lossless" formats like lagarith in RGB mode, or even uncompressed 8-bit YUV or RGB , aren't treated as truely lossless because of this levels behaviour.

I don't use cineform anymore, but that was the behaviour a while back with PP. Others have commented that this issue with PP was fixed
Click to expand...

On CS4 and CS5, I regularly work with Lagarith RGB, and have not seen this behavior.
 
RX782 said:
On CS4 and CS5, I regularly work with Lagarith RGB, and have not seen this behavior.
Click to expand...

You might not have noticed because your files probably didn't have superwhites or superdarks

What format was the original source footage before lagarith ? Y'CbCr colorspace? Did it have highlight values Y > 235 , Y < 16 ? How did you do the RGB colorspace conversion (in avisynth, through vdub?) , and what levels did you use (TV or PC) ie. what matrix did you specify (e.g. rec709, PC.709 etc...)
 
You must log in or register to reply here.
Back
Top