MOTUnation.com

Great day for DP.

mikehalloran wrote: ↑Wed Apr 20, 2022 5:05 pm There are probably hundreds of posts of this subject over the years. It's an issue.

From DP X to DP X+1, yes, almost always a problem. But has it normally been a problem going from DP X.n to DP X.n+1?

hi how do you merge the MIDI track with the virtual instrument track having automation , without loosing the automation data, it seems that copy paste erase the data automation , is there a way to merge both tracks ?

thanks
Cheers!

gman wrote: ↑Thu Apr 21, 2022 1:13 am... it seems that copy paste erase the data automation , is there a way to merge both tracks ?

thanks
Cheers!

Could this be the answer for you?

• Merging tracks by channel will now move data to the instrument track if it's part of the selection.

gman wrote: ↑Thu Apr 21, 2022 1:13 am hi how do you merge the MIDI track with the virtual instrument track having automation , without loosing the automation data, it seems that copy paste erase the data automation , is there a way to merge both tracks ?

thanks
Cheers!

they don't exist on the same edit lane, just like how Soundbites, Pitch, Clips etc. for an audio track don't live in the same lane. In the Sequence window you can open up lanes of MIDI and track automation on the same instrument track.

"Allow "pick a track" dialogs like the one associated with the “Track Record Enable” command (control-shift-R) to select tracks above 99 with numeric entry."

Does anyone know what this means?

Seeing so many improvements/fixes to QuickScribe has gotten my hopes up that the stuck RESPELL tool might have gotten some love. No mention of it though-- will check it.

Also nice to see lots of crash prevention items listed-- hoping that means more stable performance in my humble little world.

stubbsonic wrote: ↑Thu Apr 21, 2022 8:48 am Seeing so many improvements/fixes to QuickScribe has gotten my hopes up that the stuck RESPELL tool might have gotten some love. No mention of it though-- will check it.

Also nice to see lots of crash prevention items listed-- hoping that means more stable performance in my humble little world.

I've been working all AM and this update has really been excellent.

It asked me something about updating VI's or something like that when I first opened a project and I hit yes, and whatever it did did not cause any problems.

Everything seems much snappier and transparent.

Noticeably!

I think I may have to rebuild some templates in order to get around some of the Legacy MIDI track issues I'm having should I decide to use them (I could do without, but it would be nice). Not looking forward to that.

crashed for me within first few minutes of using it. Will look forward to a minor update. I welcome the new instrument track improvement....which some people have bizzarly argued against having for I don't know how many years. hey...it didn't ruin DP did it!?!?! Well when using V-Racks its a moot point anyway, but it is nice sometimes to quickly just create an instrument track and start playing it. I think a welcome improvement, but in truth...most DP power users probably won't use it that much either...so there is that.

They only partially fixed the articulation Map feature I had been asking them about...channelizing of MIDI events... I have created another tech note in hopes they will get there all the way...

dewdman42 wrote: ↑Thu Apr 21, 2022 10:14 am I welcome the new instrument track improvement....which some people have bizzarly argued against having for I don't know how many years. hey...it didn't ruin DP did it!?!?!

Well, to be fair, all us "nay-sayers" were suggesting was to preserve the current flexibility. So both parties got what they wanted-- 1. the ability to have 1-to-1 MIDI to VI, and 2. Preserve current ability to route multiple MIDI tracks to multiple VIs, as one always could.

bayswater wrote: ↑Wed Apr 20, 2022 9:57 pm

mikehalloran wrote: ↑Wed Apr 20, 2022 5:05 pm There are probably hundreds of posts of this subject over the years. It's an issue.

From DP X to DP X+1, yes, almost always a problem. But has it normally been a problem going from DP X.n to DP X.n+1?

From my own experience: Absolutely can be an issue. No reason to believe that it will.

My two ventures into DP Hell were with 7.12 to 7.24. Reinstalling 7.12, my files opened; 7.24, DP crashed and didn't even leave a trace report. MOTU told me my files were corrupted but couldn't explain why/how. I eventually figured out that it only affected files that had been created on my Beige G3 and G5 and that there were Permissions issues. Took a couple weeks to manually restore a bunch. Moving the files to a G4, zipping them and moving back to my 2010 iMac and unzipping, resolved the rest.

The other was DP 9.51 to DP 9.52. That was the change that caused me to discover APFS Snapshots to quickly restore to 9.51 without purging and reinstalling. Once I discovered that the culprit was a set of corrupted AIFF-C files recorded on a CD recorder and batch converted them to .wav, only then was it safe for me to reinstall 9.52.

Yesterday, I installed DP 11.1. I did not let it convert my MIDI tracks. I did this Sunday's mix and all went well. I then fired up 11.04 and loaded one of my Easter tracks. Audio and MIDI played fine but SampleTank Audio didn't load. Although I knew this was an easy fix, I reinstalled 11.04 and everything played back as it should.

As I have written previously: The last installer you run overwrites files in the shared resources. Every time, no exceptions. Whether or not this affects you is not something I can answer but there are so many changes between 11.04 and 11.1, you need to remember this if something doesn't behave.

These are not the only shared folders on the Mac.
Macintosh HD/Library/Application Support/MOTU/Digital Performer
Macintosh HD/Library/Audio/Plug-Ins/MOTU Control Surface

In addition, you have these Preferences in the (user name)/Library
com.motu.DigitalPerformer (folder)
com.motu.DigitalPerformer.plist (file)
com.motu.MotuAudioSystem (folder)

With DP 11 and Monterey, this doc is no longer accurate.
https://motu.com/techsupport/technotes/ ... 20suffice.

I use real-time MIDI processing. Always have, always will. No MIDI on instrument tracks for me

Deleting my converted Legacy tracks and recreating them seem to do the trick. Acts like it's supposed to, and eliminates crashing. I'm not going to do this with ALL my templates. No more converting Legacy tracks for me for a while.

mikehalloran wrote: ↑Thu Apr 21, 2022 12:11 pm

bayswater wrote: ↑Wed Apr 20, 2022 9:57 pm

mikehalloran wrote: ↑Wed Apr 20, 2022 5:05 pm There are probably hundreds of posts of this subject over the years. It's an issue.

From DP X to DP X+1, yes, almost always a problem. But has it normally been a problem going from DP X.n to DP X.n+1?

As I have written previously: The last installer you run overwrites files in the shared resources. Every time, no exceptions. Whether or not this affects you is not something I can answer but there are so many changes between 11.04 and 11.1, you need to remember this if something doesn't behave.

This is good info, and good to keep in mind. My original reminder to rename the DP app was mostly to remind people that installing DP11.1 will overwrite the previous version of the app unless it's given a different name. I think MOTU has always made the effort, when possible, to make things easily backwards compatible, but as Mike points out YMMV.