Mini and osx no longer recognizing firewire audio device

i have an m-audio firewire solo hooked up to my mini, which is just a simple firewire instrument interface. i went to bed last night and everything was working fine. woke up this morning and the sounds is now coming from the internal speak, not my stereo. nothing is wrong with the firewire port because its still lighting up and running, but osx is telling me there is no m-audio device connected to the computer. i tried to reinstall the software but that did nothing. should i try to completely uninstalling the software and then reinstall? i also installed m-audios upgrade about a week ago but had no problems up until now. if none of this works, should i strat wondering about a potential virus and possibly formating the hard drive?
any help is certainly appreciated

I have a similar device. A fresh install of the device may help.
For my device the manual says to turn off all power saving settings. Do not let the computer go to sleep, not the screen, not the hard disc, not anything.
That is probobly unrelated to the computer not recognising it.
It's not a virus.
Make another user account in the System Preferences. Log out of your account and into the newly created one. Does it work?
If you still have no luck, run the apple hardware test with the discs that came with the computer. A simple search can tell you how to do it.

Similar Messages

I have a mini and it is not recognizing my iPods and iPads. Is there a setting i screwed up?

have a mini and it is not recognizing my iPods and iPads. Is there a setting i screwed up?

Device not recognized in iTunes for Mac OS X
Mac OS X v10.6 or later: iOS device not recognized in iTunes after restart

ISight and Firewire Audio Devices

I am having issues with my Firewire audio devices and my iSight camara. If I am using my external Firewire audio device (Firewire 800) I get errors on my audio device and somethimes the iSight camara. If on plug in one of the devices things seem to run ok. I have a recording studio and work with other studios on line. Is there any fix for this....

Hello again, David,
No change since your previous posts:
http://discussions.apple.com/thread.jspa?messageID=4995560 and
http://discussions.apple.com/message.jspa?messageID=5004577#5004577
If you have not already done so, send your concerns directly to Apple via iChat Feedback.
(If you have other suggestions/comments for Apple, use Product Feedback for the product most closely related to your concerns.)
You will not get a response by using "Feedback", but at least you can be certain that Apple will see your comments for consideration in future products or updates.
EZ Jim
PowerBook 1.67 GHz w/Mac OS X (10.4.10) G5 DP 1.8 w/Mac OS X (10.5) External iSight

My iphones and ipods no longer show up as devices when I plug into my computer to use itunes

Does anyone know why my iPhone and iPod no longer show up as devices when I plug into my computer to use iTunes?

Hi jacquelinex,
Welcome to the Apple Support Communities!
If your devices are not showing up in iTunes I suggest your read over and follow the troubleshooting steps in the attached article.
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/TS1538
Have a great day,
Joe

10.4.11 external firewire audio device noise/distortion

Hi
Subsequent to upgrading to 10.4.11 I now have persistent noise from my external firewire audio device. It's an Edirol FA-101 and worked perfectly in 10.4.10 and earlier. I tried replacing the firewire cable with no effect.
The FA-101 is a class compliane device so uses Apples built in firewire audio drivers.. has anyone else had firewire audio problems with 10.4.11?
Thanks
Mark

No I doubt it... FW can be strange sometimes.
Look in Sytem Profiler, if it says you don't have FW at all, then remove all power from the iMac, let it set a few hours to Drain down, plug back in everthing.
Or...
http://docs.info.apple.com/article.html?artnum=301733

MBP 17" Boot Camp Firewire Audio Devices

Hello Everyone.
If your having installation / dead audio issues with a firewire audio device in Boot Camp running Windows XP such as the Presonus Firepod or Tascam FW 1884 you should try downgrading your firewire drivers from Service Pack 2 to SP1.
As showed in this article:
http://www.rme-audio.com/english/techinfo/fw800sp2.htm
Please note I also had to rename my services pack 2 file (C:\Windows\Driver Cache\sp2.cab) to another name so windows wouldnt use it when downgrading.
Both my Firepod & Tascam now opperate as expected.
After a day of searching and crying I found (loosly) the answer in these forums.
Thanks everyone, hope this info is useful to someone else too. ^_^
Best,
Timothy - trash80.net
Mac Book Pro 17" Mac OS X (10.4.7)

