Jump to content

Unable to access settings

Jdiesel

By Jdiesel
in Roku

 Share

Recommended Posts

ebr Emby Team

ebr   14910

Posted
Posted

Luke - look at this.  Looks like the server is sending across the raw image instead of a resized/cached one:

2017-09-14 09:32:34.657 Info HttpServer: HTTP GET http://xxxxxx/emby/Items/9b04e01bbaac5e89aa060a176cd3c6a0/Images/Primary/0?EnableImageEnhancers=true&tag=7936d74fd9345e1f5dab6fce96a3b6d6&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 09:32:34.658 Info HttpResultFactory: Transmit file /mnt/storage/movies/My Pet Dinosaur (2017)/poster.jpg
2017-09-14 09:32:34.658 Info HttpServer: HTTP Response 200 to xxxxxx. Time: 1ms. http://xxxxxx/emby/Items/9b04e01bbaac5e89aa060a176cd3c6a0/Images/Primary/0?EnableImageEnhancers=true&tag=7936d74fd9345e1f5dab6fce96a3b6d6&maxheight=350 
2017-09-14 09:32:34.677 Info HttpServer: HTTP GET http://xxxxxx:8096/emby/Items/f7e95069c7014136a9676bd675108e33/Images/Primary/0?EnableImageEnhancers=true&tag=ada7068866f2e4612b2581423bf30a2c&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 09:32:34.677 Info HttpResultFactory: Transmit file /mnt/storage/movies/Despicable Me 3 (2017)/poster.jpg
2017-09-14 09:32:34.678 Info HttpServer: HTTP Response 200 to xxxxx. Time: 1ms. http://xxxxx/emby/Items/f7e95069c7014136a9676bd675108e33/Images/Primary/0?EnableImageEnhancers=true&tag=ada7068866f2e4612b2581423bf30a2c&maxheight=350 
2017-09-14 09:32:34.695 Info HttpServer: HTTP GET http://xxxxxx/emby/Items/1f22a1922fcdc63cbb0cf3e3e59fea1b/Images/Primary/0?EnableImageEnhancers=true&tag=e54cd172dc1686ceac561847e5f5932e&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 09:32:34.696 Info HttpResultFactory: Transmit file /mnt/storage/movies/Slackers (2002)/poster.jpg

By contrast, from my server:

2017-09-14 11:45:27.810 Info HttpServer: HTTP Response 200 to 192.168.1.137. Time: 249ms. http://192.168.1.134:8096/emby/Items/3be6be0117b0c63a200df0c1c3282cc4/Images/Primary/0?EnableImageEnhancers=true&tag=d8ba2956be36276b92645ef14def8c0c&maxheight=350 
2017-09-14 11:45:27.825 Info HttpServer: HTTP GET http://192.168.1.134:8096/emby/Items/5dbd1ba2ae321744b14720ecf528941b/Images/Primary/0?EnableImageEnhancers=true&tag=000bf7d02d6ae29915a2a9f212ca7081&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 11:45:27.826 Info HttpResultFactory: Transmit file C:\Users\spam\AppData\Roaming\Emby-Server\cache\images\resized-images\1\118272b7-6776-a9bd-88ed-6004bdca21f3.jpg
2017-09-14 11:45:27.829 Info HttpServer: HTTP Response 200 to 192.168.1.137. Time: 4ms. http://192.168.1.134:8096/emby/Items/5dbd1ba2ae321744b14720ecf528941b/Images/Primary/0?EnableImageEnhancers=true&tag=000bf7d02d6ae29915a2a9f212ca7081&maxheight=350 
2017-09-14 11:45:27.850 Info HttpServer: HTTP GET http://192.168.1.134:8096/emby/Items/f653e0fabefb4753feef5053439caf65/Images/Primary/0?EnableImageEnhancers=true&tag=8d953a366ba1bec67841269f4e476699&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 11:45:27.851 Info HttpResultFactory: Transmit file C:\Users\spam\AppData\Roaming\Emby-Server\cache\images\resized-images\f\f953ce5c-cea3-ec47-7598-94d3c44696cd.jpg
Link to comment
Share on other sites
Jdiesel

Jdiesel   1113

Posted
  • Author
Posted

 

Luke - look at this.  Looks like the server is sending across the raw image instead of a resized/cached one:

