Playing araound a bit I understand now, that the described behaviour only occurs when I have another upnp device running.
When TwonkyMusic server is running, it seems that MiniServer will not start, since SSDP-port binding fails.
Shouldn't it be possible to have more than one device running?
Regards,
Ralf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i have tried it with TwonkyMusic and also had the same problem. but you can first start renderer and then TwonkyMusic, this works fine. but we will try to find another solution.
Regards
Da
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hallo ,
wenn ich versuche renderer zu starten, dann bekomme ich die Fehlermeldung couldn't init SDK: UPNP_E_SOCKET_BIND.
Das Problem liegt irgendwo in der libupnp-api, beim Versuch an den SSDP-port 1900 zu binden.
Hat das schon einmal jemand gehabt?
Gruß,
Ralf
Hallo Ralf,
welche Version der libupnp benutzt du denn?
Gruß
Julian
------------
Hi Ralf,
which version of libupnp do you use?
regards,
Julian
Hi Julian,
I am using 1.4.1 from sourceforge Download.
Playing araound a bit I understand now, that the described behaviour only occurs when I have another upnp device running.
When TwonkyMusic server is running, it seems that MiniServer will not start, since SSDP-port binding fails.
Shouldn't it be possible to have more than one device running?
Regards,
Ralf
Hi,
i have tried it with TwonkyMusic and also had the same problem. but you can first start renderer and then TwonkyMusic, this works fine. but we will try to find another solution.
Regards
Da
Hi,
probably we can do nothing. :-(
We have searched a bit, and found http://www.twonkyvision.de/forum/viewtopic.php?t=2418.
Do you have a problem like that one you described with another UPnP-software? Does it only occur, when TwonkyMusic is running?
regards
Julian