Google Drive as source

[ddurdle 75]

I do not know if it tried, but I've tried and it keeps pulling bandwidth where the emby server is installed.

 

Make sure to have passthrough = true in the settings for the videostream web ui.

[lepitismak 1]

Make sure to have passthrough = true in the settings for the videostream web ui.

 

where i can found this config?

can help me? i dont see anything about that

[lepitismak 1]

you are talking about direct path on emby for android tv?

i dont know how active this correctly.

you can help me?

[lepitismak 1]

Make sure to have passthrough = true in the settings for the videostream web ui.

 

this is on server side ou app side?

[ebr 15665]

Hi.  Please take support discussions out of this feature request topic .

[lepitismak 1]

Hi.  Please take support discussions out of this feature request topic .

 

whe this request will be apply? 

[idasa 0]

 

good night is that I have an emby server with your python script and it's good the only thing that fails me is that when he put forward a movie he stays

[lepitismak 1]

any plans for that?

[erikblues 4]

And transcodings are already available with Drive so no need to transcode with Emby server.

I always thought Google Drive would be a great feature, but the fact that transcoding can be done in the cloud is simply amazing!!! This means Emby could run on much weaker devices!!!

 

I hope to see this soon!

[chivigoku 0]

Hi there,

 

Any news?

Is there any possibility to implement this feature?

 

cheers

[Luke 40079]

Not at this time but you can use drive mounting tools as a workaround.

[chivigoku 0]

Not at this time but you can use drive mounting tools as a workaround.

 

Hi @@Luke

 

thanks for your update.

I´ve seen that @@ddurdle has this feature for Emby-servers

https://github.com/ddurdle/GoogleDrive-VideoStream_extra

 

However, I do not see the way to install it.

Has to be installed on Kodi?

 

I´ve got a Nvidia shield and I have Emby server on here

 

Thanks

[Rosario Family 2]

On 9/30/2016 at 12:39 PM, Luke said:

Cloud libraries are very much in our future plans, thanks.

2020 and the plan stayed in the cloud pretty much!!

[Carlo 4552]

Personally I'm kind of glad.  Hosting media in the cloud has never worked well overall unless you subscribe to Amazon S3 or similar for storage or built your own storage system on a colo machine or similar.

In that time frame (since 2016), a competitor came out with a completely cloud based version of their product that never really worked, spent close to 2 years trying to fix it then shut it all down wasting all the dev resources as well as burn customer bridges.

Just look at all the issues you see here in the forums with people trying to use mounted Google drives for storage and hitting obstacles outside the bounds of Emby or what Emby can control or fix.  I spend a decent amount of time each day trying to help and educate users on why Google Drive storage is a bad idea for Emby use.

From a personal standpoint I hope Emby never embraces this more than using for sync/download functionality where it can fall back to the local version if there is a problem since the amount of issues would likely sky rocket if something like this was ever officially sanctioned.

Frankly friends and family won't want to use your system if it's constantly having issues, works some days and not other days when you hit a quota Google enforces.  Almost every person would be better off purchasing one large drive or two and making the best use of it.  Having 500 to 1000 quality movies and a couple dozen TV Shows that always work is better than trying to create a "Netflix" size system filled with fluff.  A lot of people get GD working on a small or test system but as soon as they start to share it with a couple of people the usage goes up and "bang" quotas muck things up.

I know this is a feature request, but I'd highly encourage you to rethink wanting to store your media offsite with no control over outcome. Storage media is cheaper than ever and you get a lot more of it for the $ as will since 2016. It's also much faster and easier to use locally with far less headaches or growing pains.

[FancyNerd92 9]

You can do that.

For example if you have your server on Windows, install the Google Drive for Windows and then you will have the Google Drive on "This PC" near to your C:/.

After that go to your libraries and add it as you do.

Hope to help

[18star 1]

I hope to add WebDAV protocol support to Emby so that it will no longer be limited by local storage.

[adminExitium 295]

6 hours ago, 18star said:

I hope to add WebDAV protocol support to Emby so that it will no longer be limited by local storage.

In the meanwhile, you can use rclone to mount the WebDAV remote and present it as a regular FS for Emby to use: https://rclone.org/webdav/ & https://rclone.org/commands/rclone_mount/

Edited July 25, 2024 by adminExitium

[user84 36]

With all of the conversation on this forum about privacy, I am absolutely amazed that this idea would get any traction whatsoever. Very confusing.

[Luke 40079]

12 minutes ago, emrdaniels said:

With all of the conversation on this forum about privacy, I am absolutely amazed that this idea would get any traction whatsoever. Very confusing.

Hi, this is only a request and discussion at this point, just like any other feature request.

[Carlo 4552]

It's not that you can't have media in the cloud, it's how it's used.
For example, if you use any type of drive mount so cloud storage appears locally as Drive Z: or similar then Emby is going to treat it as a local drive. That's a lot of access depending on your library settings. Everyone of your media files would essentially be downloaded multiple times as different parts of the library scanning are performed. 

On the other hand, Emby supports strm files which are nothing more than a text file with the name of the movie and strm extension. It has a single text line in the file which is a URL to the media file itself.  Emby Server treats strm files differently during library scanning by not probing them for metadata but instead does this on the fly during first use. It also doesn't try to create index/bif files or do anything that would require transferring the file when not being played.  If these files originally start out on your local computer before being pushed to the cloud, you could generate index/bif files, nfo, have graphics in the directory, etc before upload.

So it's not that you can't have media in the cloud, it's that you want to do it smartly so as not to waste resources especially bandwidth that comes into play for things like Google Drive.