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

Pages: 1 ... 7 8 [9] 10 11 ... 13
121
The other issue is that you can get different resolution support over different inputs.  VGA inputs will sometimes only support "computer" resolutions, and not true 720p or 1080p, whereas DVI/HDMI will support more.  It all depends on the firmware for the TV's, and the quality of the ASIC's and display engines built into the TV's.  Usually, the less expensive TV's (which are usually the smaller models too) will not have the same capabilities as a more expensive (name-brand) TV.

Just my experience from shopping around...

/Mike

122
Users / Re: HomeOS - Microsoft reinvents LinuxMCE
« on: May 09, 2012, 09:08:02 pm »
kyfalcon,

do you need any more pointers to start?

Kyfalcon,

Me thinks you've been "volun-told"...  ;)

/Mike

123
Users / Re: Design Question - New system install
« on: May 08, 2012, 07:55:56 pm »
JaseP,

I personally can't get access to my PCI/PCIe cards, only because my motherboard doesn't support AMD's IOMMU (the technology that allows you to map the physical devices to virtual machines).  VT/d is the Intel version.  Most server-class motherboards support it, which allows for Xen's/KVM's PCI pass-through to work in datacentre environments.  Ditto for VM-DirectPath, which is VMWare's version of the same concepts.  So, if I wanted to fork out the money for an 890FX or higher chipset motherboard, I could get it to work.  I'm not rolling in dough, so I'll be improvising by running a Myth-backend on the Host OS which will manage the cards, while the master backend resides in a VM.  Next time I have to life-cycle hardware, I'll be getting a mobo with IOMMU support.

So, yes it does work; it's just dependent on having the right hardware support for it.  The processor, chipset and BIOS all have to support it, which can be challenging with consumer hardware.  It can be more challenging with Intel, because some processors support VT/d, and some don't; buyer beware.  The only downside to passing through cards is that it negates the ability to Vmotion a guest from one host to another, because it introduces a physical dependency.

Hope that helps!

/Mike

124
Users / Re: Recommended alarm panels?
« on: May 08, 2012, 02:33:53 pm »
I have a Texecom 816....
Got the Serial connector to my Core, and thats about it.
Still getting around to learn C+ so that I can try and intergrate.

Karel

Karel,

If it's a Serial connector, a GSD is probably more appropriate, and probably a lower entry level than learning C++.  There may be existing templates you can re-use, and simply replace the appropriate commands with those from your alarm panels protocol page.

HTH!

/Mike

125
Users / Re: Design Question - New system install
« on: May 08, 2012, 02:51:51 am »
He might have other workload he wants to run on that same server.  There's nothing wrong with virtualizing the core (or anything else for that matter) if you have the reason and know what you're doing.  I'm running 5 other VM's in addition to a virtual LMCE core, which lets me experiment with LMCE without disrupting the "production" environment.  I'll probably stand up anther Virtual core as a dev environment to work on some stuff, and connect it to the virtual MD I sometimes play with.

