Pages Navigation Menu

Help and hints for MOTU Digital Performer

10 steps for basic DP Troubleshooting

Posted by on Oct 5, 2009 in troubleshooting | 0 comments

Whenever you experience weird behavior during DP use–for something that you know was working fine the day before–there are a few basic troubleshooting steps that I recommend before trying anything drastic. [I define something drastic as uninstalling/reinstalling DP, or re-installing OSX] Step 1: Save your project using ‘Save As’, then close DP. Restart DP and open up your Saved As project. Still the same problem? Step 2: Reboot the computer. It amazes me how often rebooting fixes things. [Like all my ilok VIs not being recognized yesterday, for example!] Still the same problem? Step 3: Create a new empty project, and try your problematic operation on fresh audio/midi data. A single track is all you need for this purpose. If the operation works fine on this new project, then something unfortunately got corrupted on your problematic project. If you...

Read More

How to find a key command-Quickly!

Posted by on Sep 24, 2009 in workflow | 0 comments

[DP7 Manual reference: Page 147] A thorough understanding and use of key commands [DP7’s Commands Window, Shift-L] is crucial to getting work done quickly in DP. Many commands are difficult to remember, so you will need to search for them. Let’s say you’re working in the Conductor Track, experimenting with tempo changes. You suspect that there must beĀ some keyboard commands relating to tempo operations, but you don’t have those memorized. Open up the Commands Window, and type ‘tempo’ in the search field. The first highlighted result is “Scale Tempos…” [from the Region Menu]. This doesn’t help. Now what? In order to see the next result of your search query, you have two options: 1) keep clicking the search button at the top right of the commands window, leaving your search term ‘tempo’ unchanged. 2) Hold down the Option key...

Read More

automating volume and pan on a midi VI track

Posted by on Sep 20, 2009 in midi editing, virtual instruments | 0 comments

In order to send volume and pan changes to your midi VI track, you need to send CC7 for volume and CC10 for pan. Sure, everyone knows that. But if you’re not careful in DP, you may notice that the track does NOT respond to the CC7 and CC10 data you have entered in the Midi Editor or Sequencer Editor window! What causes this? In DP midi tracks, the midi CC data for pan, volume and track mute is still referred to as ‘automation’ data, the same way that ‘automation’ classically refers to things like audio track volume/pan/send levels. And this is managed from the Mixing Board for the tracks involved. Let’s see how this works. In this simple example, I have a DP7 project with only 2 active tracks. One is the Instrument Track which has Kontakt 3.5...

Read More