MOTUnation.com

Hey Xag,

It could definitely be a defective cable but it's impossible to tell without other devices to test.

You didn't mention which driver version you're running. I would give the latest audio installer from MOTU.com a run and see if that helps.

Are you using the 1/4 inch inputs Analog 1/2 or the Mic/Inst input 1/2? I know this sounds weird but Logic, by default, assigns numbers to any ins/outs that it 'sees'. Since Mic 1/2 are the first ins it sees, all of the following Analog ins (1/4in) are offset. So if you hook into Analog 1/2, you wil...

Sorry to say but I have to agree with bad andy on this one. If the audio files are SD2 and touched a non-hfs file system, the original metadata (ie resource fork) is lost. :( The restoration of the lost resource is beyond my skill set so I'd be tempted to contact data recovery guys and see if there ...

Might be worthwhile to try resetting the creator/type of these DP files. I've used Filetype in the past when servers chewed up some project files during transfer.. IIRC the creator should be MOUP and type PERF

Hey Blair,

Third-party AUs will probably (unless it's different under 10.7) reside in:

Mac HD>>>>Library>>>>Audio>>>>Plug-ins>>>Components

Might wanna check that you removed any Modartt/Pianoteq stuff from here? or check those plugs for Lion updates??

Check setup-configure audio system -configure hardware driver. Does the mic appear here? If so, click to highlight it and then ok to publish the inputs to the track I/O list.

Setup > Set View Filter > Set All

Hey Marc, Think you may be on to something with the length of these cables. My experience with a buddies PCI system was that we could only use runs of about 15 ft. (same as FW). Although he did end purchasing some uber-expensive cable that he ran out to ~20 ft without timing issues to his 2408. So t...

Any idea if they tested on 7.24? Not that it would make a difference but your profile says you're using 7.22. It's a long shot but worth looking at any differences between the two systems. If there isn't a particular reason you're sticking with 7.22, updating would be MY next move.

Hey Gavin, Since you mentioned it, does your system still freak if you disable all the other parts and just try to run the 5 omnisphere voices? Could be something else in the project that's tipping the CPU load vs when the Spectrasonics guys tested on their rig? Just throwing it out there...Who know...

What about the input monitoring mode under Setup > Configure Audio System? Doesn't this have to be set to monitor record-enabled tracks to hear busses on live patch through?

Bit of an old thread resurrect? I've seen this trick help out FireWire devices in general (including audio interfaces). Maybe worth shot? I would turn off any FW gear before attempting the swap. Check out the vid (way easier than explanation): http://www.youtube.com/watch?v=s4JfbDW6AtI" onclick...

My buddy ran into this "problem" with his audio express and contacted MOTU after a few hours of :smash: . Believe it or not there is an easter-egg feature that allows auto power-on. I'd never use it but can imagine it would make sense in some setups. From memory, you boot up in firmware up...

Hey Jack,

Definitely sounds like dumping the system font cache is in order. I prefer to use Onyx for this but you could also try booting your system in Safe Mode and restarting.

Cheers

This one has got me before and it's tucked away in the Audio Monitor (Shift-A) mini-menu. There should be a Base File Names On submenu or something close to that.