MediaMonkey forum

wiz wrote:I just installed MonkeySqueeze on MediaMonkey 4.1.18.1853. When I enable MonkeySqueeze I get the following errors.

Error #-2147012891 -
Files "C:\Users\Donald\AppData\Roaming\MediaMonkey\Scripts\AutoMonkeySqueeze.vbs", Line: 736, Column: 1

Error executing script event.
OLE error 80072EE5

MM is installed on Windows 10. LMS is installed on a Windows 2012 R2 server.

Any Ideas?

I'm running 1853 and having no issues. Uninstall/reinstall Monkeysqueeze and see if that helps. Also reboot PC, hold tongue on left side of mouth etc...

Have you used Monkeysqueeze before and had it working?

This is the first time I installed MS or any add-on.

Apologies. Didn't realize I needed to setup the options before enabling MS. I no longer get the error. Now I just need to figure out how to get it to play music

Hello Gingernut63 (and others on this forum)

I'm new here, trying to install and run MonkeySqueeze, and running into trouble early on with the Comms test between MediaMonkey and my LMS server......

Here's my setup:
- Windows 8.1 PC (firewall deactivated while installing/testing)
- LMS 7.9 on Synology NAS (no password protection - static local IP address 192.168.0.19:9002
- Monkey Media 4.1.23 (running in admin mode) - music library correctly scanned and displayed - great piece of software
- MonkeySqueeze 3.3 (looks great, alas can't pass the first hurde.....)
- PC and NAS on Linksys basic ethernet switch, router access thru powerline adapters

Here's my issue: when clicking the "test comms" button in Monkey Squeeze, I immediately get a "comms not working" message - "testing" message while polling and waiting......

How do I make this work ? Is it a version mismatch issue, a networking issue ? I've uninstalled and reinstalled everything, to no avail (incidentally, I could not do a "clean" uninstall of MonkeySqueeze as my parameters (IP and port #, MAC addresses etc. seemed to still be there after uninstall)

Than you so much for your help !

JLT

Hi JLT

Usually this is the easy part of the setup.

In your browser go to; LMS > Settings > Information Tab and also open the MonkeySqueeze options page; MediaMonkey > Tools > Options > MonkeySqueeze.
Compare the IP Address and HTTP Port No.on each page They should be exactly the same values - IP Address:192.168.0.19 and HTTP Port No.: 9002. Please note that Synology units use port 9000 for another application so that is why the Port No. is 9002 for LMS.

Also you can try the LMS Hostname in place of the IP Address, this will sometimes work where the address does not. This depends on your network setup.

Read through the User Guide for further hints.

Let me know how you get on.

Thank you for spotting. I tried to connect my Squeezebox Touch again without success... a low prio nice to have popping up every 6 month.

After having read this, I only needed 3 minutes. I connected Squeezelite-X to MonkeySqueeze 3.3 and it worked. Then I synced Squeezelite-X and Squeezebox Touch, set volume of Squeezelite-X to 0 and voilà!

It baffled me that after I unsynced players, I was able to use Squeezebox Touch directly in MonkeySqueeze.

DIfference before and now:
Squeezebox Touch test comms showed version of the Player stuck at 7.8.
connecting to Squeezelite-X changed it to 8.0.0. and remains.

It works perfect! THX

Gingernut63 wrote: ↑Tue Mar 15, 2016 5:30 am This appears to be a handshake issue, the Squeezebox Classic may not work with MonkeySqueeze.

To confirm, install the software based player SqueezePlay (link below) on the PC, and then run and link it to the LMS music library. Go to LMS Web Page > Settings > Information and place the SqueezePlay MAC Address in the MediaMonkey > Options > MonkeySqueeze > Squeezebox Player Settings (Player 2?). Select the player, and then enable MonkeySqueeze and see what happens...

https://storage.googleapis.com/google-c ... .0r328.exe

If SqueezePlay connects and plays music then the Classic will not work with MonkeySqueeze. If the same issues occur with SqueezePlay then we have other issues to address.

Have fun

I'm wondering if there are plans to make a MM5-compatible version?