Messages

16

Users / Re: MD boot issue in 810

« on: October 15, 2009, 08:58:02 pm »

On the core, open a prompt and edit the file in nano:

Code: [Select]

sudo nano /usr/pluto/bin/files.d/fstab-disklessMove to the last line with text on it (line 28).  It should look like this:

Code: [Select]

mkdir -p "${Parm_RootLocation}/var/spool/asteriskAdd a double-quote to the end so it looks like this:

Code: [Select]

mkdir -p "${Parm_RootLocation}/var/spool/asterisk"Save and exit nano ([Ctrl]+X then Y then [Enter]).  Then reboot your MD and see if it worked ...

If not, the MD may also be missing a hosts file.  I had created one as part of troubleshooting before I did this step, so I'm not clear whether that's a required step for the workaround or not.

17

Users / Re: MD boot issue in 810

« on: October 15, 2009, 07:49:37 pm »

I added a quote to /usr/pluto/bin/files.d/fstab-diskless on the core, which got me through to the AVWizard.

18

Installation issues / Re: Setting up Core – MDs.

« on: October 15, 2009, 03:36:50 pm »

A number of us are having this issue with the current build.  I haven't heard of or found any workarounds yet, so we may be waiting a bit until someone is able to look at it.  Unless anyone else has an answer?  I am also stuck at this point.

19

Users / Re: Call for donations for features.

« on: September 25, 2009, 07:38:04 pm »

is that patch in the current release?

Not as far as I know, but I did just notice a recent update on the trac ticket that someone had added the libpcrecpp library dependency to UpdateMedia.  Perhaps they are getting ready to integrate it?

I would love to apply and test that patch if it isn't already in the latest release. I only use the script as a workaround until the feature was added, and provided it in case anyone else is as impatient as I am.

I would really appreciate any testing and/or feedback.  Unfortunately, I don't currently have a functional 0810 build environment to provide you with binaries, but if you have one set up and wanted to try the patch, I'd be happy to help however I can.  The patch and my instructions for setting it up are in the trac ticket http://trac.linuxmce.org/trac.cgi/ticket/158. 

20

Users / Re: Call for donations for features.

« on: September 25, 2009, 04:55:32 am »

Can somebody work on trying to get this into UpdateMedia itself? We shouldn't have to run a "script" ... perhaps by doing some introspection of the files we can at least set format, and use directories for the others.

-Thom

If you're referring to donpaul's script, the autotag patch I submitted six months ago integrates with UpdateMedia to do this and more.  It is based on file / directory path, allows regular expressions, and allows you to set/update/add MediaType, MediaSubType, ShortAttribute, LongAttribute.  

Edit: To clarify - it does not do any introspection on the files, though I think that's a good idea and separate from the autotag patch.

21

Users / Re: Call for donations for features.

« on: September 07, 2009, 05:54:40 pm »

That's definitely a possibility, but hopefully unlikely to be an issue.  Most of the changes are in new files, with only 5 existing UpdateMedia source files modified, so even if a conflict arises it should be fairly easy to resolve.  (Unless UpdateMedia changes drastically, of course.)

22

Users / Re: Call for donations for features.

« on: September 07, 2009, 01:19:56 am »

I believe he was almost there and was just working on the web interface. I can see that he still comes to the forums occasionally but hasn't posted in quite a while, so I have PM'd him to ask how it is going.

