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 seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Check the forums before you commit to using M1 for serious work just yet. Lots of people having other kinds of problems, many plugins still have to run in rosetta mode, etc... I'm not saying it can't or won't work..I'm just saying...its still early to be jumping to M1 and quite likely you will have at least as many challenges on the new platform in other ways, notwithstanding that somehow this particular bug may not be present in the M1 version of DP.
Me personally I am not even considering Apple Silicon for my DAW until a few more years go by...not only because I want a higher power MacPro working with it, with lots of Ram, etc...but also because lots of software and hardware drivers are still catching up with it,
5,1 MacPro 3.46ghz x 12 cores,96gb, Monterey (OpenCore), Lynx AES16e-50+X32
Sadly I can’t work at 128 or lower, my template makes my computer choke. But, because most of the heavy lifting is done on the slave computers I don’t need software compatibility from that many vendors. AltiVerb, VE Pro, Waves, and maybe UAD and I’m good to go. Don’t even need Kontakt.
I don't see why your template would be choking at 128 if you're using VePro to host most of your instruments especially. But anyway, good luck with whatever you decide.
5,1 MacPro 3.46ghz x 12 cores,96gb, Monterey (OpenCore), Lynx AES16e-50+X32
dewdman42 wrote: ↑Tue Feb 22, 2022 1:18 pm
don't forget also that to get around this issue in DP, you can always just use a lower buffer setting while recording your MIDI tracks.
That’s what I’ve been doing in the last couple of days. I might have to turn off some stuff now and then to get performance to a reasonable level , but it’s not a big deal.
I tried doing a few things in Logic, but to my surprise, with the updates to latency management in DP 10, it is more usable at higher buffer settings than Logic when recording VIs, even though Logic is still more CPU efficient overall.
Another CPU report is in. Here are the known CPUs with the problem:
• 2012 12-core Mac Pro 5,1 ("cheesegrater")
• 2017 27” iMac 18,3 with Quad-Core i5
• 2017 Macbook with 2.9GHz Quad-Core i7
Matt Batson at MoTU now says that "it's definitely not defined to the Xeon CPUs, more Intel for sure".
If we can keep assembling a list and opening tech support tickets at MoTU maybe the engineers will decide to address this.
smashprod wrote: ↑Wed Feb 23, 2022 12:02 pm
Another CPU report is in. Here are the known CPUs with the problem:
• 2012 12-core Mac Pro 5,1 ("cheesegrater")
• 2017 27” iMac 18,3 with Quad-Core i5
• 2017 Macbook with 2.9GHz Quad-Core i7
Matt Batson at MoTU now says that "it's definitely not defined to the Xeon CPUs, more Intel for sure".
If we can keep assembling a list and opening tech support tickets at MoTU maybe the engineers will decide to address this.
I sure hope they can get to the bottom of it. If other DAWs can work around this problem it *seems* like MOTU ought to be able to find a solution to it. I know they blew me away with the first version that cut down the latency on record enabled tracks. (I think the strategy is to use a smaller buffer size just for rec-enabled tracks that ignores the global setting?). A LOT of people are going to be using Intel Macs for at least another year or longer until there are economical M1s on the market. Heck... I'm just doing pop/rock stuff... I might hang on until the future MacMini M1 Pro(?) not only is released, but used units start to show up on the market. Having to do a wholesale upgrade of my audio interfaces, etc. and losing certain software for good is something I want to put off while I can.
I recently got a Console 1 and although it sounds great, looking at the Effect Performance window makes me want to continue to lean on my old Liquid Mix (which is still working thanks to 32 Lives!) since it has its own DSP. Until I can make the jump to an M1 system and upgrade all that needs to be upgraded, I want to save my CPU cycles.
James Steele wrote: ↑Wed Feb 23, 2022 3:19 pm
I sure hope they can get to the bottom of it. If other DAWs can work around this problem it *seems* like MOTU ought to be able to find a solution to it. I know they blew me away with the first version that cut down the latency on record enabled tracks.
Ditto. On the 2018 Mini i7, this is easy to repeat in DP, but I'm unable after several tries to repeat it in Logic. Not that Logic timing is perfect -- after a lot of tests, it looks like Logic is consistently recording MIDI about 15 msec early regardless of the buffer size.
And on the latency thing: it's difficult to even test this in Logic with the buffer at 1024 because of the clearly noticeable delay -- that you can hear in DP if you listen for it, but it doesn't interfere with your playing. I can only do it by reducing levels on the recording track to inaudible levels, so all I hear is the metronome and keyboard noise.
bayswater wrote: ↑Wed Feb 23, 2022 5:39 pm
And on the latency thing: it's difficult to even test this in Logic with the buffer at 1024 because of the clearly noticeable delay -- that you can hear in DP if you listen for it, but it doesn't interfere with your playing. I can only do it by reducing levels on the recording track to inaudible levels, so all I hear is the metronome and keyboard noise.
One good use for a keyboard that has a built-in piano or other bread and butter sound... you can always monitor the built in audio when performing a part, then play back from the VI.