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:DP 8.05 still appears to have a bug in data entry in the newer waves plugs in the SE window.
Now, the buggy pull downs have been fixed, this is good. But when one tried to manually enter an amount of an edit point in the data window, it does not work. You can;t even click with a mouse and drag the amounts. So, one step forward one step not.
Well, this is weird. I'm using the new J37 among other Waves plug in and everything is working good.
In fact, I already produced 2 full songs with hundred of tracks and plug ins, with many VI's, tons of pitch editing and didn't had a single crash. Even with a session of Ableton Live slaved via rewire in the back.
I'm using a MAC PRO Dual Eight Core Intel Xeon 2.93, 16gb. MAC OS X:10.8.4 with 3 monitors powered by two 'ATi Radeon HD 7970 OC 3GB' cards and PCI 424 running three 2408's.
Wondering what's causing the problems to you and other people. For me this is one of the best DP Updates ever!
So youre saying that you can go into the SE window, click an automation point, go up to the data window at the top of the SE and ENTER a different value?
Yes.
8.07 64bit, Spire, Nexus, Fab FilterDiva, Gladiator, Nexus, Sylenth, Stylus RMX, Live 9, Reason 6.5, Komplete 8, AD Keys, AD Drums, Geist, Ivory, Waves 9 Mercury, Sound Toys, Fab, VEPro, Reason, Live, UAD2, x3 2408mk3, PCI424, MAC PRO Dual 3.46 Ghz 12 core Intel Xeon, Memory: 64gb ram, MAC OS X: 10.8.6
Phil O wrote:Update on my last post. This only seems to be happening on audio tracks. I can resize MIDI, aux, master fader, and conductor track by dragging. Is there a lock audio track size button somewhere or somethin'
+1 here
I have a file where it is impossible to resize audio tracks beyond a certain size. On the other it is possible. Someone will have an idea?
The resize "bug" I came across was related to a bad install. It WENT AWAY after a clean install. If you are having similar problems I suggest a re-install and if that doesn't fix it call MOTU. Mine is working FINE now.
Marlynebob, it sounds like your problem is different. You CAN resize, but not to maximum. Is that correct?
Phil
DP 11.34. 2020 M1 Mac Mini [9,1] (16 Gig RAM), Mac Pro 3GHz 8 core [6,1] (16 Gig RAM), OS 15.3/11.6.2, Lynx Aurora (n) 8tb, MOTU 8pre-es, MOTU M6, MOTU 828, Apogee Rosetta 800, UAD-2 Satellite, a truckload of outboard gear and plug-ins, and a partridge in a pear tree.
Marlynebob, it sounds like your problem is different. You CAN resize, but not to maximum. Is that correct?
It's true. I can not resize "Huge" and "Immense", but if I delete MIDI tracks can I resize "Huge" but not "Immense". I must say that I have great track noon in this file.
On the plus side: HUGE thumbs up for the VI optimization that MOTU claimed was very Omnisphere centric. Way, way lower CPU hit when running Omnisphere than before. As Omnisphere has become by go-to inspiration box for video game textures, I am loving this!
Jim Bordner
MacPro 5,1 (3.33Ghz 12-core), 32g RAM, OS X 10.14.6 • MOTU DP 10.11 • Logic Pro X 10.2.5 • Waves Platinum, UAD-2, Slate Digital, Komplete, Omnisphere 2, LASS, CineSamples, Chipsounds, V Collection 5[color]
Gravity Jim wrote:On the plus side: HUGE thumbs up for the VI optimization that MOTU claimed was very Omnisphere centric. Way, way lower CPU hit when running Omnisphere than before. As Omnisphere has become by go-to inspiration box for video game textures, I am loving this!
Once in a while I open a project and can't click on anything. i.e. click on anything does not respond. Keyboard shortcuts do work but can't record enabled a track. I have to restart DP for it to work again.
New Rig |MAC Studio | OS12.6 | 64GB RAM | Storage | miniStack STX 18TB, (14TB HDD, 4TB SSD) | Crucial X8 4TB SSD |
Softwares | DP 11.22 | VEPRO7 | Audio Interface | M4 |
--
old rig | MAC Pro 2 X 2.26 GHz, 8-Core | 10.11.6 | 32 GB RAM | DP9.52 | 2408mk3 | MTP AV
Gravity Jim wrote:On the plus side: HUGE thumbs up for the VI optimization that MOTU claimed was very Omnisphere centric. Way, way lower CPU hit when running Omnisphere than before. As Omnisphere has become by go-to inspiration box for video game textures, I am loving this!
Oh boy!! Some good news!!
Gosh how I dread "New Version Day!"
Ha!
James, I've had almost no trouble with ANY version of DP8, and this is no exception. It's running great, the new features work as advertised... On my system, this is the best DP EVER.
Jim Bordner
MacPro 5,1 (3.33Ghz 12-core), 32g RAM, OS X 10.14.6 • MOTU DP 10.11 • Logic Pro X 10.2.5 • Waves Platinum, UAD-2, Slate Digital, Komplete, Omnisphere 2, LASS, CineSamples, Chipsounds, V Collection 5[color]
marc, if you're using jbridge, make sure you have the jbridge icon on your dock, if dp opens frozen, click on the jbride icon and then click in dp, that's the work around i've found to get past this....
mac pro 2.26 octacore 24gigs of ram/ El Capitan10.11, dp 10, mackie dxb, 3-2408mk3, waves mercury 10, ozone 3&4&5678, sound toys, izotope rx, melodyne editor, uad 2, bluetubes, 22" polkadotted dildo, omnishpere 2, trigger 2 deluxe, addictive drums, komplete 9, e/w ql symphonic orq platinum, ql choirs, ql stormdrum 2, ql gypsy, ql ra, ql goliath, ql pianos, superior drummer 3, ez drummer 2, garritan bigband, amg kickass brass, ztar, wife, dogs, droped my protools rig at the city dump
Gravity Jim wrote:On the plus side: HUGE thumbs up for the VI optimization that MOTU claimed was very Omnisphere centric. Way, way lower CPU hit when running Omnisphere than before. As Omnisphere has become by go-to inspiration box for video game textures, I am loving this!
I am glad for that. The bad side is that VI’’s inside of VE Pro, when VE Pro’s buffers are higher than zero, play out of sync. Thus, auditioning drum loops, stylus rmx loops etc, get whacky. With all the updates and talk about better VE Pro integration I was hoping this would be fixed. Not sure where the problem lies, Dp , VE pro?
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
I've done my homework on this re-size thing and I've found something that may be causing people to think there's a problem where there isn't one. There IS a slight difference in the re-size behavior between DP 7.24 and DP8.05 (I can't speak for earlier versions of DP8, as I don't have them.)
In DP 7.24 you can drag ANYWHERE to the left of the waveform/MIDI data/conductor data and re-size vertically in the SE window. In DP 8.05 you must be completely to the left of the little "scale" section (for audio tracks only). If you hover over the scale section, you'll still get the little hand and when you click, you'll still get the little fist, but when you drag, it will do nothing. So, be sure you're to the left of the little "scale" section for audio tracks. I think this is simply a difference in behavior, not a bug.
Just to be clear, this was NOT the problem I reported in my initial post. I was having a problem where I wouldn't even get the little hand. Also I couldn't select the little L's and R's in the bundles window and the Open button wasn't working on the welcome window. A re-install fixed all of these.
Phil
DP 11.34. 2020 M1 Mac Mini [9,1] (16 Gig RAM), Mac Pro 3GHz 8 core [6,1] (16 Gig RAM), OS 15.3/11.6.2, Lynx Aurora (n) 8tb, MOTU 8pre-es, MOTU M6, MOTU 828, Apogee Rosetta 800, UAD-2 Satellite, a truckload of outboard gear and plug-ins, and a partridge in a pear tree.
Marlynebob, it sounds like your problem is different. You CAN resize, but not to maximum. Is that correct?
It's true. I can not resize "Huge" and "Immense", but if I delete MIDI tracks can I resize "Huge" but not "Immense". I must say that I have great track noon in this file.
DP 11.34. 2020 M1 Mac Mini [9,1] (16 Gig RAM), Mac Pro 3GHz 8 core [6,1] (16 Gig RAM), OS 15.3/11.6.2, Lynx Aurora (n) 8tb, MOTU 8pre-es, MOTU M6, MOTU 828, Apogee Rosetta 800, UAD-2 Satellite, a truckload of outboard gear and plug-ins, and a partridge in a pear tree.
It seems that the solution (or bug) in the number of tracks used.
I have a file where I chained 6 titles and for each title I have a MIDI track folder, which represents a large number of MIDI track. (about 100 MIDI tracks, 30 audio track...)
I've made a test by deleting the MIDI tracks and now, I can resize again as I like to track size.
According to me this problem is not related to the 8.05 release (or even earlier)
This is the first time I have a file so big and I do not understand where the problem was
I noticed that Altiverb and Soundtoys' Little Microshift no longer "steal" the transport with 8.05!
Also:
• Double-clicking on soundbite in the Tracks overview once again scrolls to that soundbite in the sequence editor.
This is so great! A solid release. Memories of 7.24.
DP11, 2019 16-Core Mac Pro, OS 14 Sonoma , 64GB RAM. RME HDSPe MADI FX to SSL Alphalink to SSL Matrix console, and multiple digital sub consoles. UAD Quad PCIe. Outboard stuff.
Is there a lock audio track size button somewhere or somethin'
