Collecting Data In the Interest of Solving Problems

[dweiss]

••• MOTUFireWireAudio.kext: v. 1.2.5, created 4/28/05
••• MOTUPCIAudio.kext: v. 1.0.8, created 4/25/05
no Firewire driver installed

Hardware:

Express XT USB
PCI -424 /2408/2408MkII

Problems: Stuck notes on VIs. Unpredictable frequency. Sometimes none for days and then frequent.

Occasional quits

System 10.4.4 on a Dual 1.8

Apps
DP5
Waves Musician Bundle and Native Powerpack
Kontact 1.5
B4
Reaktor Session
Trilogy
Stylus RMX
Auto Tune
Ivory
Garritan Personal Orch
PSP Vintage Warmer and PSP42
UAD-1
MTRON

[muzishun]

Thanks for doing this, Shooshie...

SYSTEM #1:

MIDI Driver- 1.2.2 (hey, it wasn't broke!)
FW driver- n/a
PCI Audio- 1.0.8

Background Apps:

Clockworks- 1.51
CueMix- 1.41

SYSTEM:
10.3.9
Dual 2G (June 2004)
2.5 GB RAM

HARDWARE:
MTP-AV USB / Networked to second serial version
PCI 424, 2408mk3, 2408
Radikal SAC-2K USB Controller

APPS:
DP 4.5
VST Wrapper 4.1.3
Korg, Linplug, reFX, Spectrasonics, Steinberg Synths
Elemental Audio Plugs
Various free plugs and soft synths
Reason 3.0

===========================================

SYSTEM #2: (just finished an album project, so started new system on new partition)

MIDI Driver- 1.3.2
FW driver- n/a
PCI Audio- 1.0.9

Background Apps:

Clockworks- 1.51
CueMix- 1.4

SYSTEM:
10.4.5
Dual 2G (June 2004)
2.5 GB RAM

HARDWARE:
MTP-AV USB / Networked to second serial version
PCI 424, 2408mk3, 2408
Radikal SAC-2K USB Controller

APPS:
DP 5
VST Wrapper 4.1.3 (4.1.5 crashed DP)
Korg, Linplug, reFX, Spectrasonics, Steinberg Synths
Elemental Audio Plugs
Various free plugs and soft synths
Reason 3.0

[Shooshie]

SYSTEM #2: (just finished an album project, so started new system on new partition)

MIDI Driver- 1.3.2
FW driver- n/a
PCI Audio- 1.0.9

Muzishun, keep an eye out for stuck notes on this new partition's setup. MIDI Version 1.3.2 is the suspicious driver. If it goes that direction, and you want to try a newer but stable driver:


MOTU USB MIDI Driver version 1.3.1.sit



Shooshie

[Klaus]

SYSTEM #2: (just finished an album project, so started new system on new partition)

MIDI Driver- 1.3.2
FW driver- n/a
PCI Audio- 1.0.9

Muzishun, keep an eye out for stuck notes on this new partition's setup. MIDI Version 1.3.2 is the suspicious driver. If it goes that direction, and you want to try a newer but stable driver:


MOTU USB MIDI Driver version 1.3.1.sit



Shooshie

Keeping the thread up
you sure meant 'older' but stable driver...
not sure if it is the driver.
Best

Klaus

[matwell]

Not sure if it's the driver either. I have 1.3.2 and stuck MIDI notes are *never* a problem on my system.

[muzishun]

SYSTEM #2: (just finished an album project, so started new system on new partition)

MIDI Driver- 1.3.2
FW driver- n/a
PCI Audio- 1.0.9

Muzishun, keep an eye out for stuck notes on this new partition's setup. MIDI Version 1.3.2 is the suspicious driver. If it goes that direction, and you want to try a newer but stable driver:


MOTU USB MIDI Driver version 1.3.1.sit



Shooshie

I definitely have stuck notes on this system. Thanks to this thread, I will try v1.3.1. Thanks for the link.

[Shooshie]

you sure meant 'older' but stable driver...
not sure if it is the driver.
Best

Klaus

Yeah, I meant 'older.' Actually in his case, he has a very old driver on the other system. I was thinking "newer than that one." But you're right; 1.3.1 is an older driver.

Now, as regards your systems, Klaus:
Correct me if I'm wrong, but you've got driver 1.3.2 on one system, and 1.3.1 on the other. Is that right? I don't have a MIDI interface listed for either machine. What kind are you using?

Is one of those systems more stable than the other? Do you get stuck notes equally on both systems?

Shooshie

[Shooshie]

Not sure if it's the driver either. I have 1.3.2 and stuck MIDI notes are *never* a problem on my system.

That's probably going to be a key in solving the problem. Your system is a little different in that you use a Digi 002 FW audio interface. That makes me wonder if the problem could be a combination of driver issues, such as MOTU MIDI plus MOTU Audio hardware and drivers. You're also using a Quad, and I think there are only about two others reporting quad G5s. They both have stuck notes, though.

I still don't have all the information entered on everyone else, yet. When I do, I may see more patterns. But right now, the one pattern that does stand out is that almost all of the 1.3.2 MIDI drivers can be associated with stuck notes, while either none or maybe one of the 1.3.1 drivers has stuck note issues. Very clear relationship, but it would be nice to figure out why yours is different.

How much MIDI do you do? Is MIDI your primary or secondary work mode? Many people report that stuck notes get worse over time as they work. Do you work in MIDI for long stretches?

Shooshie

[Klaus]

you sure meant 'older' but stable driver...
not sure if it is the driver.
Best

Klaus

Yeah, I meant 'older.' Actually in his case, he has a very old driver on the other system. I was thinking "newer than that one." But you're right; 1.3.1 is an older driver.

Now, as regards your systems, Klaus:
Correct me if I'm wrong, but you've got driver 1.3.2 on one system, and 1.3.1 on the other. Is that right? I don't have a MIDI interface listed for either machine. What kind are you using?

Is one of those systems more stable than the other? Do you get stuck notes equally on both systems?

Shooshie

System with MIDI driver 1.3.2 : Mostly audio work, no MIDI, AM III ( SPdif ) with Digi coreaudio driver.
System with MIDI driver 1.3.1 : VI's only and Reason 2.5 running it's own MIDI tracks, just slaved to DP, no stuck notes at the moment.
896HD with 8 ADAT too,
MTPAV-USB retired at the moment

Best

Klaus

[matwell]

Not sure if it's the driver either. I have 1.3.2 and stuck MIDI notes are *never* a problem on my system.

That's probably going to be a key in solving the problem. Your system is a little different in that you use a Digi 002 FW audio interface. That makes me wonder if the problem could be a combination of driver issues, such as MOTU MIDI plus MOTU Audio hardware and drivers. You're also using a Quad, and I think there are only about two others reporting quad G5s. They both have stuck notes, though.

I still don't have all the information entered on everyone else, yet. When I do, I may see more patterns. But right now, the one pattern that does stand out is that almost all of the 1.3.2 MIDI drivers can be associated with stuck notes, while either none or maybe one of the 1.3.1 drivers has stuck note issues. Very clear relationship, but it would be nice to figure out why yours is different.

How much MIDI do you do? Is MIDI your primary or secondary work mode? Many people report that stuck notes get worse over time as they work. Do you work in MIDI for long stretches?

Shooshie

With DP, MIDI is 99% of what I do, except for printing my synth tracks as audio to transfer into Pro Tools. I work for hours and hours, with zero stuck notes. In the old days (DP v2.7, v3.x, v4.x) I was using mostly my rack of hardware synth modules, with two MIDI Express XT's. Also, using Sample Cell cards. *Never* had stuck notes. Now, I have switched over to mostly virtual instruments, with only 4 hardware synths that I rarely use. With DP 4.61 and now DP 5.0, I still never have stuck notes.

'tis a mystery...

[buzzsmith]

OS 10.3.7-DP 4.5

••• Motu MIDI Driver.kext: v. 1.2.2, created 10/7/03
••• MOTUFireWireAudio.kext: none
••• MOTUPCIAudio.kext: v. 1.0.6, created 1/14/05

no major bugs right now, but I'll fill out the questionnaire, as well.

=bz=

[excatcher]

Motu MIDI Driver.kext 1.3.1 created 4/12/05
MOTUFireWireAudio.kext 1.2.5 created 4/28/05
MOTUPCIAudio.kext 1.0.8 created 4/25/05

OS X 10.4.6
DP5
MOTU 2408 mk3
MOTU 24 I/O

Main bug: all existing audio often drops out whenever I record ANYTHING, be it audio or even MIDI data. I stop, record again, and it's fine.

[dweiss]

OK, I didn't want to believe it but weird things are going on in DP5.

I recorded two interlocking 2 bar piano parts which played back fine for about a half hour. All of a sudden the volume of the two parts starts rolling, louder, then softer at the same point every 2 bars. I examined the tracks and sure enough the velocities reflected what I was hearing. Very strange. There's the slightest chance of this being my error but it's hard to imagine how. The parts were just playing back the whole time and all other tracks are audio.


The other oddity is that after muting a part it will decide to play for a couple of seconds anyway from time to time. This I'm 100% sure of and it's happened in a couple of my sequences.

[MIDI Life Crisis]

OK, I didn't want to believe it but weird things are going on in DP5.

I recorded two interlocking 2 bar piano parts which played back fine for about a half hour. All of a sudden the volume of the two parts starts rolling, louder, then softer at the same point every 2 bars. I examined the tracks and sure enough the velocities reflected what I was hearing. Very strange. There's the slightest chance of this being my error but it's hard to imagine how. The parts were just playing back the whole time and all other tracks are audio.


The other oddity is that after muting a part it will decide to play for a couple of seconds anyway from time to time. This I'm 100% sure of and it's happened in a couple of my sequences.

This last thing I reported online (and to MOTU) last week. MOTU said it is not a bug because nobody else has reported it. Huh? See a thread called MIDI Leaks or something like that. You'll also find when you select a section and playback the selection (opt-space) tracks will leak out from other, unselected parts.

Also, DP 5 sending double notes (creating phase shifting) from time to time is also a bug. May be related to hung notes, which now only seem to appear after very long sessions (like 12 hours or more - I do a lot of those these days).

What else.. oh yeah, odd volumes... after probably 100+ hours in DP 5, these seem to have subsided. But every one in a while, I get a blast from some track that wants to be "louder than before." Once I edit it, it stays edited, but it still happens every once in a while.

Overall, working in a lrge orch score that is quite dense (think Mahler...) DP 5 seems to be working quite well. CPU spike reports are diabled, so I don't see those. But no performance problems on a G5 Dual 2.0. playing back full screen (19") QTime is accurate and rock solid timing wise.

Hardly doing any digital audio except bouncing to full frame QT movies and burning DVDs for the conductor, et al. All playback great on his system and the music sounds better than in my studio (he has more $$$ to spend on speakers )

[dweiss]

Thanks for the input, Crisis. Good to know that other(s) have the same issue. I'll forward the issue to MOTU.