2019-03-17, 20:49
@cguZZMan another question for you.
By looking at logs, I see that the actual file being played back comes from a call to http://127.0.0.1:60325/download/ followed, I'm guessing, by DriveID and ItemID, and ending with the actual filename.
Does this solution equals to streaming a file through the http protocol? I ask because using Kodi DSPlayer using VideoPlayer (the default player in Kodi) generates a little number of download events (checked in the admin console in Google), whereas using DSPlayer (which uses DirectShow filters) generates a *huge* number of download events. I'd like to better understand how the file actually reaches the player, as that might give me hint to properly configure DirectShow filters in order to limit the number of download events.
Thank you.
By looking at logs, I see that the actual file being played back comes from a call to http://127.0.0.1:60325/download/ followed, I'm guessing, by DriveID and ItemID, and ending with the actual filename.
Does this solution equals to streaming a file through the http protocol? I ask because using Kodi DSPlayer using VideoPlayer (the default player in Kodi) generates a little number of download events (checked in the admin console in Google), whereas using DSPlayer (which uses DirectShow filters) generates a *huge* number of download events. I'd like to better understand how the file actually reaches the player, as that might give me hint to properly configure DirectShow filters in order to limit the number of download events.
Thank you.
