Well, it worked and then it didn’t.
Core Audio seems to be temperamental, or is it OSX?
First try after reboot gave an excellent volume output.
Then it went back to previous state.
Don’t know what to think about it.
Thank you all.
This post is becoming a huge behemoth: Neither Audacity v2.1.1 nor v2.1.2 would not launch.
I’ve read Gale’s post about Audacity not launching and followed instructions therein (please see "audacity.cfgattachment.).
There is no line under “Directories” that looks like TempDir=/tmp/audacity1.2-<your user name
I don’t want to delete that line without further instructions.
Thank you all again,
Ruben
I thought I did, sorry; I would’ve liked to re-attach it but both extension cfg and extension rtf are not allowed: what can I do?
Copying the file’s text is not giid as it is quite large, so?
Ruben
So does the problem only start after the plist files are recreated? It’s a thin chance, but it might be possible to edit the plist files. You would not do that in TextEdit though.
I’m beginning to wonder if it’s not time to do a clean install of Snow…
Something is reproducing the error in the plist files. That’s like wrestling a bear. Could it be Soundflower? Any chance there’s a leftover from a JackOSX install?
You could uninstall and reinstall Soundflower for sure. In the /Applications/Soundflower/ folder, double-click “Uninstall Soundflower.scpt”. In the window that opens, press the “Run” button. You should see “Done!” in the results, indicating that the uninstallation completed satisfactorily.
Gale
Now (today), I don’t have to select the USB headset in Audacity before the headset can be heard in other applications.
Can’t tell why it is now correct.
BTW, do you remember I couldn’t upload the .cfg file either in .rtf or in .cfg format?
Just tried to upload it as a .txt file but it is not accepted either.
Maybe you could tell me how to edit the plist files if necessary.
It is a pity you cannot read the .cfg file; I believe it would help you on knowing what’s happening.
I don’t know which kind of file can be uploaded.
Thank you
Please read my latest reply to Gale Andrews.
I don’t believe soundflower is the culprit.
I’ve just been able (today, 15 minutes ago) to listen through the headset and through the internal speakers without having to go to Audacity to change the output.
I’ve done a clean install of OSX 10.6.8 a couple of weeks ago.
What is a JackOSX install?
Thanks
Jack is a Linux audio router, just like SoundFlower. Often, people who have installed SoundFlower have tried JackOSX or one of the other versions for Mac before. Removing it correctly is not always easy for most users.
Having both SoundFlower and Jack is a sure way to trouble.
But as you have a clean install from a few weeks ago and never heard about Jack, that’s not the reason why you have this strange error…
Nobody has a rational explanation for what is happening so you may have to think a little outside the box.
Soundflower is a kernel extension so has considerable scope to make system changes. We don’t even know which version of Soundflower you have or whether it is appropriate for Snow Leopard. Early versions of Soundflower were very buggy.
Well you could open Finder and check if the plist files you deleted have been recreated.
If they have been recreated, you can copy them to your Desktop in case they come in handy.
Text files are allowed if they have .txt extension. Files with .cfg extension cannot be allowed for security reasons. If you ever want to post audacity.cfg, make a copy and rename it in Finder to audacity.txt.
I see no strong reason to disallow .rtf extension so I have enabled it.
TextWrangler would work, as the plist files are XML rather than binary. Let’s go into that only if we need to.
It would not help with the strange audio problem that seemingly you alone are having.