2018.3 & 4 Running Well Here.

[TNM]

Originally Posted by CHRIS AIKEN

I updated my specs... 3.5 GHz Intel Core i7. I was mostly commenting for the guy who had a problem running 3 tracks, no plugins, at a 64 buffer. Live VI's at a low buffer is another issue for sure...I tend to stay at 128 for that.

Ok yeah.. that's where I stay, 128 to play live Vi's..

It's interesting the hackintosh has that issue as well (as i presume unlike on a real mac you were able to disabled intel cpu throttling)..

I believe it's quite simply a pro tools specific issue.

Yeah the guy having an issue recording 3 tracks at 64 buffer, that's not right.. my 7 year old imac does that even at 32 buffer without issue.. A lot of it comes down to audio interface drivers, the OS of course and if on windows, any dpc latency issues

[climber]

I updated from 2018.1 yesterday morning. Just installed over existing version. Then spent the afternoon and evening doing some mixing and MIDI drum editing and programming on an original tune I’ve been working on. Loaded another tune with about 30 tracks including Keyscape and RMX. No errors and it ran fine at 512. Then I laid down some background vocals for a friend. 10 audio tracks, no VI’s, at 32 using my VMS with several Slate plugins in the VMR. Again, no stutter, no errors, it just worked. Today I spent much of the day editing and mixing on a couple of my tunes. Probably an average of 30 tracks on each, some Keyscape, some RMX, one with Kontakt. Worked just fine. No errors and no crashes.

Of course none of this really stressed my system, but I’m happy with how it went. Of course YMMV.

[Jazzbass56]

I’m running 2018.3 on a Win 10 Pro workstation and a New Mac Pro 12 core beast Both workstations have 64 gb of ram and 2018 is the best version I have ever had on my Windows workstation, the Mac is always stable but I’m really happy to report the Windows version is getting there, I also forgot to mention I’m running High Sierra on the Mac 10.13.3 one thing I found out for me was don’t use iCloud Drive to sync your documents folder on your workstation if that is where you store your track presets etc, that caused me some grief but now I’m not doing that it’s much better, and Windows now shuts down without hanging
So the new PT was worth the upgrade for me


Sent from my iPhone using Tapatalk

[abc1mce2]

Originally Posted by TrackerLe

Strange... I thought the bug with BX_Digital and Eq Curve track view was fixed with 2018.3...
Brainworx Digital v3 no longer crashes Pro Tools when Mix Window EQ curve is shown (PT-237575)

It seems to be on Mac...but on Windows 10... BX_Digital still crashes Protools 2018.3 when EQ Curve in the Mix Window is activated...

Can confirm the bug. If the EQ curve in the Mix Window is closed no crash. If the window is opened and you try to adjust and the EQ...crash. If you just open BX v.3 plugin no crash, just don't try to EQ anything until you close the EQ curve view.

[LDS]

Originally Posted by s.d. finley

24bit or 32 bit @48k. 64 buffer with 3 audio tracks and zero plug ins and the cpu meter is spiking like crazy, even with transport not engaged/PT not playing.
128 is better but I get the occasional AAE-9093 error. I looked up the error and its not a clocking error. When I use just one Lynx 16 with LTHD, both with up to date firmware, I still get the error. Normally its 2 Aurora 16s with a Mytek DSD DA for monitoring. If use the Mac Pro built in as the interface no spikes. MacPro is 5.1 dual hex core 3.33ghz 64 gb RAM with an SSD for the OS which is El Capitan X.11.6. I had adjusted my buffer to 256 in a 20 track session with maybe 15 or so plug in, no reverb or multi band, linear eq so nothing piggish, and still got an error.

We have almost the same spec Mac Pro. I am running a dual hex 3.33ghz 5.1, but with only 16gig of ram. I can playback 20+ tracks of audio through 5 groups and about 30 plugins... all while recording 10 new tracks, each monitoring through an additional plugin PLUS 6 stereo headphone mixes. All at 64 sample buffers, 32 bit floating & 48kHz sample rate. I am running Sierra on my system...

Here are some screenshots to give you an idea of what is possible:

https://www.dropbox.com/s/2i6ranj6v2...45227622_o.jpg
https://www.dropbox.com/s/txi4iv5ihb...99791991_o.jpg




Are you using your Aurora's via a HD Native card? Or some other protocol? From my experience, not all audio interfaces are created the same. The session above was running an Antelope Zen Studio which runs pretty ok... but it does seem to chew up considerably more system resources than an RME PCIe or SSL Madixtreme card does. I do get spikes... but they seem to bounce around 20-30% on top of whatever Pro Tools is using.

[BScout]

Originally Posted by abc1mce2

Can confirm the bug. If the EQ curve in the Mix Window is closed no crash. If the window is opened and you try to adjust and the EQ...crash. If you just open BX v.3 plugin no crash, just don't try to EQ anything until you close the EQ curve view.

Yeah, no crash on Mac. Haven't checked Windows yet. (and strangely, since we are talking about the EQ view, the Brainworx digital v3 doesn't have any effect on that eq view in the first place with the latest version of the plugin and 2018.3)

[s.d. finley]

I found a couple bugs on 2018.3 today. I had several audio tracks record enabled and when I tried to drag a hardware output send from one record enabled audio track to another I could not. If I had the audio track not record enabled, I could drag and drop its send to an audio track that was record enabled.
Also dragging and dropping multiple files at once from the regions bin into the edit window caused the scribble strips on my C/24 to FREAK out during the process. Yes I am still having CPU spikes too. Another one happened during recording today.

[s.d. finley]

Originally Posted by LDS

We have almost the same spec Mac Pro. I am running a dual hex 3.33ghz 5.1, but with only 16gig of ram. I can playback 20+ tracks of audio through 5 groups and about 30 plugins... all while recording 10 new tracks, each monitoring through an additional plugin PLUS 6 stereo headphone mixes. All at 64 sample buffers, 32 bit floating & 48kHz sample rate. I am running Sierra on my system...

Here are some screenshots to give you an idea of what is possible:

https://www.dropbox.com/s/2i6ranj6v2...45227622_o.jpg
https://www.dropbox.com/s/txi4iv5ihb...99791991_o.jpg




Are you using your Aurora's via a HD Native card? Or some other protocol? From my experience, not all audio interfaces are created the same. The session above was running an Antelope Zen Studio which runs pretty ok... but it does seem to chew up considerably more system resources than an RME PCIe or SSL Madixtreme card does. I do get spikes... but they seem to bounce around 20-30% on top of whatever Pro Tools is using.

Yes I am using HDN with 2 Lynx Aurora 16s with the LTHD cards all with updated firmware. Thats great with your system. Too bad my system sucks. This is really absurd. I have an HD Omni at my other studio I am going to bring it in and see if that makes any difference. If it does not then its the stupid HDN card which is also absurd!! I NEED 64 I/O.

[s.d. finley]

Originally Posted by dankin

Yes. Happened with 2018.1 as well. I'm on 10.12.6

Yes, but the actual area where the tool changes seems to have moved little bit further south if you know what I mean. For me the selector for the trim tool seems to need to be lower in the region for it to change.

[dankin]

Originally Posted by s.d. finley

Yes, but the actual area where the tool changes seems to have moved little bit further south if you know what I mean. For me the selector for the trim tool seems to need to be lower in the region for it to change.

I haven't noticed that yet. What I've been seeing is after working for a while, sometimes the tool won't change from the hand tool, but it still works. It's just a little weird seeing a hand tool while yo trim a region, or add a fade. If I quit PT and reopen it will be fine for a while, then it will happen again.