Andriy Babak 0 Report post Posted March 5 Hi, I am currently trying to automatically get web-playable movies when publishing the sequnces of frames. I'd like to discuss whether it's an optimal way of doing this and to ask some questions. I am registering for "ftrack.location.component-added" event, get the location and the component, check if a component's "system_type" is "sequence", ask the location to provide a file system path to frames, create a movie from these frames and fire up the "ftrack.connect.publish.make-web-playable" event providing the version id and the movie file path. The movie is generated fine, the event is published but nothing new is added to my version, the movie is not there. If I try to publish these frames together with this movie manually (by selecting the movie as web-playable in the ftrack connect), everything works as expected. Any suggestions? Thank you. Regards, Andriy Share this post Link to post Share on other sites
Andriy Babak 0 Report post Posted March 5 Actually, I've been able to fix this by inspecting the "make_non_encoding_web_playable.py" example. On more question though. When the "ftrack.location.component-added" event is fired up, the event['data'] contains either "component_id" and "location_id" (when the client uses the new ftrack connect) or "componentId" and "locationId" (when the client uses the old one). So I need to check both. Is it an expected behavior? Thanks. Share this post Link to post Share on other sites
Andriy Babak 0 Report post Posted March 5 Yet another short question. I believe for this kind of plugin it makes sense to turn it into a separate script that runs on a dedicated server rather than using it as a plugin on client nodes? How do you usually deal with this situation? Thanks Share this post Link to post Share on other sites
