Tuesday, June 07, 2005

Reducing heat in a multiple drive system: enable power saving

I'm not sure I know everything that went wrong with my Vantec/IDE saga, but it did make me very conscious of how darned hot my XP system is nowadays. I have 3 200 GB drives and one removeable 80GB drive in one tower case. I've added extra fans and, far more importantly, better room cooling, but there was one simple fix that didn't occur to me until recently. I used XP's power save utility to spin the drives down after 10 minutes of non-use. So far that hasn't bothered me at all and it sure drops heat output.

Sunday, June 05, 2005

systeminfo: handy XP command line system information utility

I thought I'd heard most XP tricks, but this one was new to me.

Atomic I/O letters column #45:
I'd like to be able to keep tabs on how long my WinXP computer's been running since the last time I rebooted. I know there are plenty of uptime monitoring utilities with all kinds of features, but can't I just use a console command?

Answer:

You're looking for the 'systeminfo' command. It defaults to spitting out a bunch of configuration data for the computer you're using, including the uptime. You can also use it with the /s option to get the same info from any other Win2000 or WinXP computer on your network - or on the Internet - for which you have a login. The /u and /p options let you specify the username and password.

Saturday, June 04, 2005

Repairing Permissions is Useless

Unsanity.org: Exercises in Futility Part 2: Repairing Permissions is Useless

"Repair permissions" is a common recommendation for OS X troubleshooting. Personally, I've had permissions problems with applications (incorrect group), but OS X disk utility repair permissions did nothing (I fixed the problem manually). This article explains why; the OS X utility seems only to repair permissions on a some core systems files. Any other permission problem, typically due to bad behavior by an app installer, cannot be fixed this way.

In practice corrupt preference files and corrupt caches are a much more common problem source than permissions repair.

The more savvy the tech writer, the more likely they are to say repairing permissions is grossly overrated.

Friday, June 03, 2005

iClip lite: a useful Tiger widget?

The Unofficial Apple Weblog (TUAW)

I've tried various multi-clip utilities, but this one appeals to me. Elegantly simple.

Macintosh Audio Recording: Ric Ford's review of the Edirol R-1 and OS X sound editing software

Macintosh Audio Recording (Part 7)

Ric Ford [MacInTouch]

In addition to what I wrote before (jf: about the Edirol R-1), here are some more observations after recording several concerts live:

* The levels display is a different mode in recording than in record-pause; you have to hit the Display button several times to get it. (Levels show only in these two modes.) Initially, with live music, I had the levels at about half. This proved to be way too low. I guess they're peak meters, rather than RMS or average meters, so you need to get them up pretty high for music with a large dynamic range. I did well keeping them at about 75% "full". (This is even more critical at 16 bits than at 24.)

* Sensitivity seems to be less than that of an Mbox. I had the input level all the way up for some low-volume stuff in a small hall, and the levels were pretty low. I was glad I had 24 bits when it came time to mix.

* As I'd hoped, the Audio-Technica AT-822 stereo mic is a great match for the R-1. Hook 'em up, get good mic placement and levels, and you should have a recording you can use for a high-quality CD with minimal minimal effort and processing. I like the AT-822 better than the built-in omnidirectional mics, at least in a hall with echo. The omnis got a little muddy with a big band and needed some help later with EQ.

* I've successfully used Lexar 80x WA 2GB CompactFlash card and a SanDisk Ultra II *4*GB CompactFlash card; once I finally figured out that the SanDisk card had a secret little switch to choose between two 2GB banks or the whole 4GB memory! Edirol warns that some Lexar cards can use too much power, which is why I bought the SanDisk, although I didn't notice a problem using the Lexar card.

* Here's a big warning: It's easy to confuse the similar power switch and "hold" switch. If you do, then change batteries with the power on, you can lose your recording! I did this once, and it was embarrassing to say the least. Now, I tend to hit "stop, record-pause, record" between songs to write the data to the card. Interestingly, I only lost the *middle* session out of several when I made the power-switch "cockpit error".

* I avoided the special effects processing during recording, trying for a cleaner recording and also to avoid their extra drain on battery life. I was afraid of running out of battery power at the wrong time, so I did the switch before it was necessary. I'm guessing battery life is about what Edirol estimates - some 2.5 hours on a set for recording. An AC adapter is included, too.

