Now that we can playback from a local web-server the next step is a full local media server to cover all our needs :)
Currently Shotgun stores thumbnails, videos and attachments it the cloud. For many scenarios this is very convenient.
But for all those under strict security restrictions it means they have a bare shotgun without thumbnails, videos, attachments and without the awesome WebPlayer.
One approach would obviously be to host Shotgun locally and another to only have an internal media server while keeping Shotgun in the cloud.
It's obviously a bigger project but I thought the media server option could be explored here and if there is a lot of community interest Shotgun might consider implementing it.
So here is what I assume the current workflow to be:
- media gets into shotgun via the browser and via the API
- first it gets uploaded to the shotgun server and then forwarded to S3 for optional trans-coding and then storage
- for play-back/download the Shotgun back-end generates a temporary URL to allow the client to download/stream the data from S3 again
- if an attachment is deleted its removed from S3 storage
Here is what the workflow for a LMS (local media server) could be:
- the URL for our local storage is stored in the shotgun settings
- during browser or API based upload first an attachment ID is generated and then the attachment is uploaded to LMS via WebDAV/FTP with the attachment ID
Regarding the LMS it would be best if it was a pre-configured virtual machine/docker image provided by Shotgun with components like web server, NFS/CIFS support, queue (like redis), trans-coding tools (like ffmpeg):
- Allow for trans-coding and image resizing to be done on the machine
- The queue would also allow to distribute the trans-coding workflow over multiple LMS VM's
- The machine would be stateless and mount an external storage for storing data and configuration so there would never be any upgrade issues (just the VM gets swapped)
So would it be critical for your studio too? What other requirements does your studio have? etc.
Thanks for joining the discussion and helping LMS to become a reality some day soon!