Closed GoogleCodeExporter closed 8 years ago
Yes, I have this exactly the same. Are there any solutions yet?
Original comment by hungry4g...@gmail.com
on 2 Apr 2010 at 11:06
Have had this problem since upgrading to Snow Leopard about a month ago. No
solution
yet that I can find. Is anyone still working on Soundflower?
Original comment by chrisric...@gmail.com
on 2 Apr 2010 at 11:13
I'm having the same issue, I have Snow Leopard 10.6.2 and I'm unable to install
the
problem. After it tries to install the program, the message reads, Application
Failed
to install. :(
Original comment by whimsy...@gmail.com
on 7 Apr 2010 at 8:35
SL 10.6.3, Intel Core 2 Duo in 32-bit mode. Install fails as described by the
OP.
--johnt
Original comment by jdtang...@gmail.com
on 8 Apr 2010 at 8:36
Maybe their just not seeing enough complaints yet. Keep 'em coming! It sure
looks
like the tip of a widespread issue here to me. I'm running the core 2 duo too
by the
way...
Original comment by chrisric...@gmail.com
on 8 Apr 2010 at 5:44
I am also having this problem with Snow Leopard. A few weeks ago I purchased
some third party software unaware that it used soundflower's extensions. This
normally would not be an issue to me, but when I uninstalled their software, it
also uninstalled the kernel extensions for soundflower. Since then I have
tried install some other software that ironically also uses soundflower's
extensions. Whenever I try to install these programs they come up with 7
different .kext files that did not install properly and need to be reinstalled.
So I did what most would do and contacted the authors of the software and they
told me that was impossible for their software to cause these issues. I am not
sure exactly what the problem is and I would sure appreciate any help anyone
has to offer.
Thanks
Original comment by davechid...@gmail.com
on 22 Jun 2010 at 11:07
Attachments:
@davechiddics: Your problem sound more as if the uninstalling of other software
has removed the kext files (?)
Our problem has been that since upgrading to Snow Leopard (without removing any
software) seems to have broken Soundflower's links to the files.
When you say you've contacted the authors, are you talking about the authors of
the other software, or the authors of Soundflower?
Obviously there IS an issue here, that isn't being addressed. Having been so
long since reporting this issue, and there is still no solution, what's the
point of keeping Soundflower anymore?
It was nice to be able to use it for the few months I could, but now it's just
a dead set of files on my hard drive, so "Good bye Soundflower!"
I understand the app is free, but even free ain't worth it if the authors
aren't paying attention to their bug reports. Seven comments in two and a half
months and not one reply from from the author is not very confidence building.
Is the project fizzling out? It sure looks that way.
Original comment by chrisric...@gmail.com
on 22 Jun 2010 at 5:54
Update:
Just for kicks. Try this:
Go to Applications:Soundflower:UninstallSoundflower.app and launch it. Restart.
Download latest Soundflower (Version 1.4.3). Install it. You will get many of
the same error messages during the install. Ignore and dismiss them. Restart.
I just did this, and Soundflower now appears to be working just as before, with
no errors.
Note: If opening Soundflower isn't working from the Applications folder icon,
it's PROBABLY ALREADY RUNNING.
Check your menu bar for the Soundflower icon there. If you see it, it's already
running. Use that icon to open the control panes.
Hope this helps.
Original comment by chrisric...@gmail.com
on 22 Jun 2010 at 6:22
P.S. I am now running OSX 10.6.3
Original comment by chrisric...@gmail.com
on 22 Jun 2010 at 6:23
Wait a minute. 1.4.3 is apparently NOT the latest version (?). I got the file
from http://mac-free.com/download/Soundflower.html
It says version 1.5.1 at the top of the page, but there's a link about halfway
down the page "For Mac OSX 10.4 10.5 Download v1.4.3"
Which doesn't make a hell of a lot of sense, because I am running OSX 10.6.3,
but whatever.
It appears to be working. I haven't actually tried to do much with it yet, but
all devices are showing up in it properly now, and there are no more annoying
"kext" errors.
Original comment by chrisric...@gmail.com
on 22 Jun 2010 at 6:30
Original comment by 74obje...@gmail.com
on 15 Oct 2010 at 6:19
Original issue reported on code.google.com by
chrisric...@gmail.com
on 30 Mar 2010 at 5:21