* With a good-sized CompactFlash card, the R-1 could also make a pretty nice music player. I bought some Apple in-ear headphones to get isolation and monitoring in a small package. They're not bad for monitoring, although I don't care much for the sound for critical listening (where's the midrange?). For that, my favorite headphones are the Audio-Technica ATH-40fs, which a MacInTouch reader and sound engineer told me about. They have wonderfully flat response, but only a 1/4" plug and a long straight cord. (Radio Shack sells 1/4" to 1/8" adapter/extension cables.)

* I'm still trying to figure out what effects the built-in limiter (switchable) has on the sound. At first I thought the limiter was hurting the high-end but I think the problems I'm hearing might be from levels that were too *low*, in combination with 16-bit recording that I used at the first concert to conserve space on the card.

Later, I pushed the levels all the way up in a rehearsal with the limiter turned off, trying to get digital clipping, and it was pretty hard to hear, although I could see a little bit with an analyzer. For wide dynamic levels, I strongly recommend 24-bit (WAVE) format and trying to get the levels high enough. The jury is still out on the limiter.

After the live recording sessions, I spent a lot of time working with the audio, trying to clean up some issues with limiting, levels and EQ - none of which you'd have if the recording was done right. I was doing it on the fly in live concerts with all the attendant issues.

I continue to find the $30 Amadeus II application to be an incredibly useful, reliable and effective tool. It's a stunning value with support for all kinds of filters. Free "Carbon-MDA" VST filters include some great stuff, including dynamics (with expansion, as well as compression) and stereo image plug-ins, along with many more. (I kept tripping over "Combo", though, which sounds like something other than it is - a big guitar-amp distortion model.)

A very complementary application is Rogue Amoeba's $32 "Audio HiJack Pro", which can do almost anything, including *real-time* plug-in effects, a wonderful feature I've yet to find on any other reasonably-priced application. (Actually, DSP-Quattro has it for $150, but I didn't care for its plug-in user interface with its microscopic type.) I spent some time with BIAS Peak 4 - a 10-day trial version - finding it pretty fast and efficient, with support for 5 real-time plug-ins, but I think it should be priced at about half the $500 level it carries. I mean, you can buy an Mbox with ProTools for that....

When my hands got tired mousing around with silly graphical controls on plug-ins, I ended up trying and buying three plug-ins from Elemental Audio (Neodynium, Equium and Firium), which just stunned me with the quality and innovation of their user interface and functionality. I have no idea who's behind these (couldn't find any names), but they represent the best of the best in computer software and interface design, in my opinion. The company's *free* "Inspector" plug-in is invaluable, too, with RTAS, VST and Audio Unit versions. Even the customer experience (researching, trying and buying) was also flawless, and pricing seems quite reasonable for what you get. Check 'em out.

As for USB 1.1, I assume it works but is much slower. The other option is to simply take out the CompactFlash card and put it into a FireWire or other reader. Just don't make the mistake we did, where a friend ejected another card without dragging it to the trash first, and the Finder showed a completely foreign directory structure overlaid on my card when I inserted it. That was pretty scary, once I realized what had happened, but I quickly ejected the card, and I don't *think* that's what trashed my middle recording. Just be careful about this, and note that it can't happen if you connect the R-1 via a USB cable. (Edirol warns that certain USB cables may be problematic - those with built-in resistors - so be careful about that, too.)

All in all, I think this is an outstanding compact recording system, well matched with the battery-powered AT-822 mic or quite usable with its built-in mics. The Mbox may give you a little better signal-to-noise ratio with excellent balanced mics and its outstanding preamps, but you can do very professional live work with the R-1 and have a lot more mobility, while avoiding all the complexity and pitfalls of a Mac-based system.

The sweetest version of OS X 10.3.x (Panther)?

MacInTouch Home Page: "Panther dot 7 has got it all for now - .8 and .9 were both troublesome."

Now that 10.3 is a legacy OS, one can choose the 'stopping point' for older machines. This Macintouch expert votes for 10.3.7 as the place to stop for a machine that won't go to 10.4. I'm ok on 10.3.9 but I find this plausible.

Wednesday, June 01, 2005

iPhoto 5 bug - color shifting (Macintouch)

iPhoto 5 broke the color profile functionality that was present in past versions of iPhoto. That's bad enough, but it turned out to have a nasty side effect. Under some circumstances repeated edits of a photo causes cumulative damage to a photo's color information.

This appears not to be Tiger specific, but occurs with iPhoto 5 on Panther as well. This is a bad enough bug that one should not update to iPhoto 5 until it's fixed. From Macintouch:

Joe Zobkiw

Regarding the iPhoto/ColorSync Profile post from the Apple discussion boards, here is an interesting experiment to show the relationship between different color profiles:

Open "ColorSync Utility" from /Applications/Utilities. Click on the Calculator icon in the main window. Select two different profiles for the right and left sides (sRGB Profile on the right and Generic RGB Profile on the left, for example) and then move any slider. Note the opposite slider(s) and how far they move in comparison in order to achieve the same color in the other profile.

For example, if Generic RGB Profile has red set to .5 and green and blue set to 0, sRGB Profile has red set to .5732, green to .0975 and blue to -.0339. You can see immediately the relationship between various profiles and how if values are saved from one profile and "applied" to another profile (not using ColorSync functionality but just "saved" as belonging to the other profile) how the colors would be very different.


Stuart Hertzog

James Bailey is on the right track in pointing to a change in embedded profile as being the reason for color shifts in edited iPhoto files. But ColorSync is not the problem: ColorSync is just OSX's color management system.

It seems that iPhoto is not properly re-saving the embedded profile of an edited file, turning it into an 'untagged' file (without color management information). When a color-managed application such as Photoshop or iPhoto opens what it sees as an untagged file, it will assign whatever default RGB profile it happens to be using, thus displaying shifted color. The color information is all present and correct, it's just that the wrong profile is being used.