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

Pages: [1] 2 3 ... 25
Marketplace / WebDT 360 and accessories for sale
« on: December 05, 2012, 04:44:52 pm »
This is the red DT 360.  Hardware details / pictures available from Amazon (prices listed there are ridiculous, though...):

Included accessories:
- Charger
- Metal charging stand
- Stylus, attached by string
- Internal and external batteries
- Rubber grips
- USB WiFi adapter (internal WiFi is there, but didn't work easily with Debian)
- Flashed with Debian, running Orbiter image from a while back
- Original Windows CE DD image on CD, if you want it

PM me with offers.  Located near Boston, MA, USA.

Users / Re: Foxconn NetBox-nT330i as MediaDirector
« on: September 12, 2011, 08:43:03 pm »
It sounds like this unit is 100% functional after installing the Atheros NIC driver, setting the nomsi kernel option, and enabling WOL in the BIOS.  Can someone who owns one confirm that?  There were some HD playback issues mentioned previously, and I don't see a definitive resolution to those in this thread.

Also, how loud is the fan in this thing?

Users / Re: Removing orphaned TV recordings in mythtv
« on: May 31, 2011, 06:19:46 pm »
Dealing with MythTV database inconsistencies is sometimes a pain, and usually takes some SQL skills.

The last time this happened to me, I seem to remember deleting all rows from a few tables to start over without losing my recording schedules.  I believe there is also an older version of the orphan script - you can probably get it from MythTV's SVN.  In either case - back up the database first so you don't screw yourself.

The MythTV database is pretty flexible, in my experience.  You can usually dump it out and put it on a new system pretty easily.  So long as you are going to the same MythTV version or newer, MythTV will accept the data without complaint.  Just make sure you only deal with the media-related tables for recordings and schedules and such, otherwise LMCE will get confused.  So next time you reinstall - just take the MythTV database with you.

Feature requests & roadmap / Re: netflicks
« on: October 19, 2010, 10:08:05 pm »
I use the Sony Play Station 3, through a Schmartz SP3-IR1000, for Netflix.  I think someone made a template for the Roku box also, but I've never tried it.  It works just fine - LinuxMCE handles all the A/V routing automatically, so there is really not much to it when using it.  You do need an Orbiter though - I use a DT tablet.

Netflix looks pretty sold on whatever fancy Microsoft platform they are using for web-clients.  Last I heard, it doesn't even work outside of Internet Explorer.  I haven't checked in a while, since all my systems are Linux anyway, and there is absolutely no Netflix support for Linux PCs.

I did some work on this a while ago to see what would happen.  What I found - there are way too many reasons to have a separate media network for me to justify spending any more time on it.  For those looking to make a setup without changing existing, my suggestion is to have 2 NICs and leave one disconnected.

Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: October 19, 2010, 09:04:52 pm »
I'm waiting for a response from tbowland, and it would seem many people are in the same situation:

Code: [Select]
PM could not be sent to 'tbowland' as their inbox is full!
tbowland, you need to delete some messages, or get back to us by e-mail...

Developers / Re: Using LINUCMCE for a university project?
« on: October 08, 2010, 04:35:52 pm »
Voice control for LinuxMCE would be a great addition.  It's been discussed before, however I don't think there was any progress outside of a discussion.

As Thom said, once you have the Voice-to-Command translation working, the rest is fairly trivial.  I'm sure you could find people on the forum (myself included) who would be excited to test your development and provide suggestions for additions.

Users / Re: broken package dependency: mediatomb, linux-igd
« on: October 07, 2010, 11:04:04 pm »
There is is, thanks - installed no issues.

Need dist-upgrade, by the way, since extra dependencies are installed.

Users / broken package dependency: mediatomb, linux-igd
« on: October 07, 2010, 03:42:47 pm »
Anyone else seeing this on apt-get install lmce-mediatomb?  it is held back on upgrade and dist-upgrade.
Code: [Select]
The following packages have unmet dependencies:
  lmce-mediatomb: PreDepends: lmce-linux-igd but it is not installable
E: Broken packages

Users / DCERouter crashing, MythTV errors...
« on: October 01, 2010, 09:51:28 pm »
DCERouter keeps crashing...  It will not fully start - it crashes after about 5-15 seconds after being spawned, then it dies and is spawned again.  This repeats for a while, until the 200 crash limit is hit, then it stops.  The last thing before it crashes is a bunch of MythTV and some MediaAttribute errors.  Here's the last 100 lines:

I am up to date with the latest LinuxMCE packages.  Here's the myth version:
Code: [Select]
j@dcerouter:/var/log/pluto$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version   : 22961M
MythTV Branch    : tags/release-0-23
Network Protocol : 56
Library API      : 0.23.20100429-1
QT Version       : 4.4.3
Options compiled in:
 linux release using_oss using_alsa using_pulse using_jack using_pulseoutput using_backend using_directfb using_dvb using_firewire using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

Any thoughts on what the issue is?

Users / Re: Touch Orbiter - a new approach to Touch Based Orbiters
« on: July 23, 2010, 03:51:01 pm »
Andrew, this looks awesome... Thank you!

Users / Re: How do you feel about
« on: June 11, 2010, 05:07:52 pm »
Also, so like i apparently suck and have no been able to determine where the orbiter gets the array to decide the sort options. I have been reading the orbiter code and going through as many database entries as possible, but so far to no avail. So, if anyone has some time, feel free to take some time and look as well. Or if you already know  ;D Why am i so concerned? Well because i would like to add a 'program' sort option which would work like

      -Datagrid of programs - Select one and you get:
      -Datagrid of seasons - select one and you get :
      -Datagrid of episodes in that season

Have you tried looking at the commands that go through DCERouter when you change sorting?  That might point you in the right direction.

Also have added a 'character' attribute in my own db. Why? because it annoys me that this data goes by and its not used. May not even be usefull to most. But maybe i want to easily choose which james bond i want to see. Or how much crossover there was between 'homicide: life on the streets' and 'law and order'.

This is a neat idea.  You should consider expanding it and talk to the devs about integrating it so that everyone can use it.

It may be worth alerting FSF ( or these guys:  Either can probably give you the path to stopping this before you need to pay for lawyers.

Installation issues / Re: failed RAID1
« on: June 02, 2010, 11:21:21 pm »
sorry for the long wait in replying, life happens and i wasn't apply to work on it for awhile, i tried "sudo mdadm --stop /dev/md0" and still get the same results, when i do "mdadm --detail" it returns "mdadm: No devices given." when i do "fdisk -l" i get:

Cannot open /dev/sda
Cannot open /dev/sdb

thanks for the reply.

...If you're going to use mdadm commands, you're going to need to read the mdadm documentation...  You need to specify which device you want details about.
Code: [Select]
mdadm --detail /dev/md0
Your user cannot open the sd devices because it is not in the disk group.  Retry the command as root using sudo.


3. If the core dcerouter crashes then the media players and orbiters etc should continue running and try to reconnect in the background. The current behaviour has the effect of making the system quite infuriating sometimes (and as a result I have moved all media playback to dedicated devices - such as Xtreamers - under IR control)

Generally in our experience MD's will auto re-connect if the Core locks and has to be restarted. It has to be said that it is very rare for even our development Core's to crash/lockup. However iff you use alpha/beta code in production systems then you have to expect instability and issues...helping to document/fix those with the Dev's is what using these incomplete builds is all about.

I think what chrisbirkinshaw is talking about on a higher level is making the different pieces of the system less dependent on each other whenever possible.  The idea being that if one device or system goes "boom" others are not affected or maybe some other device or system takes over the dead one's work.  In theory, I agree with this idea of a self-healing or redundant system.  I wonder which pieces can be set up to act in this way and how much effort it would take in each case.

In my experience, if the dcerouter goes down, playback stops.  This is happening much less frequently than it used to (0710 to current 0810 builds), but I don't know if this is due to dcerouter improvements, or just because everything that talks to the dcerouter is becoming more stable.  In any case - it seems to me that media playback does not necessarily need to be so dependent on the dcerouter.  Of course features like controlling playback from orbiters would be affected if the dcerouter dropped out, but not the basic playback.  When dcerouter comes back online, it can tap into whatever is going on and update its state.

There is also the issue of notifying the human when something has failed.  It's important to know when something has gone wrong, without a doubt.  This system is supposed to secure my home - it can't fail silently.  Currently, most failures require us to dig through logs to figure out what devices are affected.  I think someone was working on an e-mail message event responder - that might be one good way to get the word out.  In order to make this robust, there would need to be a separate entity in charge of making sure everything is running properly - one that is not associated with anything that can fail.  That probably means that it could not use DCE, or at least not have its messages routed through dcerouter.

How do those of you who use the security and telecomm features approach reliability checks and error reporting?  Or do you just "trust it"?

Pages: [1] 2 3 ... 25