[Sidefx-houdini-list] HALO - was Siggraph & Maya..
fudini at gmail.com
Wed Aug 19 08:14:28 EDT 2009
A major reason I think HALO failed as an effective compositing app was
the lack of effective rotoscoping tools, a good 2D tracker and paint.
The rotoshape op looks much better now but you still need a tracker and
paint to do bread and butter compositing. If it had these I would have
give it a chance. Most of the other nodes are really quite good I think.
It would be so nice to have a paint node!
Szymon Kapeniak wrote:
> I have to admit that the lack of video format support is the last
> thing I would name if ask about missing parts in cops. As far as I can
> tell both Shake and Nuke support Quicktimes (and only this one) on
> osx/windows32 merely as Apple doesn't support linux - main os for
> Houdini. This is, after all, the only api worth to consider in respect
> to professional usage and, agreed, would be a nice addition for cops.
> But I don't feel this makes real problem for studios. If so, no one
> would use shake/nuke on linux!
> The part I miss most* in cops are stability and speed, with stability
> on a first place.
> * - well, I would also like to have HOM access to plates in cops, like
> a numpy array on demand. This would be convenient hook for rapid
> custom tool development :)
> (and only quitcktime, not wmv etc), this feature was rarely used by me.
> 2009/8/19 fudini <fudini at gmail.com>:
>> Most of the codecs mentioned are designed for distribution and playback.
>> They are "industry standard" for these purposes but aren't designed to
>> be used as source. They are compressed, lossy and undesirable for high
>> quality source material. A few are designed for editing (DNxHD, ProRes)
>> because they use sequential frames and don't have to deal with the usual
>> IPB frame compression found in most playback codecs.
>> While most compositing packages "can" load these codecs in Quicktime/Avi
>> wrappers the vast majority of these codecs just can't handle the the
>> color range required for high end film work. When quality matters in
>> film compositing we most often use single frames stored in a log format
>> such as dpx to preserve as wide a gamut as possible, composite in 32 bit
>> float linear and output again in log to be printed to film. Playback,
>> editing, source are entirely different things. Different purposes,
>> different standards.
>> Drew Whitehouse wrote:
>>> The problem *is* the cross platform support and the myriad codecs each of
>>> the container formats allow (mov, avi, wmv, mkv etc), and many of them
>>> proprietry and/or platform specific. Movie formats are also a hornets nest
>>> of patents. Touch only runs on windows, so they can take advantage of MS's
>>> DirectShow libs and Apples quicktime libs. I wouldn't be suprised if there
>>> wasn't more lines of code in the VLC movie player than in the entire houdini
>>> On Wed, Aug 19, 2009 at 1:55 PM, <craigleehoffman at aol.com> wrote:
More information about the Sidefx-houdini-list