Comments for fxphd http://www.fxphd.com visual effect and production training Wed, 22 Feb 2012 17:10:00 -0600 hourly 1 http://wordpress.org/?v=3.1 Comment on Professor Profile: Mark Bowey by David http://www.fxphd.com/blog/professor-profile-mark-bowey/#comment-11123 David Wed, 22 Feb 2012 17:10:00 +0000 http://www.fxphd.com/?post_type=blog&p=1888#comment-11123 Great insight into an awesome designer. Love to hear about his experience working with Dan Weil and what his personal project looks like. I really enjoy watching these new series of Professor Profiles. Tim Clapham, Wayne Robson or Victor Wolonsky would be really interesting to learn about. Thanks guys! Great insight into an awesome designer. Love to hear about his experience working with Dan Weil and what his personal project looks like.

I really enjoy watching these new series of Professor Profiles. Tim Clapham, Wayne Robson or Victor Wolonsky would be really interesting to learn about.

Thanks guys!

]]> Comment on Professor Profile: Mark Bowey by jose http://www.fxphd.com/blog/professor-profile-mark-bowey/#comment-11099 jose Tue, 21 Feb 2012 19:51:35 +0000 http://www.fxphd.com/?post_type=blog&p=1888#comment-11099 Thanks .!! Great to see Mark , he has great personality and he's very passionate about his work! Thanks .!!

Great to see Mark , he has great personality and he’s very passionate about his work!

]]> Comment on Professor Profile: Mark Bowey by Alessandro http://www.fxphd.com/blog/professor-profile-mark-bowey/#comment-11087 Alessandro Tue, 21 Feb 2012 15:48:03 +0000 http://www.fxphd.com/?post_type=blog&p=1888#comment-11087 Mark is a true pro. The next one to be interviewed could be Tim Clapham? Mark is a true pro. The next one to be interviewed could be Tim Clapham?

]]> Comment on Professor Profile: Mark Bowey by Amid http://www.fxphd.com/blog/professor-profile-mark-bowey/#comment-11075 Amid Tue, 21 Feb 2012 12:25:56 +0000 http://www.fxphd.com/?post_type=blog&p=1888#comment-11075 Awesome:) tnx alot Mike :) Awesome:) tnx alot Mike :)

]]> Comment on fxphd member profile – Chad Gilmour by Amid http://www.fxphd.com/blog/fxphd-member-profile/#comment-10794 Amid Thu, 16 Feb 2012 09:44:01 +0000 http://www.fxphd.com/?post_type=blog&p=1882#comment-10794 Great :) Great :)

]]> Comment on Roto strategies in FFI by Prakash http://www.fxphd.com/tips/roto-strategies-in-ffi/#comment-10744 Prakash Wed, 15 Feb 2012 22:55:45 +0000 http://www.fxphd.com/?post_type=tips&p=1581#comment-10744 Thanks a lot for a such a great tip. Thanks a lot for a such a great tip.

]]> Comment on Bring on the new Thunderbolt devices by Edward Saltau http://www.fxphd.com/blog/bring-on-the-new-thunderbolt-devices/#comment-10526 Edward Saltau Sat, 11 Feb 2012 12:33:54 +0000 http://www.fxphd.com/?post_type=blog&p=1875#comment-10526 This is great, thanks John. My problem is that I use my laptop for everything. This setup is great for the road. But all i need at home is the the sonnet thunderbolt adapter (an OWC drive in one esata port and a red station in the other) and a monitor. My question is, how can I connect a monitor with that setup as i have now remaining thunderbolt/display port? What I really need is a thunderbolt splitter. This is great, thanks John. My problem is that I use my laptop for everything. This setup is great for the road. But all i need at home is the the sonnet thunderbolt adapter (an OWC drive in one esata port and a red station in the other) and a monitor. My question is, how can I connect a monitor with that setup as i have now remaining thunderbolt/display port?
What I really need is a thunderbolt splitter.

]]> Comment on pre-production by # http://www.fxphd.com/blog/pre-production-2/#comment-10501 # Sat, 11 Feb 2012 03:25:55 +0000 http://www.fxphd.com/?post_type=blog&p=1103#comment-10501 I'm going to apparatus this kind of assessment to two forms of individuals: latest Microsoft zune lovers who will be taking into account upgrading, and the wonderful attempting to make your mind up from a Microsoft zune and a great ipod device. (Los angeles cpa gamers worth considering to choose from, such as the The Walkman X, yet Lets hope within the future . you adequate facts to make a knowledgeable final decision within the Zune vs gamers aside from ipod and iphone line likewise.) I’m going to apparatus this kind of assessment to two forms of individuals: latest Microsoft zune lovers who will be taking into account upgrading, and the wonderful attempting to make your mind up from a Microsoft zune and a great ipod device. (Los angeles cpa gamers worth considering to choose from, such as the The Walkman X, yet Lets hope within the future . you adequate facts to make a knowledgeable final decision within the Zune vs gamers aside from ipod and iphone line likewise.)

]]> Comment on Filming content- pt01 by Amid http://www.fxphd.com/blog/filming-content-pt01/#comment-10391 Amid Wed, 08 Feb 2012 09:29:53 +0000 http://www.fxphd.com/?post_type=blog&p=1879#comment-10391 Great :D Great :D

]]> Comment on Squeezing the most out of a 5D Mk II or ALEXA signal by yellow http://www.fxphd.com/blog/squeezing-the-most-out-of-a-5d-mk-ii-or-alexa-signal/#comment-10365 yellow Tue, 07 Feb 2012 14:15:46 +0000 http://www.fxphd.com/?post_type=blog&p=1860#comment-10365 A few things I've noticed: The 'extended' range with regard to YCbCr shooting cameras like the Canons is a luma thing. Chroma remains 16 - 240 even if a picture style is used that produces saturated colors. So it's only contrast thats affected going outside of that, when remaining YCC. If chroma went full range then that would be xvYCC, xvcolor(Sony) wider gamut but achieved with same color primaries as rec709 and Canons don't do that. Canons use the levels outside of 16 - 235, of coarse this is user choice when exposing but from my own tests it appears that the encoding of h264 is based on full luma levels, it's even flagged in the header of the stream as such, handling them in a color space conversion to RGB as so called 'legal' levels and that includes when strictly exposing within the 16 - 235 range results in spiked histograms when presented as RGB. Handling as full extended range is required. A decent decompressing codec will maintain levels as shot, from personal experience QT doesn't it squeezes the full luma into 16 - 235, uses the wrong color matirx coefficients and upsamples to 4:2:2 at the same time. Personally any decoding of Canon video sources via QT is unreliable including applications like MPEGStreamclip. Decoding and converting to RGB in a user controlled environment via a tool like AVISynth will result in a far better result and actually give the user what is in the h264 stream and not what the decompressing codec chooses to skew first. Not sure what a Picture Style manipulation of the linear values off the sensor has to do with 'extended' or 'legal' range, isn't that more an exposure choice? A few things I’ve noticed:

