DP9.02 Duplicate Take bug?

Discussion of Digital Performer use, optimization, tips and techniques on MacOS.

Moderator: James Steele

Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
Post Reply
User avatar
Tripi
Posts: 926
Joined: Mon Jun 06, 2005 10:01 pm
Primary DAW OS: MacOS
Location: LA
Contact:

DP9.02 Duplicate Take bug?

Post by Tripi »

I guess it's possible MOTU intended this, but I sort of doubt it. They finally (!) added a DUPLICATE TAKE key command option. I added a key command and tried it, and it works great. But, if you have a track record enabled somewhere, it will always duplicate the take on that track... not the one you have selected. If no track is record enabled, everything works like you'd expect it to. This is probably a bug/mistake, right?
12-Core Mac Pro, OS: Sierra w/ DP9 - always the latest version. Love of film music.
User avatar
Dwetmaster
Posts: 3491
Joined: Tue Aug 15, 2006 9:59 am
Primary DAW OS: MacOS
Location: Montreal Canada

Re: DP9.02 Duplicate Take bug?

Post by Dwetmaster »

That's not a bug. It's how it was intended. "Take" actions are always prioritized to record enabled tracks first, then if there's no record-enabled tracks, the command is passed to any selected tracks.
MacPro 8Core 2.8GHZ 16GB RAM OSX10.8.3
MacBook Pro 17" Unibody 2011 OSX10.8.3
896mk3, BLA Modded 896HD, BLA Microclock, MTP-AV, Yamaha KX-8, CME VX-7 Mackie Ctrl, megadrum, Presonus C-S,
DP8.04, Bidule, M5 3, Ethno 2, BPM 1.5 Kontakt4, BFD2, SD2, Omnisphere, Wave Arts P-S5, Altiverb7, PSP VW & OldTimer, VB3, Ivory 2 Grand, True Pianos, Ozone 5, Reason 4, AmpliTube3, Bla bla bla...
A few El & Ac basses & Guitars, Hammond A-100.
User avatar
MIDI Life Crisis
Posts: 26254
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: DP9.02 Duplicate Take bug?

Post by MIDI Life Crisis »

What he said, Same for NEW TAKE. The active track for recording gets all the attention.
2013 Mac Pro 32GB RAM

OSX 10.14.6; DP 10; Track 16; Finale 26, iPad Pro, et al

MIDI LIFE CRISIS
dix
Posts: 2994
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: DP9.02 Duplicate Take bug?

Post by dix »

Makes sense. It has the added benefit of letting you know a track is in Record somewhere. One of my bad habits is recording MIDI for hours and then realizing that an Audio track is also in Record and that I've been burning up disk space entire time.
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
User avatar
MIDI Life Crisis
Posts: 26254
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: DP9.02 Duplicate Take bug?

Post by MIDI Life Crisis »

Where this has bitten me recently is as follows:

Most recent track is record enabled. I go into the MIDI editor and see multiple tracks. I want to EDIT a particular track so I move the pencil icon to that track in the track selector to make it the "ACTIVE" track.

THe edit doesn't work so I erase the section to re-record it, but forget to ALSO enable recording on that track (which one can do from the edit window, of course).

I record the track and the data ends up on the last track I recorded on (and is still record enabled). So I would prefer (optionally) that when you designate a track as active in the MIDI edit window, it is also active for recording and take options.

It's a small issue. I non issue for me, really, but since we're kicking the tires, I thought it was worth mentioning.
2013 Mac Pro 32GB RAM

OSX 10.14.6; DP 10; Track 16; Finale 26, iPad Pro, et al

MIDI LIFE CRISIS
Post Reply