This project has moved. For the latest updates, please go here.

Connecting to other Engines

Mar 22, 2013 at 2:19 PM
What is the proper context for connecting to other MCEBuddy engines? I can't seem to find the proper naming convention.

I'm running MCEBuddy on 3 computers: HTPC8 (a win 8 HTPC), BEDHTPC (the HTPC in the bedroom) and Mule764 (a 64 bit machine running win 7).

They record a number of the same programs, and I'd like the machines not to convert programs that other machines have.

They all dump the converted files onto my WHS2011 machine (CoKroServe/TV Series).
Coordinator
Mar 22, 2013 at 4:27 PM
What do you mean by context?

You can just enter the IP adress or the machine name in the remote engine name box. Assuming that you're using the default port on them all it should work fine.
If they are in different subnets then you need to enable the UPnP feature to traverse subnets. I'm also assuming that the firewalls ports have been kept open (port 23332), MCEBuddy enabled the windows firewall automatically but for 3rd party firewalls you will need to do it manually.

If you don't the machines to convert the same show, create showname filters on each machine.

E.g.

HTPC8 - NCIS*;CSI*
BEDHTPC - Saimpson*;house*

etc
Mar 22, 2013 at 5:47 PM
I meant syntax. Sorry. Just wasn't sure what I was supposed to put in the box. \HTPC8\Programs\MCE2x\mcebuddy.exe vs IP address.

Thanks for clearing that up. However I'm still unclear about the benefits of doing this. Is it for multiple engines to monitor the same folder on a networked machine and distribute the queue?

As I've been getting things to work, I keep digging deeper and trying to get it "just right" for my system. Thanks for the prompt replies.

rboy1 wrote:
What do you mean by context?


If you don't the machines to convert the same show, create showname filters on each machine.

E.g.

HTPC8 - NCIS*;CSI*
BEDHTPC - Saimpson*;house*

etc
Coordinator
Mar 22, 2013 at 10:01 PM
The mcebuddy architecture is based on engine with a thin client for status and configuration.

The client is just a status reporting and configuration tool. You can setup mcebuddy on different machines to run independently.

The remote part of the GUi just allows you to easily access the state of different engines and configure them from a single machine.

I also use it to connect to my machine from the Internet by using the upnp option.

On Mar 22, 2013, at 11:47 AM, "ckronengold" <notifications@codeplex.com> wrote:

From: ckronengold

I meant syntax. Sorry. Just wasn't sure what I was supposed to put in the box. \HTPC8\Programs\MCE2x\mcebuddy.exe vs IP address.

Thanks for clearing that up. However I'm still unclear about the benefits of doing this. Is it for multiple engines to monitor the same folder on a networked machine and distribute the queue?

As I've been getting things to work, I keep digging deeper and trying to get it "just right" for my system. Thanks for the prompt replies.

rboy1 wrote:
What do you mean by context?


If you don't the machines to convert the same show, create showname filters on each machine.

E.g.

HTPC8 - NCIS*;CSI*
BEDHTPC - Saimpson*;house*

etc