After two complete reloads of OS X, Boot Camp and installing XP Pro again both times the driver CD still fails to run.
Also I cannot update firmware at all. Running firmware updater
from utilities fails with a message that this firmware is for specific machines and does not apply to this computer. (not an exact quote)
Downloading and running the firmware update for MBPro also fails with a message that this computer does not need updating. Made sense to me since the 17" was released after Boot Camp but the "not for this computer" error when trying to run it through Firmware Updater makes me wonder...
I do see that the driver CD extracts some folders\files to the users Temp folder in Windows XP, I copied those out but have not figure out the manual install of drivers yet. In fact I don't see any drivers - just misc config files and the various script files to run the drivers application.
Going to run it again this afternoon after XP Pro reloads yet again and try looking in the Windows\Temp folder for the drivers, check everywhere to see if they actually extract.
After that it should be fairly simple to manually install them and circumvent the auto-install failure of the CD.
Will post later with results.

After updating to latest Itunes version, my iphone is no longer recognized as a device in Itunes

After updating to the latest version of Itunes, my Iphone 4S is no longer recognized as a device in Itunes. Can anyone help? I am using Windows 8.

Hi 2hobbits,
If your iPhone isn't being recognized by iTunes, you may find the following article helpful:
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/ts1538
Regards,
- Brenden

My iPad Air 16 gb wifi not open and asking for an address and not mine and I am the owner of this device and I can not pave if there is a possibility of me to help me open it with my address as I opened before

asking for an address and not mine and I am the owner of this device and I can not pave if there is a possibility of me to help me open it with my address as I opened before

Read the following about, "Activation Lock".
http://support.apple.com/kb/ht5818

New HD and new motherboard on Mac Mini and OSX will not start.

Long story but will do my best to keep it short...
Purchased Mac mini #1 at CompUSA years back and bought their extended warranty. Mini died 2+ years later which coincided with CUSA going out of business. Problem was a flashing folder with the Mac logo and a "?" at startup. My CUSA store was closing out and would not service my machine and gave me a phone number for the outsourced warranty/repair department. The tech took my info and decided a new HD was in order. I rec'd the new HD in the mail and a local tech came out and installed it (but refused to test it). After the tech left the same problem was found. Called warranty department immediately (literally 5 minutes later) and they siad they would send another HD as well as a mother board which I recieved a few days later. However, this time the local tech never showed back up and after a few weeks of calling the warranty number went dead. We ended up getting a new Mac mini which has been running fine since.
My daughter needed a computer so I figured I would give it a shot. It was actually very easy to replace the HD and MB. I tried starting the mini and it powers up but I got the same flashing folder so I put in the OS intall disc and after I select the language, I get a prompt that says "This software cannot be installed on this computer". I am using the original discs that came with this particular mini. I cannot get disc #1 out of the drive now but disc #2 says "Mac OSX Install Disc 2", "includes Mac OS9.2", and Disc version 1.3 2Z691-5533-A" on it. The mini itself says Mac mini 1.25G4/512MB/40GB/Combo/Modem on the underside.
Is this due to the fact that the entire inside of the Mini is new and now not compatible with the original software? How would I know what software to buy? Am I better off just taking it somewhere to get serviced or calling it a total loss? Any guidance would be much appreciated.

One the one hand I am being told that my OS discs are not working because they are unique (or keyed) to the original machine and since that machine essentially no loger exists due to repalacing the MB, I will need to purchase new software with a new license agreement.
It is true that computer specific install software is specific to the software with which it shipped. However replacing the logic board means that the new logic board is part of the computer. Unless the logic board was not an exact replacement, it should not make a difference; the original disks should work. In other words it has to do with the hardware not the license. The software license agreement allows the installation of a certain OS to one computer at a time, unless you have a multi-user license such as a family pack, which allows installation in up to five computers in the same household. The original computer specific software can be installed on a single computer no matter how many times. If that OS in that computer has been upgraded to a later OS, that installer can be used to install to another computer of the identical model so long as it is not simultaneously installed elsewhere. However, even then, it can technically be installed on another computer of the same model although installation of a single user licensed software will be a violation of the terms of the Software License Agreement.
The second opinion was that the original mini was equippmed with a powerpc processor and that the new MB I received is equipped with an intel processor.
True. Models of the mini released in 2005 and Early 2006 have PowerPC processors. Late 2006 and later have Intel processors.
Therefore, that pesron recommended that I purchase OSX 10.5 Leopard as this OS will cover both of those processors.
Partly true.
i. If your mini was released with Tiger it will support OS X 10.5x and later. If it was released in Early 2009 with Mac OS X 10.5.6 (9G2030) it will only support versions of Leopard earlier than 10.5.6 and, certainly OS X 10.6x.
ii. It will only both computers if you have a multi-user license.
iii. New Leopard installers will only install on your old mini if the original installer itself was the problem. If the problem is elsewhere, it is not quite as certain. Unfortunately there is no sure way to know that unless you buy the Full Retail Version of Leopard and attempt installing it.
cornelius