2017-09-14 09:32:34.657 Info HttpServer: HTTP GET http://xxxxxx/emby/Items/9b04e01bbaac5e89aa060a176cd3c6a0/Images/Primary/0?EnableImageEnhancers=true&tag=7936d74fd9345e1f5dab6fce96a3b6d6&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 09:32:34.658 Info HttpResultFactory: Transmit file /mnt/storage/movies/My Pet Dinosaur (2017)/poster.jpg
2017-09-14 09:32:34.658 Info HttpServer: HTTP Response 200 to xxxxxx. Time: 1ms. http://xxxxxx/emby/Items/9b04e01bbaac5e89aa060a176cd3c6a0/Images/Primary/0?EnableImageEnhancers=true&tag=7936d74fd9345e1f5dab6fce96a3b6d6&maxheight=350 
2017-09-14 09:32:34.677 Info HttpServer: HTTP GET http://xxxxxx:8096/emby/Items/f7e95069c7014136a9676bd675108e33/Images/Primary/0?EnableImageEnhancers=true&tag=ada7068866f2e4612b2581423bf30a2c&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 09:32:34.677 Info HttpResultFactory: Transmit file /mnt/storage/movies/Despicable Me 3 (2017)/poster.jpg
2017-09-14 09:32:34.678 Info HttpServer: HTTP Response 200 to xxxxx. Time: 1ms. http://xxxxx/emby/Items/f7e95069c7014136a9676bd675108e33/Images/Primary/0?EnableImageEnhancers=true&tag=ada7068866f2e4612b2581423bf30a2c&maxheight=350 
2017-09-14 09:32:34.695 Info HttpServer: HTTP GET http://xxxxxx/emby/Items/1f22a1922fcdc63cbb0cf3e3e59fea1b/Images/Primary/0?EnableImageEnhancers=true&tag=e54cd172dc1686ceac561847e5f5932e&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 09:32:34.696 Info HttpResultFactory: Transmit file /mnt/storage/movies/Slackers (2002)/poster.jpg

By contrast, from my server:

2017-09-14 11:45:27.810 Info HttpServer: HTTP Response 200 to 192.168.1.137. Time: 249ms. http://192.168.1.134:8096/emby/Items/3be6be0117b0c63a200df0c1c3282cc4/Images/Primary/0?EnableImageEnhancers=true&tag=d8ba2956be36276b92645ef14def8c0c&maxheight=350 
2017-09-14 11:45:27.825 Info HttpServer: HTTP GET http://192.168.1.134:8096/emby/Items/5dbd1ba2ae321744b14720ecf528941b/Images/Primary/0?EnableImageEnhancers=true&tag=000bf7d02d6ae29915a2a9f212ca7081&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 11:45:27.826 Info HttpResultFactory: Transmit file C:\Users\spam\AppData\Roaming\Emby-Server\cache\images\resized-images\1\118272b7-6776-a9bd-88ed-6004bdca21f3.jpg
2017-09-14 11:45:27.829 Info HttpServer: HTTP Response 200 to 192.168.1.137. Time: 4ms. http://192.168.1.134:8096/emby/Items/5dbd1ba2ae321744b14720ecf528941b/Images/Primary/0?EnableImageEnhancers=true&tag=000bf7d02d6ae29915a2a9f212ca7081&maxheight=350 
2017-09-14 11:45:27.850 Info HttpServer: HTTP GET http://192.168.1.134:8096/emby/Items/f653e0fabefb4753feef5053439caf65/Images/Primary/0?EnableImageEnhancers=true&tag=8d953a366ba1bec67841269f4e476699&maxheight=350. UserAgent: Roku/DVP-7.70 (297.70E04144A)
2017-09-14 11:45:27.851 Info HttpResultFactory: Transmit file C:\Users\spam\AppData\Roaming\Emby-Server\cache\images\resized-images\f\f953ce5c-cea3-ec47-7598-94d3c44696cd.jpg

 

As mentioned no image processors are installed

2017-09-14 09:02:31.662 Error Main: Skia not available. Will try next image processor.
2017-09-14 09:02:31.664 Error Main: ImageMagick not available. Will try next image processor
Link to comment
Share on other sites
ebr Emby Team

ebr   14910

Posted
Posted

 

As mentioned no image processors are installed

