Mick West

Love the little trade which thou hast learned, and be content therewith

November 26th, 2007

Wiring the house with Cat5e for Gigabit Ethernet

I’d been using wireless networking at home, and generally this worked fairly well. But a couple of things were problematic. Firstly it would occasionally go out for a few minutes at random (which I ascribed to the neighbor’s wireless phone). Secondly it was rather slow using Media Center Extender for the XBox 360. It seemed to work for streaming regular definition video, but anyhing higher was dodgy, and navigating menus of content (like photos) was painfully slow.

So I decided I’d upgrade from the podunk 54Mb/s to a stunning 1000Mb/s fully switched network.

img_4350_300.jpg

This meant I had to install six wall sockets. One for the internet connection (in the kitchen, for some odd reason), one for the new switch (in a cupboard, out of the way), and four outlets (3 in the bedrooms, one in the living room for the Xbox. That means I have to lay five Cat5e cables, each one going from the switch to an outlet.
Having never done this before, I was a little uncertain how to go about it. Luckily many have gone before me.

Cutting the holes in the wall was not something I was looking forward to, as patching drywall always seems to go badly for me. I thought at first I’d have to cut large chunks out so I could install junction boxes to the studs. But I eventually figured I could just cut small holes in the wall (see pic), and then mount the faceplate with self-drilling drywall anchors. This worked out really well. Just pre-drill 1/4″ holes for the anchors to avoid crumbling the edges of the hole. It’s pretty solid.

Up in the attic there’s a whole mess of wires. It took me a while to find out the correct spots. I mostly went by existing wiring, and hence my network outlets ended up next to my cable outlets. I drilled 1/2″ holes in the header beams where needed. 1/2″ can take four Cat5e cables (so I needed 2 for the switch).

img_4409_400.jpgc184-03791.jpgIt took a few hours to get all the cable in place. Then it was simply a case of wiring the sockets. These use a standard “keystone”, which is all color coded, and very easy to wire (just double check it). The sockets come with a little plastic tool to set the wires. You don’t need any special tools, just remove an inch of the blue outer insulation (from the cable, not the wires). Then keep the wires as twisted as possible, and push them into the color coded connectors, and push them down with the tool. (Same color configuration at each end – the keystones have an ‘A’ and ‘B’ config, just use ‘A’ for everything).

I used a six outlet plate at the switch (five outlets, one cover plate). If you have more you’d use a patch panel, but this looks very neat. One problem was that the hole had to be larger, so the large anchors did not work very well. I used plain 1″ drywall screws, but you could possibly use smaller wall plugs (or actually stick a box in there). When everything was wired up, I hooked up patch cables to all the devices, and the gigabit switch, and turned it on. Everything worked first time. Woo hoo, 80 wires set in place without mistake.

Of course it’s not actually gigabit, since all the devices are actually 100Mb, but the 5-port gigaBIT switch (a D-Link DGS-2205) was only$30 or so. If I get some gigabit devices in the future, then all will be well. The cable runs were pretty short as well (like 25 feet max) so it could probably do 10Gb later.

Results? Well, the internet now no longer goes out. Media center is a lot faster – actually very usable now for browsing through photos. Everything went according to plan. Very odd.

Parts List:

Tools used

  • Drywall saw
  • Wire setting tool (comes with keystone sockets)
  • Drill with long 1/2″ bit for drilling through headers
  • Fish tape for pushing/pulling wire, especially through walls with insulation.
  • String (sometimes easier to push string through with the fishtape, then pull cable)
  • Screwdriver

Took about six hours of work.

November 10th, 2007

Fun with Ulead Video Studio and Panasonic HDC-SD1

Panasonic HDC-SD1 AVCHD 3CCD Flash Memory High Definition Camcorder with 12x Optical Image Stabilized ZoomThe Panasonic HDC-SD1 is a very nice little video camera that records High Definition video. We bought it for our trip to Alaska earlier this year, but did not really use it very much. But a couple of days ago Holly used it in videoing the birth of a new cousin, and this gave us 55 minutes of high definition video to do something with.

The SD1 records on SD-HC (Secure Digital – High Capacity) cards. We were using a 4-gig card (that’s what the camera comes with), and the 55 minutes resulted in 3.38GB of files. Most of these are the actual video and audio that is stored in .M2TS files – this is part of a kind of super mpeg format used in BluRay DVDs called AVCHD. The .M2TS files are really all you need, but they are surrounded by a directory structure which starts with the AVCHDL folder, and the M2TS files are hidden away in the AVCHDL\BDMV\STREAM (or more precisely in HDWRITER\071109_1\PRIVATE\AVCHDL\BDMV\STREAM).

This is all starting to sound rather complicated. The problem here is that AVCHD is still a fairly new format, and the programs for dealing with it are not particulalry user friendly. A case in point is the software that comes with the SD1, called “HDWriter”, which is of limited functionality, and rather confusing to use. However, it does let you burn regular DVDs of various clips, with some simple editing. And given what I was trying to do, I think I should have just used that for my initial DVD burning.

But no, I decided I needed some proper video editing software, so after a little bit of research I downloaded the trial version of Ulead Video Studio Plus, and started to use that.

The first problem you encounter was how to get the video into Ulead. I tried dragging the M2TS files in, but no dice. I then tried connecting the camera, and importing from the camera, but still no luck. A bit more googling led me to the correct solution, which was to click on “Capture from Disk”, and treat the camera as a removable hard drive, navigating down until you find the AVCHD, at which point you can import everything. That was a rather tedious process, as you have to select each clip individually, and selecting a clip takes a few seconds. Bu eventually all was selected, and I started to import.

Things seemed to be going well, and I burnt a DVD fairly easily using the first clip (about 45 seconds) and it did not seem to take particularly long. So I though I’d make a DVD with all the clips. That’s 55 minutes in total. So I plonk them all on the timeline, chose one of the cheesy DVD menu templates, and start burning.

20 hours later, out pops a non-working disc.

Yup, 20 hours. It actually took 20 hours to make a DVD. I was expecting maybe 2-3 hours, given that it had nearly an hour of high definition video to decode and recode, but 20 hours? I guess I was just being overly optimistic. I was doing the encoding a 1.66Ghz Centrino duo laptop with 1GB of RAM. Not the meatiest beast in the world. It probably would have been 3 times as fast if I’d used my Desktop machine. At least with the laptop we could just set it going, and leave it going, all day, all night, and a bit of the next day.

Then it did not work. It turns out though that this was just a bad disk. Luckily I’d told it to save an image of the disk, and I was able to simply burn a copy of that and it all worked.

What does this fun tell me? High definition video editing is not quite ready for prime time. I seems like everyone just wants to share their video over the internet anyway, and HD support is being left for people with a bit of time on their hands. Simply recording a one hour DVD from HD source took 20 hours. A faster machine would cut that down to 6-7 hours, but still.

Right now I’m recoding everything as 720×480 DVD format mpegs, seeing as that’s my target format anyway, hopefully it will be a bit easier to work with. It’s nearly finished converting now, been going about six hours. This is just using the batch convert in ULead VideoStudio, there’s probably some much faster method. I’ll have a look into it.

[UPDATE] We ended up using Adobe Premier Elements 4.0 with the converted mpegs to put together the DVD. It turned out though that the MPEGs were not really that much smaller than the m2ts on the disk. Of course they are easier to work with as they use less processor power. The mastering time for a ten minute DVD was practically real time, like 10-15 minutes, which I was very happy with. I’ve no idea how it would be with m2ts files. It did crash a few times, but just about bearable.

|