Forum Replies Created
-
Posts
-
combustion can load 8/10/12/16 and float images into its workspace. the file format is the primary ??? left from your post. if you load 10 bit CIN or DPX files then yes, it can load 10 bit uncompressed files.
//gD
suggest using a format that works better like DPX or CIN
//gD
this is detailed with an entire chapter in my book thats availbale for under 17 bucks at amazon.com
“the focal easy guide to combustion 4”
selections, masks, keying and selective effects are in there with lessons on each.
//gD
maya will work fine with combustion if you stay clear of the IFF format.
//gD
you might want to look into the plugin from automatic duck with loads an avid timeline into combustion. not required but it might shave a lot of time off your pipeline – especially since it will all be you on the same system.
//garyD
@N8 24849 wrote:
I just installed Toxik today and boy is it slow. As soon as I add a reaction node it goes to pot. Any thoughts? I added a new SATA drive and installed the software on there. That is also where my mediacache is. I also moved the footage I was working with to the same drive. I upped my VM as well to like 4 gigs. I have a P4 2.8ghz with 4 gigs of ram, and I am using a Quadro FX 3450. Any thoughts?
there are a few issues you might attend to with the described setup, and others that might be due to your setup.
reaction. this can take advantage of the videocard at the hardware level or it can be bypassed. if its off, then it will still support floating point color in the processing pipeline, but interactivity of the 3d space will go down. this is by design. to enable interactivity you have to bring up the gate UI while hovering over a player, then swipe down thru the south gate to bring up the options for that player. set it to tool output and enable interactivity.
P4. toxik is extremly mutli-processor aware and designed to take advantage of it. under the hood (this is the short description) its tiling your images into 512×512 tiles. its not the same as proxies but kinda similar – and automatic. each tile is processed by a thread/core so if, for example, you have 1080 up and apply a show tiles utility node, you will see how many processors/cores that toxik woudl ideally need to process that. if you zoom out below 50% then the tiles will reduce by 4x. in short, a single P4 isnt the best solution for Toxik.
mediacache. a single sata drive wont be able to play back much more than DV/D1. add to the fact that your source media is on the same drive as the mediacache, and that poor drive is workign twice as hard as it needs to.
i hope that helps you out. some of them you can do something about immediately (the single P4 however may prove to be your biggest problem and the most difficult to remedy).
//gD
render to 16 bit or floating point for your post production work.
//gD
16bit png is not the same as 16bit half float. while 65536 total available colors in each RGB channel does provide 281 trillion color as opposed to 8 bit 16.7 million (and thats just a shitload of color to work with for things like depth of field based on grayscale etc), its not float.
when i work in float for combustion, RPF handles it much better. this is a apples and oragnes discussion to the things the RPF G-buffers offer – which are the 3d compositing and 3d post operations.
EXR half float is nice and typically way more color space than i need – but that floating point aspect means a non-destructive color space which is just great for really bright and really dark images (especially things like fire, flares, glows and other really bright things).
//gD
between max and combustion i’d go 16bit PNG unless you need float, in which case i’d use RPF over EXR. combustion doesnt handle EXR too well (as compared to Toxik).
“MaxBustion” is PNG or RPF in my book.
//gD
its the same tracker core.
you might also lower the tolerance of the tracker box slightly.
//gD
a shot breakdown or storyboard is typically required to even start the bid process. good luck with the project!
//gD
thanks very much, ken. your generosity is only exceeded by your frequent flyer miles.
//gD
@PiXeL_MoNKeY 24418 wrote:
2. As stated 4 gb, but as I have said on other forums, don’t expect 64bit anytime soon. If they made Combustion 64bit today you would lose Quicktime and AE plugin support. Once a program goes 64bit all plugins and associated libraries used by the program must be 64bit. Since neither Apple, Adobe, or their 3rd party developers have gone 64bit don’t expect Combustion to go 64bit.
3ds Max and Maya offer 32 and 64 bit versions with the purchase of the application (you get both). also, toxik supports 64bit on linux and while the current build on windows is 32bit, many of us run it on 64 bit and its supported bu the mothership.
//garyD
exactly correct.
denim illuminare
>>>
discreet logic paint and effect (two apps)
>>>
discreet combustion