As you can see from previous posts, I’ve started automating my house. There was an ADT alarm system installed. I was given a user code, but that was it. I opted not to pay ADT’s ridiculous monthly fee since reasonable monitoring can be had for $10/month.
Looking at the panel, I have a Safewatch Pro 3000, which the internets tells me is close to a honeywell/ademco vista20p without a couple features like zone doubling.
I have a simple touchpad, not an alpha display, probably similar to the 6150, so it’s terrible to program with.
Sometimes I feel a need to automate some meme generation. Luckily I found this incredibly helpful blogpost from jackmeme. http://www.jackmeme.com/blog.php?id=1
The first thing I thought of with automated meme generation? The Weather! See my previous post about getting data from the Weather Underground API using Perl
This naturally lead to the forecast overlaid on the current radar.
Inspired by http://thefuckingweather.com/, I decided I want my daily forecast in meme form. The first weather-related meme I think of is Ollie Williams.
But that doesn’t really fit with the meme. Change fucking to motherfucking and Samuel L Jackson is PERFECT!
Smoosh those memes together and I’ve got my morning weather!
I found another source of amusement while playing with generating image macros. There is a Pyborg bot in one of the IRC channels I frequent. “She” says some pretty funny stuff, so we keep a quote list. Of course this is ripe for meme-ifying.
What does all this mean? This heavily redacted screenshot should give some idea.
Number of overall motion events over time, same for failure events. Top list of cameras with motion events, top list of cameras with failure events.
Have you heard of Logstash / ElasticSearch / Kibana? I don’t wanna oversell it, but it’s AMAZING!
I’ll start with a screenshot. You know you want this. I have to blur a few things to keep some 53cr375 about my environment.
This is my configuration for collecting Windows event logs. I’m still working out the differences between the Windows XP, Server 2008R2, and Windows 7 computers I’m collecting logs from, but this has already proven very useful.
It’s that time again! Another construction project at work!
It was decided that I would run another time-lapse webcam of the construction process. This was a little last-minute. Our electrician mounted an analog camera and plugged into a network video encoder. http://www.axis.com/products/cam_m7001/
I haven’t had time to set up a proper linux box to manage all this so I threw together a batch file and a scheduled task to run on my workstation every 5 minutes until I get the rest set up.
This uses my favorite method of generating zero padded time & date stamp files. It concatenates 0 and the variable then selects the right 2 characters.
constructioncamgrab.bat
[plain]
@echo off
REM Create the date and time elements.
for /f "tokens=1-7 delims=:/-, " %%i in (‘echo exit^|cmd /q /k"prompt $d $t"’) do (
for /f "tokens=2-4 delims=/-,() skip=1" %%a in (‘echo.^|date’) do (
set %%a=%%j
set %%b=%%k
set %%c=%%l
set hh=%%m
set min=%%n
)
)
REM zero-pad and see the result
set mm=0%mm%
set mm=%mm:~-2%
set dd=0%dd%
set dd=%dd:~-2%
set hh=0%hh%
set hh=%hh:~-2%
set min=0%min%
set min=%min:~-2%
echo %yy%%mm%%dd%%hh%%min%
set outFile=C:construction_cam%yy%%mm%%dd%%hh%%min%.jpg
NOTE: If the screen width isn’t an exact multiple of 8, the video grabbed by dshow won’t play correctly in VLC. It will look garbled like black with diagonal lines.
For example: my laptop’s resolution is 1366×768. 1360 is a multiple of 8, but 1366 isn’t. It wasn’t until I had dshow scale the output to 1280×720 that I was able to get usable video into VLC.
Now that I can view the dshow video without trouble, I’m ready to encode to h.264 and segment for HLS.
VLC_Desktop_Stream.bat
[text]
@echo off
rem Start Stream
del /q C:xampphtdocsstream*
"C:Program Files (x86)VideoLANVLCvlc.exe" -I dummy dshow:// :dshow-vdev=screen-capture-recorder :dshow-adev=virtual-audio-capturer :dshow-aspect-ratio=16:9 vlc://quit –sout=#transcode{width=1280,height=720,fps=10,vcodec=h264,venc=x264{aud,profile=baseline,level=30,keyint=10,ref=1},acodec=mp3,ab=96}:std{access=livehttp{seglen=1,delsegs=true,numsegs=5,index=C:xampphtdocsstreammystream.m3u8,index-url=http://192.168.5.55/stream/mystream-########.ts},mux=ts{use-key-frames},dst=C:xampphtdocsstreammystream-########.ts}
[/text]
Note: Some devices honor the video stream’s stated aspect ratio, even if the video dimensions are different. My screen is 16:10, but I’m smooshing to 16:9. To make this work correctly, I had to specify the dshow aspect ratio as 16:9. No amount of fussing with it on the transcode side will fix this. It defaults to 4:3.
The simplevideoplayer example will play HLS and is simple enough for this.
RokuSDK_v41.zipexamplessourcesimplevideoplayer
Comment out the other video source lines in appMain.brs and change the URL under Apple’s HLS test stream to your local webserver.
Note: For some reason, this did not play unless I had srt = “” set.
appMain.brs
[text]
‘Apple’s HLS test stream
urls = ["http://192.168.5.55/stream/mystream.m3u8"%5D
qualities = ["HD"]
streamformat = "hls"
title = "Apple BipBop Test Stream"
srt = ""
[/text]
I am a huge fan of Torque OBDII reader for android (Torque Pro) with Torque Track Recorder. It kinda sucks on my original Motorola Droid so I wanted to get it working on my Nexus 7. Which got me really excited about hooking up a webcam to my nexus 7. (I currently have an iPhone 4 so that’s not an option)
# format, cameraName=device,direction,orientation,type
# type can be ‘stereo’ for stereo capable, ‘mono’ for not stereo capable,
# ‘usb’ to enable searching for a usb device and where to put it in the list
# if found. Lines must be shorter then 256 characters
version=1
camera0=/dev/mi1040,front,270,mono // front camera
usb=/dev/video0
Motivation:
My fiance and I have a stack of DVDs. They’re dusty and inconvenient. I wanted to rip them to my network storage so I can easily watch them from my Boxee Box. It’s not that I’m lazy, but I hate doing repetative things if I can automate it.
Overview:
I’m using Perl with Win32::SerialPort to control the autoloader. I’m using Win32::DriveInfo to get the volume name of the DVD. I’m using TMDB on the off chance the volumename will pull up the movie. I’m using DVDFab 8 to rip mainmovie to an ISO file. I’m using Handbrake to encode to iPad preset. In my testing, this looks just as good as the ISO file and uses only 20-30% of the space.
To use I batch together either all movies, or all TV shows. I rip my movies into my mapped network drive, V:queue and my TV shows into V:TV_queue
I have my faster computers actually do the encoding. Multiple computers. I map the V: drive to the same fileshare. I encode my movies to V:Encoded and my TV shows to V:TV_Encoded
ripinator.pl
Main program. It requires gripper, ripper, and traycmds. I broke this into multiple pieces to make it easier for me to keep track of.
Enumerates all CD/DVD drives attached to the computer and iterates through them probing the gripper arm to each tray. If a tray is detected, the drive number and drive letter are noted.
It then checks the levels of the bins.
If there are discs in the desginated input bin, it will load them into the drives and start the ripper.pl script
If there are discs done ripping, it will unload them into either the reject bin, or the output bin, depending on the exit code
This will continue until either something crashes, a disc is completely unreadable, or there are no more discs left to rip.
gripper.pl Description:
Contains subs Required Setup:
Set COM port on line 218
getVersion()
Returns the version of the autoloader’s firmware
getSerialNumber()
returns the serial number of the autoloader
goHome()
moves the gripper arm to the top of the unit
getStatus()
Queries the autoloader’s status. See command notes for more info
getPosition()
Gets the current position of the gripper arm
getBin($bin)
gets a disc from the specified bin
putBin($bin)
puts a disc in the specified bin
getDrive()
gets a disc from the specified drive
putDrive()
puts a disc in the specified drive
probeTray()
probes the gripper arm to the disc tray, returns drive number
sendCommand()
sends a command to the autloader. see command notes for more info
traycmds.pl Description:
Contains subs Required Setup:
Put nircmd in C:nircmdnircmd.exe
@allDVDdrives = closeAllDrives()
Closes all CD/DVD drives. Returns an array of all the CD/DVD drives attached to the computer.
closeDrive($drive)
Closes the specified drive
openDrive($drive)
opensthe specified drive
getVolName($drive)
gets the volume label of the specified drive
ripper.pl Usage:
perl ripper.pl $drive $tray Description:
Rips DVD to specified location. makes and removes lock files for ripinator. Looks up TMDB, if available, uses moviename and year for filename, if not, uses volumename. Required Setup:
Get an API key for TMDB
set $dest_dir where you want ripped DVD ISO files to be stored
set $dvdfab as path to dvdfab.exe
enter TMDB API kay on line 96
cmdtest.pl Usage:
perl cmdtest.pl !e1C Description:
Allows sending commands to the autoloader
encodemovies.pl Usage:
perl encodemovies.pl Description:
Encodes ISO files to iPad preset m4v with handbrake.
Required Setup:
Set machine name, path to handbrake, source and destination folders.
encodetv.pl Usage:
perl encodetv.pl Description:
Encodes ISO files to iPad preset m4v with handbrake. Splits each title into a separate file. Required Setup:
Set machine name, path to handbrake, source and destination folders.
Back Story:
A few years ago, we had a Rimage DVD production robot at work. I dubbed it Trogdor the Burninator. Rimage had some pretty scummy practices… The ink cartridges are standard HP cartridges, but had a little tag in the label that will keep the software from loading if you don’t buy the Rimage branded cartridges. I’m sure they would have gouged even more if they could think of a way to do it. So we replaced it with a newer, nicer one from Primera. It was an improvement in pretty much every way. I got the old one since no one else wanted it. SCORE!
I took it up as a project again. I had saved the old software from Rimage and was able to get it to run for 30 days between wiping and reloading the computer it was attached to. This was enough time to determine that the connection between the printer and the RAS 13 autoloader was RS232 serial. I sniffed the traffic between long enough to figure out which commands did what, and what replies meant. This is by no means definitive, but it’s enough to use an otherwise useless piece of equipment.
