MOTUnation.com

Well...Right now the only thing I can do is not to use the "Wait for note"...which I've been using on a regular basis since Performer V1...and even then...the notes get stuck quite frequently...I tried switching to Logic or Cubase...and I didn't like them at all...DP has been my sequencer for almost 20 years...I want to stick to what I'm used to...

If you're going to this much trouble, I'm surprised you haven't tried backing up your MacBook, wiping the drive clean, and starting from scratch, installing the latest versions of everything, and leaving off anything that you don't use.

I'm confident that DP is not the problem here. There are thousands of people using it without the problems you are describing, including myself. It has always been my experience that when there are problems with an installation of software that is known to be good, the problem is in your system.

By starting with a fresh slate, you eliminate whatever is deep inside causing problems. I have done this many times over the years, enough that I was able to be confident when taking DP out on stage in front of thousands of people holding expensive tickets. It never blinked. 100% record of flawless performances.

This is still possible. At this point, complaining is merely delaying. If you cannot eliminate the problem, it's time to start from scratch. Don't install little apps that aren't essential to DP's performance. First get DP running flawlessly. Then you can install your little apps and utilities one-by-one and see if they pass the test. If DP still runs fine, then you may keep those apps aboard.

I assure you, unless your computer or other hardware is flawed, you can run a flawless system with DP. Start with DP alone, then add things gradually. When you finally add an app, a plugin, or a VI which starts the problems, then you have identified it.

Suppose you could get to work on that? There's nothing more we can do.

There IS one other thing which I do not know if you have tried:
• Open a new file.
• Using the LOAD command [File/Load] load the chunks (sequences) that you are having trouble with, each into a new file.
• Rebuild your audio and MIDI bundles.
• Reconfigure your VI's

If that doesn't fix anything, then you need to do what I said: start from scratch. The reason I'm pretty sure that the problem lies either in your files or on your system is that DP 7.0 - 7.1 work extremely well on nearly everyone's system who reports on it here. It's not without flaws, but certainly not on the level you describe.

Time to fix it! You'll be glad that you did.

Shooshie

Hi Shooshie...In my previous post I stated that I did start from scratch...I bought my Macbook in January of this year...and started fresh...I also wiped my HD and did a clean install of Snow Leopard and installed only needed programs and turned off spotlight, etc. that I didn't use...and stll didn't work. So I even went on to replace the internal HD with a 7200rpm drive and started all over again...and still the problem exists...Also, everytime I'm testing I'm using a "new file"...At this point I have tried everything that I can do within my knowledge...I'm opened to try anything at this point...

Sorry, I hadn't reviewed the whole thread, and I'd forgotten your earlier posts. Well, I'm out of ideas. I don't know why DP won't work on your system. But it works elsewhere. That's a heck of a predicament, isn't it?

Are you actually using Mach V.2? It has not been updated for Snow Leopard. It may not be fully functioning. I have not had M5.2 open in quite some time now. I don't remember how it plays in Snow Leopard.

Have you tried clearing out the caches in OSX? You might try it for the heck of it. Do a Safe-Boot: hold down the shift key while rebooting. Once it finishes booting to the Finder, and stops accessing the drive, then reboot normally. Also, have you repaired permissions?

What about turning off half of your plugins? Set up a plugin set for testing, then turn half of them off. If the problem persists, turn all of them off. If the problem goes away, then add them back a few at a time until you get to one that causes things to go back the way they were.

Somehow I doubt that any of this will have any effect, since you've reinstalled OSX and DP. When you reinstalled, did you start from a blank disk? Did you do installations from the original DVDs, or did you copy things over from your backup?

I wish I knew the answer, but do check out my questions. Maybe you've overlooked one or two things.

Shooshie

I just read through this thread, and am wondering if the problem may be with your MIDI interface or its settings rather than the Macbook. Have you explored this possibility at all?

This is not the type of problem that should persist after going through the steps that you have taken, unless it is external to your Mac. Maybe you could try a different interface, or go through the interface set-up from scratch.

