MOTUnation.com

After upgrading to DP6 and downloading latestest Firewire audio driever, MIDI works fine for a little while, then there is no MIDI IN communication from my keyboard controller. I have an M-Audio keystation pro 88 that is hooked up (MIDI out to MIDI in ) to my MOTU 828 MK II. The MIDI keys in DP6 still work, and MIDI information already recorded plays back through both soft synths and synth modules. Even the MIDI activity light on the 828 still flashes when playing controller, but no MIDI getting to DP6. IT would sometimes happen with DP 5 but now its very consistent, Especially when I explore different things in DP6, all of a sudden there is no MIDI in communication to DP6. ANd there is nothing reading in the MIDI monitor. AT first I thought the only way to "get it working again, is the shut down and restart both the DP6 AND the Mk II. I don't need to restart OSX or the controller--i tried all combinations for what works after restarting, but just now it fixed itself when i quit and re-launched DP6 without even shutting down the MKII. Just this last time, it happened when i was in the process of recording, via MIDI and a soft synth. I would hear to very very high pitch, almost inaudible, and then the MIDI notes would freeze. I repaired permissions--didn't help. MOTU TechLinks just say its an Apple problem. Apple thinks its a MOTU hardware problem, but suggested to check Firewire connections. Or possibly re-boot--don't wanna go thee if I don't have too. Any advice from out there> My specs are below---anyone.....HELP!

OSMac OS 10.5
OS version 10.5.7 (updated wrong info)
CPUIntel Core 2 Duo, 2.4 Ghz, 1 processor, 2 cores
RAM 4GB

I would try the 10.5.6 combo update.

I realized that's an old OSX on my specs. I have 10.5.7. i still think its the MOTU 828 mkII firewire unit that is the culprit. . I used a simple Roland MIDI interface and had no problems. When it did give me that "high pitched" sound, the MIDI didn't die on me. It was as if the MOTU 828 "burped". I guess it still could be an OSX Firewire communication problem, but using a simple USB MIDI interface at least alleviates the problem, so far.

peter i am having the same EXACT problem with an Oxygen 8.

i had it hooked up using the USB only for years on an imac G5 OS 10.4.11 and i never had any problems. now after a computer upgrade to an intel imac dual 2.6 OS 10.5.7 using the same Oxy 8 i am having this problem. it has taken me a week to track down that it is either a driver problem or some kind of OS conflict somewhere, i was leaving open the audio/MIDI setup window and rescanning MIDI 2 or 3 times then it would come back for a moment then poof gone again over and over. at first i thought that it was the USB cable, then the hub, then directly into the mac. all same problem.

then i connected a midiman 2x2 to the mac. the Oxy 8 via a MIDI cable to the midiman added the new devices to the A/M setup and it works just fine.

i am stumped and hoping to find a solution.

i just bought an AC/DC power supply to power the Oxy 8 but that didn't help my original setup connected via USB

imac OS 10.5.7
DP 6.02
Oxygen 8
M-Audio Keystation drivers

ron

Ron, I wonder if the third party software companies like MOTU already know ther is some type of glitch with OSX and they want Apple to fix it by leaving us hanging and complaining to Apple, and not try and override it themselves. Interesting that yours in a USB connection. Mine is Firewire and assuming its a firewire thing. I'm planning on stopping at a local Apple Store, with my Apple care info at hand and snoop around. I'm also having similar problem with Finale and MIDI imput, via the MOTU 828. I'm curiuos to see if an added MIDI usb connection will alleviate that problem (not necessarily solve it) and I wonder if September's Snow Leopard will help it or compound it.

I heard something about 10.5.8 would contain changes / bugfixes to the MIDI and audio frameworks.

/B

hi peter

i did a test with my old iMac G5. i plugged the Oxygen 8 in via USB and it fired right up as before. i unplugged then plugged it into the new iMac via USB
and the same problem continues

