MOTUnation.com

My first orchestral job on the new dp6.01. Have approx 64 MIDI tracks open and get sudden volume spikes on all external and internal instruments. It doesnt happen on a small pop tune, just this large track count. I use cumix and dp6.01. I have no audio tracks going and only stylus open. I use cumix and 2 2408's and 1 hd192..Doesnt matter what my buffer is set to as well. My computer is an 8 core with 10gigs of ram...Anyone else have this issue????

Thanks

Ugh-- I hope that this isn't the old volume surge or MIDI blurt issue rearing its ugly head again! I was really hoping this had been fixed.

This topic has a longish history, unfortunately. There were lots of threads (too many to list here), but I remember that some go back to DP 5.0 with at least one report of the symptom earlier than that. It has been one quirk that has flummoxed a lot of people who have had the problem.

http://www.motunation.com/forum/viewtop ... =1&t=30846

http://www.motunation.com/forum/viewtop ... =1&t=23964

http://www.motunation.com/forum/viewtop ... =1&t=21367

Yup, I've gotten these volume spikes in 6.01 as well - it's kind of something I've gotten used to from 5.13 unfortunately, and when it came up in 6.01, I just shrugged my shoulders and kept working. I'm thinking to send an email to MOTU when I have a big MIDI project again and this happens.

I've heard MOTU has said they can 't reproduce this problem, but I'm thinking it has to do with AU instruments, and lots of VIs running. Don't know if they test with this kind of configuration .

jlaudon wrote: I've heard MOTU has said they can reproduce this problem,

jlaudon wrote:... but I'm thinking it has to do with AU instruments, and lots of VIs running. Don't know if they test with this kind of configuration .

I'll agree with you on the AU Instruments part of it, but I just saw it happen with one VI running and no fx.

Man. MOTU can reproduce the problem? Wow. That's a MAJOR turn of events that simply had to happen if a solution is ever to be found.

Just to be clear, did you hear that MOTU CAN or CAN NOT reproduce this problem? I somehow got the feeling through your wording in there that maybe you left off the 't for the word can't. Not being cynical; just really wondering whether you meant it the other way, or if MOTU really HAS been able to reproduce this problem? I'd love to know that they're working on it. That's one reason I've avoided any large-scale projects lately. (and inertia is another reason )

Shooshie

Whoops! Oops! Sorry for the false hope - should have been 'can't' - that's what happens when I'm holding a baby in one hand and typing with the other .

Leave it to the 2 most alert (and hopeful) guys on this board (James is too, but I see him as more of a guitar god than man ) to notice my post. Granted this is an embarrassing problem when clients are around, I feel like I have to apologise for MOTU ("oh, this is a brand new upgrade, an update should take care of it really soon...").

Oh NO! They MUST do something about this.

jlaudon wrote: Whoops! Oops! Sorry for the false hope - should have been 'can't' - that's what happens when I'm holding a baby in one hand and typing with the other .

Holding the baby-- that is ultra understandable.

Still-- for a moment it was a very nice thought to think a fix might actually be in progress!

What do mean sudden volume change? Say, while your listening to a violin patch, triggered from MIDI note on data on a track, then all of a sudden it's volume jumps? cc#7, bam?

Yes that's right. And if the mixing window is open you'll also se the faders leap.

dogBoy wrote:What do mean sudden volume change? Say, while your listening to a violin patch, triggered from MIDI note on data on a track, then all of a sudden it's volume jumps? cc#7, bam?

You might want to check the thread links in the post above (second one down) for more details, but during playback there will be an increase in volume for a few seconds and then it goes back to normal.

1. It happens with event chasing on or off
2. It has nothing to do with the numbers of VIs loaded because it happens on large and small projects
3. It happens with or without automation
4. It's not hardware related where the same hardware is used with other DAWs that have not shown the symptom (at least on my system)
5. To the extent that it's not hardware related, it's not likely that it's driver related for the same reasons cited in #4
6. It's a symptom that has been around at least since DP5
7. It's not format specific because it happens when using even one MAS instrument or one AU instrument
8. It happens on both PPC and Intel
7. It happens in both Tiger and Leopard
9. Because I have 4 or more GB of RAM (8GB, actually), it's not a physical memory issue

Giving DP some benefit of the doubt, it could be a defect with Virtual Memory-- but this is thwarted by results seen in #3 and #4

This is also a symptom that is a little different than the famous MIDI bursts (aka: The DP Sneeze) where MIDI note on/off data gets clogged somewhere and then that data purges itself in a single burst at once (when hitting the spacebar) regardless of MIDI start/stop locations. It is "believed" that this particular problem was remedied with DP 6.01 only because there have been no recent reports lately about it.

These symptoms are not (in my experience) displayed on the meters or faders.

--and does it happen whether or not your controller keyboard is off.

I seem to have solved it at least for my VI's by inserting a controller #7 message after every patch change. If the instrument/patch is selected for the first time, or the cc#7 value is different from what it's supposed to be in that instrument/patch, it doesn't change automatically when the patch is selected. This I think is just the way it works. Audio tracks on the other hand...

I noticed the volume change when I recently got a MAC PRo & DP6, DP6.01. I have no interface and only a USB MIDI controller, so running only VI's.
Once I inserted CC#7 in the beginning of a MIDI>VI, the volume surges stopped. Also volume automation in the mixing window enabled "WITHOUT" any continuous data in the MIDI track helped the surges.


On my G4-DP6.0 with a serial MIDI express running outboard MIDI controllers and modules and VI's , I have no volume surge. Whether I have a CC#7 or not.

T

dogBoy wrote:--and does it happen whether or not your controller keyboard is off.

Yes, and with one shoe off or one shoe on. Very strange!


Shoosh