Quote:
Originally Posted by
z3r0 
I can see Houdini and Nuke in a suite. It would be interesting to see how both could be developed to have more integrated workflows similar to how apps adobe creative suite interact with each other and allow you to easily jump between another.
Houdini is a well-regarded app regarding dynamics and Renderman integration and has a node compositor too but app developers have difficulty balancing number of features with quality of features and if you try to bundle great apps together, you can end up with monolithic apps that have no room to grow. If you make too many small apps, the workflow becomes too complex and having to jump between intermediate files all the time.
I think the best idea is to have a centralised application that is extremely modular. This allows developers to push forward parts of the application while keeping the workflow tight. If the modular components are controlled by 3rd parties though like you get with Maya plugins, the costs go up and can lead to compatibility problems when the core app gets updated. It doesn't seem like anyone has figured out the right way to build a pro app if there is one, least of all a suite of cross-platform apps (and they often need to be cross-platformt to get the level of refinement).
Quote:
Originally Posted by
z3r0 
I can see Mari taking the market over ZBrush.
Mudbox is probably a closer rival to it. I'd see Mari competing more with Bodypaint. Again though they all have a lot of common features now. Modo even does animation and rigging. It's always the same. They start out small and they get artists who want to streamline workflows with feature requests. Eventually, we will have about 10-15 3D apps that all have similar feature sets.
Quote:
Originally Posted by
z3r0 
I'll take Houdini over Maya any day of the week. The Maya interface is bloated.
But would you get a job with it? I don't support this reality but it is a sad reality that employers will ask for 3DS or Maya experience. No doubt there will be Houdini jobs but far fewer than the main two and that's what Apple would have to consider too. With NLEs like Final Cut, you can jump between them no problem, Premiere, Vegas, Avid whatever it's all just insert clip, scrub, mark, scrub, mark, cut, fade to black. It's slightly more than that before any editors get annoyed but it's pretty easy to go between them. Someone that has only used Maya could sit in front of Houdini with a blank expression on their face for an hour and not do anything.
I think some things like 3D modelling/rendering etc are best left up to the people who know what they are doing. That's a totally alien world to Apple. I don't mean in the sense that Apple don't know what they are doing - they do but in their area of expertise. Pixar would know what was needed, The Foundry would know. I don't think Apple would know what a BRDF was if it bit them in their anisotropic aluminum ass. For that reason they wouldn't be able to offer any improvement over the competition. Until you understand what is needed to improve an industry and how to improve it then you can't. The fact that they dropped Shake and stuck with Motion shows they don't understand the industry enough. Nor do they have to, they just need to know how to make good hardware and the software to run it. Pro apps are best done by the people who rely on them and refine them daily in their workflows.
Final Cut in its present state is not what I'd call an Apple application, it's still an application Apple bought from someone else. It doesn't feel right when you use it and you get bizarre error messages or UI glitches or it runs really slow or any number of things really. When the editing works it's great, when it's not, it's infuriatingly bad. Final Cut for example shouldn't hang up when you export the timeline to compressor. That's the dumbest thing ever. Here you have a multi-tasking OS running one of the most popular NLEs feeding into a batch video compressor and when you hit export, you have to wait until that one task is done before you can do any more editing?? Why can't it process the timeline in a sub-process and just protect the source files the process is using?
It's things like Compressor taking hours to compress minutes worth of HD footage on a quad-core that says they must not be using this app regularly or they would do something about it and do it pronto. I think they will make improvements to their Pro Apps but they don't do it with the passion they have for their other apps e.g the iApps. Would it be so hard for Steve to walk out at WWDC and say 'look here's the new Final Cut and we made it 64-bit, with full Python scripting, Cocoa, new UI, faster Compressor optimised for Sandy Bridge'. Even in the 'one more thing' section is all that's needed.