Audio Patch Thru Problem

[bachconnelly]

Hey guys.. I have a weird, but probably obvious problem. When I am recording on multiple tracks and I hit the Audio Patch Thru button to monitor them... it will only playback one of the tracks. For instance I hit audio patch thru and then hit record on my vocal track.. I hear the mic for that... then I hit record on my keyboard track and now I only hear the keys and my vocal track is gone!?!? What the hell am I doing wrong?!? I also have some other questions about the audio patch thru and how to route it to different places.. but that's for another day.... thanks guys!

Daniel

[bassie12]

I've had numerous strange audio patch thru incidents. This always happens on an older dual 2.0G5(at a studio where I work a lot), but never on my dual 2.7(home). Unpredictable monitoring behavior, just one side of a stereo pair going into input...just strange. NOT funny-strange, but bulls**t strange especially when DP5.01 decides to get goofy two thirds of the way through a three hour piano overdub session(yesterday). As much as I hate Digidesign, I almost booted up the studio's protools rig yesterday.

I found a new DP5.01 goodie the other day: clearing peak meters interrupts audio playback and record. On both machines.....great, thanks MOTU.

I've kept 4.61 active on both machines...just keep a folder of prefs for each on the desktop and option drag the appropriate set into library/preferences/Digital Performer before booting. This way I can choose my poison:

Audio & record interrupts on DP5, clicks & dropouts while editing during playback in DP4.6....

I must admit I've been shopping for AMD/Opteron based PCs and looking closely at Nuendo & Sequoia, especially for basic tracking dates. DP5's unpredictablilty, the latency BS that is now endemic to MAC based native DAWs and the software bloat that MOTU(and others) have accepted as a birthright to be remedied by faster and more expensive hardware, rather than effective coding has me looking elsewhere. It's not just Motu. Apple has never fulfilled the their promises for coreaudio, while native PC DAWS(Nuendo, in particular) routinely operate with latencies of 1.5msec.

Apple's almost annual overhauls of OS X haven't made it any easier for software developer's, I'm sure...but at least we can putz around with widgets while we wait for what seems like an hour for DP5 to reboot and wade through the WAVES authorizations....

I'm especially impressed with Nuendo's control room/studio/headphone routing setup. Has anyone in MOTU's design team ever sat at a Neve or SSL console? Of course, if they did they'd never admit it.....if only our government could keep secrets like the crowd in Cambridge.....

After 21 or so years of being a MAC die-hard, a DP advocate since the advent of the pci324, and Performer user since the MAC512 days, I'm done. Apple & DP will both have to prove their claims before I spend any more cash on software or hardware upgrades.

Sorry for the rant...but that's where I am now

[shuvel]

amen bassie, amen!

[bachconnelly]

I agree with you bassie.. and I do use an SSL for almost all of my projects. The biggest thing DP lacks is that there is no way to attenuate the level of the audio output when using the audio patch thru.. or am I just a dumbass and not aware of where that is....

Daniel

[bassie12]

In 4.61(5.01 too, sometimes), the fader on the mixer controls audio patch through level, assuming you are using a MOTU interface.You can further modify input levels using cuemix. If you have other hardware, you need to use the control software for that device.

Speaking of control software, how come logic, nuendo, sequioa, protools...etc can provide full Mackie Control Universal implementation, amd MOTU can't even get the pan pots to work smoothly......ARGHHHH!