Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not all renders shown in gui #40

Open
PeterS1957 opened this issue May 20, 2021 · 20 comments
Open

not all renders shown in gui #40

PeterS1957 opened this issue May 20, 2021 · 20 comments
Labels
help wanted Extra attention is needed

Comments

@PeterS1957
Copy link

i have more than 5 renderers in my network, but i can see only 2 out of them in the GUI. And every time i start swyh-rs the second renderer shown is changing to another one. The first one stays the same. How can i select a specific renderer out of 5, is it possible to scroll the list ?

@dheijl
Copy link
Owner

dheijl commented May 20, 2021

What is your screen resolution? What happens if you maximize the swyh-rs Window? Is it on Windows or on Linux?

But I know that I should probably make the frame with the renderer buttons scrollable. My system shows 3 renderers with room for more that is taken from the log frame below the buttons:

Knipsel

@PeterS1957
Copy link
Author

PeterS1957 commented May 20, 2021 via email

@dheijl
Copy link
Owner

dheijl commented May 21, 2021

The logical explanation is that only 2 renderers are shown because only 2 are detected, and that for some reason detection stops at 2. Can you post the logfile here as an attachment? It's in your home directory in the folder ".swyh-rs".

@PeterS1957
Copy link
Author

PeterS1957 commented May 21, 2021 via email

@dheijl
Copy link
Owner

dheijl commented May 21, 2021

That explains it: you have 4 renderers that are physically one device so that they share the same ip address and even the same ip port number.
The last one that responds to the ssdp discovery broadcast is the one that is shown, as renderers are identified by their ip address (I keep list of renderers in a hashmap keyed on ip address).
I don't see a solution that is not specific for your unique situation.

@dheijl
Copy link
Owner

dheijl commented May 22, 2021

I have been looking for a solution, and I could easily add the device name to the key to allow adding all the renderers with the same IP/port, but I can't solve the problem of identifying the correct rendering subdevice when it sends a streaming request to swyh-rs, because at that moment the source IP adress is all the information that I have...

@PeterS1957
Copy link
Author

PeterS1957 commented May 23, 2021 via email

@dheijl
Copy link
Owner

dheijl commented May 23, 2021

I would need to check if it is possible to recover the device name/id from the streaming request HTTP headers that the device sends.
I published a prerelease 1.3.17 that dumps the request headers in the log if set log level to debug.

@PeterS1957
Copy link
Author

PeterS1957 commented May 24, 2021 via email

@dheijl
Copy link
Owner

dheijl commented May 24, 2021

Enjoy!

dheijl added a commit that referenced this issue May 26, 2021
to see if they can help solve #40
@dheijl
Copy link
Owner

dheijl commented May 26, 2021

I added code in the 1.3.17 prerelease that dumps the streaming request headers in the log if you set log level to debug.
So no need for the sniffer trace if you install 1.3.17 and attach the debug level log here.

@PeterS1957
Copy link
Author

PeterS1957 commented May 26, 2021 via email

@PeterS1957
Copy link
Author

PeterS1957 commented May 31, 2021 via email

@dheijl
Copy link
Owner

dheijl commented May 31, 2021

Thanks, but I don't see any attempt at actually streaming to one of the "squeezebox" devices, and it's the streaming request from one of the squeeze box subdevices that I need to see if I can solve the problem.
Unless of course streaming does not work at all, but if you press a renderer button for a squeezbox in swyh-rs I suppose I should at least see something in the debug log...

@PeterS1957
Copy link
Author

PeterS1957 commented May 31, 2021 via email

@dheijl
Copy link
Owner

dheijl commented Jun 1, 2021

Thanks for the log.
Unfortunately I don't think it's ever going to work: the Logitech Media Server does not accept the DLNA/AVTransport commands I use for streaming, it rejects everything with a HTTP 500 error (internal server error), and I have no clue what it expects me to send instead...

@dheijl dheijl added the help wanted Extra attention is needed label Jun 2, 2021
@desaiamogh
Copy link

I am not sure if this is the same issue.
I have upmpdcli setup on rpi 3 and it works just fine from my PC. When I connect to a VPN, SWYH-rs can not see the renderer anymore. It seems to only search the renderers on the vpn network.

Is it possible to to detect renderers on all the networks connected on the PC ? Ar atleast allow it to select the network you want it to be on?

@dheijl
Copy link
Owner

dheijl commented Jul 2, 2021

Your issue is not related, but it's a valid request. Currently the interface that can connect to the internet is used. I could add a dropdown with the available networks and remember the last choice, while keeping current behaviour on the first start after installation.
I added a new issue for this enhancement.

@desaiamogh
Copy link

Your issue is not related, but it's a valid request. Currently the interface that can connect to the internet is used. I could add a dropdown with the available networks and remember the last choice, while keeping current behaviour on the first start after installation.
I added a new issue for this enhancement.

That'd be really good ! Thanks.

@dheijl
Copy link
Owner

dheijl commented Jul 2, 2021

@desaiamogh: Should be fixed in 1.3.17 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants