MOTUnation.com

marcuswitt wrote:what a volume surge are you talking about? i am just asking cuz i have never seen a problem like that in DP...

i am sure that if the MOTU R&D guys knew about it then it will be fixed in DP6.

Hope! Because it happens too often.

It's probably too much to hope for, but for me it would be very helpful if DP6 provided the ability to create user-assigned keyboard shortcuts to access the audio plug-ins in the Audio menu. I use several of them regularly - Trim in particular - and I find that the need to navigate my way through to the plug every time I need to use it hampers workflow and impedes concentration. But maybe that's just me.

Cheers,

Geoff

chamelion wrote:It's probably too much to hope for, but for me it would be very helpful if DP6 provided the ability to create user-assigned keyboard shortcuts to access the audio plug-ins in the Audio menu. I use several of them regularly - Trim in particular - and I find that the need to navigate my way through to the plug every time I need to use it hampers workflow and impedes concentration. But maybe that's just me.

Cheers,

Geoff

It's not only you. I know what you mean. What you ask for would be nice.

In the mean time, and you probably know this already, when I need to add a plug in to a track (and it's already been assigned to another track elsewhere), I just copy it directly from that other channel's insert (I'm not in front of DP now, but I think the shortcut is cmd-opt-drag). The settings get also copied, so you probably will want to re-tweak, but you'd have to do this anyway if you opened it from the menu.

Also, now that we're talking about plug-ins, it would be nice if there was some kind of button on them all that by pressing it, it would make the plug-in float over other DP windows... kind of like PT. This could be a toggle button, so changing the floating status would just be a click away...

Don't recall this coming up, but has there been any news about MIDI file names having been improved so that things like Cherry Picker don't have to be used?

I'm also wondering if the track list behavior isn't more sensible now-- it tends to jump to its topmost position requiring lots of scrolling on large projects.

Also, the track list in QuickScribe allows for no tracks to be selected. But the GE insists upon having at least one MIDI always selected at all times. Add to this the list defaulting to the top, and this gets unwieldy quickly.

The nice thing about Track Folders is that clicking on and off the folders in a track list selects or deselects all tracks in that folder. This is makes it easy to quickly start with a clean slate, but it also forces one to use track folders when they may not otherwise be necessary.

I know-- we won't know until it gets here, but it would be nice to be rid of the old tediae.

spirit wrote:MOTU has an unfortunate policy regarding bug fixes. Probably they think that if they acknowledge bugs and some of their competitors don't, that they will lose customers.

I used to be release manager / primary tech support guy for Tempo II (what they copied to create QuicKeys). It was very popular with musicians to do studio automation back in the day (late 80s) - Herbie Hancock an Chris Yavelow (MIDI Bible Author) were users.

We documented all of the commonly encountered bugs in a README file along with a list of workarounds we (or our customers) had figured out. A competitor began to use this as a bullet list for why their product was superior. Their product had plenty of issues too, but they didn't publish theirs.

So I can't really blame MOTU for their policy.

SixStringGeek wrote:

spirit wrote:MOTU has an unfortunate policy regarding bug fixes. Probably they think that if they acknowledge bugs and some of their competitors don't, that they will lose customers.

I used to be release manager / primary tech support guy for Tempo II (what they copied to create QuicKeys). It was very popular with musicians to do studio automation back in the day (late 80s) - Herbie Hancock an Chris Yavelow (MIDI Bible Author) were users.

We documented all of the commonly encountered bugs in a README file along with a list of workarounds we (or our customers) had figured out. A competitor began to use this as a bullet list for why their product was superior. Their product had plenty of issues too, but they didn't publish theirs.

So I can't really blame MOTU for their policy.

Hey, I used Tempo II before I used QuicKeys! I do remember it had some issues, but now I can't remember much about it. Didn't it change names at some point? Anyway, my brother used QK, so I started using it, instead. At some point there was no other choice, so QK it was, from then on.

Shooshie

Shooshie wrote:Hey, I used Tempo II before I used QuicKeys! I do remember it had some issues, but now I can't remember much about it. Didn't it change names at some point?

My apologies. It got a plugin system and became Tempo II Plus. The plugins were really clever, but weird. For instance, you could take a little snapshot of a chunk of screen, then set up a branch based on whether that chunk of screen matched your picture. Useful for waiting for a button to be enabled or progress indicator to complete.

Sadly, it died from mismanagement (like most nifty bits of software). Funny thing is QuicKeys is a direct clone - Don Brown - chief programmer at CE - took Affinity's president to lunch, filled his praise with how cool Tempo was, picked his brain about how it worked, then went off and wrote QK. Idiot president lapped up the flattery and gave away the IP.

It was cool in its time though and I loved hearing the crazy stuff users did with it.