then i checked the driver versions. the new intel version is 3.2.3 (2002-2007) and the old iMac uses 3.1 (2002)
i swapped the 3.1 version into the new intel iMac but no go

so that leaves my having to connect using the midiman 2x2 and the Oxygen 8 via MIDI cable
thinking positively ............ at least it works.

i hope that it gets fixed for us

I borrowed a simple edirol usb MIDI interface. It didn't crash on me. So far. So now Im waiting for me for my own edirol usb MIDI interface, being shipped any day now. It doens't solve the problem hoping it would at least over-ride it. As I'm still using the Firewire MIDI interface, I noticed as it consistently crashes, though i suspect its my MOTU 828mkII misbehaving, I only need to re-boot DP6 to get it back to work. Someone mentioned 10.5.8 coming out. Will Apple bother with that with 10 .6 coming in the fall?

Ok...
I am really upset now.
I have had nothing but problems with USB and Firewire.
I purchased a separate Sonnet USB PCIe card and plugged things into it like timepieces, MIDI express etc.
Still have problems.
MOTU states this is a Apple problem?

Tell them to quit hitting that pipe out back!

All My USB instruments show up fine in Cubase 5,Nuendo, and Logic PRo!!!.

But they do not show up in DP anymore since they updated it.
I have tried everything and now given up.