On a six core AMD 2.8GHz system with 8GB RAM, I'm running the Core, a Windows Home Server 2011 instance (iTunes server for all the iDevices), a Astaro VPN end-point server, my mail/calendar server (Zarafa), MrHouse home automation, and a Ubuntu Desktop environment as a virtual hosted desktop.  During peaks, my load is about half what the system is capable of; I'm I/O bound more than CPU bound due to SATA disks.  When SSD's drop in price, I'm going to pick up a bigger one for the VM disk storage (I have the various databases on LVM's from a 40G SSD to handle the IOPS requirements, and to lessen the load/latency from the disks).

As far as networking goes, I have two NIC's in the system.  Eth0 is br_ext, a bridged network device connected to my home router which gives outside access.  Eth1 is br_int, another bridge, but for the internal LMCE managed network. The core owns that network, so any physical device connected to the switch on that NIC is seen by the core, as is any virtual Server connected to the br_int.  The virtual core's eth0 is connected to br_ext for Internet access, and for access from the existing production environment.  It's eth1 is connected to br_int, and it provides dhcp and all related services to the "internal" network, as per LMCE's architecture.  So, I can run both environments in parallel, without affecting the wife and kids.

So, the takeaway is, if you have a reason to virtualize it, go for it.  If you don't have a use-case figured out, then you might not want to, because it can be more work.  With great flexibility comes a lot of (your) overhead.

Hope that helps!

/Mike

126
Users / Re: Cameras, Motion, and notifications
« on: May 07, 2012, 03:47:36 am »
Mike

Did you get anywhere with this? I've been planning to head down the same route... experimenting with using my IP camera to generate events based on motion detection. Also still struggling a bit searching the wiki and forums to see if there is a "standard" way to do it.

James


James,

You can generate e-mail alerts using the respond to events Wizard.  The basic gist of it is:

A sensor is tripped, what device equals your camera, when = Day, Night, or blank, What trigger state = tripped = 1.

You can then add commands using the advanced wizard.

Pick the General info Plugin on the core, and choose event Send Email.  Fill in the blanks as listed.  That will just send you an e-mail; no pictures attached.  Presuming you're on 10.04, you'll need the package 'heirloom-mailx' installed; that is the mailx that modern Ubuntu's are using now.  The Mailx template listed in the Wiki is no longer necessary, and probably should be removed from the wiki to prevent confusion.

It would be cool if the General Info plugin Send email function was extended to support directly adding attachments, and for allowing a script to be run which is then piped into the mailx command for e-mailing.  The security plugin might need to be extended to transfer/transmit security and sensor data to the Send E-mail function.  Just thoughts... I'm not volunteering you for anything  ;)

I'm looking at Kmotion2, but starting to think that integrating it might not be the best idea.  It may be better to figure out how the masks and other advanced functionality is done, and add that directly into LMCE Web-Admin pages.  Give me a couple of months to figure this out; I'll likely post interim measures along the way.  I've done some PHP scripting in the past and fairly recently, so I'm a less intimidated by that than by C++ code.

Hope that helps!

/Mike

P.S.  I found some folks who have configured their (non-LMCE) motion.conf  to send e-mails with picture attachements.

on_picture_save mailx -s “Test mail” -a %f email@gmail.com

127
Users / Re: Cameras, Motion, and notifications
« on: May 07, 2012, 03:22:02 am »
Question to anyone presently using the Cameras functionality.  How do you presently access or view the stored camera footage?  I don't see anywhere to view the stored events/alerts in the Roaming Orb Orbiter, I only see it in the LMCE Web Admin (Security -> Alerts Log).  Am I correct in assuming that this functionality is presently limited to the WebAdmin only (meaning not present in MD Orbiters)?

Thanks for your time!

/Mike

128
Users / Re: Is it supposed to behave like this?
« on: May 04, 2012, 05:53:57 pm »
Kyfalcon,

The problem is more that RoamingOrb (or the Dianemo iOS app) displays nothing at all; they won't load any screens if a "modal" type dialog is on the regular orbiters.  You launch the app and it spins away doing nothing.  Attempting to log into the web orbiter does the same thing; there is no orbiter UI.  This could lead the user to believe that the "system" is broken if they don't have a regular orbiter to see the message on.  There might be a reason for this behaviour, in which case something should be done on the WebOrbiter or WebAdmin to allow the user to understand that their input/action is required.  If there isn't a reason for this behaviour, then I guess a bug would need to be filed.

Don't know for sure, but it might relate to an existing bug: http://svn.linuxmce.org/trac.cgi/ticket/548

My concern is for the End-user experience for those who might have a core, uPnP boxes only for media, and iDevices for controlling it, which could be a use-case for people just getting into LMCE with entry level or existing hardware.

Thanks for your time!

/Mike

129
Users / Re: Cameras, Motion, and notifications
« on: May 04, 2012, 05:01:36 pm »
Jamo,

Cool!  Thanks!  Being a SysAdmin type, my strengths are more in the system and infrastructure layers, so I'll look at getting Kmotion2 and motion playing nicely together.  We'll definitely trade notes...

Thanks for the assist!

/Mike

130
Users / Re: Cameras, Motion, and notifications
« on: May 04, 2012, 03:25:13 pm »
Jamo,

I've installed Kmotion2, but haven't got it all working yet.  I haven't had a lot of free time to investigate, as I'm doing a college zOS course on the side, and it's chewed up way more time than I'd anticipated.

I'm still trying to figure out how to integrate it cleanly, so that MotionWrapper and Kmotion2 don't fight over control of the cameras or events.  Kmotion2 expects to do the camera configuration and management, and it's not managed the same as the underlying motion on the system.  Plus I'll have to figure out how some of the LMCE infrastructure works, so it would all work "automagically"... so, I've got a bit of a learning curve ahead of me.  I might also look at ZoneMinder as an alternative front-end and for events, just to compare/contrast functionality, capabilities and possible integrations.  (I've rolled out ZoneMinder in the past).

The ironic thing is that I first started looking at LMCE as a means to reduce the level of effort required to maintain my own "home-rolled" infrastructure... ;)

Sorry I can't be of more help than that!

/Mike

131
Users / Is it supposed to behave like this?
« on: May 04, 2012, 03:14:49 pm »
Morning folks!

