MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
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."
toodamnhip wrote:
A whole new system for controller CC data, with faders to automate CC data just like audio. That would bring the crazy world of VIs under control. It’s a feature that could truly put DP back into the forefront. Make all the Pro Tool and Logic guys cry for DP.......
I've got to be missing something here? You can assign any hardware controller with faders to any MIDI CC then MIDI learn that fader to the VI. I'm not sure why it would be better to have a mixer type panel with CC data?
It's a layer of complexity that probably won't happen, but I've often thought that it would be cool if you could use the same fader that's permanently assigned to CC7 in the MIDI track to any CC you want it to be assigned to. With a bonus of for instance Kontakt maybe not reseting the fader unless you draw volume data...
M2 Studio Ultra, RME Babyface FS, Slate Raven Mti2, NI SL88 MKII, Linnstrument, MPC Live II, Launchpad MK3. Hundreds of plug ins.
toodamnhip wrote:
A whole new system for controller CC data, with faders to automate CC data just like audio.
Is that what the Reshape modes are for? That doesn't solve the ramp bug, but does what fades would do and more.
I have always used control surfaces, from Artist Mix to Raven. When you have faders at your finger tips, you don’t need to “mouse around”..lol...
When I control strings vibrato or swells, or what have you, and I have faders under my finger tips to do so, thats ultimate control. I can pencil in things as a secondary option where applicable. But if I can control my audio with faders, I’d like to control my CC data the same way. I so wish mote would make a control surface. Then all of this could be tightly integrated. I don’t think that will ever happen. But perhaps more control surfaces will come out and show CC data being “fader-ized”.....
Last edited by toodamnhip on Sat Aug 11, 2018 8:54 pm, edited 1 time in total.
Mac Pro (Late 2013
2.7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
Mojave
DP 10.13
MOTU 8pre, MTP AV, 828 mkII
Tons of VIS and plug ins. SSD hard drives etc
toodamnhip wrote:
A whole new system for controller CC data, with faders to automate CC data just like audio.
Is that what the Reshape modes are for? That doesn't solve the ramp bug, but does what fades would do and more.
I have always used control surfaces, from Artist Mix to Raven. When you have faders ate your finger tips, you don’t need to “mouse around”..lol...
When I control strings vibrato or swells, or what have you, and I have faders under my finger tips to do so, thats ultimate control. I can pencil in things as a secondary option where applicable. But if I can control my audio with faders, I’d like to control my CC data the same way. I so wish mote would make a control surface. Then all of this could be tightly integrated. I don’t think that will ever happen. But perhaps more control surfaces will come out and show CC data being “fader-ized”.....
I totally agree I'd love a motorized control surface that would do cc-1.
This is the standard with sample libraries now, and none of the motorized surfaces address this.
OSX Big Sur (latest). Mac Pro Late 2013 ("trash-can"), 3.5 Ghz 6-Core Intel XeonE5, 64GB RAM. Motu DP 11.31, Vienna Pro Server, Presonus Notion, Osculator, Keyboard Maestro, Tanqueray or Bombay Sapphire.
toodamnhip wrote:
A whole new system for controller CC data, with faders to automate CC data just like audio. That would bring the crazy world of VIs under control. It’s a feature that could truly put DP back into the forefront. Make all the Pro Tool and Logic guys cry for DP.......
I've got to be missing something here?
yeah, count me in, too? "Missing something", that is.
I've been using the little control surface Korg NanKontrol2 with some of it's faders assigned to CC1, CC7, CC11, etc. It lets me control those parameters and writes the data in to the MIDI track's CC section. No, they're not motorized, but I think they're accomplishing what you're speaking of?
DP 9.52(OS 10.13.6), PTools 11.3.3, Sibelius 2021.12,
MacPro 5,1 mid-2010, 2 x 2.93Ghz 12 core, ATI Radeon HD 5870, 64 Gig RAM, 4 x >120G SSDs, 2 x 25" LCDs
couple o' hardware synths, loadza legal libraries
Kurz Midiboard, MOTU MTP AV
JSmith1234567 wrote:...I'd love a motorized control surface that would do cc-1. This is the standard with sample libraries now, and none of the motorized surfaces address this.
FWIW, my old Yamaha 01v mixer had motorized faders I can asssee fb to any controller. It’s been in mothballs for a decade now. Maybe I’ll sell it as a controlller. Lol.
JSmith1234567 wrote:...I'd love a motorized control surface that would do cc-1. This is the standard with sample libraries now, and none of the motorized surfaces address this.
There are allot of motorized, as well as not motorized control surfaces out there, as well as iPad virtual controllers.
The problem is not sending cc data other than volume.
They will all do that one way or another.
What they won't do is two-way communication with a DAW for cc's other than volume and pan.
The deepest integration seems to be Eucon, but that still unfortunately won't do two-way communication for other cc's.
OSX Big Sur (latest). Mac Pro Late 2013 ("trash-can"), 3.5 Ghz 6-Core Intel XeonE5, 64GB RAM. Motu DP 11.31, Vienna Pro Server, Presonus Notion, Osculator, Keyboard Maestro, Tanqueray or Bombay Sapphire.
toodamnhip wrote:It would be really nice if there was an ability to MARK any given undo history entry so that when there is a crucial point a user wants to go back to, he can MARK that moment with some sort of little flag. We all get into those crucial edit moments, when we’re making a major change in a tune . A change that we may want to go back to in the event it turns out to be something we don’t want. Often, I do a save-as in these instances. But to be able to mark crucial moments in the progress of a song would be very helpful
Me too !
http://gonetolunchmusic.com/
Current sex toys : DP 11.32, Mac M1 Studio OS 13.6.3 64 gb Motu M4. Sounds by VSL, Addictive Drums 2, Native Instruments, Orange Tree, Bolder Sounds. Plug-ins by PSP, VSL MIR Pro 3D, 2CAudio, Waves & Lexicon. Scores by Dorico Pro 5.4.
monkey man wrote:I'm counting on a NAMM announcement and preview.
I figure I'll finally be able to move on from 8.07 'cause I should be able to buy v9 and qualify for v10.
That's the plan, anyway...
On my 2010 cheesegrater Mac, I need to go back to 8.07 for every mix. I do so when a DP 9 files gets large and automation starts reading back unreliably in 9. Once I get to the final stages of a mix in 8.07, if I go BACK to 9, my computer usually bogs, showing me that, on my 2010 cheesgrater, DP 8.07 is more efficient.
Also, 8.07 loops better, without the glitching that can occur in 9 after certain edits. Seems like 8.07 is just a leaner version in general. I give this info for anyone considering leaving 8.07. This includes users installing High Sierra. If your comp is close to its power limits, 8.07 may be better for you. Of course, with a new Mac pro slated for release in 2019, I am sure DP 9 and 10 will be the way to go with such a new comp. But for older computers, be careful about ditching 8.
Mac Pro (Late 2013
2.7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
Mojave
DP 10.13
MOTU 8pre, MTP AV, 828 mkII
Tons of VIS and plug ins. SSD hard drives etc
Now would be a good time for me to upgrade from DP8, but I'm not sure what the timeline is for DP10, and reading a little here it seems like I'm probably better off waiting to see.