Suggestions for next DP update

[MIDI Life Crisis]

It is an assumption on the poster's part that iLok or other protection schemes will eliminate the printed manual. The manual is not the copy protection scheme, the key code along with the original disk in the optical drive is. Clearly, that is not working, but I do think a more robust protection scheme should be in place.

Pirates and thieves SUCK! They are among the lowest form of scum on the earth. That is a fact.

We see them here at their anual [sc] meeting...

[erikjamesmusic]

+1000 for "MIDI Learn" or "Assign MIDI Controller". This corresponds to a right-click menu, etc.

-tab to transient
-"normalize" audio effect

[kassonica]

+1000 for "MIDI Learn" or "Assign MIDI Controller". This corresponds to a right-click menu, etc.

-tab to transient
-"normalize" audio effect

Err Normalize is already there, just not in real time, but off line.

[tonwurm]

- MIDI regions (á la logic, protools, nuendo, cubase, sonar, reaper...)

- elastic audio

- faster screen redraw

[James Steele]

Anyone have a list of the shortcut commands? Steele?
Also. NO ILOK EVER!

Huh? No.

I LIKE ILOK!!!

[Phil O]

I think it's reasonable to assume that the folks who make decisions at MOTU are not complete idiots, yes. I'm sure there have been discussions (perhaps even heated debates) over what's in the best interest for MOTU regarding copy protection. My guess would be that it comes down to bottom lines - "what are we losing to piracy vs what does copy protection cost us." I don't know what iLok costs, but it can't be cheap. iLok ain't making all their money off hardware. So when MOTU sees that their losses due to theft exceed their costs for copy protection, that's when they'll switch protection schemes. I'm just sayin.

Personally, I consider copy protection a necessary evil (with the emphasis on evil). I agree that pirates are the scum of the earth, and it's all their fault. If we need to go to iLok then so be it, but I won't like it.

My suggestion for next DP: Easy way to calibrate/compensate outboard gear latency.

Phil

[frankymax]

My suggestion for next DP: Easy way to calibrate/compensate outboard gear latency.

Phil

Yes- that's a great idea!! Plus, how about a paragragh in the manual on Buffy and what it does. Last I checked it's the plug-in without any info!

[KEVORKIAN]

My suggestion for next DP: Easy way to calibrate/compensate outboard gear latency.

Phil

Yes- that's a great idea!! Plus, how about a paragragh in the manual on Buffy and what it does. Last I checked it's the plug-in without any info!

On of my hopes is for an External Instrument plugin (with automatic delay compensation) that can be used with Rewire instruments as well as External hardware via inputs/outputs. Many other DAWs have such a plugin at this point and a similar one for DP would be very welcome!

[Phil O]

Plus, how about a paragragh in the manual on Buffy and what it does. Last I checked it's the plug-in without any info!

From and old thread:

Maybe this feature can join the ranks of the similarly-undocumented "Buffy" plug-in.

OK. So let me tell you about Buffy. Way back in the olden days there was this device called the ADAT. DP touted sample accurate ADAT transfers with the MOTU 828 (the 828 has an ADAT sync connector). I was finding that from time to time the transfers were off a bit. Well, not quite a bit. No, more like off by exactly the number of samples as the buffer setting. I called Motu Tech support. At the time there was this jerk working there that didn't know jack (luckily he's gone now). Anyway, I called tech support at Sweetwater where I bought the 828. They put me in touch with an engineer at MOTU who actually listened to me. Much time was spent experimenting and reporting the results. Well, to make a long story short, the next update to DP included a plug-in called Buffy. Yep, you have me to thank for that one.

Phil

[frankymax]

Thanks for that info Phil- now if MOTU can just incorporate that into the manual!

[Phil O]

Thanks for that info Phil- now if MOTU can just incorporate that into the manual!

Yeah, the paragraph could start out, "So, there once was this jerk in tech support."

[kassonica]

Yeah, the paragraph could start out, "So, there once was this jerk in tech support."

Please tell me your here all night

[Frodo]

Maybe I'm being too picky, but.... what the heck.

I love Clippings. It would be great if there were a way to "View Clipping Contents". One thing that hangs me from time to time is not being able to import a clipping because I have no 100% accurate reference to the contents of those clippings.

For those of you who use them, you know that one must have a specific number of active tracks of a specific type and in a specific order to match the source clipping before it will import properly.

When the source template is ordered differently from the destination template or project, the Clipping cannot be imported--- unless:

1. One knows the specific track type and specific track order. I have to write this stuff down by hand or take a screen shot so that I can create a folder with the right track types in the right order, then move the individual tracks into place within the new project one track at a time. Once done, I then delete the original "temporary" tracks.

2. One creates individual clippings for each track and imports them individually.

Chunks? Similar issue on this end.

Having a View Clippings Contents option would save the step from having to open the clipping source project (a day or more later) or having to use a screen grab to the same effect.... and not all clippings are comprised of all the tracks in a source sequence.

[Phil O]

Agreed, Mr. Frodo. I've had the same experience with clippings. "View Contents" would be a great feature!

Phil

[FMiguelez]

1. One knows the specific track type and specific track order. I have to write this stuff down by hand or take a screen shot so that I can create a folder with the right track types in the right order, then move the individual tracks into place within the new project one track at a time. Once done, I then delete the original "temporary" tracks.

2. One creates individual clippings for each track and imports them individually.

Chunks? Similar issue on this end.

I would like to have a View Clipping Contents command too. There are so many things MOTU could do to overhaul these little DP wonders which are fantastic!

Frodo, I take it you are talking about Clippings whose contents are bits and pieces of MIDI/audio WITHOUT the actual track, and or plug-in clippings, am I correct?

If I may, I'd like to add a number to your workaround list:

3. One creates the clippings with the source tracks included (whatever they are), so when you import the clipping, you don't need to worry about the type of track things belong to. Just drag and drop and play, and everything will look the exact same way like when they were created (the source)

While we are at it, clippings should also preserve the folder structures. As of now, you just get the tracks and contents, but they forget/ignore the folder structures (if they were created like that).