I don't recall exactly, but I think you said you had both a Timepiece AV and a Traveler - if the Timepiece has MIDI I/O, maybe you could eliminate the Traveler and see if the problem persists, and vice versa? Then you could determine if the device is defective or just set up incorrectly. There may also be updated drivers for these devices available from MOTU.

Just a thought - hope this helps...

I updated all the drivers, firmware, etc. I tried eliminating MTP AV and just using the MIDI on the Traveler mk3. Vice versa...and it's the same. If you can, please see if you can produce the bug using the steps in my previous post. The problem exists when the "wait for note" function is ON while in Audio mode...

A note for Swooshie- some great ideas, but I have also started from scratch and ended up with the same issues. I have gone thru 2 computers, various OS systems, DP versions, and even took my MTPAV out and used a MidiMan unit for a while. I still get hanging notes. Had them from the first day I went from OS9 to OSX. But when I went to a new computer I did not install just 1 thing at a time though. I was so sure it was the old computer I installed everything I needed, which looking back might have been stupid. So although I have started with a clean slate a few times I have not done a piece by piece install to try and apprehend the bandit.

But the idea of installing 1 thing at a time is a good one, so I might do a little subtractive analysis, taking things out one by one and seeing what happens. BTW- I have done that with my few remaining synth modules- taking them out of the picture to see what happens. No luck with that.

Who knows, maybe it is a combination of having a certain DP preference setting along with a certain VI, along with a certain external synth, along with a non-music app on the drive....

Bruce and Jacey714, can you eliminate the audio interface and use built-in audio? Will that fix anything?

In my case, I have gone from a MOTU 1224 to an 828MK11. The upgrade did not help anything. I know some folks have had major VI hang ups, but mine are mostly MIDI tracks. If I do a seq with only VIs and no MIDI synth tracks I almost never get hanging notes. Its only when I introduce 5080 track, or triton track that the hanging notes start popping up.

But it is worth it to run the little test of disabling the 828 and seeing what happens. At this point I would stand on 1 leg, sing the hokey pokey, and where women's clothing to get this thing finally figured out!

Jacey/Bruce:

If you use only internal VIs and do not use external MIDI devices, does this problem still exist?

And if you don't use 'wait for note', then there's no problem?

As Shooshie and I suggested in previous posts, try using built-in audio just for kicks.

Jacey-when MOTU replies to your tech link, please tell us what their suggestions were.

I feel crappy for you guys!
I'd go nuts if I was having the MIDI problems you describe.

I tried running DP in audio mode with the Traveler disconnected and still had problems...I did try just using VI's...and the notes didn't disappear...However, there was a bit of a weird behavior where the very beginning of the sample seemed cut off...as if the sample was playing ahead of the beat and got cut off...This happened when the "wait for note" was ON. As for external MIDI devices...It's skipping and flying notes all night long...

As mentioned in the previous posts...This problem exists when "wait for note" is ON while in Audio mode...

jacey714 wrote:As mentioned in the previous posts...This problem exists when "wait for note" is ON while in Audio mode...

It just doesn't happen on my system. I use "Wait" every day, hours at a time, as I record tracks in MIDI. Specifically, I nearly always use "Wait for note." I have never seen the problem you're describing. I hope you get it figured out.

Does this happen on a new install of DP when you start with a new file with nothing recorded in it?

Shooshie

Just curious what you have for these settings;

Smart Selections On or Off
Note Event Chasing On or Off
MIDI resolution setting

any other preference setting that you think could effect this condition.....

Smart Selections Off
Event Chasing On
MIDI resolution setting 480 ticks per beat
CC ramp resolution: 5 ticks

I'd have to open DP to check things like Prime Seconds and so on, but those kinds of settings may be a factor in jayce's problem. Can't rule anything out.

That does make me wonder what Jayce has set his buffer to, how many busses he's got set, how many tracks, what 3rd party plugins/VI's are loaded, and just all the settings.

Shooshie wrote:Smart Selections Off

OMG!! How can you be functioning with Smart Selections off!?!? Why would anyone try to function with Smart Selections off? All you have to do is press the command key to disable it temporarily in those rare cases where it is not useful.

I have to assume that seasoned veteran Shooshie must have some reason why he does not use this feature... but then I must question his sanity!