![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
Now that Pro Tools is finally 64-bit, I am considering switching over from Cubase in order to more easily collaborate with some fellow songwriters. However, I am experiencing a "deal breaker" MIDI latency issue with the PT v11.1.2 demo running under Windows 7 Pro 64-bit.
Firstly, I should probably mention that there is no appreciable latency when playing (via my Virus keyboard) virtual instruments in Pro Tools. My RME RayDAT audio buffer is set 128 samples and performs well. However, when playing any of my hardware synths (that are monitored in Pro Tools via Aux Inputs,) there is a very noticeable lag (that feels like an extra 512 samples or so). I am pretty sure the issue is related to the MIDI thru function in Pro Tools because if I play my Virus Kb, for instance, directly into Pro Tools (by disconnecting its MIDI cable and turning on the keyboard via the "Local On" parameter,) there is no latency. It's only when I use the MIDI thru in Pro Tools to trigger the Virus that I experience the significant lag. My 18 hardware synths are connected to my PC via 3 MOTU MIDI Express 128 interfaces. I don't experience this MIDI thru latency issue in Cubase when using the MOTU interfaces. I have disabled the MIDI Delay Compensation preference in Pro Tools. But this didn't eliminate the lag. I would be extremely grateful for any suggestions on how to resolve this issue. As it stands, there is no way I could use Pro Tools with this MIDI thru latency problem. I would just stick with Cubase (which works great) and export my tracks as audio files if I need to collaborate with someone who is using Pro Tools. Thanks for your help! |
#2
|
|||
|
|||
![]()
Link here to main PT 11 ADC Issues list.
__________________
T- ----- Waterstreet Studio Main: MacPro 2012 ([email protected]), 48GB, Apple/Samsung SSDs, WD Blacks. macOS 13.3 DSP & IO : Pro Tools HDX2(2018.3), 2x UAD Octo, HDIO 16x16 Analog IO(3), HDIO 16x16 Digital IO Plugins: Avid, DMG Audio, Kush, oeksound, P'n'T, Plugin Alliance, Softube, SoundTheory, Sonnox, Sound Radix, SoundToys, UAD, VEP, etc Hardware: API, Chandler, Hardy, Moog, Neve, Shadow Hills, Smart, Summit, TC Electronic M6000, UREI, etc Microphones: Telefunken, Neumann, Shure, AKG |
#3
|
|||
|
|||
![]() Quote:
|
#4
|
||||
|
||||
![]()
Hey Style,
My setup is very similar to yours. I've had the midi-thru delay problem ever since I started using Pro Tools back in version 7. No problems in Digital Performer but, in Pro Tools, with three different midi interfaces, and many different experiments over multiple versions of all the related software, the thru-delay is always there. I don't monitor the synths through Pro Tools either. The only thing that goes through Pro Tools is the midi data. I monitor the synths directly from the console. I have resorted to turning the midi-thru off in Pro Tools and patching the synths directly in Clockworks for the MTP AV's that I use. (The guys at MOTU suggested that.) The midi still gets recorded weird though with random notes shifted earlier than I played them - like a lot earlier - usually an eighth or quarter note. I have to go back and find them all and shift them. Frustrating. Clearly, Pro Tools has not figured out this midi thing. I don't have these problems with VI's - just external synths. For any serious midi recording with external hardware synths, I just can't use Pro Tools. Time is money. I use Digital Performer and then transfer the tracks to Pro Tools after that. Sometimes, I don't bother to transfer them. I just do the project in DP. I've scored many commercials and TV shows with DP. I've been doing this for 35 years. Have you discovered any workarounds? (I PM'd you about this, by the way)
__________________
Timothy Ripley Composer, engineer, musician ripcurrentmedia.com [SIZE="1"]Mac Pro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5, 32 GB 1866 MHz DDR3 AMD FirePro D500 3072 MB, Dual 4Tb Thunderbolt G Drives Acer B326HUL 32" 2560 X 1440, VIZIO video monitor Mojave 10.114.6, Pro Tools 20.3.0.163 Digital Performer 10.11, MOTU 1248 (Thunderbolt), MOTU 2408 MkII (x2), MOTU MTP AV USB (x2) |
#5
|
||||
|
||||
![]()
SOLVED!
Quote:
THAT WORKED! Do you know how many years I have been dealing with this without discovering that? Thank you, thank you, thank you. If you're ever near DC, I'll buy you the refreshing beverage of your choice! For those with the same problem, here is the 'workaround'. 1. Open the file. 2. Switch the playback engine to built-in audio and set the buffer to 32 (which of course quits and re-opens the file. The delay was still there in my case) 3. Switch back to your preferred audio interface (mine is a my MOTU 1248 - which of course quits and re-opens the file. The delay was then GONE!) 4. Set the buffer back to your preferred setting. This setting will now not affect the midi-thru timing no matter where you set it. I have to do this every time I start up Pro Tools. I was hoping it would stay as long as the computer is powered up, but quitting and re-opening Pro Tools causes the midi-thru delay once again and I have to re-do the above procedure. I've read several threads trying to get to the bottom of this issue and have never seen a solution posted. I wonder if this problem is unique to MOTU interfaces? Loopzilla2, are you using a MOTU midi (or audio) interface? Why in the world is thru-midi is affected by the audio engine? Probably something to do with delay compensation since that must deal with midi data too, but why the delay with no plugs and only one track? My concept of the delay compensation is that it works on the playback side of things. Why would you ever want to delay live midi? Questions, questions... but happy! ![]() Setting the buffer to 32 samples is an important detail. Pro Tools seems to assign that same buffer setting to the midi-thru data when the session file is opened. After the session is open, you can change it with no effect on the midi thru data timing. More discoveries: If you change the buffer to 32 samples and always open your projects with it set that way, you won't have to do the 'switch-audio-to-internal-and-back-to-your-preferred-interface' step when you open it up - even if you quit Pro Tools. PT seems to set the midi thru delay from the audio buffer setting that is current when the file is opened. Big buffer = big delay. Once the file opens, you can change the buffer to your preferred setting and it will not affect the midi thru timing. These are my findings and could be unique to my system. I just wanted to document things here so that they might help someone in the future.
__________________
Timothy Ripley Composer, engineer, musician ripcurrentmedia.com [SIZE="1"]Mac Pro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5, 32 GB 1866 MHz DDR3 AMD FirePro D500 3072 MB, Dual 4Tb Thunderbolt G Drives Acer B326HUL 32" 2560 X 1440, VIZIO video monitor Mojave 10.114.6, Pro Tools 20.3.0.163 Digital Performer 10.11, MOTU 1248 (Thunderbolt), MOTU 2408 MkII (x2), MOTU MTP AV USB (x2) Last edited by Tim Ripley; 12-09-2016 at 02:26 PM. |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Latency issue with midi function of Mbox3 | deepakkabirgyan | General Discussion | 1 | 12-22-2013 11:29 AM |
Sync issue, pro tools MIDI and MIDI controller, timing issue | Angelo of Onello | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 10-29-2011 08:57 AM |
Midi Latency Issue - Please help me someone | metro williams | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 2 | 01-23-2010 09:18 AM |
MIDI beat clock latency issue!! | overseasmusician | Pro Tools M-Powered (Win) | 0 | 11-04-2007 05:57 PM |