MOTUnation.com

This might work for you. I haven't tested it and would probably only change existing data and ramps. If you wanted to insert your own ramps you'd need to incorporate using clippings with something like Keyboard Maestro. In any case, deadlines looming. 1. Open DP and create a Blank Project 2. Open th...

I hope I'm understanding you correctly, but I think this would be easy enough to achieve using snapshot automation using the 'From Counter to next change (ramp)' option. Set your wiper to the initial point and set your eq as desired then take a snapshot of the plugin params. Now move wiper to the en...

Command-D should do the trick

Here's a thought I know this might sound a little daft. Before you start doing the process of doing your automation you could create volume control points on the grid for the full duration of play then delete the unwanted control points as required. Square wave automation shapes do conform to the gr...

You could draw straight lines close to the locations you want disregarding the inaccuracies and afterwards select quantise from the region menu, click on the what to quantise dropdown and select controllers.

Just a thought

Greg

Hi Mike MOTU provide an OSC Programming Guide which outlines the dictionary of available commands accessible to OSC. However, it doesn't really go far enough in terms of examples. If I could be sure that the incoming / outgoing port was the same for OSC communication then I would continue to hack aw...

To the great cognoscenti on this board I've been trying to design an OSC control surface for DP and though I can send most commands to DP over either UDP or TCP, I can't seem to receive a response from DP with any 'Get' commands over TCP. At the moment I'm trying a very simple set of commands from T...

That's the answer. By far the simplest!

I'm not sure that you can enable any other automation types for a MIDI track other than Volume, Pan and Track Mute. Snapshots work really well for audio and allow multiple automation types to be written in the desired manner, but I don't think MIDI tracks are the same.

I can't see an easy solution for this, but this might be a little less laborious than your current clicking solution if you have a significant number of MIDI tracks. 1. Create three individual saved searches in the search window for CC1, CC7 & CC11 where the output 'action' of the search is 'Dis...

I imagine someone else has contributed this answer somewhere already by now, but here's mine for what it's worth. In a nutshell, use the temporary group command to apply the same actions to whatever number of tracks are in view. For example, say you have 3 MIDI tracks triggering 3 Violin patches on ...