Difference between revisions of "Mac OS X"

From Audacity Wiki
Jump to: navigation, search
(Network Home Weirdness)
(Added: Compressor - working correctly?)
Line 493: Line 493:
- July 15, 2007
- July 15, 2007
= Compressor - working correctly? =
Audacity 1.3.3 beta on OS X 10.4.10. It seems to me that the built-in compressor is not working correctly.
* When you apply the effect once (say with threshold -12dB, ratio 4:1, normalise to 0dB), the compressor seems to work, and one peak seems to be hitting zero dB. However, if the compressor is applied to the same selection again, nothing much happens to the top peaks, though some of the lower peaks change slightly. If you keep applying the compressor, after a while nothing more happens, with some peaks standing out, but the rest of the waveform at intermediate volume. The expected behaviour (with normalise turned on) would of course be all audio getting louder with each application of the compressor effect, and volume to become more and more similar throughout the clip.
* If I set the threshold to -50dB, ratio 10:1, normalise, I'd expect the volume to come out very uniform, and high. Instead, the region goes very quiet.
Discussion here: http://audacityteam.org/forum/viewtopic.php?f=15&t=47&p=135

Revision as of 12:13, 15 September 2007

Audacity is fully supported under Mac OS X. However, there are a number of quirks, and because of subtle differences between Mac OS X and other platforms, you may discover bugs that are specific to Mac OS X.

Many differences between the platforms relate to the audio platform API - in the case of Mac OS X, this API is called CoreAudio . Unlike most other APIs on other operating systems, the CoreAudio API does not have any options for setting the input source of a recording device.

Other differences are due to wxWidgets, the cross-platform API that Audacity uses. There are bugs in the Mac version, wxMac, that can affect Audacity. One bug involves Unicode support: because of this bug, Audacity cannot successfully work with files that are inside of a directory containing non-ASCII characters (usually international characters or accented characters). It apparently also has an artificial restriction of file name length, limiting your filenames to 32 characters despite support by OSX for much longer names.

The Audacity team is looking for someone to help with the UI design for the Mac version of Audacity. The goal is to customize the Mac version so that it fits the Aqua UI as much as possible, while keeping as much code in common with the Windows and Linux versions as possible. Contact the developers if you have suggestions or would like to help out with this.

See http://docs.info.apple.com/article.html?artnum=300832 If no sound in Quicktime or Realplayer after using Audacity 1.2.3 - try checking Audio MIDI Setup (Applications/Utilities). I find that Audacity consistently changes the Audio Output setting from 44100.0 Hz to 96000 - and changing it back brings back QT and RA sound.

Non-functional AU effects

Using 1.3.2 and OS X 10.4.8. Most of the AU effects work but not reverb. I have tried Apple's MatrixReverb which comes with Garageband, and Freeverb3. What's up? Rob [email protected]

Audacity was not able to lock the temporary files directory

I got that error when I opened it how do i fix it? Email:[email protected]

Please help!

Crash on Start - Err Code 1000

Hi, I'm running a powerbook G4 (1GHz) and Audacity crashes upon start with error code 1000. Any suggestions?



Crash when click RECORD on PowerBook with 10.4.2

I am using a (new) PowerBook 12" with 10.4.2 and Audacity crashes when I hit the Record button. I have tried all manner of changes (including trashing) Preferences, to no avail. A favorite tool gone bad? ... Al 07/19/2005

I was having the exact same problem on a 500MHz Titanium PowerBook with an M-Audio Duo USB audio interface, using 10.4.2; but by setting the Default Sample Format (under the Quality tab in Audacity Preferences) to 32-bit float (the default) instead of 24-bit, the crashing stopped. ... Eric 10/03/2005

I reported this bug in the (widely ignored) audacity bugzilla a while back, and subsequently tracked down the source of the problem. http://limpet.net/audacity/bugzilla/show_bug.cgi?id=232 for details.

Chevy 2006-12-29 -> Same issue here with Audacity 1.3.2 beta on 10.4.8 on a Core 2 Duo iMac. No issue recording with 1.2.5 on the same machine

Need to support Drag and Drop of Files

Dropping a file onto the Dock icon or onto an application window should open the file.

Disappearing Quick Time sound

