Pro Tools 2019 !

[arche3]

Just fix the CPU errors. I'm thinking the new audio engine will do that.

Sent from my SM-G975U using Tapatalk

[noiseboyuk]

Originally Posted by arche3

Just fix the CPU errors. I'm thinking the new audio engine will do that.

Sent from my SM-G975U using Tapatalk

Don't want to be a prophet of doom, but I think PT users should brace themselves for 2019.5/6/47/whatever it ends up being. This is a major rewrite of a core component that has persistently failed in internal testing, putting us where we are now. I'd love to believe that when it finally rolls out it is perfect in every way and solves every problem anyone has ever had with PT, but my experience of software in general and Avid in particular suggests things might not be quite that smooth.

FWIW I think this looks like a great update, and I think that in the end we'll all be better off for it. But I'm under no illusions that it will be pain-free, and I sure won't be the first to update.

Given all this, I think Avid has a responsibility now to add months to everyone's subs. IIRC, the end of March was a moment when many people's subs ran out, and 2019 should have been out by then. I think Avid need to do the right thing and add free months for everyone between April and whenever this update appears and is STABLE. They have patently not fulfilled their part of the bargain between them and us for the annual fee.

[Simon2065]

The reason for the delay is all explained by Avid in the Pro Tools Expert interview/transcript. I suppose Avid became acutely aware of the rising discontent and decided to do something about it. Sounds like they could have released the update for all users except the HDX users without too much trouble, til they sorted the issue there.

[Obsidian Dragon]

My 2 cents:

I hope they fix the CPU errors, add folders, etc. with the next release or engine update. That is all good and needed. What concerns me is the compatibility with Mojave. By the time the update it comes out, Apple will have released several iterations of Mojave beyond the version they may be writing for. It is just a matter of time before Apple releases the next version of OSX (named whatever) and we will be is a similar situation. I don't know the solution as Apple keeps marching forward with its OS cycle and Avid has a significant lag it catching up each time. Perhaps Avid need target writing code to a published standard for the Apple environment (if that exists) and avoid proprietary code that is tied to a specific version of the OS. I realize that Apple changes the standard over time but since other developers have that standard to follow, they seem to be able to minimize the changes needed and time to update software. But what do I know?

[Gentoo]

Originally Posted by Justin1524

How about...

• Support for VST, VST3 and AU plugins like Studio One has
• Import/Export to more audio formats such as FLAC and ACC like Studio one has
• Two separate buffers for input and output like Studio One has
• Ability to set input buffer down as low as 16 samples like Studio One has
• Melodyne ARA integration
• Ability to use VST/VST3/AU plugins like Studio One has
• Scale timeline by click holding and moving up/down like Studio One has
• Packing tracks into folders like Studio One has
• Built-In Project/CD Burning like Studio One has
• Complex routing to VIs and plugins like Studio One has
• Better, clearer, fatter metering of inputs and outputs like Studio One has
• Install on up to 5 computers Mac/PC with same license, no subscription fee like Studio One has.
• Bug fixes free, pay for major upgrades like Studio One has
• Great communication with customers, like Presonus has
• Chordtrack/detection like Studio One has
• Scratchpad like Studio One has
• Many, many more innovative features like what Studio One has.
• Super stable and fast launching. Studio One wins!
• Integration with Waves Soundgrid and/or SG versions of all Avid plugins
• While we're at it, VST3/AU versions of all Avid plugins and VIs so we can use them in other DAWs.

Seeing how none of these is likely to happen why do I continue my Ultimate subscription? LOL @ voice packs. Packed with features NOT.

This is the post I agree with. I have Cubase Pro 10 as well as Pro tools and I keep Cubase and upgrade every year because it gives me features that I need. Rather than copying a plugin and clicking alt/option to copy to other tracks, why not add a channel with a fader where you can drop one instance of a plugin on it for all the tracks in that group? Cubase does this. Support for VSTs is long overdue! Every other DAW does. This isn't harming me too much right now because I mostly use stock plugins, which in my opinions, Pro Tools stock plugins are much better than Cubase's which is why I prefer PT for mixing. My Izotope plugins do work in PT as well.

Reading this update looks like I'll be sticking with PT 12 yet again. I update Cubase every year but so far, Avid hasn't given me a reason to update Pro Tools.

[JFreak]

VST will never happen, its automation is sub-par to RTAS and AAX
AU will never happen, it is nonexistent in Windows and PT is cross-platform

[deanrichard]

Could you explain what you mean by that? What is it that you think is lacking? With VST every parameter can easily and quickly be automated, and most DAWs offer switches and envelopes to control any and every parameter. Were you under a different impression?

Originally Posted by JFreak

VST will never happen, its automation is sub-par to RTAS and AAX
AU will never happen, it is nonexistent in Windows and PT is cross-platform

[JFreak]

Originally Posted by deanrichard

Could you explain what you mean by that?

VST plugin automation is not sample accurate and are drifting a little from bounce to bounce

[TrackerLe]

Can you give us a link for your theory...


I use Cubase and Nuendo and the automation is totally accurate when bouncing with VST Plugins...

[JFreak]

Here's a thread from Steinberg forum. I'm not an expert on this area though. VST spec as I've let myself understand is not sample accurate but the plugin control changes happen within X samples window, dependent on your playback buffer.