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 - jonesam31

Pages: [1]
1
Users / Re: Tagging AVI's,MPG's etc as Movies / TV Shows
« on: May 14, 2008, 05:20:06 pm »
Guys,

Thankyou so much, that's exactly what I wanted and needed, I do know SQL pretty well and what you've put there will really help. Don't know why I didn't think of it!!!?!?!?!?

Cheers again!

Andy

2
Users / Tagging AVI's,MPG's etc as Movies / TV Shows
« on: May 05, 2008, 10:55:57 pm »
I have a large collection of AVI's/MPG's/BIN's some Movies and some TV Shows.

I have tagged all my movies by genre, by using the "Edit attributes for all files in this directory", what I can't find is a method to do the same for tagging the files as TV Shows or Movies. What would be good is a tool that recursively tags files in an entire directory structure to a certain specification.

Any ideas?

Thanks. Andy.

3
Users / Re: How to setup a Disked Media Director for MCE 7.10
« on: May 01, 2008, 10:38:57 am »
The reason I need to do it wirelessly is because there is no cable around the house and I'd like a few of these dotted around so cabling would be difficult.

What I want is to be able to view my movies / tv series that are stored on NAS's that are mapped to my Core. I understand I could just have more than one Core but I like the idea of having everything mapped to the core and the Media Directors simply playing it, also maybe down the line the bluetooth follow-me stuff which I don't think you can do with multiple cores.

If i'm missing the point here please let me know...

Thanks again!

4
Users / How to setup a Disked Media Director for MCE 7.10
« on: April 30, 2008, 11:07:48 pm »
I am having a load of trouble getting a Media Director to work with my new Linux MCE 7.10 setup, I tried installing Kubuntu, then MCE on top which is the way it was written in a post on the web somewhere but I had huge problems with the setup.

So where I am now is:

Core - Linux MCE 7.10
Media Director - Linux MCE 7.10

Both installed from DVD, all I did was on the Media Director, in the Launch Manager changed Core's IP to the one of my real core however it still seems to be using local details like rooms and media. Is there somewhere else I am supposed to tell it to be a dumb Media Director and not a full Core??

Thanks,

Andy

5
Users / Re: Pluto Home Core and Disked Media Director Linux MCE - Not Working
« on: April 30, 2008, 11:04:19 pm »
Yes, I was however shortly after typing the message to this forum I realized that I was mixing two different technologies so this is where I am now:

Core - Linux MCE 7.10
Media Director - Linux MCE 7.10

Both installed from DVD, all I did was on the Media Director, in the Launch Manager changed Core's IP to the one of my real core however it still seems to be using local details like rooms and media. Is there somewhere else I am supposed to tell it to be a dumb Media Director and not a full Core??

Thanks,

Andy

6
Users / Pluto Home Core and Disked Media Director Linux MCE - Not Working
« on: April 30, 2008, 11:18:36 am »
Hello all,

I having a huge amount of trouble getting a Media Director to work with my Pluto Home Core. I need the Media Director to be wireless so as far as I understand it, I need to install Linux MCE on the MD PC. This is what I've done so far:

1. Install Kubuntu 7.10 from Live CD, then managed after hours of the install didn't move to the second part after a reboot to install Linux MCE on top of that.
2. Install Full Linux MCE 7.10 install from DVD.
3. Install Full Linux MCE 7.04 install from DVD.

When all three of the above are completed I get stuck on the Linux MCE Launch Manager with the following:

Finished spawning new children devices - core
Finished respawning of new children devices

then after a short pause...

Connection to DCERouter terminated
Reconnecting to DCERouter as requested
Connecting to router 10.1.0.25
Connect OK....


It goes through this loop continually and never connects up properly.

Watching DCERouter.log on the Pluto Core i get the following around the time the Connection to DCERouter terminated:

3   04/30/08 09:52:32   DCERouter (server)   Device died... count=142/200 dev=DCERouter

Wed Apr 30 09:52:32 BST 2008 died

But every few times I get something like this:

   Badly formed message