This feature is complete and posted to a trac ticket (http://trac.linuxmce.org/trac.cgi/ticket/158).  There's more I would like to do with it, but I wasn't planning any further work on it until I got some feedback from others that were actually using it or I had some need come up for my own use. 

I agree that it would seem to meet the needs you describe.  I am using it to automatically tag files that come in under 'movies', 'tv', etc. folders.  It also uses regular expressions on filenames to automatically tag 720p, dvd, etc. 

23

Users / Re: Auto tagging folder - just a thought

« on: June 09, 2009, 04:25:00 pm »

Unfortunately, my 0710 development image seems to be out of commission, along with the MD that was the only machine I could run that image from.  I'm not sure how quickly I'll be able to resolve this (could be a while), but the patch for 0810 and additional info is at http://trac.linuxmce.org/trac.cgi/ticket/158 in the meantime.  If anybody has a 0710 dev environment and wants to take a stab at it, I'd be happy to provide any help I can!

24

Users / Re: A few getting started questions

« on: April 17, 2009, 03:21:12 pm »

I see that the internal network of LinuxMCE is connected to the WAN port of the wrt54g. I do not have personal experience with the unit, but am not sure if the wrt54g will work properly as a 5-port switch. Please note that putting an AP (as opposed to a switch) behind the LinuxMCE server is going to get you a lot of trouble since proper DHCP by the Core server is very important.
Also, my experience is that eventually you always end up wishing for more ports on your switch, so I'd suggest that now is a good moment to buy an 8-port

The wrt54g works fine on my internal network with dhcp disabled.

25

Users / Re: Audio Media file format question

« on: April 05, 2009, 06:15:49 pm »

Since I'm already running 0710, I'm inclined to work on that branch. However, if it's close enough to the 0810 release or if there have been enough changes to UpdateMedia since 0710 to make merging across branches impractical, I'll take a look at trunk instead.

I know what you mean, and that's the direction I initially went with some UpdateMedia changes too.  It worked out fine starting out with 0710 and I added some specific steps that helped me compile UpdateMedia under 0710 (http://wiki.linuxmce.org/index.php/Building_From_Source#Building_UpdateMedia), but keep in mind that (a) the 0810 build is a little more sane to work with (IMO anyway) and (b) patches won't be accepted against the 0710 branch.  However, it was an easy merge when I ultimately made the switch to 0810, so I think you will be fine. 

One last note - if you decide to go for 0810 for development, you want the 0810 branch, not trunk!  That was a mistake I made as well .  Some great instructions here for setting up a chroot dev environment: http://wiki.linuxmce.org/index.php/Building_LinuxMCE_0810

26

Users / Re: Splitting Audio / Video Pipes

« on: April 02, 2009, 12:27:12 am »

I updated my device template, removing the HDMI input and adding an Optical input with the same IR code.  Reloaded and retested, but same behavior:

Code: [Select]

08      04/01/09 18:21:58.837           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 116 (AVR-886S / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6e69b90>
08      04/01/09 18:21:58.837             Parameter 71(PK_Command_Input(Optical)): 932 <0xb6e69b90>
--
08      04/01/09 18:21:58.837           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 114 (PT-52LCX66 Discrete Inputs / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6e69b90>
08      04/01/09 18:21:58.837             Parameter 71(PK_Command_Input(HDMI)): 361 <0xb6e69b90>
--
08      04/01/09 18:21:58.837           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 114 (PT-52LCX66 Discrete Inputs / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6e69b90>
08      04/01/09 18:21:58.853             Parameter 71(PK_Command_Input(Component 1)): 712 <0xb6e69b90>

Good point, though.  I was assuming that "HDMI" was just a label and didn't have any videoness attached to it, but this is something I should have tested out before I got to this point.

Any other ideas?  Anybody know if this is just a bug?

27

Users / Re: Splitting Audio / Video Pipes

« on: April 01, 2009, 10:09:04 pm »

Thanks for the response.  I agree, they are similar configurations.  If I understand yours correctly, this is what your configuration would look like with my setup:
http://i39.tinypic.com/zwgkro.png

The key difference here is that there is not a video pipe from the receiver to the TV.  And in fact, I can approximate that as a workaround with my setup:
http://i44.tinypic.com/10x4njt.png

This fixes the problem with the extra Input Select command.  The reason I'm not using this workaround is I have an xbox with audio and video going through the receiver just like the DVR, which I would like to add next.  That will require the video pipes going through the receiver properly, so I can get LMCE to properly switch inputs on both the TV and receiver.

I don't want to mess up your setup, but if you would like to test it I'd be curious if you get the same behavior as me if you temporarily route the DVR video pipe through your receiver (rather than directly to the TV).  I'm guessing that with that setup you will see an extra Input Select command for the TV when selecting a video from the MD.

What I really want to know though, is whether this is the expected behavior of the a/v pipes and I am just misunderstanding how they are being used, or is this a bug?  In the meantime, I'm going to dig into the media plugin and try to understand the logic that is sending these commands. 

28

Users / Re: is there one interface to play .vob/mkv/xvid files

« on: April 01, 2009, 02:50:34 pm »

Yes, these are all recognized as video by LMCE and presented the same way.  You then can use tags such as genre or media type to filter your view as you browse the media.  This requires that your media is properly tagged, but with the genre organization you mentioned, you should be well-positioned to use the upcoming auto-tagging feature (http://forum.linuxmce.org/index.php?topic=7116.msg50212#msg50212) to both tag your current genres as well as automatically tag new media that you copy in under that existing structure.

29

Users / Splitting Audio / Video Pipes

« on: April 01, 2009, 01:55:14 am »

I am having trouble properly configuring my a/v pipes, and would really appreciate any suggestions or clarifications.  Here is my setup:
http://i43.tinypic.com/2a65aj6.png

In other words, my MD has video going directly to the TV and audio going to the receiver (through the improperly labeled HDMI input - I'm assuming that doesn't make a difference?), while my DVR has audio going to the receiver and video going through the receiver to the TV.

When I choose Live TV from the DVR, the expected Input Select commands are sent:

Code: [Select]

08      03/31/09 18:50:17.103           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 116 (AVR-886S / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6d95b90>
08      03/31/09 18:50:17.103             Parameter 71(PK_Command_Input(Component 2)): 713 <0xb6d95b90>
--
08      03/31/09 18:50:17.103           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 114 (PT-52LCX66 Discrete Inputs / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6d95b90>
08      03/31/09 18:50:17.103             Parameter 71(PK_Command_Input(Component 1)): 712 <0xb6d95b90>

However, when I select a video from the MD, I get something unexpected:

Code: [Select]

08      03/31/09 18:44:36.480           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 116 (AVR-886S / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6d95b90>
08      03/31/09 18:44:36.480             Parameter 71(PK_Command_Input(HDMI)): 361 <0xb6d95b90>
--
08      03/31/09 18:44:36.481           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 114 (PT-52LCX66 Discrete Inputs / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6d95b90>
08      03/31/09 18:44:36.481             Parameter 71(PK_Command_Input(HDMI)): 361 <0xb6d95b90>
--
08      03/31/09 18:44:36.481           Received Message from 10 (Media Plug-in / Living Room/Family Room) to 114 (PT-52LCX66 Discrete Inputs / Living Room/Family Room), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6d95b90>
08      03/31/09 18:44:36.481             Parameter 71(PK_Command_Input(Component 1)): 712 <0xb6d95b90>

There is an extra command going to the TV, tuning it to the receiver's input.  If I delete the video pipe from receiver to TV, the issue is resolved, so I have to assume that sending the audio to the receiver is for some reason activating that output video pipe.  Am I doing something wrong here?  Any help is very appreciated!

30

Users / Re: Auto tagging folder - just a thought

« on: March 29, 2009, 04:54:17 pm »

I sent a patch off to Thom for review.  If anyone wanted to test in the meantime, I would be grateful.  I've attached a patch for 0810, but if someone with 0710 wants to test, let me know and I can probably produce some binaries for you. 

Here are a couple screencaps of the front-end (hey, I said I was no php guy  ):
http://i44.tinypic.com/96gjk5.jpg
http://i44.tinypic.com/15x7ple.jpg
http://i43.tinypic.com/eb53q1.jpg

Here is some more information for anyone wanting to try the patch:

This code depends on libpcrecpp.  Install it with 'apt-get install
libpcrecpp0'

The basic structure of the changes is:
 - src/AutoTag - this produces libAutoTag.so and the AutoTag
standalone.  This handles managing rules and provides 'run rules now'
functionality.
 - src/UpdateMedia - I integrated libAutoTag.so here to automatically
tag newly-added files only.
 - web/lmce-admin - A couple new screens for managing rules and
restoring backups

After patching, you should just need to (1) 'make && make install' in
AutoTag, (2) 'make' in UpdateMedia, (3) deploy the new UpdateMedia to /usr/pluto/bin (backup the old one first), (4)
deploy the lmce-admin updates.