Shotgun is standardizing the way we handle file uploads for all hosted sites, as we work on our architecture to enable improvements in reliability and quality of image transcoding. One change coming soon is direct upload to S3. This feature will be progressively enabled on hosted sites over the nex…

Hi Zoe! [image] zoe.glynn: You have not built in retries to your file upload operations . As with the Shotgun-conduit architecture, failures will sporadically happen when uploading directly to S3. A retry on the spot typically works. Couldn’t that be implemented into the Shotgun API itself? …

When uploading media directly would we need to perform any colorspace transform to comply with browser support? I’m assuming this was/is currently handled at the middle step on the Shotgun Servers. Is their a particular codec for movie files? etc…

To be honest, we debated this heavily internally, but eventually chose not to ‘hide’ some default retry loop within the basic upload function because it came down to the caller knowing their retry context better than us. e.g. to block or not until success?, and we thought it best that people conside…

Hi Zoe! Thanks for your honest reply. I can see your point and I appreciate your efforts to make this as flexible for the community as you can! In my opinion you can keep the upload function as is and “just” add a convenience function (“upload_with_reties” ?) that catches maybe 80 percent of the r…

Hi Zoe, Just to verify, the version of tk-core (>v0.18.149) is the only adjustment which is needed for SGTK. Is this correct? I’m asking because we have a customized tk-config-default2, with a couple of customized frameworks and apps. Currently we are two versions behind the official release. Do w…

Hi Christian, correct, tk-core v0.18.149 (even though it is well behind the current official release) is sufficient to be compatible with requirements for direct upload.

Dear community, Due to the exceptional circumstances created by COVID-19, we are postponing this deprecation to April 21, 2020. The main post regarding the schedule has been updated accordingly: Deprecation of old versions of Shotgun API, RV and iOS - April 21 2020

Sorry for being off topic, but if Shotgun is moving to python API 3.0, wouldn’t that mean it is now actually compatible-“able” with Blender? Blender dropped 2.0 quite of a while ago…

Thanks for the dialogue here, Fabian, and your sample implementation to illustrate what you’re thinking of. It’s great to be able to take this back to the team, although it will be some time before we get around to revisiting what’s included in the API.

Python API (< 3.0.37) deprecation & Direct Upload to S3

Flow Production Tracking

johnny.duguid April 15, 2020, 7:24pm 34

FYI!

Topic		Replies	Views
Deprecation of old versions of Shotgun API, RV and iOS Flow Production Tracking python-api , announcement , rv , ios , deprecation	7	7694	June 16, 2020
shotgun_api3.shotgun.ShotgunError: Could not upload file successfully, but not sure why Pipeline Integrations python-api	6	2163	March 25, 2021
DIY Transcoding - how to disable automatic transcoding Flow Production Tracking	32	6107	January 24, 2023
ShotGrid Integration 1.3 Release Notes Pipeline Integrations release-notes , release-notes-english	17	5325	May 10, 2021
Movie upload issues with the api Pipeline Integrations api , python-api	5	1769	April 2, 2020

Python API (< 3.0.37) deprecation & Direct Upload to S3

Related topics