Jump to content


Photo

Emby and Emby Beta share the current connected server


Best Answer speechles , 05 March 2019 - 04:08 PM

This should be expected.

 

The reason is because of how Roku treats the storage space of the registry. It is not per application. It is per developer ID associated with your application. Yes you read that right. If you change developer ID you have to keep a separate Roku now for anything using the old developer ID. If you develop several apps that need their own storage space in the Roku registry each must be developed on their own unique Roku box. Yes you read that right it is not a typo. For each app you develop on Roku that you want separate space needs it own Roku. You make 4 apps and you want unique space on all 4? You need 4 Roku.

 

To do it with Emby your main box has your main developer ID. Now on your second Roku box you can set a second developer ID. Then use this to develop the Beta on.

 

In keeping these two developer ID separate is alot more work for very little gain to end users. It will slow down things and possibly cause problems if we forget any of the above and which box to develop each application on to generate the PKG. To keep all of this all from unravel and possibly cause us headaches it must be a single developer ID for both. Hopefully you understand. The app ID an app is assigned is merely a convenience to launch/install the app from the Roku store. It isn't really used to track the registry.

Go to the full post


  • Please log in to reply
4 replies to this topic

#1 pcm2a OFFLINE  

pcm2a

    Advanced Member

  • Members
  • 136 posts
  • Local time: 10:37 AM

Posted 05 March 2019 - 03:47 PM

Is it by design that if you log into server 1 with Emby, exit and launch Emby beta you are looking at the same server? It might be nice if these were totally separated instances where Emby could be connected to server 1 and Emby Beta could be connected to server 2 for some beta testing.

 

Steps to reproduce.

1. Install Emby on roku

2. Install Emby Beta on roku

3. Launch Emby and connect to server 1

4. Exit Emby

5. Launch Emby Beta and notice you are automatically connected to server 1

6. Switch to server 2

7. Exit Emby Beta

8. Launch Emby and notice you are automatically connected to server 2


Edited by pcm2a, 05 March 2019 - 03:53 PM.


#2 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15171 posts
  • Local time: 04:37 PM
  • LocationKent, England.

Posted 05 March 2019 - 03:49 PM

Each Emby server needs to use a unique port number if on the same PC, otherwise just a different IP address is required.

Many people have multiple Emby servers running quite happily side-by-side.

#3 pcm2a OFFLINE  

pcm2a

    Advanced Member

  • Members
  • 136 posts
  • Local time: 10:37 AM

Posted 05 March 2019 - 03:53 PM

Sorry if my original post was not clear. I have updated it with step by step instructions to reproduce. This has to do with the Emby client on Roku and not the emby server.


Edited by pcm2a, 05 March 2019 - 03:53 PM.


#4 speechles OFFLINE  

speechles

    Advanced Member

  • App Developer
  • 4448 posts
  • Local time: 08:37 AM

Posted 05 March 2019 - 04:08 PM   Best Answer

This should be expected.

 

The reason is because of how Roku treats the storage space of the registry. It is not per application. It is per developer ID associated with your application. Yes you read that right. If you change developer ID you have to keep a separate Roku now for anything using the old developer ID. If you develop several apps that need their own storage space in the Roku registry each must be developed on their own unique Roku box. Yes you read that right it is not a typo. For each app you develop on Roku that you want separate space needs it own Roku. You make 4 apps and you want unique space on all 4? You need 4 Roku.

 

To do it with Emby your main box has your main developer ID. Now on your second Roku box you can set a second developer ID. Then use this to develop the Beta on.

 

In keeping these two developer ID separate is alot more work for very little gain to end users. It will slow down things and possibly cause problems if we forget any of the above and which box to develop each application on to generate the PKG. To keep all of this all from unravel and possibly cause us headaches it must be a single developer ID for both. Hopefully you understand. The app ID an app is assigned is merely a convenience to launch/install the app from the Roku store. It isn't really used to track the registry.


Edited by speechles, 05 March 2019 - 04:13 PM.

  • ebr likes this

#5 pcm2a OFFLINE  

pcm2a

    Advanced Member

  • Members
  • 136 posts
  • Local time: 10:37 AM

Posted 05 March 2019 - 04:19 PM

I understand and appreciate the very detailed description of how the process works 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users