|
|
Soundflower for Snow Leopard Well I don't know about you but the current build of soundflower doesn't seem to work with snow leopard until now. Here is the snow leopard soundflower package. As per the licensing and distribution agreement i have to include the source file that you can download in order to re distribute sound flower. As per sound flower bed that works as well. install my snow leopard soundflower package then either build the soundflower bed from the source or download the binary from google code and do a custom install from the current distribution 1.4.3 make sure to not install sound flower only sound flower bed from the current build because there is a problem with their kext file which you will probably know if you are reading this.
|
if you don't know what sound flower is it is an amazing virtual audio routing device that can be used alone or in concatenation with an aggregate device set up to maximize your systems audio bus. in particular relation to QC you use it to route your itunes into a qc audio patch so you do not need to adhere to apples visualizer conformity protocols. on a sweet not itunes has lifted its security protocols to allow things like 3rd party plugins and video input so conforming to their protocol is not all that bad however as it is now you still need to have a visualizer running in itunes to get an audio spectrum running through quartz which will take up cpu power. so you can conform to protocol with a blank qc file or do the quick thing use soundflower while testing your developments.
Well, it's not been in need of much updating since November 2008, the latest date in it's currently Open Sourced home and when I installed it anew and afresh, I found the following upon allegedly installing Soundflower.
The SF installer has not gotten a .kext that is SL compatible, dust, so I guess you must have installed over a pre-existing installation from your 10.5 installation base.
See attached example.
The SF facilities are unavailable and frankly , I have until now, found Kineme's Audio Tools to be a very flexible set of QC patches, accessible via almost any supported Audio .kext's and environments.
yes thats the error the current build gives, i did not do an upgrade from 10.5 im working from a clean build. just install the snow leopard version over the current build to fix .kext then use the current build to custom install sound flower bed only ! do not over install the current build after you install the snow leopard build. see attached picture for verification that it works. you where getting this error from the package you got on my site ?
Apologies for my tardy reply,dust, been busy with paperwork and such and today has been spent tracking down why the repair permissions routine failed on one of the Remote Management agents, keychains need to be rebuilt, passwords needing to be reset and even worse, failures on logons to essential sites.
The error I got was after my doing a fresh install of Soundflower, drawn from the Google code repository , upon an installation that had no prior SoundFlower installed at that time.
Just for badness' sake •~ ---> see attached pic.
YesItsReallySoundFlower in 10.6 - first time in captivity poops :-)
dust, you're a star.
so yeah im really going to convert over to sl sooner than latter im doing little by little cause i have spent the last year setting up leopard and i don't want to let go just yet but i am ready for the change. some of my QB projects do not run in SL and some do. as far as passwords go for remote management SL gives me errors on my server i made a new user from a fresh install. really im the only user but i have 2 of them cause my terminal stopped working telling me that the admin did not give me permissions to run it but i am the admin so i thought a new user would fix the problem no, but when i try to remote into my new user it wants my old user password which is just weird. im finding certificates in my keychain that try to give themselves root privileges. don't know if its from fastpasstv.com or what but one night i was setting up my developer certificate for apple because i forgot to export my certificate from leopard and being a clean install the only keys where mine. well had some issues with keychain signing because of old provisioning files and well got frustrated gave up. the next day i went nuked all my provisioning files and back into keychain and there was some fucker trying to give himself root access. well i deleted his keychain and installed my certificate.
i noticed chriswright has a keychain that must be for k3d don't know but i like him so didn't delete him plus he wasn't trying for root although any application that gets installed via the package manager should be set to root so theoretically any software you install could have bad intentions. some times i fuck with people trying to compromise my itouches security i give them access and watch what they do most of the time its a bot collecting stupid info. if they go for my mail i cut them off. so just be careful with remote stuff. i don't really have any information to protect at the moment but be carful all the same.
particularly with girl friends and roommates. i had my wife and an old roommate try and bring fed charges cause i set up my home server and network vnc. thankfully the state i live in is a one party consent so there is no law against recording telephone and security camera via the internet or any remote place. really it was just my wife and old roommate playing girl power and trying to ruin my life but it didn't work.
I get your strategic reasoning, dust, careful setting of one foot in front of the other, I dig that.
Still haven't figured out about the provenance of the Snow.qtz, but I reckon that has nowt to do with the keychain problem, that just needed a good repair.
The security problem[s] is / are becoming increasingly prevalent - hi ho off we go to register at MacShadows :-)
I think, if I had retention of the wisdom to do so, I'd probably just heap 'coals' on the heads of those motivated by malice aforethought to softly shame them.