Keyboard and Mouse no longer recognized when Boot Camp'ing into Windows XP

Mac Pro early 2008, Mac OS X 10.6.2, all updates applied. WinXP SP3. Standard wired Apple smooth mouse.
I normally use Parallels 4.0 to access my Windows XP on this Mac. That's been working fine and continues to do so. I upgraded to Snow Leopard not long after it was released. My Parallels is set to use the Boot Camp partition as the basis for its virtual machine.
I haven't started Windows directly from Boot Camp in some time. It used to work fine also. I am not sure I have accessed it directly from Boot Camp since I upgraded to Snow Leopard.
In any event, when I try to boot into Window, my slim wired Apple USB keyboard and mouse are not recognized. I get to the opening Windows Log-In screen and at that point, I can't move the mouse cursor and I can't type anything into the Windows password input box. The red mouse laser light flashes once every 7 or 8 seconds but also doesn't stay on.
Starting Windows under Parallels still works fine. I downloaded the BootCamp 3.1 Windows 32-bit upgrade from Apple. I tried running it in Windows under Parallels. Something ran for a while when I did that but there was no installation screens or dialogs after I clicked the "run" button.
Not sure what to do next.
Thanks.

Adding to the above: I also tried plugging in an Microsoft USB keyboard at the point when Windows freezes at the Windows log-in screen. The keyboard is not recognized and the only way I can leave this screen is to power-off the computer.

2010 Mac Mini and OSX Lion

Hi Everyone,
Hoping I can get some advice.
I have a 2010 Mac Mini and am thinking about upgrading to OSX Lion.
Although I know my Mac meets the system requirments (Intel Core 2 Duo, 2Gb RAM), I was wondering what the performace is like on with these specs.
I mainly use my Mac for iTunes, Safari, Twitter and iPhoto if that makes any difference.
Thanks!

It works ok for me, I've got a 2010 mini (base model) and am using it as a server for web, iTunes and VPN. It handles lion fine, the only quibble is that being always on it heats up during the day a lot, more so than when I had Snow leopard installed. It's not to unacceptable levels though. But as dingy and beezelbubba say, Ram is cheap nowadays and if you've got the spare cash it's always worth it.

Ipad mini and iphone no longer syncs "last page used" of my ebooks

My ipad mini and iphone recently stopped syncing the page locations for my kindle e-books. Each time i go from one device to the other i find my book on the same page it was when i last used that device and when I tap the sync circle icon it tells me that i am "currently at the furtest location across all your devices." Not! it used to sync them but now it doesn't and I don't know why.
Christine

Sounds like the problem is with the phone. Do a hard reset and go from there.
Basic troubleshooting steps.
17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G + 120G OCZ Vertex 3 SSD Boot HD 

High pitch squeal related to Firewire audio device after 10.6.2 audio patch

So the recent Mac Pro audio update 1.0 (applied on 10.6.2) has reduced my CPU temperature with audio playback (Presonus Firebox Firewire audio interface) and that is great. Also haven't had any machine crashes (grey screens) recently which is also great.
The problem is that when the Firebox is plugged into the firewire port of the Mac Pro there is a constant high pitched whistle of slightly oscillating frequency. If I unplug the Firebox the whistle goes away in a few seconds.
After prolonged use in a quiet room (the kind of room you need for audio recording / mixing work!) the noise is enough to drive me crazy.
I read a post on another forum with other people having the same problem. Can anyone comment here on seeing the same thing? Is there any known work around or fix for this?
When the CPU is under heavy load (e.g. H.264 compression etc.) the noise subsides only to return when there is normal load (i.e. half a dozen apps running).
Help!
Thanks

