Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Nightlander

Pages: 1
1
Plugins / Re: MusicBee Remote (Remote Control for Android)
« on: July 06, 2018, 12:17:03 PM »
Thanks a lot for the great app! I am trying to set up the remote plugin but can't seem to connect my android device to the host. It looks like a similar problem to the previous comments on this thread, so it might be the same bug. Basically, after installing the plugin, I get a settings window with a wrong IP in the private address list. When I try to specify the correct IP, it doesn't appear on the address list. Also, I cannot connect from the Android app. When I scan, it gives a "A remote service could not be found". When I try manually, it gives another error message.

I have also installed the fix you provided on the previous page. This prevents the desktop app from giving a Stopped prompt when specifying an address, but it doesn't solve the connection problem, at least in my case. I have tried different ports, with no result. These are some of the messages I get in the debug log:

2017-07-17 01:06:19.0727 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
Socket starts listening on port: 3000

2017-07-17 01:06:19.0727 [ERROR]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
While starting the socket service
Only one usage of each socket address (protocol/network address/port) is normally permitted

2017-07-17 01:06:19.0727 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
broadcasting message BroadcastMessages: 2={"context":"nowplayinglyrics","data":"Lyrics Not Found"};3={"context":"nowplayinglyrics","data":{"status":404,"lyrics":""}}, _content: nowplayinglyrics

2017-07-17 01:06:19.0727 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.ServiceDiscovery : 0
Starting discovery listener at 239.1.5.10:45345 for interface 192.168.0.103

2017-07-17 01:06:21.9851 [DEBUG]
MusicBeePlugin.InfoWindow : 0
Selected source is -> Library

2017-07-17 01:06:21.9921 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
07/17/2017 01:06:21 : OnClientConnect Exception : The IAsyncResult object was not returned from the corresponding asynchronous method on this class.
Parameter name: asyncResult


2017-07-17 01:06:21.9921 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
07/17/2017 01:06:21 : OnClientConnect Exception : You must call the Bind method before performing this operation.

2017-07-17 01:07:11.8554 [ERROR]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
While starting the socket service
Only one usage of each socket address (protocol/network address/port) is normally permitted

2017-07-17 01:07:18.9768 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
sending-all: {"context":"ping","data":""}

2017-07-17 01:07:18.9768 [DEBUG]
MusicBeePlugin.AndroidRemote.Networking.SocketServer : 0
Ping: 16/07/2017 18:07:18

I would really appreciate some help. Maybe it´s a simple thing I am overlooking!

Got same error with socket being already in use, then I looked at the installed plugins and musicbee remote was listed there twice... No wonder socket was in use; both of those instances were active. After initial setup of copying the .dll to plugins folder, another copy of the plugin appeared to user\appdata\roaming\musicbee\plugins folder as well and for the times I tried, it got copied there automatically. So I just deleted the one in program files and after that it pretty much worked except for the one thing...

Android itself. Firstly, had to disable notifications as it was seriously sucking battery. Then, if it was first run of the app, everything worked. BUT if app was previously being used and I relaunched it, it showed the track where it was left off when lastly used, not the track that was currently playing. Also could not control the playback any more although connection worked just fine and dandy. Then I tried to remove app history from phone and relaunch app and what do you know... it worked! Basically had to do that every time before opening the app… It seemed as if it would have worked if I had kept notifications on and it was constantly updating the position, too constantly as it was pretty much emptying the battery. Phone is nokia 8 with latest android.

Pages: 1