 |
AAX SDK
2.1.1
Avid Audio Extensions Development Kit
|
A list of known bugs affecting AAX plug-ins.
AAX SDK example plug-ins' controls do not write automation properly when in 'touch' mode (frequently revert to default value while writing)
Resolution: This bug is fixed as of the 1.0.4 SDK
AAX DemoGain GUI example plug-ins do not correctly handle alt/opt-click for resetting controls to their default state
Resolution: This bug is partially resolved as of AAX SDK 1.0.4. See also PTSW-158348 and PTSW-158381.
AAX SDK JUCE example plug-in does not "snap to default" on option-click
Resolution: This bug is fixed as of AAX SDK 1.0.4
C99Compatibility constructs are incorrect when used with VS2012
Resolution: This bug is fixed as of AAX SDK 2.1.1
Misleading warning message when attempting hardware debugging using a non-local TIShell.out
The "Load ProTools Plug-in Symbols" script gives the following warning: D:/Code_7/dev.ws.backup-win7-concert/AAX/Internal/SystemSoftware/TIShell/CCS_Project/TIShell/../../../../../../WinBag/x64/Release/bin/TIShell.out does not exist! Please question everything.
This error message includes a hard-coded path that is not relevant to the running system. This error is benign but it can be confusing.
Resolution: This bug is unresolved
AAX SDK: Win32 example plug-in GUI does not appear in Windows 8
Resolution: This bug unresolved
AAX DemoGain_VST: Text box entry is not acknowledged upon click outside of window
Resolution: This bug is unresolved
AAX SDK Win32 example plug-in does not "snap to default" on option-click
Resolution: This bug is unresolved
AAX SDK VSTGUI example plug-in does not respond to 'alt' or 'win' modifier keys (Windows)
Resolution: This bug is unresolved
AAX DemoGain_VST and DemoGain_Cocoa require initial click on GUI to take focus before editing (OS X)
Resolution: This bug is not yet resolved. For OS X, one workaround is to modify VSTGUI's cocoasupport.mm file in order to add a handler for the acceptsFirstMouse selector:
Special thanks to Nick Protokowicz for suggesting this workaround.
AAX SDK: Incorrect output from scatter/gather DMA example plug-in when increasing playback buffer size while audio is present (Native decks)
Resolution: This bug is unresolved
AAX SDK: Output from DMA example plug-in is one buffer early
Resolution: This bug is unresolved
Global symbols due to statically linked boost libs in Pro Tools components may conflict with plug-in components that use boost
Resolution: This bug is unresolved
Meter decay setting is not applied to plug-in meters
Resolution: This bug is unresolved
Plug-ins do not receive parameter touch state when automation-enabled in Pro Tools 11.1
Resolution: This bug is fixed as of Pro Tool 11.1.2
Some plug-in state changes do not trigger the Pro Tools session "dirty" flag
Resolution: This bug is pending further information; it may be fixed in Pro Tools 11.1.2
Unexpected behavior for plug-in auxiliary output channels > 128
Resolution: This bug will be fixed as of Pro Tools 11.1.3
In some cases AAX plug-ins do not show the correct Control Name Variation on control surfaces
This bug can occur when a page table references parameters by ID and some parameters' ID strings are exactly as long as the control surface's display. In this scenario, the control surface will display the parameter's ID string rather than a Control Name Variations (abbreviation) string of equivalent length.
Resolution: This bug is unresolved
Failure to load AAX plug-ins with spaces in DLL filename
Resolution: This bug is unresolved
Auto-generated AudioSuite plug-in GUIs are non-functional
Resolution: This bug is unresolved
AAX AudioSuite: PreRender() is not called before each preview pass
Resolution: This bug is fixed as of Pro Tools 11.1
Plug-ins are not unloaded and cannot be swapped when EnablePlugInHotSwap option is enabled
Resolution: This bug is unresolved
Pro Tools 11 developer builds hang when LLDB is detached
Resolution: This bug is unresolved
Pro Tools 11 developer builds hang when LLDB is attached at the PauseDuringLaunchToAttachDebugger dialog
Resolution: This bug is unresolved
It is not possible to launch the Pro Tools 11 development build from a debugger
Resolution: This bug is unresolved
Plug-in preset menu takes a long time to load with many presets
Resolution: This bug is fixed as of Pro Tools 11.1
AAX_ePrivateDataOptions_KeepOnReset is not implemented
Resolution: This bug is unresolved
Plug-in parameters can get stuck in touched state; touch/release tokens do not always match
One race condition that could result in this bug behavior has been addressed in Pro Tools 11.1.0. However, the bug can still occur when using EUCON control surfaces due to a mismatch in touch/release tokens sent from those surfaces.
Resolution: This bug will be resolved as of Pro Tools 11.1.3. It is unresolved in Pro Tools 10
AAX_eProperty_Related_Plugin_List doesn't work when using with AAX_eProperty_SampleRate.
Resolution: This bug is fixed as of Pro Tools 11.1
AAX plug-ins whose context field IDs are not defined in Describe cause a crash in Pro Tools
Resolution: This bug is unresolved
AudioSuite GUI work causes audio playback glitches and stutters
Resolution: This bug is due to a design limitation in Pro Tools and there are no plans to address this behavior. The bug only occurs when Previewing audio through an AudioSuite plug-in that performs expensive calculations in its GUI routines.
If an AAX plug-in does not declare all the fields in its context block, undefined behavior may occur (possibly a crash)
Resolution: This bug is fixed as of Pro Tools 10.3.8 and Pro Tools 11.0.2
On Windows, VSTGUIv4 plug-in GUIs do not receive key events (PT11 only)
Resolution: This bug is addressed with a patch to the AAX SDK's VSTGUI extension implementation as of AAX SDK 2.1.0
Session tempo should be available during EffectInit()
Resolution: This bug is unresolved
Pro Tools does not respond to SetParameterNormalizedValue() while offline bouncing
Resolution: This bug is fixed as of Pro Tools 11.1. However, note that we do not recommend implementing linked parameters using direct calls to SetParameterNormalizedValue(). For an explanation of the correct approach to parameter linking, see Linked parameters, with examples provided in the SDK example plug-ins.
Undo key events do not reach plug-ins (Windows)
Resolution: This bug is unresolved
Use of DigiTrace results in eTISysSwapScriptTimeout
Resolution: This bug fixed as of Pro Tools 11.1
DSH can't load Hybrid DSP plug-ins without acquiring the DSP deck
Resolution: This bug is due to a design limitation in the DAE dish and it will not be resolved.
This series of commands will fail for the DSP configurations of AAX Hybrid plug-ins:
To work around this limitation, use the acquiredeck command:
DigiTrace: AAX_TRACE_RELEASE crashes at highest optimization setting
Resolution: This bug is unresolved
DigiTrace: Only one parameter can be sent per trace on HDX
Resolution: This bug is fixed as of Pro Tools 11.1
AudioSuite: Error 1224 on AudioSuite render when significantly changing the length of a clip (Windows 8)
Resolution: This bug is fixed as of Pro Tools 11.1
AAX_ITransport::GetTimeCodeInfo returns invalid values for AAX Instruments
Resolution: This bug is fixed as of Pro Tools 10.3.7 and Pro Tools 11.0.2
Related types come up as inactive when going from HDX > Native
Resolution: This bug is fixed as of Pro Tools 11.1
AAX plug-in meters are not cleared during silence
This bug is new to Pro Tools 11. It does not occur in Pro Tools 10.
Resolution: This bug is unresolved
AAX Hybrid plug-ins cannot be opened as AudioSuite (AAE -7103 error)
Resolution: This bug is fixed as of Pro Tools 11.1
Incorrect audio buffer length provided when a native plug-in (erroneously) registers AAX_eProperty_AudioBufferLength
Resolution: Since this is an unsupported plug-in configuration this bug will not be fixed
Re-add support for AudioSuite "progress" dialog re-naming (was supported in Pro Tools 9 and earlier)
Resolution: This bug is unresolved
AAX MIDI plug-ins' MIDI channels are not uniquely labeled
Resolution: This bug is unresolved
Native engine strides by 2048 samples at 96kHz (expect <= 1024)
Resolution: This bug fixed as of Pro Tools 11.0.1
AAX_IHostProcessorDelegate::GetAudio() responds to invalid iLocation as if everything succeeded
Resolution: This bug is unresolved
AAX_IHostProcessorDelegate::GetAudio() ignores input audio buffer parameter
Resolution: This bug is unresolved
Plug-ins defining AAX_eProperty_RequestsAllTrackData quit when processing a timeline region with no audio
Resolution: This bug is fixed as of Pro Tools 11.0.2
Failures returned by 3P AAX-AS PIs in Pre- Analyze/Render are not used by the host
Resolution: This bug is fixed as of Pro Tools 11.1
AudioSuite: plug-in parameters are not changed upon 1st click after you click Bypass. [Win]
Resolution: This was found to be an issue in certain plug-ins with JUCE-based GUI implementations. In JUCE, the real-time variants of the of the modifiers key getter method can cause seemingly unrelated problems with the responsiveness of the GUI. In this instance, the symptom was that plug-in parameters would not be changed on the first click inside the GUI window.
The workaround for this issue, and for other unusual GUI behavior in these plug-ins, is to always use juce::ModifierKeys::getCurrentModifiers(); do not use juce::ModifierKeys::getCurrentModifiersRealtime().
Sample rate specific plug-ins cause Pro Tools to throw a misleading error message when opened in non-supported sample rate sessions
Resolution: This bug is fixed as of Pro Tools 11.1
Make automation link by Parameter ID instead of Parameter Name. Fall-back to Parameter Name if no match
Resolution: This behavior is supported starting in Pro Tools 11.1
Stereo instrument plug-ins: "MIDI Node" field in plug-in window header disappears when insert is dragged to a new slot
Resolution: This bug is unresolved in Pro Tools and will not be fixed for the foreseeable future.
After making a Preview pass, AudioSuite plug-ins no longer make calls to InitOutputBounds()
Resolution: This bug is fixed as of Pro Tools 10.2.1
AAX plug-ins receive meaningless Clock data on Native decks, and less-than-ideal data on DSP decks
Resolution: This bug is fixed as of Pro Tools 10.2
AAX VI Issue - All AAX VIs do not have MIDI Nodes
Resolution: This bug is fixed as of Pro Tools 10.2
AAX VI Issue - Instrument Tracks do not automatically map to the AAX VI that is instantiated on them
Resolution: This bug is fixed as of Pro Tools 10.2
Incorrect error message when power is not connected to HDX card (EDIT: occurs with pre-A1 HDX prototypes only)
Resolution: This bug will not be resolved
Some plug-ins' DSP Instance counts are much lower in Pro Tools 10.2 than in Pro Tools 10.1
Resolution: This issue affects plug-ins that employ more than one buffered data port and that support many instances per DSP chip on HDX. As of Pro Tools 10.2, there is a limit of 164 buffered data ports per DSP (this is equal to the total I/O limit per DSP.)
To work around this issue, use as few data ports in your plug-in's algorithm context as possible. Note that DMA transfers on HDX occur in 128-byte chunks, so packet sizes below 128 bytes do not increase transfer efficiency on HDX.
See this forum post for more information: https://developer.digidesign.com/index.php?L1=5&L2=13&L3=56&LC=/viewtopic.php?f=93&t=228
Plug-ins write automation with pairs of updates, causing undesired "stepping" in recorded automation
Resolution: This bug is fixed as of Pro Tools 10.2 and 10.1.1
Poor plug-in performance with multiple processors selected; plug-ins are not consistently assigned to the same worker/thread by DAE, leading to cache thrashing.
Resolution: This bug is fixed as of the audio engine changes in Pro Tools 11
AAX DSP plug-ins with same DLL name are not properly labeled in the System Usage window
Resolution: This bug is fixed as of Pro Tools 10.2
Mouse cursor does not reliably update when positioned over plug-ins. Instead the mouse cursor shows the current Edit Tool.
Resolution: This bug is fixed as of Pro Tools 10.2
GUI elements fill window in some 3P AAX plug-ins GUIs on Windows
Resolution: This bug is fixed as of Pro Tools 10.2
pluginGestalt_SupportsControlChangesInThread is not properly implemented for AAX plug-ins
Resolution: Parameter updates are handled by a non-main thread for all AAX plug-ins as of Pro Tools 10.1
Silent failure when plug-ins attempt to register components with different platform support
Resolution: This bug is not yet resolved. This is an expected constraint, but the silent failure is unexpected
GetCurrentTDMSampleLocation() returns the wrong value.
Resolution: This bug is fixed as of Pro Tools 10.2
When an AudioSuite plug-in modifies the output audio length, the audio is not positioned at the correct location
This bug is due to AudioSuite handles processing. A plug-in that modifies the output audio length may move audio from the handle region into the visible clip region, which is unexpected behavior from the user's perspective.
Resolution: This bug is unresolved. The workaround is for plug-ins that experience this issue to disable AudioSuite handles, thereby only processing the audio that the user sees on the timeline.
eFicGestalt_GetASPreHandleLength and eFicGestalt_GetASPostHandleLength return the wrong handle length values upon a call to AnalyzeAudio with 'WHOLE FILE' mode selected
Resolution: This bug is fixed as of Pro Tools 10.2
Highlight info sent to plug-ins before GUI is created.
Resolution: This bug is fixed as of Pro Tools 10.0
Crash on Pro Tools quit when plug-in GUI is open (OSX)
Resolution: This bug is unresolved in Pro Tools and will not be fixed for the foreseeable future. Plug-in workarounds are demonstrated in the DemoGain_GUIExtensions example plug-ins:
a) Separating all Obj-C elements into a separate bundle that is loaded manually by the main plug-in bundle (see DemoGain_Cocoa) b) Applying an NSAutoreleasePool to the AAX GUI object destructors (see DemoGain_VST and DemoGain_JUCE)
See this forum post for more information: https://developer.digidesign.com/index.php?L1=5&L2=13&L3=56&LC=/viewtopic.php?f=93&t=228
AAX MIDI plug-ins do not get correct MIDI routing on Instrument tracks
Resolution: This bug is fixed as of Pro Tools 10.2
AAX: Configurations with duplicate PlugInID properties are silently hidden with no error
Resolution: As of Pro Tools 10.2, duplicate PlugInID properties will trigger the following DigiTrace log:
DTF_AAXHOST DTP_NORMAL
"AAXH ERROR: Attempted to add new configuration with duplicate ID: %x" existingID
MIDI packet alignment is not identical between DAE and AAX
This is a known bug in Pro Tools 10.0. This bug results in corrupted MIDI stream data to AAX plug-ins.
Resolution: This bug is fixed as of Pro Tools 10.0.1
Groups do not follow changes to "Inserts" Globals group settings
Resolution: This bug is unresolved
Re-add support for AudioSuite "progress" dialog re-naming (was supported in PT 9 and earlier) (see PTSW-159768)
Resolution: This bug has not yet been resolved.
AAX SDK Win32 GUI example plug-in does not draw correctly
Resolution: Duplicate of PTSW-156286 (see above.) Resolved as of Pro Tools 10.2.
|
1.8.5
