The thing about any pipeline tool is that you need to do some tinkering to suit your workflow. No, you wouldn’t use AYON if you are already using Shotgrid/FTrack/NIM/Kitsu managing your pipeline. There are certainly scenarios however where you would use FTrack or Kitsu for shot management but use AYON to manage your pipeline.
As AYON is opensource, if you’ve got someone cluey or a TD, you could get AYON to have the same functionality as Flame at just the cost of your TD. Or you can even engage Ynput to write those integrations for you.
The thing I love most about AYON is that it has a GUI tool to build custom pipelines for each project where someone like me who only has enough python skills to break stuff can design a whole pipeline using tokens. Very cool. The shot management tools in AYON are also improving.
@ALan - if you already have ftrack installed, and you only use flame for shots, then this is a good way to show that you can add one shot to ftrack, in a way that ties in with other ftrack users.
that’s a good demo.
(of adding one shot, maybe multtiple shots?, maybe multiple shots sequentially or simultaneously?)
does it publish and track batch renders?
can you do a sequence publish from scratch and create shots from flame?
To me it seems you have to launch Flame from their webgui for a particular shot for it work. that doesn’t fly.
Never heard of clickup… but of course it’s trusted by a gazzilion big name companies… … like… every… other… tool … out … there… Amazing. Must be a mess at IBM, them using all these platforms at once.
Yea its more like airtable or just a super flexible project management tool that we sorta like to use because it combines wiki and office planning and shot tracking in one, its all a bit hacky but we are building shot publishing and tools on top of it.
