emby connect slower vs emby address

[syralk 12]

Hi

just saw that when I use Emby connect on the Roku it take more time to connect then using the real address.

I mean each time I open the app.

and the behavior only do that when I'm using remote connection.

it can take 1-2 minute to connect when I open the app if the setup is Emby connect

if the setup is using the real url and port without emby connect its instant.

and its only behaving this way remotely.

 

[Luke 37029]

The initial connection to the server might be slightly slower, but then after that it will be exactly the same.

[syralk 12]

The initial connection to the server might be slightly slower, but then after that it will be exactly the same.

So It is normal it's happen each time I open the app?

 

Sent from my ONEPLUS A3000 using Tapatalk

[Luke 37029]

It checks our Emby Connect domain for updated information. It really shouldn't be noticeable though, it's just a small data request.

[syralk 12]

It checks our Emby Connect domain for updated information. It really shouldn't be noticeable though, it's just a small data request.

Thanks

It's just do that on the Roku

On the other device emby connect is really fast.

 

 

Sent from my ONEPLUS A3000 using Tapatalk

[Luke 37029]

@@ebr will an in-app log help identify what portions of startup are taking the longest?

[ebr 14905]

Unfortunately, no as there are no time stamps in the Roku logging.  (something we should look at adding)

[Luke 37029]

ok perhaps @@speechles can do this at least for the startup portions so that we can troubleshoot this. thanks.

[speechles 1917]

The building of the timestamps is done from unixtime so there is time lost doing the conversion to something we can read(make sense of) as humans. But that aside..

 

There are two functions. Debug() and DebugT(). Debug does not waste time building timestamping nor provides it. DebugT does both.

 

My proposal would be, since in debug mode things are slower anyways an extra few milliseconds is moot. We just have debug as an alias for debugT atm.

Function Debug(message as string)
    ' add this as the first line
    DebugT(message) 
      ... rest of function continues ...
End Function

In this way for the time being everything gets timestamped on logs.. maybe this makes too much text to send in via logging with timestamps on literally everything? Maybe just do the connection manager? Let me know which way to go and I can do whichever you want.

Edited December 31, 2018 by speechles