News:

HOT TIP! Commands and groups can be copied and pasted directly from your command editor to the forum, and vice versa. This makes sharing command XML on the forum much easier!

Main Menu

Can VC tell if XBMC is playing media?

Started by ih8gates, April 13, 2014, 02:43:01 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ih8gates

#15
I have a port conflict with another app that didn't allow me to change its port, so I changed XBMC's. It's an app that I still use, so I can't change back to 9090.

(PS: I'm really sorry I didn't think of that earlier! Sorry about the fire drill.)

jitterjames

#16
No problem.  It would be an easy thing to forget, and I'm sure I would have done the same.  I'm just glad that I got lucky and noticed it. It somehow looked funny to me to see 9091!

Anyway, I'll see about making this an option in a future release (soon), but it will be for VC version 2 only.  I'm only doing critical bug fixes on version 1.

In the meantime if you could temporarily revert to 9090 just for the sake of testing that would be appreciated.

ih8gates

I tried reverting (closing the conflicting app, updating XBMC's custom config and restarting XBMC), but then I started getting errors when Vox tried to connect to XBMC. There was probably something else grabbing the port.

I'll look into upgrading to 2. Are updates to that code fairly regular as you make changes?

jitterjames

Yes usually.  It depends on what kind of changes I get myself wrapped up in and how hard they are to complete.

You can try this.  Replace your voxcommando\plugins\xjson\xJson.dll
with the attached dll.

This is for VC version 1.  I have hard-wired it to use port 9091, so no one else should use this.

repeat: THIS FILE IS ONLY FOR IH8TGATES (unless you also want to use port 9091 for json notifications)

In version two there will be a setting for the tcp port.

ih8gates

I appreciate this!

At first, I started getting a connect error, then realize that in my testing, I'd changed 127.0.0.1 to the machine's IP. But didn't have the "let remote machines control XBMC" flag set.

Everything's working correctly now with the updated dll.

Thanks!