I have a peekaboo game with the Apple AUDIO/MIDI config. Now it is on...now it is off. Only happens with Firewire 896, 828, 24/IO's.
My USB instruments show up fine in AUDIO/MIDI config. (Roland Fantom xr's, Yamaha MOTIF XS, M3.
But DP does not see them.

Also I purchased a Alesis MAster Control. To control DP...

DO NOT DO THIS!!!
All kinds of hell broke out with the Firewire interface's. Crash, Apple Grey curtain of death. DP crashes, Hangs. MOTU needs to update there drivers NOW! They need to get with the PRogram like get the 800 firewire.

I called Apple and they read my Crash report and...YES it is bad code, improper handling of memory and Bus collisions etc from the good old MOTU stuff.

So.
Do not waste your money on USB cards, and Firewire Cards. They do not solve anything.
I am using the new MAc Pro Nahalem, and I get POPS and CLicks at random, high pitched noises, subsonic pulses on SUb woofer.
I solved some by unplugging half of the motu stuff. But then how do i use the studio.

Here is my setup.

1. HD192
2. Three 24/IO's
3. PCIe MOtu card with four firewire
4. 828MkIII
5.896MKII
6. Three MIDI Expres 128's
7. One MIDI Express XT
8. Sonnet PCIe USB card
9. G-Technology PCIe eSata 4 Port Card
10. G-Technology 10TB raid


I have Nothing but problems with MOTU stuff. No Tech support to speak of, crashes, Collisions with Firewire devices from OTher vendors, USB MIDI devices not working anymore with DP. Hell my Nikon Camera and Sony PMW-EX3 HD cam crashes now since i added DP , and drivers update from MOTU. Final Cut Pro...well forget about that using anything with a firewire now.. That gets all messed up with studio because MOTU doe not handle the bus properly and collisions everywhere Apple told me.

So
With that said, Save your money and do not purchase any USB or Firewire cards as it will be a big wast of money until MOTU gets off its 6 and writes some good driver code and updates DP, and there COre Sound engine drivers.

See if you look at the problem it is the passing off of the hyper-threading with the new Nahalem MAc PRo, Mac Books etc. MOTU's code is bad and until Apple comes out with a fix don't expect MOTU to...They already got our money, and MArketing seems to be running things there now, not common sense or customer loyalty. I even wonder if they own a new Mac?. I love MOTU, do not get me wrong but unless we all complain, (Lets all call this week all week to Tech support and demand our problems fixed!!!) they will go on letting us loose our money, and TV shows, Video Game scores etc because they do not seem to want to solve the problem.

Notice how there is not 1 (ONe) FAQ on their website on these issues on the forum? wonder why? because that would hurt marketing and people would buy Cubase and Logic Pro because it all works and does not crash also someone actually answers the tech support line at Apple and Steinberg! also they even give you 24/7 support if you pay in the film industry.. Go look on MOTU site and try to find this problem... Ha Hey i got an idea..try filling out a tech support work ticket. LEts have a contest and see if anyone gets a reply within 1 month on that!!! NOT MOTU must have 1 guy answering it all.

Kind Regards,
Barend

bbendorf wrote: Notice how there is not 1 (ONe) FAQ on their website on these issues on the forum? wonder why? because that would hurt marketing and people would buy Cubase and Logic Pro because it all works and does not crash also someone actually answers the tech support line at Apple and Steinberg! also they even give you 24/7 support if you pay in the film industry.. Go look on MOTU site and try to find this problem... Ha Hey i got an idea..try filling out a tech support work ticket. LEts have a contest and see if anyone gets a reply within 1 month on that!!! NOT MOTU must have 1 guy answering it all.

I was following your post. By now, you are just rambling. Could it be that the reason there is not a FAQ about that particular issue is because the amount of people experiencing that does not grant it?
Also, this forum does not belong to MOTU. IT is independently run by James Steele.

Have you tried speaking on the phone with a tech support rep? Please don't tell me you haven't been able to get trough. I live in Mexico, and I get them on the phone every time I need. You just have to call early (9 am Eastern time), and be patient. Ok, the the patient part is not my speciality

Now, have you visited Steinberg's or Logic's forums lately? You will have as many dissatisfied costumers there as well. It's not that their software is bug-free either. There is no such thing.

I can understand your frustration, but I assure you that if you take a more proactive approach, you will find more answers. Have you tried searching this forum for answers to your problems?
Ok. MOTU's tech support is far from great, I'll give you that. I agree there's room for a lot of much needed improvement, but take into account MOTU is a very small company, at least compared to Apple.
But if you REALLY want to get in touch with them, you will. Just wake up early and hit the phone.

BTW, you DO own quite a lot of DAWs!

some idiotic sequence of numbers wrote: flyaway
akin
jasminecameron
brandonmorgan
hoopr

Get out of our forum, you spamming yerk!

Hello guys,
I do have the same problem with the MIDI input on my mpd24 controller with DP6.02. the controller's pads and kobs messages are recording ok in DP but there's no way to get the MIDI tracks back to the physical MIDI output of the mpd controller.
I tried all the basic preferences trashing /new audio MIDI setup/... but none worked. so I went the hard way:
I reinstalled a whole new OS on an other drive. then installed DP5.13 and everything was working flawless again. then I upgraded DP 6 and my MIDI output's signal disappeared again.
the conclusion is quite clear! a quirk in the MIDI part of DP6.
I now use an extra m-audio usb card meanwhile
best

Maxime

I don't know if this is relevant or not, but since I installed 10.5.7, I've gotten periodic kernel panics, and when I read the log, the first thing implicated is my (idle) MOTU PCI 424 card.

I've been hearing great things about 10.5.8, so I think there were significant bugs in 10.5.7 in regards to audio and possibly MIDI. I'd upgrade to 10.5.8, using the Combo Updater from Apple's site. Then see if the problems persist. (I haven't yet, but I've been busy at something else for the past couple of months)

Shooshie

i'll be upgrading from 10.5.7 to 10.5.8 today. i'll report back if anything gets fixed

i upgraded today and plugged my oxygen 8 in via USB but using a power adapter this time and all works as before

i'll keep you posted as to any problems

homebilly wrote:i upgraded today and plugged my oxygen 8 in via USB but using a power adapter this time and all works as before

i'll keep you posted as to any problems

"Works as before" meaning that it's working again? Or that it's still broken? I'm assuming you mean it's working again. It might be instructive to use it without the power adapter so that we know which action actually fixed it: upgrading? Or the power adapter? (Or both?)

[edit] from the context of rereading what you'd written in earlier posts, it's clear that the power adapter wasn't the issue; never mind.[/edit]