Pro tools 2018.10

[DarkandKurious]

I would be amazingly happy with an update that:

Fixed multi-input mode in Audiosuite.

Really, that's all I want - for Audiosuite to work properly again. 2018.7 has been killing me, slowly at a snail's pace.

[Tobias Eichelberg]

+ I'm hoping performance is improved the way it was in 2018.6. In the recent version I'm getting CPU spikes that just don't occur in the previous version on my 2013 trashcan MacPro. Even on very small sessions with few tracks and a handful of plug-ins. But the plug-in search function is soooooo good, I can't live without it any more!!

[innesireinar]

The 2018.6 does not exsist. Maybe you are referring to the 2018.4

[abomeerza]

Originally Posted by innesireinar

The 2018.6 does not exsist. Maybe you are referring to the 2018.4

؟!

[AlexLakis]

Open up iZotope Radius settings in Elastic Audio so users can edit the settings based on source material! (Or at least change them back to the settings in Pro Tools 7.4)!

[midnightrambler]

Originally Posted by AlexLakis

Open up iZotope Radius settings in Elastic Audio so users can edit the settings based on source material! (Or at least change them back to the settings in Pro Tools 7.4)!

Oh yeah still waiting for this one ....

[TNM]

Originally Posted by abomeerza

I can't wait for it
I wish they added the track folder
I think it's the most important feature
We're always working session contains more than 150 tracks
So please AVID do it

https://www.pro-tools-expert.com/hom...-release-notes

They promised the folders in 2018, so let's be confident!

I think pitch will come next year as it was highly voted in the last poll.

2018.10 is actually going to squash the midi out no connected reload bug once and for all I have been told, and some more performance optimisations at low buffers! can't wait!

[TNM]

Originally Posted by ~ufo~

I hope they fix:

-crippling bad stability when recording at low buffers (not even lowEST buffer)
-idiotic persisting bug where 4k sample delay introduced when any send is active without an active receiving channel or plugin. This has been there since day1 of PT11!!!!!!
-annoying bug where saving as a template fails to save the active window configuration.

Can you explain the 4K sample delay bug to me please? I am not quite understanding it.

[~ufo~]

Originally Posted by TNM

Can you explain the 4K sample delay bug to me please? I am not quite understanding it.

If you are recording in a session that has a send active but that bus is not being received by an active channel or plugin, this open ended send will cause the delay compensation engine to add about 4000 samples.
So if you’re recording, you’ll get a huge delay in your monitoring.
You need to either turn off ADC, or make sure there’s no open ended send.

If you’re like me and have a template with fx sends preset, but the FX aux tracks inactive, to be activated whenever you need an effect, the only option is to turn off ADC when you record. Not a huge deal, but annoying.
This bug was not present in PT10 and before, it got introduced in PT11.
I immediately got a support case going, it has a big number and now we’re five years later and it’s still there. Nuts.

[TNM]

Originally Posted by ~ufo~

If you are recording in a session that has a send active but that bus is not being received by an active channel or plugin, this open ended send will cause the delay compensation engine to add about 4000 samples.
So if you’re recording, you’ll get a huge delay in your monitoring.
You need to either turn off ADC, or make sure there’s no open ended send.

If you’re like me and have a template with fx sends preset, but the FX aux tracks inactive, to be activated whenever you need an effect, the only option is to turn off ADC when you record. Not a huge deal, but annoying.
This bug was not present in PT10 and before, it got introduced in PT11.
I immediately got a support case going, it has a big number and now we’re five years later and it’s still there. Nuts.

I never de activate aux tracks but I do de activate individual plugins on them and haven't seen an issue.. maybe that's why I haven't come across this. Thanks for the explanation.

Totally different thing, but it reminds me (in the way that Avid is handling it) with the change in radius.. where they changed the preset settings so all slowdowns on transient material sound awful and they sounded perfect prior to that change. That's something they could fix in around 60 seconds and hundreds of people have asked but for some reason they just won't. Point being, maybe this is like one of those situations, where Avid broke something that was working fine, and just don't care. Pretty much all DAW devs are the same unfortunately.. I could run off a string of fundamental issues that a newer release of a daw broke, and the company (I am looking at you apple, steinberg, ableton, presonus!) just refuse to fix it. I don't get it nor will I ever.