LOOK! I installed Lion but the firewire is NOT recognized on my Mac Pro!

is the 32 bit kernal in lion a hybrid 32/64 bit kernal like snowleopard was? While i'm in 32 will it run 64 bit apps in 64 bit? because switching back and forth is going to be frickin annoying.

It will run 64-bit apps. It does change how memory is managed.

If you check MPG and use huge files for CS5.x it does help some to use 64-bit kernel mode.

The OS is hybrid, and it is kernel not kernal.

Leave it set to 32-bit mode.

I wish it actually was a pure 64-bit kernel OS though.

thank you for the spell check. lol. I wish I could blame the new auto correct but I turned it off. jokes aside I really appreciate the good advice. I shall indeed leave it in 32 for now. I wonder why initial boot was 64? oh and restore is so nice. I <3  for that one.

Thank you Theodore, your solution fixed my problem. m

I am in the same crappy boat. Only I am going on 3 straight days trying to fix something that should never have been possible. Like most of you, none of my audio devices are being seen, inside or outside of any of the pro apps I currently working in. I had a client fly in from the east coast, (I am west) and when she arrived we not only were unable to hear any playback, all the recording we were scheduled to do was lost, i still had to pay all my session players and crew. What kills me is how naive the tech reps at the senior, Austin TX level sound about all this. The day apple takes responsibility for us losing money because of the trust we give them is a day that will never happen. If we do anything on the job that costs others money we are help accountable but not the company I have supported since 1984. I am way beyond frustrated and I apologize for venting. I still love Apple but they sure screwed the pooch on this one. I'm gonna have to start referring to them as Gus Grissom... By the way, I did reimburse my client her 922 bucks for air too.

Any "x.0" (as in Dot Zero) is to be avoided, never jump off the clifrf, let others do the final beta testing, wait 6-9 months, wait for "Service Packs" to come out.

They call new and latest bleeding edge tech for a reason.

I've seen posts with links to alpha (pre-beta and not much in testing even) being posted for some devices while waiting for a beta and only later for a more final versions. And that takes months. The first heady month of 1 million new beta testers! and for reports of problems to filter in.

CLONE YOUR SYSTEM and DATA Have a redundant set. And if you have spare time to use, test and take new toy for a Sunday drive to see how it handles the road, not under production conditions. If you can afford to, a spare machine for running Tests can be ideal.

Snow Leopard came out in August 2009, last year at this time we had 10.6.4, which wasn't without its issues either. Next year at this time, Lion will still be around, maybe there are features and you want Lion.

People had a strong distaste for IT and its culture and rules for holding off on deploying updates until they were thoroughly tested and any problems identified.

Its actually a bit worse than I mentioned. I would have never taken the OS the day it rolls out had I not been told I had to because of my apple server. I have both server, and client drives and server was a mandatory update. Once I did that, it also required updating the other drives snow leopard OS.

I have been in love with Apple since buying what has been recorded as their 562 macintosh sale the day after the superbowl in January 84. I have been through it all and have never waivered. So, in my earlier post I mentioned loving apple still however like many, I am very disappointed in what appears to be a decline of apreciation for veterens like myself and like you too. Do you remember in 07 when Soundtrack kept experiencing kernal crash whenever you plugged in a M-Audio devise through firewire? That was like the first time Apple had ever really been infected by an outside act. I was the guy who first reported it, and then stayed on the team to uncover the source and fix. I have been down the road with apple.

Today, this is not the same company Steve created. It hardly means I am going anywhere. It is by far and away, hands down the best operating system and hardware available; As I said, I am more disappointed in their lack of concern for those of us who's entire career has been dependent upon a relationship that no longer exists. I agree with you as an end user we take responsibility for our choices, and as an enterprise partner and iTunes content producer-supplier it stings me a great deal. I dont care as much about the losses, I care that apple doesn't care about my losses. Thats what *****. FYI, you can reach me at iTunesProducer@me.com. wink

actually its occuring on new mac pro's such as my 2. I have a mid 10 and and 11. Both are afflicted with a loss of audio.

Just got this from Tascam...

Unfortunately that unit has been discontinued for a few years now and we are no longer developing drivers for it, so I doubt a Mac OSX Lion/64 bit driver will be released. I apologize for any inconvenience.

Thank you for your interest in Teac/Tascam products.

It seems as if this is a bit more problematic than a simple 32 bit mode boot… I booted into 32bit mode (single boot & persistant) However the Tascam is not recognized by the system.

Looks Like I will be installing a second 10.6 only partition for recording - crappers.

I was using an imac 2.8 corde 2 duo

This was a great unit while it lasted, but it is time for an upgrade, I have heard that RME does a good job at supporting legacy products with new drivers well after being discontinued.

The issue: Tascam FW 1884 is not visible in Lion.

The cause: Tascom only provides 32-bit drivers for their legacy devices, and will not update them for the 64-bit kernel. Lion defaults to a 64-bit kernel for many more computers than Snow Leopard did. So if you have a newer machine, it's likely now booting to 64-bit kernel mode whereas SL was in 32. You need to override the new default for your hardware.

The solution: Boot your machine into a 32-bit kernel by default

- cd /Library/Preferences/System Configuration

-Back up your "com.plist.Boot.plist" file

-Edit your com.plist.Boot.plist file.

-You'll need "sudo" with the editing command of your choice, since this file is owned by "admin"

-Add the follwoing in the <dict> section:

<key>Kernel Architecture</key>

<string>i386</string>

-Reboot.

Now your Mac will restart in 32-bit kernel mode by default. Your FW1884 should now show up just as it did in Snow Leopard, provided you have the 32-bit drivers installed.

I have notieced that I've had to slighly increase my latency, and I am getting a few audio dropouts I wasn't seeing in Snow Leopard. I'm going to see if I can fix this or if I need to move back to Snow Leopard. In the meantime, I've got some music to make.

The Tascam FW 1884 runs okay for me in Lion with the 32Bit kernel on an 27" Core-i7-iMac but I am experiencing the same occasional audio dropouts every few minutes. Audio comes back after a few seconds and the kernel logs read:

DoStartAudioTransfers w/resync

TASCAM FW1884 Audio Device: InitiateAudioTransactions

I sincerely hope this is something that Apple will address with an update because it happens to affect all soundcards. As we all know, Tascam has faded out the FW1884 and there will be no further development on the drivers 😟

I wish there was an adequate replacement for the 1884. Such a wonderful, high quality, all pro, all-in-one console. The next best thing seems to come from M-Audio with the Project Mix but that's got way less functions and looks way less pro and high quality.