Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Quicktime 10-bit - picture is destroyed (few color, grain...)

J

Jan Tomanek

Member
Joined
Mar 25, 2011
Messages
10
Reaction score
0
Points
0
Hi all,

please I have BIG BIG problem with our PIPELINE.

I have FCpro, Combustion etc.
8 core Mac pro, Snow leopard, latest update, ATI GPU...

When I render into ALL 10bit codec in 10bits - PRO RES 4444, 422, 10-bit uncompressed to quicktime, mov is destoryed
(it depend on MOV, but sometimes it has just 2-5 colors, sometimes there is just BLACK and white GRAN etc...) But image is destroied and has NO 10-bits
When I render to any 10bit codec like 8-bit, there is no problem.

Today, I completely format computer, made totally NEW instalation of OSX, FC pro etc, and NOTHING!!!!!!!!!

UAAA!!!! All day work for nothing. :emote_hanged:

But the most interesting is, that on my APPLE MACBOOK AIR it work without problem!!!!!!!!!!

Only different is, that on AIR is Nvidia and on MACBOOK pro is ATI... Is it possible that problem in rendering to quicktime can be in ATI card???
I know that some problem with ATI and NVIDIA is in COLOR, but it use GPU for rendering, but QUICKTIME encoding??????????

Any suggestion????
Thank
 
can you break down your workflow completely, what software you are using, what is going to what, and all your settings?

I've rendered out of RCX with r3d's to 10-12 bit codecs all year long, and not a single issue in the color following apart. all flavors of pro res, uncompressed, and even 8 bit compression with h264 all flawless.

screen grabs and comparisons will help too.
 
As I wrote it work on my notebook, but not on our new Macbook Pro workstation.

It happen when I render from Combustion, Shake, it doesn't matter. When I render 16bit or 10bit sequence of images, all is good. Also when I render 8bit to "uncompress 10bit", 4444, 422 pro ress. But when I want to render to same codec like 10bit, picture is destroid (I'm home now and I have example in studio, so I have no picture), but image is totally mess. (like if you use filter "generate fractal noise) ;-))
 
you're not explaining the workflow properly, I have no clue what your pipeline is. are you rendering out of rcx first? then when u go through ur composite software and render out there are issues? are the files ok everywhere but the composite software? there's no knowing what the issue is unless you layout the whole workflow to be analyzed.
 
There is no much explain...

When I want to render to 10bit MOV from ANY appl (Shake, Combustion...) the result is destroied image.
Beleive me, that I'm not computer or postproduction amateur and I try every combination which aimed to new instalation of system, but nothing! :-((((
 
There is no important what is source image - it's same with float PNG, 16bit TGA or JPG.... ;-((( same problem
I don't use RED one at all - we made CGI movies, but I'm here because there is many professionals.
 
well it matters because you posted in the RED WORKFLOW section, and this is in the wrong section if you aren't dealing with r3d's in the process. but while we are here, I'll see if I can help you root out the problem the best I can. but if 10 bit is farked out of the composite software, the ATI card really might be the root of the problem. I'm not sure if combustion and shake use GPU to process the frames, I know most composite software does it though. What happens if you render out 16 bit, bring it back in and re render it as 10 bit as a test? do you have access to after effects or nuke? you can spit it out of combustion or shake as 16 bit dpx (lossless) and render to pro res in AE. or do the whole project in nuke instead. combustion and shake are older pieces of software with no support anymore. funky things might be happening now with gpu and the system.
 
It's a good point Tom, but all sequence are OK (16bit, 10-bit or float). So my suspicion is that NOT Combustion, but Quicktime USE GPU for some operations... I'll try to change GPU to some NVIDIA.
I can't try 16bit MOV, because I don't know any 16bit codec for apple.
BUT AGAIN: with the SAME Combustion it WORK on my notebook!!!!! (same system, same combustion, same FCP...) only Nvidia
 
I found on APPLE.COM - about QT10 - there could be any core using GPU
-----------
GPU-accelerated
video decoding.
QuickTime X accesses the H.264 video-decoding capabilities of the NVIDIA graphics processors found in many of the latest Mac computers. Using the GPU to decode video not only provides a fluid playback experience but frees the CPU for other tasks.
-----
 
if u have ae installed u can do 16 bit dpx out of combustion, and try to use AE to reconvert the dpx to the pro res you need.

have you also tried finishing what you've done in combustion, export at 16 bit dpx or tiff, (i think you said that worked)
and bringing that back in to combustion to try quicktime again?
 
I wrote, that there is no important what is source image - it's same with float EXR, PNG, 16bit TGA or JPG.... ;-(((
 
You must log in or register to reply here.
Back
Top