In Jack’s GIF it shows the cogwheel button menu opening on the Playable Version.
There is an option in that menu called “View Source File” which will open a download to the original media.
@Ricardo_Musch That does it indeed. Thank you! I should looked at that GIF more carefully.
Followup question: Is it possible – using, for instance, a script or by some other means – to add that downloading functionality in the list view. (The more direct / fewer clicks / less friction required to download the more likely team members will adopt it into their workflow)
Yes, you could look at developing an AMI (Action Menu Item) though an SGTK app or a web service to run custom code.
For example you could use an AMI pointing at a custom python script file handler or a web service to receive a post request about what version(s) are selected and then run some APi code to get the download link and then redirect the user to the actual download link (expires every so many minutes for security reasons).
2nd Followup question: Download problem – it seems some files don’t load into the browser and therefore can’t be download. The mp4 transcodes are fine, so the original files are legible on the AWS server, but nonetheless can’t be downloaded.
The button does not allow downloading?
In that case the MP4 was transcoded by some piece of software and uploaded via the API to the MP4 field. This bypasses ShotGrid’s own transcoding service and therefore the original file is not downloadable via that button as it was not uploaded for transcoding.
I am unsure if there is a way to access the MP4 file through the API.
The button does works to the extent that it opens a browser window with a link to the media, but for reasons TBD sometimes that link shows a ‘can’t play’ media icon (see attached png) and it doesn’t download.
That might be an Apple Safari-specific icon.
Looking it over carefully, it looks like the “download media” page is really a link to a minimal HTML page with a video element with ‘src’ pointing to the S3 container. My guess is the media is browser incompatible (e.g. Avid media) causing the video object to fail, which in turn causes the download to fail.
If that’s the case AND I’m able to figure out the API approach you mentioned above, it should be possible to integrate a download feature into the “Version” list view and set up the download so that it works reliable.
RE MP4 was transcoded by some piece of software
In all cases the original media was uploaded to AWS S3, which in turn handled the transcoding BUT it’s likely a lot of that original media uses browser-incompatible codecs.