2017-09-14 09:02:31.662 Error Main: Skia not available. Will try next image processor.
2017-09-14 09:02:31.664 Error Main: ImageMagick not available. Will try next image processor

 

Yes, but the server should not be sending the full-sized original image.  It should be re-sized to the requested size and then sent out of the cache.

 

Oh, wait - the server can't resize the image because you literally have no image processing library available in your setup.  Well, that is going to be a performance problem for not just Roku but probably a lot of apps.

 

Luke, can we fall back to GDI in this instance just to do rudimentary re-sizing?

Link to comment
Share on other sites
Luke Emby Team

Luke   37049

Posted
Posted

If that's the problem then i wouldn't worry about it because that will be solved once we have the .net core server in an install package.

Link to comment
Share on other sites
Jdiesel

Jdiesel   1113

Posted
  • Author
Posted

 

  1. Uninstall the app.
  2. Bring down your server so that the app won't find it automatically
  3. Start the Roku app and let it go to the Connect screen

 

Now you can bring up whichever server you want and manually connect to it.

 

 

This doesn't seem to work. Still not able to get the login screen to show up.

Link to comment
Share on other sites
speechles Emby Team

speechles   1917

Posted
Posted

Try and delete the roku apps/devices from the devices tab of the server. Then repeat the steps ebr gave. This should make a fresh start.

 

In blue neon, when on the user login screen (use sign out if logged in) there is an option to "clear registry" with a little garbage can all the way to the right. You can use this to clear what blue neon remembers, you dont need to uninstall/reinstall to do this. After click garbage can, press home, and then reopen app.

 

With the official app, you can do this too...but...not until you login. Until you login, no "clear registry" for you!

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites
Jdiesel

Jdiesel   1113

Posted
  • Author
Posted

Try and delete the roku apps/devices from the devices tab of the server. Then repeat the steps ebr gave. This should make a fresh start.

 

In blue neon, when on the user login screen (use sign out if logged in) there is an option to "clear registry" with a little garbage can all the way to the right. You can use this to clear what blue neon remembers, you dont need to uninstall/reinstall to do this. After click garbage can, press home, and then reopen app.

 

With the official app, you can do this too...but...not until you login. Until you login, no "clear registry" for you!

 

Sent from my Nexus 7 using Tapatalk

No luck. I even went as far as deleting my devices folder in the data directory. Tried loading the app with no network connection and not nothing happens but a spinning circle. BlueNeon loads fine though.

 

Are there any files accessible on the Roku via the telnet connection? Is it possible to debug?

Link to comment
Share on other sites
speechles Emby Team

speechles   1917

Posted
Posted (edited)

Unfortunately, the roku boxes all have their own embedded publisher ID. To get debug, the package must be uploaded to that device. This means you need a .zip of the app. Then when you upload this to your device it is signed with your publisher ID. If the publisher ID of the roku running the app matches the one signed in the app and the app is running in "dev" space you can get debug. Only one zip can exist in dev space at a time. You can tie several roku to the same publisher ID, but the same restrictions apply to all. This means until emby team makes an open source roku app again, they are the only ones who can debug your issue.

Edited by speechles
Link to comment
Share on other sites
ebr Emby Team

ebr   14910

Posted
Posted

 Tried loading the app with no network connection and not nothing happens but a spinning circle. 

 

No, I imagine this won't work - you should get a warning from the Roku device itself.

 

What I wanted you to do was just bring down your Emby Server so the app wouldn't find it.

Link to comment
Share on other sites
Jdiesel

Jdiesel   1113

Posted
  • Author
Posted

No, I imagine this won't work - you should get a warning from the Roku device itself.

 

What I wanted you to do was just bring down your Emby Server so the app wouldn't find it.

 

I had also tried this, stopped the server for a few minutes then tried loading the app and the same thing occurred. I have done multiple factory resets on the Roku, removed and reinstalled the app, tried the beta and the stable version, deleted devices from my server, nothing allows me to get into the app. I am able to use the BlueNeon app though. I suspect it has something to do with firmware 8.0 and the offical app itself. So it appears that until the app is updated to support 8.0 or Roku downgrades my Roku I will not be able to use my Roku for Emby.

Link to comment
Share on other sites
Jdiesel

Jdiesel   1113

Posted
  • Author
Posted

Roku issued an update which either overwrote/cleared some settings or fixed the issue. I was able to get to the login page and login to my Mono server.

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...