Jump to content

Long time to resume play from iOS, tvOS

atrpm

By atrpm
in General/Windows

 Share

Recommended Posts

atrpm

atrpm   3

Posted
Posted

Using Emby Windows Server 4.3.1.0, connecting to a Google Team (Shared) Drive, using RaiDrive (also tried NetDrive).

 

Everything works pretty good except when trying to resume play (like at minute 20 or something like that) from iOS or tvOS (latest stable versions), it take like 4 sec to resume from android/fire tv, but it takes like 25secs from iOS or tvOS.

 

Starting a show from the beginning takes 2-4secs. 

 

Not sure what could be causing this. I attached logs maybe they provide more details. In the logs I played the same media in iOS (taking a very long time to start) and then fire tv taking 4secs.

emby.log

Link to comment
Share on other sites
atrpm

atrpm   3

Posted
  • Author
Posted

Hi there, are you in or out of network when trying to do this?

 

Hi Luke, thanks for the quick reply. I'm in network. 

Link to comment
Share on other sites
atrpm

atrpm   3

Posted
  • Author
Posted (edited) 
UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 13_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
2020-03-17 15:48:56.227 Info HttpServer: HTTP Response 200 to 192.168.7.79. Time: 0ms. http://192.168.7.76:8096/emby/Items/4622/PlaybackInfo?UserId=af28729e09e2450caa5caae87afa8b07&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=140000000
2020-03-17 15:48:56.241 Info HttpServer: HTTP Response 206 to 192.168.7.79. Time: 56018ms. http://192.168.7.76:8096/emby/videos/4622/stream.mkv?DeviceId=89CA8242-EE5A-49A5-8F84-C13A6D7D2301&MediaSourceId=761234f2ce8e98dc470bfec37244f590&Static=true&PlaySessionId=ac3c6db10d264ec4963a9bccf0556f44
2020-03-17 15:48:56.248 Info HttpServer: HTTP POST http://192.168.7.76:8096/emby/Items/4622/PlaybackInfo?UserId=af28729e09e2450caa5caae87afa8b07&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=140000000. UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 13_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148

Looking at the logs, this line looks interesting... 2020-03-17 15:48:56.241 Info HttpServer: HTTP Response 206 to 192.168.7.79. Time: 56018ms

Edited by atrpm
Link to comment
Share on other sites
atrpm

atrpm   3

Posted
  • Author
Posted (edited) 
2020-03-17 17:26:53.467 Info HttpServer: HTTP GET http://192.168.7.76:8096/emby/videos/4622/stream.mkv?DeviceId=89CA8242-EE5A-49A5-8F84-C13A6D7D2301&MediaSourceId=761234f2ce8e98dc470bfec37244f590&Static=true&PlaySessionId=841dc72a2aba403fb2b45a4691e5d7e0. User-Agent=mpv 0.30.0-UNKNOWN, Accept=*/*, Range=bytes=1436582100-, Connection=close, Host=192.168.7.76:8096, Icy-MetaData=1
2020-03-17 17:26:53.472 Error HttpServer: Error processing request
	*** Error Report ***
	Version: 4.4.0.28
	Command line: C:\Users\Albert\AppData\Roaming\Emby-Server\system\EmbyServer.dll
	Operating system: Microsoft Windows NT 6.2.9200.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Runtime: file:///C:/Users/Albert/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
	System.Environment.Version: 3.1.2
	Processor count: 6
	Program data path: C:\Users\Albert\AppData\Roaming\Emby-Server\programdata
	Application directory: C:\Users\Albert\AppData\Roaming\Emby-Server\system
	System.IO.IOException: System.IO.IOException: The media is write protected. : 'Z:\path/to/media'
	   at System.IO.FileStream.Seek(Int64 offset, SeekOrigin origin)
	   at System.IO.FileStream.set_Position(Int64 value)
	   at Emby.Server.Implementations.IO.IOManager.GetResponse(HttpRequestOptions options, MediaProtocol protocol)
	   at Emby.Server.Implementations.IO.IOManager.GetResponse(HttpRequestOptions options)
	   at Emby.Server.Implementations.HttpServer.HttpResultFactory.GetContent(StaticFileResultOptions options, Int64 offset, Int64 length, CancellationToken cancellationToken)
	   at Emby.Server.Implementations.HttpServer.FileWriter.SetContentResponseHeaders(Nullable`1 reportedTotalContentLength, CancellationToken cancellationToken)
	   at Emby.Server.Implementations.HttpServer.HttpResultFactory.GetStaticResult(IRequest requestContext, StaticResultOptions options)
	   at Emby.Server.MediaEncoding.Api.Progressive.BaseProgressiveStreamingService.ProcessRequest(StreamRequest request, Boolean isHeadRequest)
	   at Emby.Server.Implementations.Services.ServiceController.GetTaskResult(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath restPath, String responseContentType, CancellationToken cancellationToken)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath, CancellationToken cancellationToken)
	Source: System.Private.CoreLib
	TargetSite: Int64 Seek(Int64, System.IO.SeekOrigin)
	
2020-03-17 17:26:53.472 Info HttpServer: HTTP Response 500 to 192.168.7.79. Time: 5ms. http://192.168.7.76:8096/emby/videos/4622/stream.mkv?DeviceId=89CA8242-EE5A-49A5-8F84-C13A6D7D2301&MediaSourceId=761234f2ce8e98dc470bfec37244f590&Static=true&PlaySessionId=841dc72a2aba403fb2b45a4691e5d7e0
2020-03-17 17:27:00.810 Info HttpServer: HTTP OPTIONS http://192.168.7.76:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 13_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
2020-03-17 17:27:00.810 Info HttpServer: HTTP Response 200 to 192.168.7.79. Time: 0ms. http://192.168.7.76:8096/emby/Sessions/Playing/Progress
2020-03-17 17:27:00.819 Info HttpServer: HTTP POST http://192.168.7.76:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 13_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
2020-03-17 17:27:00.821 Info HttpServer: HTTP Response 204 to 192.168.7.79. Time: 2ms. http://192.168.7.76:8096/emby/Sessions/Playing/Progress
2020-03-17 17:27:05.405 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs/embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36

Ok, I think I figured it out. The drive was setup to be read-only (because that user only have access to read) and I updated to the latest beta, saw this in the logs... removed the read-only setting and it seems to be working as expected now...

 

Just interesting that the issue only happens with apple products. 

Edited by atrpm
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...