[dmdsoftware]

Does it fail with playback with cache (as with cache, authentication headers are not passed on as python does the downloading of the content)?

Playing with cache works, but it then doesn't download fast enough from gDrive. To clarify: it works, it starts caching, it starts playback. Once playback starts, it appears not to be downloading as fast as it should (and could) and after a little while it drops back to the Kodi interfaces with the file downloading.

During the caching period I see bandwidth use in excess of 50Mbps. Once playback starts, it drops significantly... with just occasional peaks but insufficient to keep on playback. Which at a certain point, stops and goes back to Kodi with "downloading" in the top right corner. Also, when this happens, download speed does not pick up again but keeps this "pattern" of slow speeds (and in Kbps) and occasional spikes to 30Mbps.

And... well, I tried caching with regular DVDPlayer... it starts right but then it slows down and playback doesn't even start. With both players it cached about 350MB of a very big file. In both cases it slowed down after, DVDPlayer simply didn't start. DSPlayer started (playing what was in cache) and then exited once the cache was depleted.
Here it is, happening on DVDPlayer: http://xbmclogs.com/pn0sgezqv

The only thing that works flawlessly is DVDPlayer with no cache use (using just the internal Kodi cache, appropriately incremented).

And, by the way, I asked nevcariel (developer of LAV Filters, used by DSPlayer), this is what he had to say about authentication headers: http://forum.doom9.org/showthread.php?p=...ost1759110

I'll review your attached log to validate there are is no issue become encountered that shouldn't be.

In general, original streaming I moved to alt=media which proved to resolve "slowness" issues for a lot of users, as it tells Google you are a media player so stream it accordingly. Prior, I used it without, which tells Google to treat the download request as a regular download. Some users had issues maximizing their bandwidth with this method. I'm going to add an option to toggle it to see if that improves it for you. From my perspective I saw no speed changes between the two methods, but there were a number of users who reported issues with the original method that rejoiced with the change.

I don't have an account on doom9 and I'm having an issue trying to post to that thread. Can you post a clarification request?

"KODI allows passing along additional header information in a HTTP/HTTPS request by passing it along in the URL with a |. Such as a URL "https://www.google.ca|Authentication: Bearer 1234" which would attach Authentication: Bearer 1234 to the header of the request. Is there an equivalent way to pass long authentication information that can be appended to the header of the http request? See http://forum.kodi.tv/showthread.php?tid=77500 -- note this has been implemented in KODI since v12"