I've been playing around with LMCE 10.04 in a test environment for a while now.  I'm mostly using iDevices and RoamingOrb to access it, and I've noticed that if the core has detected a NAS or something like that which causes a message to appear on the Orbiters asking the user to do something about it, the Proxy/Web Orbiters that RoamingOrb depend on are blocked and become un-responsive.  The web orbiter is also similarly blank.  Is it supposed to behave that way?  Could something be done to prevent the RoamingOrb orbiters from being blocked?  I'm thinking of the use case where someone might only have iDevices and uPnP boxes, and a blocking event might cause the (non-technical) user to think the system was broken or locked up.

Thanks for your time!

/Mike

132
I would think that Myth 0.25 is going to be a huge improvement over 0.23 in terms of integration.  It really looks like the Myth devs have put some thought into how it integrates into other things.  The services API exposes a lot of the set-up and operational aspects of MythTV to external control, which in theory could be put into the LMCE Myth plugin.  Similarly, the Myth System Events could be used to send DCE messages to indicate to the DCErouter (and the rest of the LMCE system) what Myth is doing.

http://www.mythtv.org/wiki/Services_API

The Capture service is a series of APIs related to the capturing of recorded content. It includes methods of settings up capture devices, card inputs, and may also be expanded in the future to more directly control those interfaces.

The Channel service is a collection of methods for editing channels, adding channels, deleting channels, and modifying lineups and XMLTV services.

The Content services provides a means of serving video, music, and image content from your MythTV system's collection. Images can be dynamically scaled and served by the backend according to your request.

The DVR service allows the programmer to interface with recorded metadata in a variety of ways.

The Frontend service is actually run on Frontend systems (default port: 6547) and allows query of location, playback status, sending remote control messages, and sending popup messages, among other tasks.

The Guide service is a group of methods for accessing the program guide information for use in scheduling, and guide grid applications.

The Myth service is dedicated to MythTV specific settings, and is a series of utility APIs for influencing the way MythTV works on a low level including Storage Group configuration, settings modification and query, hardware profiling, and database backup and repair.

The Video service is used to query and modify video metadata, look up metadata, add new videos to the library, and other video-library-specific functionality.

http://www.mythtv.org/wiki/MythTV_System_Events

    * Recording pending
    * Recording started
    * Recording finished
    * Recording deleted
    * Recording expired
    * LiveTV started
    * Playback started
    * Playback stopped
    * Playback paused
    * Playback unpaused
    * Playback program changed
    * Master backend started
    * Master backend shutdown
    * Client connected to master backend
    * Client disconnected from master backend
    * Slave backend connected to master
    * Slave backend disconnected from master
    * Network Control client connected
    * Network Control client disconnected
    * mythfilldatabase ran
    * Scheduler ran
    * Settings cache cleared

I've un-installed the MythTV plugins from my test LMCE system, and am looking at getting Myth 0.25 running and stable from the infrastructure point of view on my 10.04 LMCE test system.  I'm a SysAdmin, not a programmer, so the LMCE Plugins are beyond my ability and available time for the foreseeable future.  If a real programmer wants to take a crack at the plugins, I'm more than willing to help at the infrastructure layer and with testing  (although it'll have to be in a couple of weeks; my z/OS final exams are coming up soon!).

BTW, 12.04 will bring other complexities with it due to the re-basing of the kernel, drivers and utilities, and user-land, so it may be better to make the new Myth (and other major infrastructure changes like qOrbiter) work on 10.04 first, and then port forward to 12.04.

Hope that helps!

/Mike

133
I'm not using LMCE in production right now; I'm testing it and playing with some proof-of-concept ideas that I'll throw forward for inclusion when I get them usable.

I am running a production MythTV 0.24 environment, with a master back-end, a slave back-end/front-end, and three other front-ends.  The Slave and the front-ends all run MiniMyth.  I'll likely be upgrading them to 0.25 when Debian-Multimedia has it in stable.  I've run Myth since 0.21 (with Freevo for three years before that), and it's been generally stable and the WAF/KAF has been high.  The Myth stats page shows 4050 episodes recorded over the last three years, with a mixture of Analog cable, Digital OTA, and a Digital cable box (6 tuners in total).

Myth and VDR both exist in LMCE now for a reason.  Some of those reasons may be technical, some may be historical.  Out of curiosity, I'd posted a poll asking what people were using.  76% of the people who had responded indicated they were using Myth.  I believe Dianemo has moved to using primarily MythTV (Dianemo users are welcome to correct me if I'm mistaken).  It would be interesting to see a technical comparison between the two, and see where the strengths and weaknesses are between the two, and how well each can/do integrate into the LMCE system.  That kind of capability and requirements analysis could help drive decisions around architecture and features.  It doesn't necessarily mean that the less capable is removed; if the devs wish to support both, it could be used as a tool to drive innovation to address the deficiencies.  It could also determine where to best spend limited amounts of developer time if there's a huge gap in capabilities.

