Connect

 

The Standard Disclaimer

The views expressed on this blog and its related web sites or podcasts are mine alone and do not reflect the views of my employer, clients, investors, wife, children, pets, parents, friends, friends-of-friends or anyone else with whom I may be acquainted.

 

Navigation
« Allchin: 'I would buy a Mac if I didn't work for Microsoft' | Main | links for 2006-12-12 »
Tuesday
Dec122006

GarageBand Mystery Solved, thanks to Chris Breen and the iLifeZone

Until very recently, I was using Audio Hijack Pro to record my podcast. I would select CD quality as my output file which in the case of Audio Hijack is an uncompressed AIFF file.

When I attempted to import the file directly into GarageBand to add music, credits, disclaimers, etc., the audio would play sloooooowwwwwly. I couldn't understand why. Some of my co-workers in the audio production department at Audible suggested that it might have been a problem with the way the application wrote the headers on the files. Subsequently, I would convert the AIFF file to WAV and upon import into GarageBand, the WAV file would play just fine.

While listening to Episode #18 of the iLifeZone, Chris Breen (of MacWorld and PlayList magazine fame) "turned up the geek knob" (his words) and explained the problem, although in a different context:

I was recording at a 48 kHz sample rate. GarageBand expects a sample rate 44.1 kHz and more importantly, it's not designed to downsample the file in order to play it back properly.

Who woulda thunk it?

;)

Now I'll know what to do when it happens in the future. Thanks to the iLifeZone gang for the solution.

[tags]iLifeZone, Chris Breen, Podcasting, Audio Recording, iMovie, Audio Hijack Pro, Rogue Amoeba, Scott Bourne, Derrick Story, iLife, Apple, Mac, Macintosh, OS X, On Digital Media, John Federico[/tags]

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>