Has anyone heard from MOTU re: terrible MIDI?

[hardingray]

Exciting new development:
I managed to port bits and pieces of my setup back to DP3.1. I used the same simple drum track I was using in DP4.52. And... I'm still having the stuck notes in my devices that are running from the second MTPAV (serial).

So, I guess this becomes a new question:
Why am I getting stuck notes/MIDI log jam on the second MTPAV?

A quick recap:
One MTPAV is USB, and is connected to the computer. The second one is serial and is networked to the first. It is this second one that's having the problems (as far as I can tell). All the of the stuck notes I'm hearing are on devices connected to the second (networked... serial) MTP.

I'm playing a simple drum beat on channel 8 of a device that's on the second MTP, and every minute or so (DP3.1/OS9 AND DP4.52/OSX) I get a flurry of notes on every other device that is assigned to channel 8 of the other ports on the second MTPAV.

Thoughts? Incantations?

Hardin

[Shooshie]

Wow. I just read this whole thread, or at least most of it. I'm shocked and amazed. I didn't know this was really a problem. I'm going to post my system here, for what it's worth, because I have never had this problem.

I don't use virtual instruments, so that may be a clue. I have files ranging from a few tracks to a few hundred, and all of them work without problems. I've got Controller 64 both as switches and as continuous data, and again, no problems. Never a stuck note; never a timing problem. Tap tempo sometimes behaves a little strange on recording, but plays back properly. I just cannot imagine what is causing all the problems I've been reading about here, but I sure hope everyone finds the answer.

Just in case this means anything, here is my trouble-free system:

G4 dual 1GHz, 1 GB RAM
IBM Deskstar internal 80 GB IDE drive
Glyph external 80 GB FW drive
LaCie 120 GB external FW drive
Que 80 GB external FW drive
MTP AV (USB)
MTP AV (Serial, daisychained to USB MTP)
MOTU 896
MOTU 1296
MOTU 2408 mkII
Various synths, including Kurzweil 2600
Digital Performer 4.52
MOTU Clockworks 1.51
MOTU PCI Audio Console 1.30
MOTU Firewire driver 2.41
MOTU MIDI Driver 1.2.7
Waves Platinum Bundle
WaveShellMAS4.2.3_X

I don't know whether my system should give you hope or if it's just a disaster waiting to happen, but so far I've had no problems. I'm assuming this will continue, since I have no intention of altering my system until Tiger.

Shooshie

[midiot]

Fair Warning!!!
Having the same problem also with midilite LAN Box-LC DMX lighting let me tell you scanners do not like stuck notes I am worried about breaking mirrors. (This is the first time I wanted safety glasses to program). My whole show is programmed and this is not usable at all for live performance. My 7600/132 is more stable on DP 3.11 with a handicapped USB MTP-AV using USB to serial adaptor, and I have tried the old trusty serial MTP AV and both have flawless timing with either on OS9. (Small Rant) All I want is the stability that MOTU has provided well, before Performer was ••œDigital••Â

[Resonant Alien]

I've lost track of this thread, so forgive me if I am repeating a theory that has already been tossed out, but....

I read either in this thread or in another one that someone narrowed this problem down to the Mackie HUI USB driver in the MOTU Control Surfaces folder. He said when he removed the Mackie HUI driver, everything was fine, but when he put it back, MIDI was wack again. Apparently is has to do with it being USB? I am using Mackie Control, which is MIDI interfaced, so I don't know much about HUI.

RA

[ACMMD]

I, too was having terrible stuck note problems with only a few MIDI tracks running. I read on this thread that turning off "generate MIDI beat clocks" worked. It does!

Before turning this item off in the preferences menu, my MTPs were lighting up like Christmas trees. I'm sure the notes were sticking because there was just too much MIDI information going thru the interfaces. Now things seem to have calmed down, with only pertinent MIDI channels lighting up.

Glad this board is available. MOTU seems to be ambivolent to this issue.

[ACMMD]

