Pedro Conforti
Forum Replies Created
-
Hi,
I’ve came across this step by step guide, which says the input image has to be 100% white. Could not check it since I don’t have a i1 Pro (only a i1D3), but here it goes anyway:
https://www.negativespaces.com/blog/2013/4/22/sony-oled-calibration.html
As an i1D3 and Sony PVW 2541 oled owner, I would really appreciate if someone could share any updated information about the offset values to be applied to this particular colorimeter to match my 2541 to a good old D65 CRT whitepoint… after many years of joyful colorgrading, since I bought the 2541 I feel cursed and very frustrated by this oled green cast thing! Still struggling to make it work with Lightspace CMS and give me back the WYSIWYG confidence I used to have with Sony CRTs!
Pedro
Pedro Conforti :: Colorist
pedroconforti.com
———————–MAIN SYSTEM
DaVinci Resolve v10.1.4.009
OSX 10.9.2 Mavericks
Hackintosh i7 3.69Mhz 32Gb RAM
GTX 780 + onboard video (GUI)
Tangent Element
Decklink HD Extreme 3DSYSTEM 2
DaVinci Resolve v10.1.4.009
OSX 10.9.2 Mavericks
Mac Pro 8 core 2.26Ghz 48Gb RAM
GTX 570 2.5Gb (macvidcards) + GT120 (GUI)
Euphonix MC Color
Decklink Mini -
Hey Nik, I’m on the same boat as you… would there a good soul be around to the rescue? Or have you found the solution?
I have been trying to create a simple, primaries only LUT for ages, but it always gives me this bizarre inverted colors image when I try to apply it on Resolve.
This is what I am doing (with a single node, primaries only grading): Project Setting > Lookup Tables > Generate LUT From Current Grading
Can’t understand why this doesn’t work. I have been trying this apparently simple procedure since Resolve v9, with no sucess. Tried it on 3 macs with different GPUs…, and always the same result.
If someone can shed a light over this I’d be very grateful. It would help a lot – and also prevent me to go bananas over this!
Thanks,
Pedro
Pedro Conforti :: Colorist
pedroconforti.com
———————–DaVinci Resolve
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (macvidcards) + GT120
Tangent Element
Decklink HD Extreme 3D -
Hi John,
I got rid of the problem by uninstalling the NVidia CUDA driver and reinstalling a previous version. I’d suggest you to check if you are running the recommended CUDA driver version (which varies depending on your OSX version), and even if you are, uninstalling in and reinstalling again, or maybe a previous different version. It worked for me. I am running 10.8.4 and CUDA 5.5.28 on a GTX570
Best,
Pedro
Pedro Conforti :: Colorist
pedroconforti.com
———————–DaVinci Resolve
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (macvidcards) + GT120
Tangent Element
Decklink HD Extreme 3D -
Thanks for the replies, guys.
So the strangest thing just happened: problem is “magically” gone. Will try to describe so it may help anyone, but I doubt it since I can’t figure what happened for the problem to disappear.
After many (MANY) boots, PRAM and SMC resets, setting the software for using less resources (8 bits, no gui update, etc.), uninstalling v10 and reinstalling v9 -and doing the same with many versions of the CUDA drivers, nothing would work, so I ended up installing v9 back again, which used to work well, but with the latest CUDA driver this time (5.5.28 – I tried 5.5.25 but it did not work properly for me). But I was still getting the same errors of of “GPU memory full” where used to be none when I was running v9 with some older 5.0 CUDA driver.
So I gave up and went to sleep (just me – I never turn off my Mac Pro, neither put it to sleep). And I woke up this morning, ran v9 again… and noticed the “Insufficient Hardware” warning was gone after the login screen. So I opened my last session and everything was fine again. As I did the ultimate mistake of saving the session when I installed v10, I could not open in in v9, so I was brave (or stupid) enough to, after all of this, reinstall v10 over v9, with the strong belief that since the CUDA / GPU memory errors were gone, it would work. And it did.
So far everything back to normal. But as I said, cannot figure what happened after I went to bed… the TI fairy, maybe? 😀
Pedro
Pedro Conforti :: Colorist
pedroconforti.com
———————–DaVinci Resolve
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (macvidcards) + GT120
Tangent Element
Decklink HD Extreme 3D -
Same problem here. Can’t get the matte submenu on a node after adding the grain clip as a matte. Only if I add the matte for a specific clip, but not globally. Can’t figure out what am I doing wrong.
Pedro Conforti :: Colorist
Link Digital
———————–Resolve Lite 9
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (flashed) + GT120
Tangent Element
Decklink HD Extreme 3D -
Chris,
Since I was using a powered hub with nothing else but the panels connected to it, I guess this was not the problem. But this hub was connected to another hub (a passive one) which was causing the problem.
So when I finally connected the powered hub straight to the computer, the problem disappeared.
Always good to remember about it, anyway.
Thanks,
Pedro
Pedro Conforti :: Colorist
Link Digital
———————–Resolve Lite 9
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (flashed) + GT120
Tangent Element
Decklink HD Extreme 3D -
Just figured it out, and you guessed right… bad USB!
I am using a powered USB hub, but it seems I have to connect this hub straight to the computer instead of to my Cinema Display’s USB ports or another hub, as erratic behaviour like this starts to happen if I do it.
Thanks!
Pedro
Pedro Conforti :: Colorist
Link Digital
———————–Resolve Lite 9
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (flashed) + GT120
Tangent Element
Decklink HD Extreme 3D -
Hey Ivan, thanks a LOT for the tip!
I was having exactly the same problem: images looking fine on QT but too dark on FCP 7. And I knew something was wrong, because the problem did not exist on FCP X, only on FCP 7.
Since I am using the i1 Display Pro, I was able to tweak the advanced settings, where I was able to save the ICC profile as ICC2 instead of the default ICC4. And that did the trick! Now QT and Final Cut 7 look the same again.
Forums around here have been saving the day way too often lately!
Best,
Pedro
Pedro Conforti :: Colorist
Link Digital
———————–Resolve Lite 9
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (flashed) + GT120
Tangent Element
Decklink HD Extreme 3D -
Hey Margus,
That was my first idea, so to check this possibility and before cleaning anything, I’ve opened the Synapse app, which with the Tangent Hub installer (the Tangent Hub is required to use the panels with most softwares).
Synapse analyzes the panels and all the controls to see if everything is ok, and points out if any button / know / wheel / ball moves. But Synapse doesn’t see any movement coming from the gamma ring. Only if I touch the panels then the software detects that the ring has moved. So it led me to believe that it is not a physical problem, as dust or anything, but rather something is software or USB interfacing.
Thanks for the reply, though.
Best,
Pedro
Pedro Conforti :: Colorist
Link Digital
———————–Resolve Lite 9
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (flashed) + GT120
Tangent Element
Decklink HD Extreme 3D -
UPDATE:
The problem is back. This is really annoying, makes the software unusable, as the gamma luminance is always changing by itself.
It’s so strange, because the hundreths go down at a very constast pace, just like seconds.
If anybody has a clue about the reason, please let me know!
Thanks,
Pedro
——-
Hey Sascha,
I was unaware that Resolve 9 was out, so I’ve download and installed it over my Resolve 9 beta 3 and the problem is now gone.
Thanks anyway!
Pedro
Pedro Conforti :: Colorist
Link Digital
———————–Resolve Lite 9
Mac Pro 8 core 2.26Ghz 48Gb RAM
OSX 10.8 Mountain Lion
GTX 570 2.5Gb (flashed) + GT120
Tangent Element
Decklink HD Extreme 3D