Pro Tools 11.3.2

[johnsimmons]

So as per the other thread yes currently seems 11.3.2 is only in the 12 users accounts, i have one asset and sure enough there it is (but not in my 11hd section) . haven't installed yet but here's the mac read me if anyones interested - I'm hoping the midi engine bug fix sorts some of my omnisphere crashes

Issues Resolved in Pro Tools 11.3.2
Video
When initiate playback from the machine that isn't running AVE in satellite environment, Video Engine Synchronization error is encountered. (UME-1189)
Absolute Grid is not calculating properly for 29.97DF, resulting in incorrect time stamping (PT-200337) Unable to import IMX or DNx .mov files created by Telestream Vantage (UME-1155)
Apple Pro Res created in Final Cut 7 fails to import. (UME-1143, UME-1136)
Unable to link to file [x] due to either a missing CODEC or the file may be unsupported (UME-1146) PT/AVE is unable to play back the later MXF files of a chunke clip. (UME-1181, UME-1170)
AVE plays back incorrect chunked MXF after being disabled and re-enabled. (UME-1174, UME-1162) PT/AVE is unable to playback XDCAM MXF media created from still images.(PT-203250)
AAF from Premier Pro won't import into Pro Tools. (PT-204486)
Pro Tools is linking to the wrong audio file in a very simple AAF sequence (PTSW-197309)
Could not complete the Import Tracks command because an unexpected error happened while trying to find a media file's location (PT-205213)
Exporting to Interplay from Pro Tools fails if there are 2,500+ clips in the sequence. (PTSW-195054)
Pro Tools does not prompt for unmounted ISIS workspaces when importing a sequence from Interplay (PTSW-192068)
Changing the Media Destination (ISIS workspace) when exporting to Interplay has no effect (media is ALWAYS exported to source workspace) - causes export to FAIL if user does not have write permissions to source workspace (PTSW-197668)
General
Satellite performance improvement, especially engaging playback on two or more systems at once. Fixed several cases where "There was a problem stopping Pro Tools" dialog is posted and loss of connection occurred, which results a force reboot of the entire Satellite network. (PT-200576, PTSW-197654, PTSW-197081) – Satellite General improvement, please review.
Back and Play commands are intermittently ignored when multiple Pro Tools satellites are linked. (PT-204134, PT-204934, PT- 204863)
Pro Tools audio engine does not resolve properly to virtual transport when an offset is entered on Soundmaster. (PT-200813)—9-pin general improvement
PT and Soundmaster lock up out of sync. (PT-200575, PTSW-196197)—SoundMaster general improvement
If Virpad PEC/Direct paddles are toggled while Pro Tools is trying to lock to Soundmaster in Remote Mode, Pro Tools may lock up out of sync. The Soundmaster will show the offset. (PT-203073, PT-203068)
A stop command issued during FastForward or Rewind from a CB SR-4 9-pin Remote Controller while preference for 'Allow 9- pin Transport Commands in Local Mode' is enabled, is ignored. (PT-203070)
Plug-ins
Fixing an MIDI Engine allocation leak, which results Pro Tools to crash after a certain amount of playback time with certain 3rd party VI (PT-201209, PTSW-197366, PT-200286)
Fixed an instance of crash during offline bounce with plug-ins such as AutoPan, Click II and Space. (NEW to 11.2.2) (PT-200499)
Pro Tools and Pro Tools | HD Software 11.3.2 on Mac OS X 10.8.x, 10.9.x, and 10.10.x — 8/14/15 4
Miscellaneous
Audio does not import with QuickTime files created in Elemental software (PT-205671)
Offline/Online Bounce: Solo Has NO Affect on Bounce. (PTSW-196884)
Crash on Bounce to QuickTime with multiple stems and import after bounce is selected. (PTSW-191177)
DiskCache does not fill until playhead relocated (PT-202090, PT-204608)
Clicks and Pop noise when opening session with Sig gen + master fader set at -inf. (PT-201861)
A copied Object-selected clip with a sync point pastes out of sync (PT-201921, PT-202860)
Since 11.1, PT hangs when trying to create files on XSAN partitions >36TB (PT-200254)
Saving Pro Tools sessions or creating audio media on ISIS 4.x (seen with 4.6.1, 4.7.3, 4.7.4) can take 5-10 seconds (SSENG-555, PT-203003)
Surround Panning automation causing FULL SCALE glitches if play at 1/2 speed (PTSW-197381)
Mono subpaths of stereo paths cannot be individually delay-compensated using the Native mixer (not a problem on HDX). (PT- 201823)
Aux and Audio tracks don't phase align in sessions with certain routing. (PT-203491)
Recorded audio from the bus doesn't align with the source audio track. The latency equals the induced amount of delay in the session. (PT-203813)
Delay comp - Records early if changing track order (HDX) (PT-205150) Crash record enabling an audio track from a template (PT-203411)
Yosemite only - Cannot navigate to folder with "Select Areas to Search" function of Expand to New Tracks and indexing does not work at all version for 11.3.x (PT-200218)
Performing AudioSuite "whole file" processing across multiple clips can result in full code noise, corrupt files and incorrect audio (PTSW-200613)
Fast forwarding or rewinding while in Quick or Track Punch mode causes the cursor to jump to the end of session. (PT-200901) Crash while indexing drive in workspace that contains SDII files. (PT-204202)
Pro Tools can hang when calculating Elastic Analysis on network shares such as ISIS (PT-202256)
Error when attempting to load MIDI patch names files. Cannot see patch names at all. (PT-203571)