Well, I spoke too soon. What seemed to be a fix was just a flash in the pan. MTPs look great, but the note are still sticking. I would love to just sit here and create music, but no, instead I will be a compuer tech. THHHHTTTTTT.

[vbassguy]

So........Has anyone heard from MOTU........?..........
EVER ?

[hardingray]

I'll try to hit all the replies in one go:

Shooshie: It might just be a bad MTP in my studio. I'm not going to blame DP4.52 yet. The 1.3 MIDI driver hasn't made things better or worse for me. If thing are working for you, very cool. Glad to see that a dual MTP network CAN work.

midiot: I remember those days well (though on the Opcode side of the fence). The heady days of the late 80s where MIDI was MIDI and audio was just a fleeting memory.

Resonant Alien: I've pulled my HUI drivers to no avail.

Edgar: That was me that suggested turning off the MIDI clock. It reduces the log jams, but I still get them every few minutes. Of course, with it off I lose sync with all my delays, arpeggiators, etc.

vbassguy et al: since I was able to have the same problem when I ran OS9 and DP3 yesterday, I'm not going to point the finger at MOTU's software. It seems like maybe my MTP-serial is not able to handle the load, or that the MTP-USB isn't playing nice with the network. Try the 1.3 MIDI driver, and pulling the HUI driver. These have worked for several people on this thread.

[toodamnhip]

I started this thread long ago..my MIDI has now been great. I have removed my mackie driver and done this and that, but I think it was driver 1.3 that helped
I did find the 1.3 driver helped.....

Now I want the beach ball from hell to go away when changing audio settings etc and x fades to work faster

<small>[ April 09, 2005, 01:05 AM: Message edited by: toodamnhip ]</small>

[Kevin Kliesch]

To directly answer the original question of this thread:

Yes.

MOTU's rep called me at home the other day to see how I was doing (!). He wanted to check in to let me know that MOTU is aware of the problem but is having a hard time reproducing the stuck note issue. Since they cannot get their machines to do this, they do not know when a fix will be forthcoming.

I almost offered my G5 to MOTU for testing, but since it's in use every day, I'd be out of a day job.

Although the end result is that those of us still experiencing the problem won't see a fix for a while, I was very pleased that MOTU took the time to call me directly. Customer service is definitely their forte.

[Digitalperformer88]

Hardin!
Yes I am still here also,
As to your last post, Maybe your drum track plays poorly on the older version because it was recorded poorly on the newer version.
Try recording a simple drum track again on the old version setup and then see how it plays back regarding your MIDI jam and stuck notes, then you will know if you should point a finger at the sotware or not.
Hope this doesnt sound confusing!
Good luck!

[hardingray]

Michael:
Got it. I'll give it a try tomorrow and post back my results.

Just for those following this thread: my latest attempt was to save the simple drum beat from DP4.52 as a DP3 file, open it in OS9 with DP3.1, and I still got stuck notes on devices attached to my networked MTP.

[ACMMD]

My frustration level is down a bit after turning off Generate MIDI beat clocks. I had a recurrance of the problem last Friday, but it was due to a new file that I had failed to set up with no beat clocks. No longer are the MTPS and other interfaces lighting up, and the stuck note problem seems to have subsided. I think this is a problem with networked MIDI interfaces that are overloaded. I seldom use delays or arpeggiators, so that is not an issue. I empathize with those who need these features.

[hardingray]

I'm still having the same problems with DP3.1. I recreated (from scratch) the same simple beat. Initially it wasn't doing it until I quantized it (go figure). But then it started popping up all the time. I tried various devices and such. It really seems to happen only on devices connected to the second MTP.

My next step is to go out and but a new network cable to connect the two and see how that goes. However, it sounds like Edgar is also seeing weirdness with networked MTPs, so maybe there's no hope.

This wouldn't be my first experience with MTPs not doing all they say it can do. I've always had all sorts of problems with setups and programs in the MTP.

Hardin

[hardingray]

Got a new network (serial) cable. Same problems.

So, there are two things left to consider:

1) I have a bad MTP.

2) Networking two MTPs does not work.

Hardin