Digital Performer 11.32

[James Steele]

As mentioned, DP's Hardware Insert plugin "forgets" the latency offset when a project is closed and then re-opened. You can open the plugin, and the number you entered is still there, but it's not being observed. You have to click in the box and hit "Enter" to get DP to recognize it again. And even then, when you close the project, it will be forgotten.

Sorry to hear this is still not fixed in DP 11. All I can add is that I ran across this MOTU video at least 6 years ago and tried the steps shown in the video and immediately ran into the exact bug you describe. You can save your settings (as shown in the video), but then they are lost when you try to recall them:

https://www.youtube.com/watch?v=3Lpu62ko3_A

I'll check out your video now. Before I do, I'll mention that from my video you can see that I think I was incorrect in my initial assessment. The Hardware Insert Plugin may very likely be retaining the sample offset after a project is closed and reopened, but there's a very weird behavior where it appears that the latency of plugins on the Master Fader (possibly just the plugin on the first insert) is somehow affecting the hardware insert. And what is happening is the audio track with the hardware insert on in plays back LATE!!!

Come to think of it, when you put plugins on a Master Fader, it seems logical that all the tracks going to the same output controlled by that Master Fader should be shifted EARLIER by the number of samples equal to the latency of the plugins on the Master Fader track. My lead vocal track with the Hardware Insert plug was playing audibly LATE. ONE THEORY: All tracks EXCEPT the track (or tracks) with a Hardware Insert Plugin on it are being shifted earlier. That track is NOT, thus it plays back late until you open the plugin and re-enter the offset and then somehow that actually reapplies the latency offset for the plugins on the Master Fader.

[monkey man]

It's like we're gathered-'round the talisman from which new versions of DP spring forth.

[MIDI Life Crisis]

You might even want to try DP11.32

My music software (DP, Finale) are always up to date, and pretty much always running.

[HCMarkus]

You might even want to try DP11.32

My music software (DP, Finale) are always up to date, and pretty much always running.

I should have know better than to think otherwise.

[hammerman]

Just a heads up, I upgraded from Waves 14 to 15 today and my Ren Comp redraw issue is still there so it's definitely a DP issue. That said, I run that plug in realtime and everything is hunky dory.

[HCMarkus]

Just a heads up, I upgraded from Waves 14 to 15 today and my Ren Comp redraw issue is still there so it's definitely a DP issue. That said, I run that plug in realtime and everything is hunky dory.

Thanks for reminding me I can run a single plugin in real time. Until this issue is resolved, I'll do that.

BTW, I reported the problem to MOTU and to Waves. Work arounds are as you noted, running DP11.32 in "Live Mode" or reverting to DP11.31. Interestingly, I have a few Waves v13 still running and they do not seem to be impacted... they work fine in 11.32 Pre-Gen mode.

Audio is not impacted in any way, this is simply a GUI redraw issue.

[mhschmieder]

The issues and bugs listed on the front page are ones that are fairly critical at my end, though I didn't really expect them to be addressed, as I never saw anyone discuss them (though I may have noted some of them here).

Not sure how I missed this update. I could have sworn that I updated within the past month, but it might have been one of those times when a thunderstorm knocked out the power and I forgot what I was doing when power was restored.

[HCMarkus]

The issues and bugs listed on the front page are ones that are fairly critical at my end, though I didn't really expect them to be addressed, as I never saw anyone discuss them (though I may have noted some of them here).

In 11.32, I was happy to see fixes for two bothersome bugs I had reported. Editing is easier now.

[crduval]

Hi folks, just wondering if anyone else is experiencing stuck notes on VIs, when input monitoring is on: for me, it happens if you run the wiper backwards over MIDI notes, or sometimes as I am clicking and dragging MIDI notes to edit them, either in the sequence or MIDI editor view. It's annoying as heck. The stuck notes generally stop once you hit play, although I've had to remove and reinstall Falcon instances a couple times for stuck notes that would not stop. Hitting the panic button on my MIDI controller has no effect, MIDI monitor confirms there is no MIDI triggering these notes. I'm running Ventura on an M2 MacBook Air.

Any ideas? LMK, thanks!

Chris

[James Steele]

…although I've had to remove and reinstall Falcon instances a couple times for stuck notes that would not stop. Hitting the panic button on my MIDI controller has no effect…

I haven’t experienced this so far, but if I might make a suggestion: a quicker way to stop the stuck notes might be to temporarily disable the instrument track by clicking the blue enable button in the Track Overview window, and then click again to reenable it.

[crduval]

…although I've had to remove and reinstall Falcon instances a couple times for stuck notes that would not stop. Hitting the panic button on my MIDI controller has no effect…

I haven’t experienced this so far, but if I might make a suggestion: a quicker way to stop the stuck notes might be to temporarily disable the instrument track by clicking the blue enable button in the Track Overview window, and then click again to reenable it.

Good idea, thanks! BTW I meant re-instantiate Falcon, not re-install (freaking spell check)- but this would still be much faster.

[James Steele]

…although I've had to remove and reinstall Falcon instances a couple times for stuck notes that would not stop. Hitting the panic button on my MIDI controller has no effect…

I haven’t experienced this so far, but if I might make a suggestion: a quicker way to stop the stuck notes might be to temporarily disable the instrument track by clicking the blue enable button in the Track Overview window, and then click again to reenable it.

Good idea, thanks! BTW I meant re-instantiate Falcon, not re-install (freaking spell check)- but this would still be much faster.

Oh yes... I knew you meant re-instantiate! I did that, too, when I would get stuck notes until one day it dawned on me to disabe/re-enable the track.

[HCMarkus]

...temporarily disable the instrument track by clicking the blue enable button in the Track Overview window, and then click again to reenable it.

Works great if a plugin or VI ever starts acting up. Disable/Reenable. Very quick!

I've had to use it a bunch with MODO Bass2. Haven't had to do it since DP11.32 update; time will tell.

[James Steele]

I've had to use it a bunch with MODO Bass2. Haven't had to do it since DP11.32 update; time will tell.

Bro! Same here! MODOBASS 2 is just a nightmare when it comes to stuck notes. It's especially bad in Pro Tools for some reason. I don't use Pro Tools much at all but I have quick test project I made when I first installed Pro Tools and it uses MODOBASS 2 and it's ALWAYS getting stuck.

Now that I'm getting my studio together, I should stop being lazy and restring one of my REAL basses and try using that. I'm not that great a bass player, so I have to use a pick, but I could see me getting much better results than what I (personally) can elicit from a VI.

[James Steele]

Works great if a plugin or VI ever starts acting up. Disable/Reenable. Very quick!

You know, I need to check, but off the top of my head I'm thinking that Digital Performer might be one of the few DAWs that let you manually enable and disable a track, effectively eliminating its CPU load?