As best as I can see, VDR basically supports DVB and MPEG encoder cards, plus some European IPTV providers (again, correct me if I'm wrong).  MythTV supports those plus the HDHomeRun series, the Ceton cards, ATSC tuner cards, and the HDPVR.  So, where a user lives, what their input sources are, and what hardware they have access to will drive the choice of VDR vs MythTV.  At the very least, quantifying some of that could be useful in setting AVwizard defaults, and building documentation in the Wiki.

My $0.02 worth before HST...

/Mike


134
Folks,

Just as a point of interest, Robert McNamara of the Torc project (torcdvr.com - a fork of MythTV) has submitted for App store approval an iOS Universal app which leverages the 0.25 Services API to create a remote control and stream/viewing application for iPads/iPhones/iPods.  It's a native iOS app, and all it's functionality is via the Services API.

http://www.gossamer-threads.com/lists/mythtv/users/513724#513724

http://www.youtube.com/watch?v=uxQDLTSucxM

http://www.youtube.com/watch?v=uGoU90bdUC8

That could bode well for a stable interface for LMCE into Myth for all aspects of control.

Just thought I'd pass that along...

/Mike

135
Users / Re: MD idle shutdown?
« on: April 24, 2012, 04:52:31 am »
JaseP,

Thanks for the pointer.  I'm not looking for that so much as for the usual kids leaving it on, or the auto-wake when the router reloads.

I'm using MiniMyth right now, and use a script to shutdown a slave backend when it's sitting on the MythWelcome screen.  I'd planned to expand it to look at how long the screensaver was running for, but haven't gotten around to it yet.

For anyone who's interested, here's the script...

Code: [Select]
#!/bin/bash
#
# Script to safely shutdown slave backend
# Minimum uptime in minutes to avoid shutting down prematurely.
MIN_UPTIME=20
#SHUTDOWNCMD="su -c /usr/bin/mm_sleep root"
SHUTDOWNCMD="/sbin/poweroff"

date

UPTIME=`uptime |cut -f4 -d" "`
UPTIME_UNITS=`uptime |cut -f5 -d" " |tr -d ','`

echo "Uptime:" $UPTIME $UPTIME_UNITS

if [[ $UPTIME_UNITS == "min" ]] && [[ $UPTIME -lt $MIN_UPTIME ]]
    then
echo "Uptime less than minimum uptime:" $MIN_UPTIME
exit 1
fi

# Check if mythfrontend is running, exit if true
if ps -C mythfrontend | grep mythfrontend -c
then
echo "Mythfrontend running, shutdown aborted"
exit 1
fi


mythshutdown -s
STATUS=$?

echo "MythStatus code:" $STATUS
#   0 - Idle
#                         1 - Transcoding
#                         2 - Commercial Flagging
#                         4 - Grabbing EPG data
#                         8 - Recording - only valid if flag is 1
#                        16 - Locked
#                        32 - Jobs running or pending
#                        64 - In a daily wakeup/shutdown period
#                       128 - Less than 15 minutes to next wakeup period
#                       255 - Setup is running

case "$STATUS" in

  0)
echo "Myth is idle, shutting down now"
mythshutdown --setscheduledwakeup
        su -c 'rm /etc/rc.d/rc/K60modules_automatic' root
        mm_service backend stop
        `$SHUTDOWNCMD`
  ;;

  8|40)
        echo "Myth is busy recording"
        exit 1
  ;;

  16)
        echo "Myth is locked, aborting shutdown"
        exit 1
  ;;


  32|33|34|35)
        echo "Jobs running"
        # Check if mythcommflag is running locally, exit if true
        if ps -C mythcommflag | grep mythcommflag -c
            then
                echo "Mythcommflag running, shutdown aborted"
                exit 1
        fi
        # Check if mythtranscode is running locally, exit if true
        if ps -C mythtranscode | grep mythtranscode -c
            then
                echo "Mythtranscode running, shutdown aborted"
                exit 1
        fi
        # This backend isn't busy with jobs, so shutdown
        echo "This backend is idle, shutting down now"
        mythshutdown --setscheduledwakeup
        su -c 'rm /etc/rc.d/rc/K60modules_automatic' root
        mm_service backend stop
        `$SHUTDOWNCMD`

    ;;


  64|128)
        echo "Awake on purpose"
        exit 1
    ;;

    *)
        echo "Busy with unknown tasks, presume this backend is busy"
        exit 1
        ;;
esac


Hope that helps fuel someone's creativity should they get around to this before I do (which is more than likely as my course runs till mid May)

/Mike

Pages: 1 ... 7 8 [9] 10 11 ... 13