I just added a new video clip of Justin "babytalking" into a toy phone at Aunty Corrina's apartment on August 16, 2003. 3 separate video clips (AVI format using Motion-JPEG compression) were shot using a Canon PowerShot G1 still camera then combined (using just copy and paste) into a 53-second video using QuickTime Player Pro 6.3 on my PowerBook G4/500 running Mac OS X 10.2.6. In QuickTime Player Pro, I then exported the combined file to an uncompressed AVI file (file ballooned to 179MB from original 12MB QuickTime file). I then used Windows Media Encoder 7.1 to create a 1.7MB Windows Media Video format file using WM8 compression for the PC version. For the Mac version, I exported to a 2MB QuickTime movie file using the "DSL/Cable - Medium" and "Fast Start - Compressed Header" settings and MPEG-4 compression (QuickTime Player 6 or higher required).
Cool!... Just tonight, a fairly detailed email I submitted about network cameras was posted on the popular Macintouch site. I emailed it out to the Macintouch guys at 5:38pm my time and like 5 hours later it was up on the site. Here's what I wrote:
The popularity of "network cameras" is definitely gaining. These are cameras that have an embedded Web server (usually Linux-based), connect directly to a network (no computer required), and stream live video to Web browsers (among other capabilities such as uploading still JPEGs to another server, motion detection, email alerts). I have an AXIS 2100 network camera at home pointed most of the time in the area our baby plays. This allows my wife and me to see live video (displayed in our Web browsers) of our baby from our offices. It also allows our parents to see their grandchild from Hawaii or Singapore too (we reside in Hong Kong).The "1st generation" network cameras use Motion-JPEG as a compression format to stream the video (my AXIS 2100 uses this). When a user first visits the camera Web page, a Java or ActiveX applet quickly downloads and installs in the user's browser and the video then starts streaming. On subsequent visits the video just instantly shows up — applet is not re-downloaded.
The "new generation" of network cameras use MPEG-4 which supports both video and audio in a single stream (Motion-JPEG only supports video so with optional audio in a separate stream, there can be AV sync problems). Some of the new models have a Pan/Tilt/Zoom control feature and work over a wireless 802.11b connection. The problem is that NONE of these cool, new MPEG-4 network cameras work with Macs!
Even the cameras that do claim to be Mac compatible have glitches. For instance, on a Mac, the video from my AXIS 2100 tends to flicker; on a PC it's a smooth as silk. With an AXIS 2130 PTZ camera demo I tried viewing from my PowerBook G4/500MHz/768MB running OS X 10.2.6 and using Internet Explorer 5.2, the video flickered badly and parts of the page seemed to completely reload. With the Safari 1.0 (v85) browser, although the Pan/Tilt/Zoom/Iris controls and preset-position pop-down menu showed up, the video never did.
So here is another cool technology that Mac users are really missing out on. I wonder if the problem is with the Mac Web browsers, the Mac OS, the Java/ActiveX applet provided by the camera makers, or a combination of factors.
I'm hoping this situation can improve with, perhaps, Apple helping some of these camera makers to rework their Java/ActiveX applets to work with Macs. Also, the more Mac users who pressure the camera makers to make their products compatible with Macs, the better.
Here's a list I compiled of some network camera manufacturers:
References:"1st generation" network cameras [Tom's Hardware Guide, Sep 2002]
AXIS 2130 PTZ camera review [Tom's Hardware Guide, Mar 2003]
I came back home tonight to find my Internet broadband connection not working. My cable modem was online (green light as usual) and so I telnetted into my ZyXEL Prestige 314 broadband router to check WAN IP address settings and everything looked just fine. Still, I was unable to ping to IPs that I know are always up (e.g. 202.14.67.4, DNS server for ISP Pacific Supernet Hong Kong). I called i-CABLE tech support and after a rundown of troubleshooting steps which took about 20 minutes and included cycling the power of my cable modem and router to reset the IP address, the tech guy ran out of options and told me he'd have someone else get back to me by tomorrow. I called tech support again to just double-check the correct Subnet Mask setting and got another tech guy. The Subnet Mask setting I had (255.255.254.0) was actually correct and I again went through the process of resetting the IP address with this new guy. After that didn't help, the tech guy suggested that I bypass my router and connect the cable modem directly to a computer via Ethernet cable. So I connected the cable modem directly to my PowerBook G4/500 running Mac OS X 10.2.6 and guess what?... My PowerBook got assigned a different IP and the connection worked! So with that, I thanked the tech guy because then I knew that the problem was on my end and specifically with my broadband router. So then using my PowerBook, I visited ZyXEL's download page over a painfully slow modem connection and downloaded a new firmware file. Using the router's Web interface I upgraded the firmware from version 3.50(CA.1) to 3.50(CA.3). Unbelievably, that did the trick!