As a hobby, I've been helping some emby users setup their Emby to use Google Drive as a media source. There are "traditional" methods such as mounting the drive as a mount point or windows drive, but there is performance impact and affect on google drive quotas.
I've written a bunch of open-source software that can setup your Google Drive as a media source for Emby, via the support for STRM files. Once deployed, the solution is self-maintaining -- new video files added to your Google Drive are automatically exported into STRMs and imported into Emby.
Another big advantage with this solution is transcoding. With a tweak, transcoding requests are now handled through Google Drive transcoding, relieving critical CPU cycles on the emby server.
The setup is a bit complicated. And although it works on Windows (I have a number of users who report back they are successfully using the setup in Windows), there is no "magic EXE" a user can download to run -- the code is in Python, so every other operating system comes with everything you need, but on windows, you'll need to setup Python. The preferred system configuration is a debian-based linux (including ubuntu). There will be plans to eventually push out a EXE file for Windows users, but it is not high on my priority list.
For the adventurous, you can setup the install yourself. But I've been lending my time (no cost) to help deploy and setup user's Emby Google Drive host. The proper setup that runs everything with optimal performance (in particular google transcoding) can be time consuming and confusing. I have deployed complete entire new GCE spun instances in as little as 30 mins, purely because I've done it enough times.
Hardware wise, there is no additional memory or cpu requirements for the code. It is designed to run on the Emby host, but it can also run on a different server. I've successfully setup working installs on as little as 256MB VPS. It'll also work fine on shared vCPU instances (free tier) on Google Compute Engine. All my test servers are hosted in GCE. The extra ram offered in the 1 vCPU package will provide great speed improvements for navigation of large libraries (by leveraging the extra ram to host the emby sqlite ibrary.db file).
I'm willing to work with new users who want to get this setup for their family, by offering my time to help speed up the setup by working with you on setting up the instances. I ask, in turn, that you support Emby by purchashing premier. All the user's I have helped were very happy with the setup that they had no issue supporting Emby by purchasing Emby premier.
If you want to help you with your setup or help you get hosted on GCE, reply here or direct message me.
If you want to setup yourself, the github links are below. Please feel free to provide feedback and request features through "issues" on github.
the service that delivers the Google Drive media:
some additional optional scripts for emby for tweaking features with regards to Google Drive hosted content:
I'm not affiliated with Emby. I'm also not doing this as a business, but as a hobby (I already have a full time job). I don't work with any hosting providers and will not recommend any hosting service provider beside Google Compute Engine. I've always been interested in movies and tv and "the cloud".