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

Pages: 1 ... 4 5 [6] 7 8 ... 368
76
Users / Re:
« on: January 21, 2014, 05:14:43 am »
I had started code to build a Pandora player and plugin based on the PianoBar source code, but other priorities got pushed up. It needs to be coded, either by me, or by someone else... -Thom

Sent from my alien_jolla_bionic using Tapatalk

77
Users / Re: MythTV - mythfilldatabase
« on: January 20, 2014, 03:42:12 pm »
let's set aside some time to remote in, so I can see what's going on. I no longer use MythTV in LinuxMCE, so would need to look at an actual installation, to see what's going on.

We have a number of scripts in MythTV_Plugin which handle guide refresh, but I am not sure where they are being called anymore, greps aren't being forthcoming:

/usr/pluto/bin/MythTvDailyFillDB.sh
/usr/pluto/bin/MythTvInitialFillDB.sh

-Thom

78
Users / Re: Smoke detector Everspring SF-812 detection
« on: January 20, 2014, 03:36:00 pm »
I would suggest testing this in 12.04, as we have rewritten the ZWave driver to use Open-ZWave. We are no longer making code changes to the old driver.

-Thom

79
Hi! Great that you want to implement support for more hardware! LinuxMCE is more than happy to accomodate, however due to the sheer flexibility and options on implementing this code, it can be a bit tough to figure out where to start.

What you want to do, is create a DCE device for your lighting interface. It involves:

1. Creating a device template, describing your device, what it needs to function, what commands it can receive, events it can send, and any plug and play information which can be used to find the interface.
2. You will need to implement the code for the lighting interface. Currently you can do this in either C++ or Ruby (or shell script, using the DCE Whisperer).

You should read the following wiki pages:

http://wiki.linuxmce.org/index.php/GSD
http://wiki.linuxmce.org/index.php/Developing_a_DCE_Device

And should you need more direction, feel free to stop by #linuxmce-devel on irc.freenode.net, and talk with developers. Hopefully we can get you on the right path.

-Thom

80
Users / Re: Doorbell - Double event trigger
« on: January 19, 2014, 05:35:35 am »
This may very well be a bug. Can you file a ticket, so we can take a look @ it? :)

-Thom

81
Users / Re: MD recommendations
« on: January 15, 2014, 04:33:27 pm »
and yes, if you have a TV that has either Ethernet or RS232, it can be controlled that way.

I am working with the USB UIRT engineer to find the problem that cropped up in 12.04 regarding the UIRT.

-Thom

82
Users / Re: MD recommendations
« on: January 14, 2014, 02:42:47 pm »
My only recommendatiion is to please get one with Ethernet.

-Thom

83
Users / Re: MD recommendations
« on: January 14, 2014, 03:20:55 am »

84
Installation issues / Re: PXE boot MD
« on: January 13, 2014, 02:03:09 pm »
Right, I forgot about the gPXE boot CD/USB/Bootfloppy :)

-Thom

85
Users / Re: MD recommendations
« on: January 13, 2014, 02:02:27 pm »
The i5 mostly would come in handy for more advanced game emulation play. The i3 that I have here in my Den is more than adequate for video playback (especially with the new Xine that we built that does va-api acceleration.)

My NUC is mostly in an open area behind the TV, so overheating really isn't an issue, but, the device itself uses a mobile i3/i5 CPU, so a little less oomph, for a lot less thermal output.

-Thom

86
Installation issues / Re: PXE boot MD
« on: January 13, 2014, 04:52:01 am »
Simply set the laptop's BIOS to boot from the network, if available. See what happens?

-Thom

87
Users / Re: MD recommendations
« on: January 13, 2014, 04:46:07 am »
The Intel NUC works well under 1204, now.

http://www.newegg.com/Product/Product.aspx?Item=N82E16856102002 <-- i3 variant.
http://www.newegg.com/Product/Product.aspx?Item=N82E16856102002 <-- i5 variant, with thunderbolt ports and USB 3.0 ports

Enjoy,
-Thom

88
Developers / Re: MPD integration
« on: January 12, 2014, 09:06:10 pm »
You need a DCE plugin on the core to handle the media stream objects.

You need either DCE players at the end points to control,
or to have a master DCE device somewhere that can coordinate the actions of the target devices.

For the former, Look at Xine Plugin and Xine Player.
For the latter, Look at the Squeezbox Plugin and Slim Server Streamer.

Pretty cut and dried.

Now go make something :P :)

-Thom

89
Developers / Re: MPD integration
« on: January 12, 2014, 08:43:34 pm »
You need to do some serious study of the media plugin, and of the Xine Plugin and Player, as this is the most feature complete media player we have, which uses ALL of the functionality of the system.

You're overthinking things, this is what happens when you try to think things through without actually digging your hands into the code. stop it.

the Media Plugin concerns itself with instances of MediaStream. Which is merely a container for a given instance of media throughout the house. Right now, the media handlers look for media devices in an entertainment area (in the DeviceTemplate_MediaType table), and then cross reference this with a vector that is populated when the different media plugins run their ::Register() methods. The two ends meet, and the relevant media plugin's CreateMediaStream is called, which, in the end, will take the subclassed media stream (e.g. MPDMediaStream), and return it back to the Media Plugin.

Once this is done, StartMedia is called, which does all the logic to figure out WHERE a stream needs to go. You're given a LOT of data in the MediaStream object (look in src/Media_Plugin/MediaStream.h), and you use this to cross reference with the device tree, to figure out ultimately where things need to go, either ending in a CMD_Play_Media() call, or a CMD_Start_Streaming() call for sending to multiple destinations.

These individual calls are merely declarative control, you're not actually sending the streams down these DCE calls, you're just coordinating signalling to the target media player as need be. Your Player's job, is to either EMBED mpd, or to control it, depending on the approach.

The Media Plugin does a _LOT_ of abstraction for you, including figuring out whether the media stream needs to be bifurcated or not (if you're sending an audio stream to a couple of media directors running Xine, a couple of squeezeboxes, and a couple of MPD endpoints, then THREE separate media streams will be created, the media streams themselves will not talk to each other.)

The Squeezebox support, for example, relies on a Slim Server Streamer, that runs on the core, and talks to the CLI interface that Logitech Media Server exposes for integration. The Squeezeboxes themselves are children of the Slim Server Streamer, and their configuration script merely sets the Controlled Via to be the Slim Server Streamer on the core. The Entertainment areas for each device are set appropriately, and are placed in their appropriate rooms.

So, what you need to figure out now, is whether to either (on the core)
(1) embed the mpd libraries and call them from C++ (spawn thread, etc.)
(2) talk to mpd over a socket to your player.

then, you need to figure the same out for the media directors.

-Thom

90
Developers / Re: MPD integration
« on: January 12, 2014, 07:28:26 pm »
Any new features go into the development trunk, which right now is 12.04, full stop. 10.04 will not receive any new features, and you shouldn't develop any new features on it.

Since this is a media plugin and player pair, you'll need to develop these in C++, full stop. No, don't argue. You'll have to, because the media plugins need to have access to class pointers of the other plugins in the router memory space to do infrastructure work.

-Thom

Pages: 1 ... 4 5 [6] 7 8 ... 368