Mark Stewart Posted October 18, 2021 Report Share Posted October 18, 2021 Hi, We're a full CG studio with episodic work, and we currently use TypedContextLinks a lot, to link AssetsBuilds to Shots and Episodes which allows dynamic scene creation from ftrack info. Last week we started playing around with Custom Attribute Links and really like how searchable they are for the end user. I like it enough that, as I'm about to do a refactor on some core tools for an unrelated issue, I'm considering either linking to (or replacing outright) the TypedContextLink workflow we currently use. My worry is that I'm unsure how well it'll handle assets that end up with hundreds of links to shots over a production run. I'm curious if the speed will be similar to TypedContextLinks, as they seem somewhat related in how they work from the little that I've played with them. Do I have any real reason for concern over performance, or should I just go for it? Thanks! Mark Link to comment Share on other sites More sharing options...
altarak Posted April 11, 2022 Report Share Posted April 11, 2022 Hello Andrew ! I have found the examples related to Custom Attribute Links : https://ftrack-python-api.readthedocs.io/en/latest/example/custom_attribute_link.htmlhttps://ftrack-python-api.readthedocs.io/en/latest/example/manage_custom_attribute_configuration.html#links But I don't find its reference documentation, could you please point me to it ? (I guess it's where limitations are described, as the "50 entitites per link" you talked about) Thanks ! Link to comment Share on other sites More sharing options...
altarak Posted April 14, 2022 Report Share Posted April 14, 2022 . Link to comment Share on other sites More sharing options...
altarak Posted April 19, 2022 Report Share Posted April 19, 2022 Hi, I would like to check if I correctly understood the limit of 50 entities per link. I created a custom object, called CameraCustomObj. Then, in the Tasks list, let's pretend I created Cam01, Cam02, ..., ... Cam55. Their type is CameraCustomObj. I then created a Custom Attribute Link, as seen on the screenshot below (Shot linked to the CameraCustomObj entity). As it's a "Single-Selection" link, a shot cannot have more than one CameraCustomObj at once. Here are 2 ways of thinking about it : -A : the "50" limit does not have any effect here (it would only apply if the link was "Multi-Selection"). -B : even with "Single-Selection", if 55 entities were created (Cam01 to Cam55), this "choice among 55 entities" hits the 50 limit, and will cause problems. Is A or B true ? Cheers, Alain Link to comment Share on other sites More sharing options...
altarak Posted April 21, 2022 Report Share Posted April 21, 2022 Hi Andrew, Thanks a lot for the clarification ! And if someday we get a project that needs 1,000,000 shots, we will have to deal with challenges related to hiring thousands of people 😉 Cheers, Alain Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now