196,951 users have contributed to 43,043 threads and 258,499 posts.
In the past 24 hours, we have 2 new thread(s), 13 new post(s) and 58 new user(s).
+1. I am waiting for this to transition to M1, especially urgent because my DAW is DP11 and there is a MIDI timing bug with DP11 on older Intel machines, so until I switch I'm using annoying workarounds :(
Working under Rosetta 2 sounds too dicey, though if any of you have had good experiences, please post.
No ETA yet??
I also use DP11 and am a beta tester and can report issues directly to the MOTU devs. What are the steps/circumstances that cause the midi timing bug w DP11/VEP you’ve found on intel???? This needs to be fixed asap regardless of AS transition.
With higher buffer settings (e.g. 1048), if you are routing a MIDI track to a VI (any VI, even a MoTU VI), MIDI records about 60 ms late. Also "Fine-tune Audio I/O Timing" does not work on these machines. The only workaround is nudging MIDI back into place after recording. I've been working extensively with Matt Batson in tech support, and the engineering team has been made aware of the bug. They have reproduced it on 2 different Intel machines, and confirmed that it does not happen on their AMD PC or their M1 Mac Mini. I don't know that it is a priority for them though.
There is an extensive thread about this on MoTUNation, "MIDI recording late", where I document what's going on in detail (though you may have to wade through some off-topic or uninformed posts to see it). If you have access to the engineering team and can help nudge them toward supporting the older Intel machines, that would be great!
I think it's been stated elsewhere that M1 support would come sometime this year.+1. I am waiting for this to transition to M1, especially urgent because my DAW is DP11 and there is a MIDI timing bug with DP11 on older Intel machines, so until I switch I'm using annoying workarounds 😞
Working under Rosetta 2 sounds too dicey, though if any of you have had good experiences, please post.
No ETA yet??
WOW. mind absolutely BLOWN. Thank you so much for bringing this to my attention. This has long plagued me too!! But I had no idea until 20mins ago that this was an actual bug effecting only DP users. I incorrectly thought this was just the very nature of latency and buffer settings etc and all DAWs experienced this. Just confirmed with Logic and Cubase using friends that those DAWs will compensate for higher buffers when live recording MIDI. DP needs to fix this RIGHT AWAY. I'm going to ping the hell out of this to the dev team. Thanks again for bringing to my attention!
Wait, what? I've used DP exclusively for composing with MIDI for years. Are you saying other DAWs have found a way to eliminate buffer latency when recording MIDI (IOW the interval between the time a key/pad is pressed and the VI sounds)? If so, I missed a memo, because it was not always so. Back in the oughts, when I used Logic, latency was definitely a thing.WOW. mind absolutely BLOWN. Thank you so much for bringing this to my attention. This has long plagued me too!! But I had no idea until 20mins ago that this was an actual bug effecting only DP users. I incorrectly thought this was just the very nature of latency and buffer settings etc and all DAWs experienced this. Just confirmed with Logic and Cubase using friends that those DAWs will compensate for higher buffers when live recording MIDI. DP needs to fix this RIGHT AWAY. I'm going to ping the hell out of this to the dev team. Thanks again for bringing to my attention!
Wait, what? I've used DP exclusively for composing with MIDI for years. Are you saying other DAWs have found a way to eliminate buffer latency when recording MIDI (IOW the interval between the time a key/pad is pressed and the VI sounds)? If so, I missed a memo, because it was not always so. Back in the oughts, when I used Logic, latency was definitely a thing.WOW. mind absolutely BLOWN. Thank you so much for bringing this to my attention. This has long plagued me too!! But I had no idea until 20mins ago that this was an actual bug effecting only DP users. I incorrectly thought this was just the very nature of latency and buffer settings etc and all DAWs experienced this. Just confirmed with Logic and Cubase using friends that those DAWs will compensate for higher buffers when live recording MIDI. DP needs to fix this RIGHT AWAY. I'm going to ping the hell out of this to the dev team. Thanks again for bringing to my attention!
No no, theres a very clear distinction that needs to be made here. I'm not saying other daws found a way to eliminate the buffer latency of - the interval between the time a key/pad is pressed to the time you hear the sound - that would basically be impossible. What Im saying is other DAWs have a way to place the actual MIDI notes that you play in real time down in the midi track at the EXACT time you physically touch the keyboard, regardless of buffer. Pretend your speakers are muted for a sec, this whole thing has nothing to do with actual sound. Set up a metronome on your iphone or something. Now, If you record arm a track in Logic or Cubase, play a midi passage to the click at a buffer of 64, the resulting recorded midi will be in time to the same extent that if you then change your buffer to 2048, record arm the track and play to the same click. That is currently NOT the case w DP. DP's buffer settings are having a negative delay/impact on where the actual midi notes get put while recording and it gets worse the higher the buffer goes.
Got it. What you describe is what I always assumed. Yeah, I guess other DAWs would need to have implemented time-travel to eliminate live buffer latency!
So higher buffers causing "negative-delay" in DP is the operative here. That is new info for me. By keeping my buffers at 512 I guess I've never noticed the discrepancy - mainly, probably because I'm not much of a player. At 512 that negative-lag is the least of my problems.
But is this a VEP issue, evang42? Or do all VI exhibit this in DP?
This problem exists in DP with any VI. For example, we tested it with a basic MoTU VI, in the actual sequence on the host computer (no VEPro, Bidule, etc.), and it is still a problem. Take the VI out, and record into a MIDI track that's not connected to anything, and MIDI is recorded correctly, regardless of buffer setting. By the way, I can set Pro Tools up with the same parameters and it does not exhibit this problem. All modern DAWs compute where to record the MIDI note regardless of buffer size, latency, etc..
Finally, this problem does not exist with AMD PCs or M1 Macs. You can record MIDI with a VI and a 1048 buffer on a M1 MacBook Pro and the MIDI notes will be recorded exactly as you played them. Matt Batson and I did a lot of testing on this, and the engineers confirmed it.
Now I see. Hence, you're hoping for an AS native version of VE Pro ASAP, so you can make the switch to an M1 Mac. As I mentioned the AU version of VEP works fine with DP. I haven't investigated, but presumably it wouldn't have the timing bug. It's cumbersome, and not nearly as convenient as the MAS version but it might work as a stopgap for you, so you could get going on an M1 Mac, until there's a native MAS VEP.This problem exists in DP with any VI. For example, we tested it with a basic MoTU VI, in the actual sequence on the host computer (no VEPro, Bidule, etc.), and it is still a problem. Take the VI out, and record into a MIDI track that's not connected to anything, and MIDI is recorded correctly, regardless of buffer setting. By the way, I can set Pro Tools up with the same parameters and it does not exhibit this problem. All modern DAWs compute where to record the MIDI note regardless of buffer size, latency, etc..
Finally, this problem does not exist with AMD PCs or M1 Macs. You can record MIDI with a VI and a 1048 buffer on a M1 MacBook Pro and the MIDI notes will be recorded exactly as you played them. Matt Batson and I did a lot of testing on this, and the engineers confirmed it.
...and now iLok is done... hopefully beside debugging it (just last little inconsistencies, the overall job was quite brilliant, well done VSL) a VEP7 universal macOS will be released...
...and now iLok is done... hopefully beside debugging it (just last little inconsistencies, the overall job was quite brilliant, well done VSL) a VEP7 universal macOS will be released...I reckon it could be awhile still. Creating a UB version of VEP must be a lot more complex than creating one for an audio plugin....many of which are still in development almost 18 months after the arrival of M1
I'm assuming VEP7 would stay on Rosetta and VEP8 would be the software to make native. Seems like a heck of a lot of work to have to do it fro VEP7 when VEP8 is probably on the horizon. It would also be a little nudge to encourage an upgrade :-)
I'm assuming VEP7 would stay on Rosetta and VEP8 would be the software to make native. Seems like a heck of a lot of work to have to do it fro VEP7 when VEP8 is probably on the horizon. It would also be a little nudge to encourage an upgrade :-)We’ll, I sure don’t like this idea. I’d like it better if VEP worked with Rosetta for me, but it does not. The MAS version of the plugin doesn’t work under Rosetta. If they updated the MAS plugin to work with Rosetta I’d be okay waiting a bit for the privilege of paying for a UB compatible upgrade.
...along these lines, I'm reading that MacOS 12.3 seems to have fixed a lot of plugins that weren't working in Monterey. I'm holding back updating for a couple of reasons, but I'm curious if, by some miracle, the update makes the MAS plugin usable on M1 Macs.
It does not. Basically unless you're running Cubase or Bitwig, VSTs don't run in Rosetta. Bitwig sandboxes the VSTs so they run in Rosetta in Bitwig native. As Far as MAS is concerned MOTU would have to implement this themselves and I would bet they decided that the 8-12 companies that make MAS plug ins would be coming to native soon enough.
So yeah, I miss the MAS VEP plug in, and hope that Vienna get going on this soon enough.
To be clear, DP11 itself is fully AS native, but as you point out VEP MAS won't work in Rosetta. I actually spoke to someone at MOTU about this and they said that Rosetta could only translate AU plugins (and not MAS) so unfortunately it's up to VSL to go AS native and deliver a MAS version to get this working again and it seems there's nothing more MOTU can do.
I also use DP11 and am a beta tester and can report issues directly to the MOTU devs. What are the steps/circumstances that cause the midi timing bug w DP11/VEP you’ve found on intel???? This needs to be fixed asap regardless of AS transition.
With higher buffer settings (e.g. 1048), if you are routing a MIDI track to a VI (any VI, even a MoTU VI), MIDI records about 60 ms late. Also "Fine-tune Audio I/O Timing" does not work on these machines. The only workaround is nudging MIDI back into place after recording. I've been working extensively with Matt Batson in tech support, and the engineering team has been made aware of the bug. They have reproduced it on 2 different Intel machines, and confirmed that it does not happen on their AMD PC or their M1 Mac Mini. I don't know that it is a priority for them though.
There is an extensive thread about this on MoTUNation, "MIDI recording late", where I document what's going on in detail (though you may have to wade through some off-topic or uninformed posts to see it). If you have access to the engineering team and can help nudge them toward supporting the older Intel machines, that would be great!
Hi dmansfield! I found an answer/fix for you on this! In DP's preferences, go to midi options and UN-check the box called "Sync Recorded Midi to Patch Thru". This SHOULD totally fix your issue (on ANY machine, apple silicon, intel, pc etc). It's a setting that tells DP to place midi either 1) exactly where you PLAYED/intended it (un-checked) OR 2) where you would normally HEAR that midi (which of course is dependent on buffer size/latency).
Okay. Not great news, but this kind of clarity is useful.To be clear, DP11 itself is fully AS native, but as you point out VEP MAS won't work in Rosetta. I actually spoke to someone at MOTU about this and they said that Rosetta could only translate AU plugins (and not MAS) so unfortunately it's up to VSL to go AS native and deliver a MAS version to get this working again and it seems there's nothing more MOTU can do.