The ‘extended’ range with regard to YCbCr shooting cameras like the Canons is a luma thing. Chroma remains 16 – 240 even if a picture style is used that produces saturated colors. So it’s only contrast thats affected going outside of that, when remaining YCC. If chroma went full range then that would be xvYCC, xvcolor(Sony) wider gamut but achieved with same color primaries as rec709 and Canons don’t do that.

Canons use the levels outside of 16 – 235, of coarse this is user choice when exposing but from my own tests it appears that the encoding of h264 is based on full luma levels, it’s even flagged in the header of the stream as such, handling them in a color space conversion to RGB as so called ‘legal’ levels and that includes when strictly exposing within the 16 – 235 range results in spiked histograms when presented as RGB. Handling as full extended range is required.

A decent decompressing codec will maintain levels as shot, from personal experience QT doesn’t it squeezes the full luma into 16 – 235, uses the wrong color matirx coefficients and upsamples to 4:2:2 at the same time. Personally any decoding of Canon video sources via QT is unreliable including applications like MPEGStreamclip.

Decoding and converting to RGB in a user controlled environment via a tool like AVISynth will result in a far better result and actually give the user what is in the h264 stream and not what the decompressing codec chooses to skew first.

Not sure what a Picture Style manipulation of the linear values off the sensor has to do with ‘extended’ or ‘legal’ range, isn’t that more an exposure choice?

]]>