Unai Posted March 22, 2017 Share Posted March 22, 2017 Hi there, I was trying the composite features in H16, and found out that no matter what I do, the Chromakey and Lumakey nodes don’t output any alpha. I thought the problem was due to my File nodes not having any alpha plane on them, but even after creating one with the Color node, the alpha doesn’t get modified, just the colour plane —keyed out areas are black as expected. Is this normal behaviour, am I doing something wrong? Not attaching any example file since the only thing I’m doing is File > Chromakey or Lumakey, check the A plane, and it either doesn’t exist or it’s unmodified by the keyer. Thanks in advance! Quote Link to comment Share on other sites More sharing options...
symek Posted March 23, 2017 Share Posted March 23, 2017 Lumamatte. (don't ask me why). Quote Link to comment Share on other sites More sharing options...
Unai Posted March 23, 2017 Author Share Posted March 23, 2017 Thanks Szymon, that would definitely be enough for a Luma key, since you can crush the alpha afterwards, but what about a Chroma key though? I forgot to mention, I’m using 16.0.504.20 on OSX 10.12.3 with an unsupported GPU (Intel Iris Pro). Do you think the GPU might be the issue? I thought COPs didn’t use it… Quote Link to comment Share on other sites More sharing options...
symek Posted March 23, 2017 Share Posted March 23, 2017 hmm... In 15.0 they both work as expected. I would assume it's a bug rather than deliberate change. I will submit a bug. Thanks! Quote Link to comment Share on other sites More sharing options...
Unai Posted March 23, 2017 Author Share Posted March 23, 2017 Cheers! Were you able to try it in 16 in your system though? Did it fail too? Quote Link to comment Share on other sites More sharing options...
symek Posted March 23, 2017 Share Posted March 23, 2017 It seems they don't work in 16.0.547 (don't produce any Alpha as you discovered). Only LumaMatte works. Bug submitted. 1 Quote Link to comment Share on other sites More sharing options...
Unai Posted March 23, 2017 Author Share Posted March 23, 2017 Thank you very much! Quote Link to comment Share on other sites More sharing options...
malexander Posted March 23, 2017 Share Posted March 23, 2017 In H16 we finally dropped the requirement that C and A must exist regardless of the actual file contents. This is good in a lot of cases (why create C and A when an EXR contains only Pz) and was pushed by the Terrain project. It was also the original intent of COPs, so I'm glad that this change finally happened. Unfortunately, due to the fact that this restriction has been in place for a dozen versions or so, a few cases that expect A to exist have now broken, the lumakey and chromakey among them. 2 Quote Link to comment Share on other sites More sharing options...
Unai Posted March 23, 2017 Author Share Posted March 23, 2017 Thanks Mark, happy to hear I’m not the only one with the problem. Hope it gets fixed! Quote Link to comment Share on other sites More sharing options...
symek Posted March 30, 2017 Share Posted March 30, 2017 From the journal: Houdini 16.0.563: The Chromakey and Lumakey COPs now have a toggle to generate an Alpha plane if it is missing in the input. It is on by default for 15.5 compatibility. 1 Quote Link to comment Share on other sites More sharing options...
Unai Posted March 30, 2017 Author Share Posted March 30, 2017 Wow, that was quick! I’ve tried it and it works as long as your input doesn’t already have an A plane. Not really sure if that’s the intended behaviour (pre-16), but hey, it’s easy to fix anyway with a Delete node. Awesome! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.