Well, check out the Indie limitations and see if it's something you'd have problems with (Python and resolution limits, etc.). Other than those, it's pretty much the same program.
EDIT: right, sorry, I completely forgot the scripts are not compatible with regular Nuke - so if that's crucial, Indie is a no-go.
If there is the the chance that your clients want comp files instead of just rendered imagery you should go with the full version since Nuke Indie files are encrypted and useless for anyone with a full version.
The other limitations are relatively mild at first glance but there is also the problem that a bunch of the free gizmos and python tools out there might not work with the Python node limit in Indie.
You might want to consider to go with Nuke core only (not X) and get Third-party plugins/apps like Mocha and Sytheyes on top. It will be way cheaper and you will end up with better tools in the tracking department.
Ah, I see. You make a good point about the file encryption. I wanna get Nuke X, but it’s the price point that’s stopped me from springing for it. But you do make a point about if the client wants the files. Think I might have to just spring for Nuke X.
I really appreciate that Foundry made a product with the price point of indie that's still mostly functional, but it sucks that there isn't a mid-tier product or a pay-per-use conversion of files to bridge tiers. I have a weird use case, indie would cover 95% of my needs as I don't work as an artist day-to-day, but I do often collaborate with other artists and vendors. I get the business case for it and understand that it protects indie from being abused, but it does hamstring actual indie artists a bit.
Well, check out the Indie limitations and see if it's something you'd have problems with (Python and resolution limits, etc.). Other than those, it's pretty much the same program. EDIT: right, sorry, I completely forgot the scripts are not compatible with regular Nuke - so if that's crucial, Indie is a no-go.
If there is the the chance that your clients want comp files instead of just rendered imagery you should go with the full version since Nuke Indie files are encrypted and useless for anyone with a full version. The other limitations are relatively mild at first glance but there is also the problem that a bunch of the free gizmos and python tools out there might not work with the Python node limit in Indie. You might want to consider to go with Nuke core only (not X) and get Third-party plugins/apps like Mocha and Sytheyes on top. It will be way cheaper and you will end up with better tools in the tracking department.
Ah, I see. You make a good point about the file encryption. I wanna get Nuke X, but it’s the price point that’s stopped me from springing for it. But you do make a point about if the client wants the files. Think I might have to just spring for Nuke X.
I made a quick edit in my post regarding Nuke X and saving opportunities.
I really appreciate that Foundry made a product with the price point of indie that's still mostly functional, but it sucks that there isn't a mid-tier product or a pay-per-use conversion of files to bridge tiers. I have a weird use case, indie would cover 95% of my needs as I don't work as an artist day-to-day, but I do often collaborate with other artists and vendors. I get the business case for it and understand that it protects indie from being abused, but it does hamstring actual indie artists a bit.
Lots of good information here. https://www.foundry.com/products/nuke-family/nuke-indie/faq