SIGN IN
::
SPONSORS
::
ABOUT US
::
CONTACT US
FORUMS
TUTORIALS
MAGAZINE
TRAINING
VIDEOS - REELS
PODCASTS
EVENTS
SERVICES
NEWSLETTER
NEWS
BLOGS
AUTODESK COMBUSTION:
Autodesk Combustion Forum
Autodesk Combustion Tutorials
Autodesk Combustion
Autodesk
Re: Why does AD bother with desktop Compositors?
Cow Forums
:
Autodesk Combustion
VIEW POSTS
•
ADD A NEW POST
•
SEARCH
•
CHANGE FORUM
Respond to this post
•
Return to posts index
•
Read entire thread
Re: Why does AD bother with desktop Compositors?
by
Eric Craft
on Jan 30, 2009 at 2:00:56 pm
[Don Nash]
"Especially regarding this "64bit Combustion shtick" you're on.
You talk about busted plugins and QT not being 64 bit as barriers. Maybe the Dev's for Toxic, Nuke and Fusion didn't get your memo.
Bad move on their part, right? Do you think we're retarded? Do you think you're the only on the forums that happens to be a bit tech savvy?"
1) None of the upper end compositors are tied to a 32 bit SDK for plugins. They all use the same OFX format for plugins, not the AE SDK. So it would mean a complete rewrite of Combustion, and I simply don't see that happening with Toxik already being available in the Nuke and Fusion market segment.
[Don Nash]
"Your 64bit argument erroneously presumes that Autodesk would ONLY develop a 64bit version! Who does that? Please...do tell. Who do you know that has come out with ONLY a 64bit version? Since there are none, why do you persist with this "they can't do it cause it will break some eggs" argument? Of course that version will have some plugins that won't work until the 3rd party dev's get on board. Now here's the complicated part...
OTHER PROGRAMS OFFER A 32Bit VERSION TOO, FOR JUST THAT REASON."
If they were to do that with the current version then there would be incompatiblities between the 2 versions. They aren't going to develop one version on the AE SDK and the other on OFX just to make it 64bit and 32bit. Again meaning a complete rewrite, which I seriously doubt is going to happen since the largest amount of the development time is going into Toxik.
[Don Nash]
"Now, regarding the higher end vs the lower end...go to AD's mainpage. See how easy it is to find information for the big guns vs. the pea-shooters (Combustion and Toxic). Then go to Adobe's website (whom also has numerous software titles)and see how fast you can find info on AE. Need I say more?
The issue about selling off software...well, they supposedly aren't getting enough $$$ from Combustion (no development...no $$$...gee, I wonder why?), and they aren't gaining any sort of a foothold with Toxic. In an economically turbulent time, that's generally what companies do, right Mr. Gates? If it's not viable enough for them to develop, do you think they feel threatened by it in someone else's hands?"
Be realistic about this, the package will either linger till its dead, or hopefully they will put some money into it, but I don't know 1) any company who could afford to buy it, or 2) why Autodesk would sell it. Remember Avid sold XSI to try and put a dent in the $66.4 million loss they were in for the quarter (they only got $35 million for Softimage).
[Don Nash]
"All this flap about Toxic being Combustion's replacement is junk, IMHO. Toxic was from the start aimed DIRECTLY at film compositing. Combustion has always been an all-around backroom workhorse...a "Jack of all trades, and master of none." If AD earnestly expects Combustion users, whom they alientated for the past 5yrs with virtually no development and no word on any...to gleefully jump into Toxic's lap, think again! When Toxic does all that Combustion does, then you have a point. Perhaps if AD would communicate with their customers a bit, we wouldn't be having this discussion."
I totally agree that Toxik lacks the majority of Combustions Motion Graphics capabilities. That is why I say improve Combustion in that area and improve Toxik on the compositing side. 1) It gives you a way to bundle the 2 packages, 2) they are now in different market segments and can compete with the other packages that match in features and price point. Making Combustion a mini Toxik isn't going to help Toxik or Combustion, IMHO.
[Don Nash]
"Differing opinions is one thing, but you insist on appointing yourself as the subject matter expert and Fact Police everywhere you go. If you must continue with that attitude, I'd hope you'd save yourself some time and frustration by not responding or simply put me on your ignore list."
That is true, but if you are going to making statements then you should know the facts. In alot of the cases people don't realize the reliance Combustion has on 3rd party SDKs that are only 32bit and think it would be a simple check box in the compilier to make it 64bit. If it was that easy they would have done it by now. The other thing is I take the time to talk with people such as resellers and those in charge of Combustion. Don't expect to get any insider information, because the employees enjoy their jobs and I don't want to risk losing it giving away information, or they simply may not have answers. The long a short of it is, you need to talk to those who actually know what is going on (and more than one person), but you need to take it all with a grain of salt.
Combustion is still alive until they officially no longer offer it as a package and anything can happen, but you need to be realistic about what can be done with it. Things like 64bit and getting higher end features that Toxik already has probably isn't going to happen. If you want the features in Toxik, Fusion, and Nuke then you probably need to look at buying one of them, because IMHO that is the only place you will get those features.
-Eric
Respond to this post
•
Return to posts index
•
Read entire thread
Current Message Thread:
Why does AD bother with desktop Compositors?
by Don Nash on Jan 29, 2009 at 1:11:05 pm
Re: Why does AD bother with desktop Compositors?
by Greg Gilpatrick on Jan 29, 2009 at 6:01:43 pm
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Jan 29, 2009 at 9:57:17 pm
Re: Why does AD bother with desktop Compositors?
by Don Nash on Jan 30, 2009 at 12:57:48 pm
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Jan 30, 2009 at 2:00:56 pm
Re: Why does AD bother with desktop Compositors?
by Alex Udell on Jan 30, 2009 at 8:48:16 pm
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Jan 31, 2009 at 12:00:49 am
Re: Why does AD bother with desktop Compositors?
by Don Nash on Jan 31, 2009 at 9:03:14 am
Re: Why does AD bother with desktop Compositors?
by Alex Udell on Jan 31, 2009 at 4:36:27 pm
Re: Why does AD bother with desktop Compositors?
by Don Nash on Jan 31, 2009 at 6:24:59 pm
Re: Why does AD bother with desktop Compositors?
by Matthew Beall on Feb 2, 2009 at 4:58:47 am
Re: Why does AD bother with desktop Compositors?
by Alex Udell on Feb 2, 2009 at 5:08:23 pm
Re: Why does AD bother with desktop Compositors?
by Don Nash on Feb 3, 2009 at 1:37:39 am
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Jan 31, 2009 at 4:53:59 pm
Re: Why does AD bother with desktop Compositors?
by Aaron Neitz on Jan 31, 2009 at 7:04:39 pm
Re: Why does AD bother with desktop Compositors?
by Don Nash on Jan 31, 2009 at 7:09:08 pm
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Jan 31, 2009 at 8:07:06 pm
Re: Why does AD bother with desktop Compositors?
by Dean DeCarlo on Feb 3, 2009 at 6:13:14 am
Re: Why does AD bother with desktop Compositors?
by Jeff Brown on Feb 3, 2009 at 7:40:07 pm
Re: Why does AD bother with desktop Compositors?
by Dean DeCarlo on Feb 3, 2009 at 7:44:25 pm
Re: Why does AD bother with desktop Compositors?
by Jeff Brown on Feb 4, 2009 at 1:17:18 pm
Re: Why does AD bother with desktop Compositors?
by Matthew Beall on Feb 4, 2009 at 2:14:52 pm
Re: Why does AD bother with desktop Compositors?
by Dean DeCarlo on Feb 4, 2009 at 3:07:24 pm
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Feb 4, 2009 at 11:25:18 pm
Re: Why does AD bother with desktop Compositors?
by Alex Udell on Feb 5, 2009 at 12:51:27 am
Re: Why does AD bother with desktop Compositors?
by Matthew Beall on Feb 5, 2009 at 1:16:27 am
Re: Why does AD bother with desktop Compositors?
by Alex Udell on Feb 5, 2009 at 1:20:40 am
Re: Why does AD bother with desktop Compositors?
by Eric Craft on Feb 5, 2009 at 2:17:34 am
Re: Why does AD bother with desktop Compositors?
by amir Qureshi on Feb 8, 2009 at 9:05:07 pm
Note:
If you are a registered user please
click here to login
before posting.
Your post will not be accepted if your name and email address are not registered in our database. Click
here
if you do not have an account.
Name
E-Mail Address
Subject
E-Mail me when someone responds
Just This Message
Entire Thread
None
Message:
Note:
The following are HTML characters and may cause parts of your post to disappear if not used correctly: < > &
To include any portion of the post in your response, highlight the desired text and hit the "Q" key.
Read more...
Add your message signature
Note:
By clicking "Post Direct" button above, you are agreeing to the Creative Cow's
Code of Conduct
.
FORUMS
•
TUTORIALS
•
MAGAZINE
•
TRAINING
•
VIDEOS - REELS
•
PODCASTS
•
EVENTS
•
SERVICES
•
NEWSLETTER
•
NEWS
•
BLOGS
©
CreativeCOW.net
All rights are reserved.
[
Top
]