So I was able to back out the update using "Kext Helper b7" and the original IOPlatformPluginFamily.kext and AppleHDA.kext files from a backup before applying the update. It's pretty easy - just drop the two files onto Kext Helper, hit "go" and then reboot.
My ears are no longer in constant pain and I can actually use the Mac Pro again albeit running quite hotter than before.
This is not a fix Apple. The problem looks unrelated to a specific device based on the posts in this thread. Please issue a usable fix for the Mac Pro Audio performance issue.

Macbook Air no longer recognizes external audio devices

My Macbook air's audio port recently stopped recognizing external devices such as speakers and headphones.
The external devices are functional with other devices and fully plugged in, but only the internal speakers will produce sound.
This problem happened just recently with audio devices that had been working fine with the laptop before. I did not use any
audio devices that I haven't used with the computer before. They are fully plugged in, and I've already tried twisting the head
of the cord to see if it's going bad. The headphones I tried to use work fine with my iPhone.
I've tried opening System Preferences > Sound, to select the device, but it doesn't show up in the device list.
The internal speakers work fine, and continue to work even though the headphones or external speakers are plugged in, and in
the case of the external speakers, turned on.
Does anyone know if updating my audio driver would help?
Has anyone expirienced and resolved this problem or a similar problem?
Does anyone know how I can actually get in touch with someone who works at apple without having to go in to their store, as
I don't have time to do that and wouldn't be able to leave my laptop for repair since I use it for college?
Any help would be greatly appreciated!
Thanks so much!
Update:
I've tried using "Audio MIDI Setup", the external devices do not seem to be recognized by the computer.

Because something has gone wrong. I have no way of knowing what, and without backups, you're in a very bad situation.
If you want to preserve the data on the startup drive, and it's not already backed up, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data, you can skip this step.
There are several ways to back up a Mac that is not fully functional. You need an external hard drive to hold the backup data.
1. Start up from the Recovery partition, from Internet Recovery, or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
2. If Method 1 fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
3. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
4. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

Firewire/Audio Device issues

I have a Yamaha Motif XS6 hooked up to my macbook pro running Mavericks. There is an audio driver downloadable from Yamaha (YSFW) which was working perfectly right up until I installed an M-Audio driver. The M-Audio device is no longer supported beyond 10.8.2 so I uninstalled it again. Since then the Motif cannot talk to the macbook pro.
The journey thus far:
I have been able to access the Motif via firewire from a different laptop which means the mLan card in the Motif is working fine.
The Firewire option is viewable under network control panel as working but I have no cable (firewire 800-800) to test it against any other device.
My own personal conclusion (that is only best guess so far) is that the M-Audio driver has knocked out my yamaha YSFW driver.
How do I test this? Are their files/drivers I can be looking for or reinstalling? (I have uninstalled & reinstalled the Yamaha SYFW driver a couple of times with no success.)
Thoughts? Ideas? Opinions? If we can make this work tonight I'll buy you a car!! (actually that's not true and wont stand up in court!)
Thanks for your help in advance.

If your Macbook is a 2009 or later model then it already uses the revision 7 LSI/Agere chipset. And it's likely not the source of the issues.
Have a look here: http://www.rme-audio.de/forum/viewtopic.php?id=4986
What a hub/repeater does is that it puts another FW chipset in between the faulty rev. 6 LSI and the audio interface, kind of translating the error away (I once used a MOTU Ultralite to make a RME Fireface 400 work on a 2008 Macbook Pro). There is no added latency or performance loss by putting another FW device in between (FW devices communicate all on their own).
Concerning FW/USB and channels. 48 channels of 24-bit audio at 192 KHz is still less than 27 mb/s and as such easily handled by USB 2. I can fire all 36 I/Os of my Fireface UC at 44.1 KHz while transferring data to an USB HD drive that is connected to the same USB hub. That is possible because the audio interface can reserve bandwidth on USB just like it can on FW, the HD just gets what's left.
The RME UFX even comes with 60 channels total and can be run over both FW and USB 2: http://www.rme-audio.de/productsfirefaceufx.php
Most USB interfaces suffer more from bad driver implementations (and early USB chipset issues) than from any limits of the USB protocol itself.
Message was edited by: T1mur

Mini and osx no longer recognizing firewire audio device

Similar Messages

Maybe you are looking for