A number of users of G5 machines have had problems with quick time after installing or running audacity. If you run Garage Band after exiting Audacity, it fixes the problem. Unfortunately, each time you run Audacity and exit, you'll find you'll need to again run Garage Band to correct whatever Quick Time or audio settings are being altered when Audacity is run.

This fix is also the solution for an audacity bug on my G4 OSX (10.4) powerbok: the sound goes missing from any Flash app after I use audacity, but running Garage Band fortunately remedies this.

Similar "Where's my sound now?" problem

After running Audacity, most sound output suddenly came through my JABRA BT200 BlueTooth headset instead of through the system audio line out. This included RealPlayer and WMP, whether streaming or playing local files, and Skype conversations (although bizarrely the Skype ringing tone still came through line out, not the BlueTooth headset!?)

Removing the headset from the system just meant that the sound disappeared completely.

However, as above, launching GarageBand solves the problems. Thanks for the tip (albeit six months after the problem first appeared for me).

 Tim Morley 

Audacity 1.2.4 killed the sound in a Quicktime stream on a Gibabit Ethernet tibook running 10.3.6 with QT 6.5.2. However, iTunes which uses Quicktime still plays and after using iTunes Quicktime sound is restored. So iTunes appears to fix the problem as well as Garage Band

Griffin iMic problem

There is a bug when using Audacity with the Griffin iMic, or with H&K soundsticks, which re-sets recording to mono 8bit only. The work around is to re-set the OS X audio parameters after starting audacity:

FYI, this bug has been found; an attempted fix appeared in Audacity 1.2.2 -Dominic Mazzoni. There are still some people with issues however, it seems. - Richard Ash

First, open the "Audio MIDI Setup" program in the "Utilities" folder, under Applications.

1. Start Audacity 1.2. When its window opens, note that the FORMAT SETTINGS FOR iMIC HAVE CHANGED IN "AUDIO MIDI SETUP" FROM "2ch-16bit" TO "1ch-8bit". This happens independently of whether I have last used Audacity with a recording setting of "1 (Mono)" or "2 (Stereo)".

2. With the iMic settings now incorrect, I can only get single channel input in Audacity with either "1 (Mono)" or "2 (Stereo)" selected in its preferences.

3. If I manually restore the correct iMic format settings (i.e., "2ch-16bit") in Audio MIDI Setup WITHOUT QUITTING Audacity, I can then record stereo input in Audacity.

[A second user notes he has the same problem, which the above workaround/explanation helped him figure out. It is very annoying. It does appear to be some kind of a bug in Audacity. Note that after Audacity launches and somehow mis-sets the parameters for the iMic as a port, even other OSX recording software will refuse to recognize that the iMic is stereo. I would be so very happy if it were fixed. ]

Audio Midi Setup can be found under /applications/utilities This should work for all Core-Audio versions of OS X

under which versions of OS X? Will this fix work on 10.1, say?
It worked for me under 10.3.4. God, I was going nuts until I found these notes; the effect of the settings change for me was horribly noisy and distorted recordings across the board, all applications, rendering my system unuseable for audio recording! -- Mark

LFJ - I am also having a problem with the iMic in version 1.2.3. My problem was that I had set it to 8kHz recording for trying to record an internet radio stream, and then it set all iMic defaults to 8kHz. When I found this page I used the Audio Midi Setup to change it back, but I haven't had a chance to try my other OSX recording s/w yet (e.g. GarageBand 2) to make sure everything is back to normal. I am also having another problem, seemingly unrelated. (See below)

MichaelG - The same problem [re-setting to 8-Bit] occurs with the HHb PortaDisc Professional MiniDisk Recorder [OS X 10.3.8 with Audacity 1.2.3]. The workaround [above] is OK. Note: If users want to see the effect on noise level, just record a period of silence onto MiniDisk then into Audacity in 8-Bit, then in 16-Bit or better: Zoom right in on both tracks and compare.

        The reason that the 8-bit background noise is so objectionable is because it contains much more energy [the energy in a waveform being "the area under the curve".]

TheDingo - I am now having this problem on 10.4, but resetting it to 2 ch - 16-bit does not help

For all those who've had problems with their iMic in OS X with stereo recordings, have been unsuccessful with the System-Preferences trick, or keep getting that "Error while opening audio device" message:

I've made Audacity play nice with the iMic, and my solution might work for you too! You need <a href="http://www.cycling74.com/products/soundflower.html" target="_blank">Soundflower</a> and Rogue Amoeba's <a href="http://www.rogueamoeba.com/freebies/" target="_blank">LineIn</a>, both freeware. Here's how you set it up:

1. Designate the iMic as your system input device.
2. Configure LineIn to pass-thru the iMic input to the Soundflower 2-channel device.
3. Set the Soundflower device as your input in Audacity.

It's a bit unwieldy of a solution, but it does the trick. I'm running OS X 10.4.2 on a 1.42 G4 iBook, using Audacity 1.2.3. I don't see why this solution wouldn't work in older versions of OS X, or even with other problematic audio interfaces (you'd want to use the Soundflower 16-channel device instead, if your device has more than 2 channels). Unfortunately, this solution still doesn't allow you to use the iMic for Audacity's output, if you've had problems with doing that as I have. You'll still have to use the system output.

Jesse, added 11/23/2005

I'm having a similar problem...my Sound Devices USBPre is recognized by the system, and can be recorded with the program AudioIn . It is recognized by Audacity but when I try to monitor I get nothing and when I try to record I get the error while opening audio device message. The above fix using LineIn and Soundflower works as long as I hit the pass through while Audacity is monitoring the signal. This is shaping up to look like a laptop bug. I'm running G4 1.33 iBook, OS X 10.4.3, Audacity 1.2.3, this ibook is brand new a day out of the box. I also started having a problem with Final Cut Pro after I configured this audio set-up...It would crash on start up during the audio plugins load...I updated the Final Cut software from version 4.0 to version 4.5 HD, uninstalled and reinstalled the soundflower software, and reinstalled the drivers for the USBPre. This cleared up the Final Cut issue. If I had to choose one, I think it was the Final Cut update that did it.

- Evan, added on 9/2/2005

I have had a problem getting Audacity to start at all in MacOS 10.4.3 using iMic on a Mac Mini - I get an "input error" and told to "check set-up preferences" or words to that effect. A Griffin tech flatly stated to me that Audacity does not work on OS 10.4+. Anybody else heard that - any thoughts? - Rich, added 11/20/05

- Clarke, added on 5 Oct 06 -

My problem is that 1.2.4 won't even recognize iMic. I've changed the system sound prefs, fiddled with the midi set-up, and Audacity still only has "default" in the input source selector. iMic works fine with WireTap Pro.

System Sound Ouput Prefs Problem

After I installed Audacity 1.2.3, it did something so that now any non-Apple audio playing software (e.g. RealPlayer 10, Windows Media Player) does not acknowledge the Sound Output source that is selected in my System Preferences pane. I originally thought this might be related to the iMic problem above, because I had the iMic selected as the output when I installed Audacity and then afterwards it wouldn't switch to the Built In Audio or Soundflower s/w output - no matter what I did, when using Real or Windows Media, it played through the iMic. However, I also installed Audacity on a system with no iMic and am now having the same problem, except on that system it always plays through the Built In audio and I can't switch to Soundflower, when it would switch just fine before installing Audacity. Apple-brand software, such as iTunes and QuickTime , seem to be unaffected. This is my first foray into open source software, and I can tell ya, it isn't giving me warm and fuzzies. At this point I just want my system back the way it was. Any ideas what it did and how I can get it back? - LFJ

Change Sound Output in SysPrefs . Open Audacity. Play a clip and be sure that the sound comes out as you chose. Close Audacity. Back to RP. Play a clip. Be happy (I was). -ep

Generate Click Track disappeared

I'm running OS 10.4.7 on a dual g4 533

mpatkinson --- at --- gmail -- dot---com

Did a lot of work involving generated click tracks in audacity 1.2.4, and then decided to try the beta 1.3.0. While running 1.3.0 I kept getting messages about deleting orphan files, etc. I clicked OK for everything and just saved my progress a lot. Now, the click track option no longer appears under EITHER version of audacity. I deleted both versions and downloaded new ones, and the problem remains between both new versions as well.

Any ideas on how to get the click tracks back in the generate menu?

1/28/05: Audacity -- Tascam US-122 compatibility problems

Mac Powerbook G4 (OSX 10.2.8): I'm having trouble recording with a Tascam US-122 pre-amp. When recording, audacity only picks up the sound intermittently (i.e. 1/4 of a second of input recorded, followed by 1/2 second silence and then another 1/4 second of sound, etc). This doesn't happen with the computer's (crappy) built-in mic, only the US-122 (newest driver installed). Interestingly, the problem occurs with Audacity 1.2.2 and Audacity 1.2.3, but not Audacity 1.2.0, which I've been using for six or eight months. I noticed on the Audacity boards that other folks have had problems with the US-122. Any ideas -- it's a bit frustrating using 1.2.0 when 1.2.3 looks to have quite a few new features? Thanks.

3/14/05: US-122 comments -
i'm using a iBook G3 (OSX 10.3.8) and with Audacity 1.2.3 i have that same intermittent problem but in Audacity 1.2.1 its fine unless you turn on record monitoring which gives the same intermittent issue.
11/27/05 - This problem seems to be solved with 1.3.0-rc-2 - <i>greg

Plantronics DSP-400 USB Mike problem

Is there a way to use a USB attached mike as an input source to Audacity (v1.2.3) under OSX (v10.3.7)? This mike works fine with other apps such as AudioIn but even if I set the input source in System Preferences, Audacity gives an error message ("Error while opening sound device. Please check the input device settings and the project sample rate") when I try to record.

You may need to change the sample rate (alter the project rate in the bottom left of the window), or record at a different bit depth / number of channels. These can be altered in the Preferences on the Audio I/O and Quality tabs.

I'm having the exact same issue, but with a Presonus Firebox input device (connects via Firewire), under OSX 10.4; no special drivers, just uses core audio. The suggestion above doesn't work - my bit depth and sample rate are exactly the same in Audacity preferences as in the Audio Midi configuration utility. This is a 6-channel audio input device, which I suspect could be the problem, but it's not configurable to behave as anything less in the Audio Midi tool. I've successfully used it with Live to record stereo tracks, so I know everything is hooked up and installed properly.

I have a Presonus Firebox as well in the same setup and am having the same issues.

Non-OS X Installation Procedure

Just downloaded the DMG image for Mac OS X. Turns out it contains an .app bundle, some folders (with what looks like libraries and language packs?), some textfiles (LICENSE.txt, README.txt), and a nonidentifiable .htb file. No instructions how to install it (.app bundle is pretty obvious, but the directories?). I start to read the text files - LICENSE.txt only contains the GPL. README.txt contains license info, compile info, and a changelog. The .hbt is just binary junk on my machine, obviously it needs some app installed. Basically, there's no information about how to do the installation at all! Where are you supposed to put the folders? In /Library?

Also, at least localization, I think, should be put INSIDE the app bundle.

The bundle should in my opinion either be converted to a monolithic bundle, or there should be install instructions, either directly in the dmg or in a text file, possibly special for Mac OS X. //TERdON

All true! But I found a way to open the *.hbt file:

When you open the >Help menu and click >Contents... the app asks you to specify the location of the help file, which must be an HTML HELP BOOK with file extension *.hbt. This is a pretty stupid solution, as imho the help file should be included in the main package AND in a normal environment the disk image will be removed after installation. Consequently the help file will not be accessible after that. :-(

Also: in my installation, in the >Interface settings I cannot change the language. There is the language option, but I can only choose from English and English... :-(( //Bignose

===Negative progress in online help?=== There doesn't seem to be a *.hbt file in the"Official" 1.25 Intel binary dmg file. It there is a help file with this version it is well hidden. I wouldn't mind downloading it separately but I can't figure out where to get it. Fortunately it is all available as online web pages. //xencuke

Language choice should depend on System Settings

The language used in Audacity should be the one set in System Preferences - there shouldn't be an application specific setting for this. //TERdON

Incorrect default "export as WAV" location

By default, Audacity tries to export WAV files to /; this isn't standard behaviour, however. By default, it should default either to a) the last directory where a file was saved or, if no files have been saved yet this session, b) the directory in which the original WAV file is.

Audacity doesnt seem to work with the Yamaha 01x. It shows up in system preferences but gives an error when trying to record or play.

Unable to open/import monaural AIFF files (July 1 2005) - resolved

All of a sudden, when using File - Open or Project - Import Audio to access a monaural (one-track) AIFF file, Audacity says it is opening/importing an MP3 file, and the "time remaining" increases rather than decreases (when this value exceeded one hour, I clicked "Cancel"). Powerbook G3 Firewire, OS 10.3.9, Audacity 1.2.3.

Double-checked audio input settings, moved temp directory to larger volume, and rebooted, all to no avail.
Oops, never mind, found the problem. When I exported these tracks from Sound Studio, the default format was "Sound Designer" and not AIFF as I had assumed.

August 18th,2005 Posted by Punkcut25 punkcut *at* gmail *dot* com

So I have two powerbooks. I do voice interviews using Skype and Audacity Recently however, whenever I try to do this. (This situation happens no matter which powerbook is local and which one is remote) The local machine is always the one doing the recording in these scenarios I skype call the remote machine. Remote user picks up We test the line we can hear and speak to each other just fine I start recording on audacity. Remote machines audio input is not registered on my machine Basically I can record the voice of the user on the local machine but not the voice of the user on the remote machine. Even though I can hear the user on the remote machine just fine.

audio output error

Aug 27, 2005

stephen --at-- brazosdedios --dot-- com

Mac OS 10.3.9 Audacity 1.2.3 similar to the input problem above but mine is on output. When I try to play a track through my Plantronics M2500 bluetooth headset, I get the error - "Error while opening sound device. Please check the output device settings and the project sample rate" but it plays fine if I select the Built-in Audio. Other apps and system sounds play fine through the bluetooth headset. Any ideas how to fix this?

Mac OS 10.4.2 Mac OS 10.3.9 Audacity 1.2.3 1Ghz titanium w/1gig of ram & plenty of HD space

Cant export to MP3 no mater how small the sample seems to be LAME seems to crash audacity with the error message "Assertion (gfc->mf_size <= MFSIZE) failed in "lame.c" on line 1501" any advice?

Change Tempo

Aug 30, 2005

dougp ++at++ ispinn ++dot++ com

Mac OS 10.3.9 Audacity 1.2.3

If you're trying to use the percentage change field to change tempo on your selection, it'll mess you up. It's not a percentage value, so don't try using it.


Open the Change Tempo... dialog box. On the bottom left of the dialog box in the FROM: field, get the number of seconds in your selection. On scratch paper, multiply those seconds times the percentage reduction or expansion you're looking for, and enter that value into the TO: field. The resulting percentage listed above won't be close in most cases. I think the equation being used to calculate the final sample length based on the percentage value given is actually some weird 2nd order function.

audio out error

Oct 7, 2005

swettr (at) seznam (dot) cz

having similar audio out problem like stephen brazosdedios: audacity 1.2.3. (on ibook g4 1.33) is unable to perform any output via my firewire sound card edirol fa-66, showing the message "Error while opening sound device. Please check the output device settings and the project sample rate". with built-in audio it seems to be ok, inputs from edirol also work. thanks for any advices.

Oct 7, 2005

I've had same problem with my firewire M-Audio Audiophile interface. I can get sound out through built-in audio without a problem, but I can't get it back out through my interface, which would be preferrable. Szajic 08:50, 2 February 2006 (PST)

Nov 21, 2006

Use the new beta version 1.3.2. They fixed it there. It works fine now with the edirol fa-66. Manjo

Audacity start problems in 10.4.2

after upgrading from 10.3.9 to 10.4.2 I ran into start problems:

        open -a audacity
        2005-10-07 09:54:11.871 open[28544] [[LSOpenFromURLSpec]] () returned -10827 for application audacity path (null).
        2005-10-07 09:54:11.872 open[28544] Couldn't launch application:  audacity
From Finder:
        you cannot open the application audacity.app
        because it may be damaged or incomplete

It came up fine when started from the disk image. Fix for me was to rename the binary "audacity" to "Audacity" after doing a kdump/ktrace on the open command.
My guess: I'm using a case sensitive filesystem on all my partitions, which was not true on the old 10.3.x system and is not true on the disk image.

.:. Definitely related to HFSX case sensitive filesystem and a bug that should really be fixed. For those unfamiliar with the workaround oulined here: [ctrl]-click on the Audacity.app, in the popup-menu, select the third item from the top, Show Package Contents... Another Finder Window opens, select column mode, navigate to Contents/MacOS. Rename audacity to Audacity.

audio input selection

Probably a simple issue, but I'm stumped. I'm trying to use Audacity on a powerbook g4 with 10.4.2 to record audio streams from a real player broadcast. Audacity shows "Default Audio Input" in the prefs. OSX SystemPrefs offers "built-in mic" and "line in" options for audio input. Neither of these options will capture the stream directly. What am I doing wrong?

Oct 28, 2005

I am having the same problem. Anyone have a suggestion? I am running 10.4.7 on a powerbook g4. I would like to select multiple input sources for recording such as "stereo out" selection.

July 21, 2006

It appears there's something about the way Mac processes audio output that prevents audacity from capturing it. But there are other programs that can.

From the Audacity FAQ at http://audacity.sourceforge.net/help/faq?s=recording&i=streaming

"Mac OS X users can capture streaming audio using a program like Audio Hijack or Wiretap Pro."

January 3, 2007

Unresponsive Play button

When having several audio files open in several windows simultaneously, the Play button keeps getting unresponsive. Usually it works in one window but not the other. Sometimes it works after pressing it several times. The problem gets worse if I have three or more windows open. It goes away if I close all windows but one.

I have also found that importing new audio files is very slow when several windows are open.

OSX 10.3.9, G4/400 Sawtooth, 512MB SDRAM. Audacity 1.2.3, 40+ GB free on disk.

I've had a similar issue - the bars showing the input levels remain, and the play button is unresponsive for a while. Unfortunately, the only thing to do is wait. I have found that if Audacity seems to be getting bogged down, restarting the program (and/or the computer) often helps. OS X 10.3.9, G3. Szajic 08:53, 2 February 2006 (PST)

I had similar problems with the unresponsive Play buttons and frozen meter displays in Audacity 1.2.4 and 1.2.6. It would always happen immediately after a passage has finished playing, or else after I hit the Stop or Pause button. I could make new selections, scroll, and zoom in/out, but I could not use the editing tools or transport buttons, for anywhere from 5 to 15 seconds. I rarely have more than one window open, but still saw that behaviour, except when playing very short (less than 5 seconds) selections. Activity Monitor would indicate maximum CPU activity during this semi-frozen state. I've recently downloaded Audacity 1.3.3 (beta) and there is now almost no lag. It's very quick to respond.

[Planish - Blue&White G3 with Sonnet Technologies G4 1GHz upgrade, 512 MB RAM, Mac OS X 10.4.9]

Trashed Audio Subsystem: Feedback Loop

From: [email protected] (Christopher C. Stacy)
Subject: audio feedback
Newsgroups: comp.sys.mac.system
Date: Sat, 26 Nov 2005 02:00:26 GMT

Sometimes my iBook G4 (Tiger) gets into a weird state where there is 
some kind of feedback in the audio system.  For example, When I try
to use an IM program (that is, the microphone in conjunction with
audio output), I will hear what is clearly a feedback sound, 
usually coming at a relatively low pitch (not a squeal).

Once the system gets into this mode, it does not matter what programs
are running, although you can only actually hear the noise if you open
up something like Skype (IM).  But even without any noise coming out
of the speakers, if you look at the microphone calibration meter
under System Preferences -> Speech, you can see that there is a
signal on the mic, pulsing away, that looks like the feedback.

Note that problem is not a simple circuit through the speakers!
I experimented in this situation using internal and external speakers
and headphones, and there doesn't have to be any noise coming out.
Apparently there are other circuits (physical or digital, I don't
know) which are involved in routing the audio, and something is
getting messed up in there.

I believe that what happens is that some program -- which I am pretty
sure is Audacity -- configures the audio subsystem in some illegal
fashion for some reason.  (It is probably an OSX bug that allows
this to happen.)

I have cured this by pushing a lot of buttons and frobbing everyting in sight.
Unfortunately, it took a very long time, and I don't really know what I did.
Mainly, I went into the Audio MIDI Setup application and fiddled with
the channel levers and (only the) Master channel "Thru" button.
Most of the controls were greyed out most of the time.
My original theory was that toggling the Thru checkbox would fix it.
It started out cleared, but I thought that secretly it was really on.
I turned it on, then turned it off.
That wasn't enough.

Does anyone understand this problem?
Do you know what to do about Audacity?
Is there an effective procedure to clear this condition,
when it happens next time?<br>

I have a vague recollection that this happened to me before,
but all I could find on the web were many, many sites with
their conversations and blog entries about people who seemed
to be as baffled as myself, never finding any solution except
to purchase some expensive third-party audio software that I
am not familiar with, and getting it to reset the subsystem.

Note from trxbloke.

This audio looping/echo is a known fault on the newest PowerBooks (17 &15 inch) There are threads on Apple's support/discussions pages. This is the first Ive heard of it on an iBook though. It seems to be a core audio problem. Possibly a data stream corruption through to the sound processors. PowerBook users are awaiting a fix. Some people think it may be a logic board fault. Killing core audio in Activity viewer seems to be a temporary cure.

hint by fab'

try to write in terminal:

# sudo killall -9 coreaudiod

and give root password. it should restart coreaudio server. that works for me!

o) fab'

'pip' sound

I'm getting a 'pip' sound at the end of all songs once they are imported into itunes. I'm recording whole records then using labels to identify the songs, then use the 'export multiple' command and converting them to mpegs. It's almost as though the exporting of the songs is causing it. Like it's a marker or something.

Anyone else come across this?


Program not brought to front from dock If you click on the program icon in the dock and audacity is maximized then it brings the program window to the front (correct). If it is minimized and you click the program icon in the dock it does not maximize the program (incorrect).

Audacity problems on MacBook (13 inch) - Presumably a Rosetta issue

So I just went out and replaced my G3 icebook with a spiffy 2.0 GHz MacBook, which is awesome.
Unfortunately, upon installing and running Audacity, which is pretty much required for the flute recording my wife does, I had to face the fact that Audacity (1.24 and 1.30 beta) was not stable on the spiffy new machine. Now, I'm working on getting GarageBand working, but Audacity is certainly my first choice.

As far as crash data goes: I don't have any. It's still my wife's computer and I have no developer tools on it. Also, I have no development experience on macs anyway. It crashes at different points each time. First, it crashed after giving me the language prompt (this was 1.30beta). Then, it crashed as soon as I clicked record. It crashed before the program started, with the icon bouncing endlessly. Then, it let me record, but crashed when I hit play. That was after seeing the same sort of thing with v1.24. Each crash was fixed smoothly with a Force Quit, which I did appreciate.

Has anyone else seen this? I've just gotten home with the machine, so maybe some of my settings are not setup properly.

Audacity cannot open MP3 encoding library

When I try to "export as MP3" and am prompted to find LameLib, I can locate it. As soon as I click on it, however, Audacity tells me it "could not find the MP3 encoding library." I've obtained LameLib from spagetticode.org/lame and opened it with StuffIt. I had no problems activating MP3 export in Windows or Linux (Ubuntu). I'm new to Macs, and I just can't figure out what I'm doing wrong.

I'm running the 1.25 (MacIntel) prerelease build on a brand new MacBook with 10.4.7.

08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)08:54, 17 October 2006 (PDT)~

Same problem here. I have tried getting LameLib from numerous sources, all with the same result.

November 25, 2006

Audacity 1.2.5 for Intel-Pre1 does not even recognize the libmp3lame.dylib file. It is greyed out when trying to locate LameLib with the default selection dialog. In fact, when I set the selection dialog to "All Files" and select the libmp3lame.dylib file, I get an alert telling me that the file I have chosen is not named "LameLib" and do I really want to use it? If I answer "yes" then it does not export MP3 anyway. So it sounds like Audacity 1.2.5 for Intel is really not set up to use the OS X Intel LAME library.

May 15 2007: I found a solution to this problem when I had a brainstorm while plonking around elsewhere in the Wiki. Download this file] and use it instead of the one linked to on the Audacity homepage. Worked like a charm.

Mono Bad (Noisy), Stereo Good

Audacity v1.2.4 and v 1.2.6 - Using Griffin iMic on a "Blue & White" (originally 300MHz G3) tower with Sonnet 1GHz G4 upgrade; OS X Tiger v10.4.9, Nexxtech "Headset with Microphone" (no model number). I've been recording mono voice tracks for Librivox.org.

If I select Mono recording in the Preferences, there is a crackly noise all through the track. It sounds like frying bacon. Not hum, not hiss or white noise, and it's about -30 dBFS. The noise is there even with the mic switched off (but somewhat reduced). I was almost going to return the iMic to the store. Moving the USB cable from the third-party four-port USB 2.0 card to the original (slower) USB port did not help, nor did disconnecting or moving other USB devices.

I later discovered that when I change the Preferences to record Stereo tracks, the recording (on Left and Right) is quite clean, except for the usual fan and room noise. My work-around is now to record in Stereo, Split the Tracks, delete one of them, and then convert the remaining track to Mono. - April 6, 2007

Update - The Audacity 1.3.3 (beta) release does not have that "frying bacon" noise when recording mono tracks that I mention above. Traciks recorded in mono sound as good as tracks recorded in stereo. - May 28, 2007

Network Home Weirdness

Audacity 1.3.3 was installed by a local admin. Users with network homes receive a 'You cannot open the application "Audacity.app" because it is not supported on this system'.

If a network user downloads and installs it, that network user can run it, but not others. There was some other weirdness with local accounts that was fixed with loosening the permissions.

It can be run from the command line. It seems to work, but starts wth the error 'The path "Languages" contains too many ".."!'.

This symptom can be reproduced by creating a non-admin user and attempting to launch Audacity from the non-admin user.

Try changing the permissions of the Audacity executable within the Audacity.app bundle.

  1. Open the Terminal.app from an Administrator account
  2. Update the permissions of the Audacity executable:

chmod 755 "<path to Audacity.app folder>/Contents/MacOS/Audacity"

The <path to Audacity.app folder> should be replaced with the full or relative path to where you placed the Audacity.app folder. For instance, if you created an "Audacity1.3.3Beta" folder inside your Applications folder and placed the entire contents of the downloaded .dmg file inside there, you would use:

chmod 755

A side note, the owner in the package is 777, this should be changed to 501.-->Please explain this for the non-commandline folks.

I've chown -R 501 the folder and chmod -R 777 the folder. Neither works. -->Please explain this for the non-commandline folks.

501 is the uid of the first local user created user (the local admin in this case). It almost always exists and is a safe bet for ownership. chown -R 501 changes the ownership of all of the files to the user with uid 501

777 translates to -rwxrwxrwx, everyone has full permissions.

So, I changed the ownership to a real user and gave everyone full permission to everything. I don't _think_ that there are any preference files written to /Library, but I didn't check. This wouldn't affect those.


Based on what I'm seeing here, and have tried myself, I'm not convinced the other authors got this to work. I have a non-admin local account that still refuses to run Audacity 1.3.3, generating the error listed above.


Do the developers read this? I've always had trouble putting together all of the dependencies to build Audacity on OSX. I wouldn't mind poking at the code if someone could give me a hand setting it up.

Vanishing Envelopes

Problem with 1.33:

Files created in Audacity 1.32 or 1.33 vanish (or are squashed to occupy a single point at the beginning of the track) when file is opened with Audacity 1.33.

In earlier versions, you could make them reappear by performing any kind of action and then undoing it - the envelopes would magically reappear. With the release of 1.33, this no longer works - after saving, closing, and reopening the file, the envelopes are gone for good. Others have reported the same problem.

I have read that this was a known bug which was repaired in 1.33, but that is clearly not the case.

Mac OSX 10.4.10 on a PowerBook G4

- July 15, 2007

Compressor - working correctly?

Audacity 1.3.3 beta on OS X 10.4.10. It seems to me that the built-in compressor is not working correctly.


  • When you apply the effect once (say with threshold -12dB, ratio 4:1, normalise to 0dB), the compressor seems to work, and one peak seems to be hitting zero dB. However, if the compressor is applied to the same selection again, nothing much happens to the top peaks, though some of the lower peaks change slightly. If you keep applying the compressor, after a while nothing more happens, with some peaks standing out, but the rest of the waveform at intermediate volume. The expected behaviour (with normalise turned on) would of course be all audio getting louder with each application of the compressor effect, and volume to become more and more similar throughout the clip.
  • If I set the threshold to -50dB, ratio 10:1, normalise, I'd expect the volume to come out very uniform, and high. Instead, the region goes very quiet.

Discussion here: http://audacityteam.org/forum/viewtopic.php?f=15&t=47&p=135