No Pro Tools 13 for me unfortunately.

[noiseboyuk]

Originally Posted by propower

Is it a necessary expense - for many - "yes".

I really don't know that it is. Find a stable version that works for you and your business, and stick with it. Most professionals pretty much do this anyway, only daring to upgrade in a period of downtime, and rolling back if necessary. Whenever a new version comes out, it's simply a list of new bugs to firefight, reducing productivity. Most of us simply find workarounds for the bugs that we know and love.

Offline bounce was a feature worth paying for. Translucency for dragging clips - I'd miss that. Can't think of anything else since PT11 that I actually use. $400 per year is not a massive business expense, but if it's effectively money down the drain for no reason, it just makes no sense to keep pouring it down there.

[JFreak]

Originally Posted by Extreme Mixing

I don't remember any upgrades that were $150. I've been using since Pro Tools 5

Wasn't PT7 era upgrades that cheap?

[propower]

I thought everything up to the PT9 was much more reasonable (started at PT4 for me). $150 seems right but i find no easy record of it

12.5 and up are for Sierra compatibility mostly in my case - though besides the other things mentioned I use and like layered editing and Freeze (when working Native). I skipped El Cap and didn't want all my machines back at 10.10.

[JFreak]

Originally Posted by propower

I thought everything up to the PT9 was much more reasonable (started at PT4 for me). $150 seems right but i find no easy record of it

Here is an article that says PT8HD upgrade 249 abd PT8LE upgrade 149 and this one says 175/75 dollar pricing for PT7 HD/LE

[Audiomonkeys]

Wich????? why are you making excuses for Avid?

[JFreak]

Wat? I'm just providing web page finds for a fellow DUC'er

But with that said, up to PT8 was Digidesign-branded PT and starting with PT9 has been Avid-branded PT so it is just logical that price chart may vary.

[Bob Olhsson]

Starting with PT 9 it was no longer tied to hardware and upgrades were raised to the same amounts as other stand-alone DAWs.

People seem to want everything both ways.

[JFreak]

Originally Posted by Bob Olhsson

Starting with PT 9 it was no longer tied to hardware and upgrades were raised to the same amounts as other stand-alone DAWs.

Yep, that was huge. It also meant Digidesign-branded versions no longer were eligible for upgrades, except PT8-->PT9 for a short period. Now you need to have PT9 or newer if you want to upgrade, or wnat Avid wihes i, to have a current version and take care of your support plan.

[yoerik roevens]

Originally Posted by ShiftStudios

I'm curious to know what you think is so bad about the S3 that makes it "not even ready for alpha testing"?

as not to hijack this thread too much, here's a minimal list of highlights: (there`s more where those came from...)

A) physical design:
- ridiculous placement of sel buttons (in itself terrible enough to not even bother about the rest anymore)
- bad placement of knobs and lcd's. my S3 is standing at about 50° degrees in order to be able to read the lcd's
- totaly useless touch strip with terrible response, best to disable as one constantly hits it by accident

B) functionality:
- no visual feedback on automation modes (biggest showstopper imo)
- poor knob behavior (no fine tuning, not linear/convenient) (http://duc.avid.com/showthread.php?t=365004&page=1)
- many many bugs where S3 layout is (partly) lost/not remembered, including:
- S3 layout resetting whenever you drag a clip from outside PT into PT
- VCA spill not recalling last setting in (standard) Multi Master Mode
- sends resetting to send A when spilling a VCA
- channels exiting trim mode after writing send automation when trim is not included in send mode

- terrible banking. many issues with edit/mix window follows banking etc...
- poor fader resolution (hardware/software?)
- softkey colour coding not working
- no access to memlocs
- I/O routing config not suited for larger sessions
- no eq/compressor only cycling
- ...

Imo at least all of the above should have been noticed and adressed before beta-testing. However, over 1 year after it`s release, we, the users, are still alpha testing this debacle.

[yoerik]

just one more for ShiftStudios:

if on any console you want to change automation mode twice in a row, i.e. you want to go from <read> to <touch> to <latch>.

normal procedure would be:

touch + sel
latch + sel
done


Now the 1 million dollar question: What would you call a console on which the right procedure would be:

touch+sel
latch+sel
latch+sel AGAIN!

?

Crazy? Ridiculous? Useless? ...

The right answer is 'Avid S3'


Colour me amazed, but according to Avid and the new Focusrite CEO apparently this is exactly how a 5k console should behave. btw, this has been reported over a year ago and is still not fixed (as most of the stuff listed above).