[RELEASE]XSqueeze - Squeezebox player, music chooser and visualiser for XBMC - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: Add-ons Help and Support (/forumdisplay.php?fid=27)
+---- Forum: Program Add-ons (/forumdisplay.php?fid=151)
+---- Thread: [RELEASE]XSqueeze - Squeezebox player, music chooser and visualiser for XBMC (/showthread.php?tid=122199)
- Maxim - 2012-02-19 06:21
fruitloaf Wrote:Have you tried port 9090 - I believe that's the correct port for squeezeslave - 9000 is the port for the webadmin
Wow. I feel silly now. Yes this was the issue. It was originally 9090, but I made an assumption that connecting to the web interface was the goal. Thank you for noticing and letting me know of my mistake.
Everything is working excellently. I'm quite happy now. Thanks again!
- bossanova808 - 2012-02-19 07:07
castalla Wrote:I reinstalled the latest version.
Ok - firstly, I don't have a touch (just Sb2, Sb3, Booms) - I do not know how the add on will deal with the touch therefore as it has a much more complicated display and I don't know what it does about offering a two line fallback set up or not. Not a lot I can do about that as there's no way I'm buying a touch (or SB controller)....if anyone in Aus. wants to loan me one, happy to implement it though.
Ok, the C application error is very unlikely to be related to this - there's no C involved and about the worst this add on could do is spawn a bunch of squeezeslave processes if you hammer it.
(To the post above - I don't want to search and destroy sequeezeslave processes will nilly as there are legitimate reasons to run more then one a machine I don't necesarrily want to interfere with - if you set it up right, this won't happen anyway....but eventually I will add enough exception handling to make sure no matter what it kills any Squeezeslave it has created on that run even if it is crashing...)
Anyway - back on topic - you need to post your log so I can have a clue what is happening - hard to help without this. At the moment I log quite a bit by default, so you don't even have to turn on debug logging.
And note, this is all very early days - the whole point of this alpha release is to get people with different setups to try it - I fully expect it to break, but since I only have so many setups I can test on, I need info - basically, reports both +ve and -ve, and log files!
- bossanova808 - 2012-02-19 08:40
Note because to the whole 'need to chmod +X every update' issue that is not fixable with the addon, I plan to push things out a lot more slowly now, since the basics are in place and I don't want to break it all the time.
So - this is planned next:
- Loading of the README.txt on first run of each version
- Server discovery rather than having to put it in manually
- Audio output chooser for those using the inbuilt squeezeasalve
- Skin support - if people provide me with skin files (basically, a 720p/XSqueezeNowPlaying.xml written for their skin, plus all associated media files such as background, icons etc) - thanks to fruitloaf for doing an AeonNox version!
- Skin support - happy to expose more data to the skin files if requested (e.g. more tracks, later ideally artist bio/album info)
- if possible, integration with script.artistslideshow
- work out why openelec has those little audio dropouts periodically (anyone have ideas on this??)
Any and all of that, really. Other suggestions taken!
- castalla - 2012-02-19 09:54
Thanks for the reply.
1. LMS running - Touch connected via LMS - default MAC -squeezeslave auto = http://pastebin.com/LzJP4ydD
2. LMS running - Touch connected - Touch MAC - no squeezeslave = http://pastebin.com/7aNmqebc
When I select xsqueeze nothing happens.
- castalla - 2012-02-19 10:04
I re-entered the LMS ip - auto squeezeslave - starts but no display
Exit xbmc - restart xbmc - error panel overlay - xbmc fails to start.
- bossanova808 - 2012-02-19 11:27
1. It couldn't find you server at all @ 192.168.1.130 on port: 9090 - is this IP right, have you tried the hostname instead, have you changed your CLI port? Can you telnet manually to 192.168.1.130 9090 and issue a CLI command? (just type test and it should echo it back to you). You should have got a pop up notification saying 'Couldn't connect to server'
2. Same thing - couldn't connect to your server
3. And again. In all of these cases if it fails it immediately does an xbmc notification so you should get a message.
You need to check your server connection and CLI port because you're not getting past that point.
also it looks like your system is trying stop during the add on startup....
...that really doesn't look right to me.
- castalla - 2012-02-19 11:51
IP is correct - diagnostics shows that port 9090 is OK
telnet never connects
- bossanova808 - 2012-02-19 12:31
well there's your issue - something is stopping access to the CLI - firewall maybe? Hoe are you doing the telnet (192.168.1.130 9090 is the windows way, not 192.168.1.130:9090)
- castalla - 2012-02-19 12:39
Yes - using correct syntax.
I've got a new router which is a real pain to figure out (interface is in Spanish).
The firewall settings are almost unintelligible - I'll play around today with various settings and see what I can discover.
- fruitloaf - 2012-02-19 15:44
It won't be the router firewall settings but the settings of the firewall on the PC running LMS that you need to change (and possibly even the settings of the PC running XBMC though this is less likely the cause).
What platform are you running LMS and XBMC on? My first bet would be to disable the firewall on your LMS computer and test again - if you can now telnet to it from your XBMC PC then that's the issue and you can open the appropriate port (9090).