[Sardi]

Originally Posted by musicman691

Or it's a phased rollout like PT12 upgrades were? They never did that before with program updates.

So they thought it would be best to stagger the roll out and prioritise PT12 license holders rather than PT11 license holders? For an 11.3.2 release?

Anyone else see the ridiculousness in this?

Oh lordy....

[YYR123]

Incentives, that's all. Not surprising and no hard feeling

I am waiting for the $99 upgrade and then we won't worry at all about this issue

[Sardi]

Incentives? That makes no sense at all. If you have 12, why would you choose to use 11? The people needing to do that would be extremely minimal.

Just seems like yet another dumb mistake to me.

[musicman691]

Originally Posted by Sardi

So they thought it would be best to stagger the roll out and prioritise PT12 license holders rather than PT11 license holders? For an 11.3.2 release?

Anyone else see the ridiculousness in this?

Oh lordy....

Exactly. I've been trying to wrap my brain around this and as Mr. Spock would say: highly illogical

[musicman691]

Originally Posted by YYR123

Incentives, that's all. Not surprising and no hard feeling

I am waiting for the $99 upgrade and then we won't worry at all about this issue

Said it before and I'll say it again - Avid is NOT getting any more of my money. I don't give a damn how inexpensive it is. It's been a fun ride while it lasted but looks like it's time to step off this crazy train (sorry Ozzy).

[Extreme Mixing]

I have a 12 asset, so I was able to download and install 11.3.2. It works, but I still had one crash last night. And many CPU too slow messages. Does anyone know what a memory leak is? Fixing an MIDI Engine allocation leak, which results Pro Tools to crash after a certain amount of playback time with certain 3rd party VI (PT-201209, PTSW-197366, PT-200286)

Sheesh...

Steve

[musicman691]

Originally Posted by Extreme Mixing

I have a 12 asset, so I was able to download and install 11.3.2. It works, but I still had one crash last night. And many CPU too slow messages. Does anyone know what a memory leak is? Fixing an MIDI Engine allocation leak, which results Pro Tools to crash after a certain amount of playback time with certain 3rd party VI (PT-201209, PTSW-197366, PT-200286)

Sheesh...

Steve

Generally a memory leak happens when a program continually eats up memory and doesn't release it for use when done with using that memory space. Happens long enough and your computer starts going slower and slower and slowerrrrrrrrrrrrrrrr

Seriously - CPU too slow messages? I presume your system was working okay before PT11.3.2. And to think from reading between the lines here 11.3.2 is the last update. But if that's true it's typical Avid - fix some things and other stuff breaks (and who knows how long we'll wait to get fixes for the muckups).

[YYR123]

Originally Posted by musicman691

Said it before and I'll say it again - Avid is NOT getting any more of my money. I don't give a damn how inexpensive it is.

I evaluate my situation and for me it's easy to upgrade, the customer always wants more features for a better price.

For me it's a no brainer, I will still run PT10 more often b/c I love the Pro Control......but now I can find that sweet deal on a dcommand that I have been looking for.

[john1192]

feeling like a 2nd class citizen as a PT11 user .. way down on the Totem Pole .. bottom of the barrel .. 11.3.2 goes to PT12 users 1st .. makes total sense if you are in Upside Down Land ..