#PRO TOOLS 12.8.3 TRIM VIDEO DRIVERS#
#PRO TOOLS 12.8.3 TRIM VIDEO PRO#

Again, rebooting/resetting the device will fix the issue for the day. I can tell that the device is 'lost' on my system if I am listening to music (as an example) because I can hear little defects in the music - like the sampling rate is not locked in. MOTU Discovery app is either greyed out or when I open it, I get a 'failed to find device' error. HOWEVER, if the computer goes to sleep - say overnight - then the latency problem often returns, or I may lose connection to AVB devices altogether. Afterwards, it runs smooth for the remainder of my session(s). Things start out fine, then there is a small crackle, and latency becomes very noticeable and requires me to reboot the 8A and/or restart the computer (Late 2013 iMac).

#PRO TOOLS 12.8.3 TRIM VIDEO PRO#

The latency issues are the same whether I'm using Ableton, Reason or Logic Pro X.

#PRO TOOLS 12.8.3 TRIM VIDEO DRIVERS#

See pics of Ableton track with old drivers and with new.I've noticed a lot of latency issues (and other problems) with my 8A and 16A lately, but I was also chalking it up to having recently installed OSX High Sierra. weird, but it made no differencet o the recording latency i'm now seeing. With the latest drivers I'm ablet o reduce my buffer setting to as low as 32mb at 48Khz, whereas hte lowest i could go with teh old drivers was 128Mb. Before, at a resolution of 1/512 there was only a latency seen of 2 ticks, which is basically negligible. It's almost a quarter beat of latency before the recording gets laid down to my track which is basically unusable at this point. Havent' test yet with my 1248 or 16A yet. If I could get a single monolithic device with 128x128 in/out and 24 auxes my life would be much simplerĪnyone else experiencing some major recording latency with the latest Motu Pro Audio Drivers in Ableton or any other DAW? I went from negligible to quite severe after I updated teh drivers in my Motu 8A. * Every now and then a device will lose another, where it will see 'Unknown Device' in the AVB stream connectionsĪll these little things make it extremely frustrating during day to day workflow. It's hard to go from 0 to 1 without jumping straight over to 3 or something I should be able to edit one device in isolation without having a weird side effect of it impacting another one.

* This may be user error, but it's incredibly frustrating/confusing - I will go enable/disable some mixer channels on one device, and they will then be disabled/enabled on another device. The source unit will be correct, and other units may see it correctly So on one unit I'll see '1248:1-2' instead of the properly labeled 'Prophet 6' or whatever. * every few days, when I select one unit that unit may not 'see' one of the other units in the left hand Devices panel Here are the bugs I still run into on a daily basis in the Web based (chrome on windows) tool, in a 1248/16a/16a/24ai system (one AVB switch).

Pro tools 12.8.3 trim video