01   04/30/08 10:14:38.218      **** dwStart: 241
01   04/30/08 10:14:38.218      **** m_dwPK_Device_From: 49
01   04/30/08 10:14:38.218      **** m_dwPK_Device_To: 0
01   04/30/08 10:14:38.218      **** m_dwPK_Device_Group_ID_To: 444923904
01   04/30/08 10:14:38.218      **** m_dwID: 0
01   04/30/08 10:14:38.218      **** m_dwPriority: 39168
01   04/30/08 10:14:38.218      **** m_dwMessage_Type: -216102912
01   04/30/08 10:14:38.218      **** m_dwPK_Device_Category_To: 1637122215
01   04/30/08 10:14:38.218      **** m_dwPK_Device_Template: 39176
01   04/30/08 10:14:38.218      **** m_bIncludeChildren: 0
01   04/30/08 10:14:38.218      **** m_eBroadcastLevel: 140612871
01   04/30/08 10:14:38.218      **** m_bRelativeToSender: 0
01   04/30/08 10:14:38.218      **** m_eExpectedResponse: 16777216
01   04/30/08 10:14:38.218      Badly formed message
01   04/30/08 10:14:38.218      **** dwEnd: 0
01   04/30/08 10:14:38.218      **** m_dwPK_Device_From: 49
01   04/30/08 10:14:38.218      **** m_dwPK_Device_To: 0
01   04/30/08 10:14:38.218      **** m_dwPK_Device_Group_ID_To: 444923904
01   04/30/08 10:14:38.218      **** m_dwID: 0
01   04/30/08 10:14:38.218      **** m_dwPriority: 39168
01   04/30/08 10:14:38.218      **** m_dwMessage_Type: -216102912
01   04/30/08 10:14:38.218      **** m_dwPK_Device_Category_To: 1637122215
01   04/30/08 10:14:38.218      **** m_dwPK_Device_Template: 39176
01   04/30/08 10:14:38.218      **** m_bIncludeChildren: 0
01   04/30/08 10:14:38.218      **** m_eBroadcastLevel: 140612871
01   04/30/08 10:14:38.218      **** m_bRelativeToSender: 0
01   04/30/08 10:14:38.218      **** m_eExpectedResponse: 16777216
13   04/30/08 10:14:38.226      TCPIP: Accepting incoming connection on socket 120, port 3450, from IP 10.1.0.247.
10   04/30/08 10:14:38.226      Thread created for Incoming_Conn Socket 120 10.1.0.247 dev -1 ptr 0x8619650
01   04/30/08 10:14:38.353      Badly formed message
01   04/30/08 10:14:38.353      **** dwEnd: 0
01   04/30/08 10:14:38.353      **** m_dwPK_Device_From: 17
01   04/30/08 10:14:38.353      **** m_dwPK_Device_To: 15
01   04/30/08 10:14:38.353      **** m_dwPK_Device_Group_ID_To: 0
01   04/30/08 10:14:38.353      **** m_dwID: 67
01   04/30/08 10:14:38.353      **** m_dwPriority: 1
01   04/30/08 10:14:38.353      **** m_dwMessage_Type: 1
01   04/30/08 10:14:38.353      **** m_dwPK_Device_Category_To: 0
01   04/30/08 10:14:38.353      **** m_dwPK_Device_Template: 0
01   04/30/08 10:14:38.353      **** m_bIncludeChildren: 0
01   04/30/08 10:14:38.353      **** m_eBroadcastLevel: 4
01   04/30/08 10:14:38.353      **** m_bRelativeToSender: 0
01   04/30/08 10:14:38.353      **** m_eExpectedResponse: 16777216
10   04/30/08 10:14:38.353      Received Message from 49 (unknown) to 0 (unknown), type -216102912 id 0, parameters:
08   04/30/08 10:14:38.353      Received Message from 17 (Asterisk / Bedroom (Master)) to 15 (App Server / Bedroom (Master)), type 1 id 67 Command:Spawn Application, parameters:
08   04/30/08 10:14:38.353        Data Parm 13(Filename): 1920169263 bytes
08   04/30/08 10:14:38.353        Data Parm 24320(): 7536640 bytes
08   04/30/08 10:14:38.353        Data Parm 3145728(): 120 bytes
08   04/30/08 10:14:38.353        Data Parm 3342443(): 1953693696 bytes
08   04/30/08 10:14:38.353        Data Parm 7631457(): 94 bytes
08   04/30/08 10:14:38.353        Data Parm 1768059695(): 1835085678 bytes
08   04/30/08 10:14:38.353        Data Parm 1929379840(): 1953653108 bytes
08   04/30/08 10:14:38.353        Data Parm 1953656688(): 838888545 bytes
08   04/30/08 10:14:38.353        Data Parm 1953718573(): 1936290405 bytes
13   04/30/08 10:14:38.400      TCPIP: Accepting incoming connection on socket 121, port 3450, from IP 127.0.0.1.
10   04/30/08 10:14:38.400      Thread created for Incoming_Conn Socket 121 127.0.0.1 dev -1 ptr 0x86197b8
13   04/30/08 10:14:38.401      TCPIP: Accepting incoming connection on socket 122, port 3450, from IP 127.0.0.1.
10   04/30/08 10:14:38.401      Thread created for Incoming_Conn Socket 122 127.0.0.1 dev -1 ptr 0x86198d8
22   04/30/08 10:14:38.401      Device ID 19's command handler registered on socket: 122 with counter 99 0x86198d8
13   04/30/08 10:14:38.407      TCPIP: Accepting incoming connection on socket 123, port 3450, from IP 127.0.0.1.
10   04/30/08 10:14:38.407      Thread created for Incoming_Conn Socket 123 127.0.0.1 dev -1 ptr 0x86199f8
13   04/30/08 10:14:38.407      TCPIP: Accepting incoming connection on socket 124, port 3450, from IP 10.1.0.247.
10   04/30/08 10:14:38.407      Thread created for Incoming_Conn Socket 124 10.1.0.247 dev -1 ptr 0x8619b60
13   04/30/08 10:14:38.410      TCPIP: Accepting incoming connection on socket 125, port 3450, from IP 127.0.0.1.
10   04/30/08 10:14:38.411      Thread created for Incoming_Conn Socket 125 127.0.0.1 dev -1 ptr 0x8619cc8
22   04/30/08 10:14:38.411      Device ID 18's command handler registered on socket: 125 with counter 102 0x8619cc8
13   04/30/08 10:14:38.415      TCPIP: Accepting incoming connection on socket 126, port 3450, from IP 10.1.0.247.
10   04/30/08 10:14:38.415      Thread created for Incoming_Conn Socket 126 10.1.0.247 dev -1 ptr 0x8619ea0
22   04/30/08 10:14:38.415      Device ID 16's command handler registered on socket: 126 with counter 103 0x8619ea0
13   04/30/08 10:14:38.421      TCPIP: Accepting incoming connection on socket 127, port 3450, from IP 127.0.0.1.
10   04/30/08 10:14:38.421      Thread created for Incoming_Conn Socket 127 127.0.0.1 dev -1 ptr 0x861a078
01   04/30/08 10:14:38.428      Badly formed message
01   04/30/08 10:14:38.428      **** dwStart: 811677490
01   04/30/08 10:14:38.428      **** m_dwPK_Device_From: 14080
01   04/30/08 10:14:38.428      **** m_dwPK_Device_To: 892809472
01   04/30/08 10:14:38.42Return code: 139
3   04/30/08 10:14:38   DCERouter (server)   Device died... count=183/200 dev=DCERouter
Wed Apr 30 10:14:38 BST 2008 died

The only thing that isn't set is in the Connections tab of the MCE Launch Manager is the MySQL details, I haven't done this because there is nothing on the web or in the logs that suggests that I need to.


I would really appreciate any help here as I know how good this setup could be I just seem to be missing something.

Thankyou in advance,

Andy Jones


Pages: [1]