aax plug-in burnthrough gridlearn-cdn.avid.com › cpp_toolkits ›...

1 AVID AAX Plug-In Burnthrough Grid

CONFIDENTIAL INFORMATION OF AVID TECHNOLOGY, INC.

Welcome to the AAX Plug-In Burnthrough Grid!

This document provides an overview of what tests you need to perform depending on the type of Plug-In, how tests

are divided and recommended session requirements.

How tests are divided:

The current test grid is divided in two main sections; one for Pro Tools and one for Media Composer. Each section

features a comprehensive list of test cases which cover basic functionality between the Plug-In you want to validate

and the Avid® software.

Each page contains one or more sections inside. Each section covers a particular area or functionality with a list of

steps to follow and what is the expected result.

What tests you need to perform:

Depending on the type of Plug-In you are planning on submitting, some tests may apply or not and others are optional

but recommended.

Please refer to the matrix featured in the Pro Tools® and Media Composer® cover pages to know which tests to

perform. The Media Composer tests should complement the ones covered with Pro Tools.

Notes:

The tests listed on the following pages focus on Plug-Ins available in both AAX DSP and AAX Native scenarios:

- If a test does not specify whether to test the AAX DSP or AAX Native version, the test should apply to both.

- If a test specifies testing on AAX DSP or AAX Native and the current product does not support one of these Plug-In

types, the test should be performed only on the available Plug-In type.

- Even if a Plug-In does not support AAX DSP, it should always be tested on a Pro Tools HDX system if one is available.

Historically we have found that some Plug-In issues are specific to the Pro Tools HDX environment and these issues do

not occur when using the built-in playback engine.



PRO TOOLS The following matrix details which tests are required and which recommended:

Effects Plug-Ins and others Virtual Instruments

Test 1: Installation Required Required

Test 2: Instantiation Required Required

Test 3: GUI & Save Required Required

Test 4: Audio Integrity Required Required

Test 5: Settings Required Required

Test 6: Automation Required Required

Test 7: AudioSuite Required N/A

Test 8: Auto Delay Compensation Required Required if applicable

Test 9: Virtual Instruments N/A Required

Test 10: Real World Recommended Recommended

Test 11: Session Xchange Recommended Recommended

Test 12: Control Surfaces Recommended Recommended

Test 13: Accessibility Recommended Recommended

Test 14: ReWire N/A Required if applicable

Recommended testing environment:

- Tests should be performed at multiple buffer sizes (32, 64, 128, 256, 512, 1024).

- Tests should be performed at different sample rates (44.1kHz, 48kHz, 88.2kHz, 96kHz and 192kHz are recommended).

- Tests may be performed at different bit depths (16bit, 24bit and 32bit Float).

- AAX DSP and AAX Native Plug-Ins should be tested on HDX systems on both Mac and Windows. Additional testing on

Native systems is recommended.



Test 1: Installation

1. Verify the installer is in a single package. Depending on the type of Plug-In, the package can contain more than one component inside:

If the Plug-In contains several features, you should be able to choose which ones to install during the installation process.

If the Plug-In contains a sample library or similar, that content should be in the same package as the installer and not placed separately.

2. Verify that the installation stages contain proper information about License Agreement, requirements, and content that will be installed.

3. Verify the Plug-In name matches at all stages of installation.

4. In case of having different binaries for AAX DSP and AAX Native or Full and Lite versions, the installer binary name and Plug-In name during the

installation stages should differentiate each version.

5. If the Plug-In uses a sample library or other related content, verify that that content is installed at the correct location.

Expected behavior: Content is installed in the correct location and the Plug-In looks for the content at same location.

6. Verify the Plug-In Presets are created.

Launch Pro Tools and Instantiate the Plug-In (or open the AudioSuite version).

Open the Presets list.

Expected behavior: The Plug-In presets should be available. You can also verify that they have been created by checking the Plug-In settings

location: /Documents/Pro Tools/Plug-In Settings/.

7. Instantiate the Plug-In on a track and save the session (if the Plug-In is AudioSuite only, open the Plug-In window). Close session.

Uninstall the Plug-In.

Re-Open the session.

Expected behavior: Plug-In is no longer available in the session.

8. Reinstall Plug-In and open the session from the previous step.

Expected behavior: Plug-In should be active and work correctly.



Test 2: Instantiation and De-Instantiation

1. Open or create session.

2. Import audio (if needed).

3. Create audio track.

Start with the lowest channel width supported by the Plug-In (mono, stereo, etc.).

4. Open System Usage Window located in Pro Tool's Window Menu.

Place the System Usage Window to side of screen for quick reference.

5. (AAX DSP) Instantiate (insert) Plug-In.

Verify that the selected Plug-In usage matches the specs.

Each DSP type may require different usage %.

6. (AAX DSP) De-Instantiate (remove) Plug-In.

Expected behavior: The Plug-In usage % is cleared and the DSP is available.

7. Once removed, (AAX DSP) insert a different Plug-In onto the same DSP chip.

Expected behavior: DSP memory has been completely cleared and new DSP usage percentage is displayed.

8. Start audio playback.

Repeat steps 5 & 6 during playback.

Expected behavior: There should be no unexpected errors or audio glitches, etc.

9. Perform steps 5 & 6 using the Plug-In's AAX Native version, checking for anything unexpected in the CPU usage meter (in System Usage Window).

Expected behavior: CPU usage should not be significantly different when testing with/without audio playback.

CPU usage should be reasonably consistent with other Plug-Ins of the same category/complexity.

10. Check Dynamic Plug-In processing is working (on AAX Native Plug-Ins only).

Playback the last portion of a clip and continue playback after it has finished.

Expected behavior: When there is no more signal to process, the Plug-In's CPU usage should drop down in less than 10 seconds.

Dynamic Plug-In Processing will not be enabled for Virtual Instruments, as well as Plug-Ins in the "Other" category (only in Pro Tools 11).

11. Create 2-3 tracks for every channel width the Plug-In supports.

12. Verify that the Plug-In is available for all channel/stem widths (According to Plug-In Specs).

Insert each "channel width" Plug-In at rest and during playback.

Verify both AAX Native and AAX DSP version availability.

13. OPT (Mac) / ALT (Win) + instantiate across multiple (and different widths of) tracks.

Expected behavior: OPT + instantiate should only insert on similar track widths.

ex. OPT + instantiate on mono tracks should insert on ALL mono, but not on stereo, 5.1, etc.



14. If the Plug-In supports AAX DSP and AAX Native:

Toggle the Plug-In between AAX DSP and AAX Native (using the pop-up menu in the Plug-In window).

Use the onboard "DSP/Native toggle" button.

Try both "toggle" options during playback and at rest.

Expected behavior: Plug-In should toggle from AAX DSP to AAX Native and back without errors.

15. If the Plug-In has separate binaries for the "Full" (DSP+Native) or "Native" versions:

Instantiate the full AAX DSP version and AAX Native (if available).

Save and close the session.

Remove the "Full" binary and install the Native version.

Expected behavior: The Native version should open in place of the "Full" version.

16. Make the Plug-In Inactive and then Active again.

Expected behavior: CPU / DSP memory usage % should drop when Plug-In is made inactive (Native / DSP respectively).

When a Plug-In is made Active again, CPU / DSP memory usage % should be re-allocated.

17. Perform the DSP re-shuffle test:

Fill the DSP chips with several (AAX DSP) instances of Plug-Ins.

Perform a re-shuffle.

Expected behavior: There should be no errors.

*If Validator test tool is available, a Cycle Count test can be used to test last step.

18 .In Pro Tools "Preferences » Display", select "Organize Plug-In Menus by Category".

Expected behavior: The Plug-In is located at the correct category of the Plug-In insert list.

In Pro Tools "Preferences » Display", select "Organize Plug-In Menus by Manufacturer".

Expected behavior: The Plug-In is located at the correct manufacturer menu.



Test 3.1: GUI Accuracy and Responsiveness

1. Upon initial Instantiation, verify the UI displays as expected (per Design Spec).

2. Close & re-open the UI multiple times, test at rest and during playback.

Display several Plug-In windows simultaneously.

Hide and show all floating windows (CTRL + ALT + START + W on Win / CMD + OPT + CTRL + W on Mac). Test at rest and during playback.

Expected behavior: UI should redraw as expected when windows are restored.

3. Adjust various parameters.

Expected behavior: The response of the controls should be as fast or slow as expected.

4. Adjust all dynamic features (EQ graph, moving UI components).

Expected behavior should be as per design specs.

5. After adjustment, close and re-open UI.

Expected behavior: There should be no UI issues and all UI should be consistent with latest changes.

Dynamic (moving) displays are still functioning during playback.

6. Save and re-open session with Plug-In UI open.

7. Verify Plug-In dynamic graphics redraw correctly.

You can download a free measuring tool like Quartz Debug, Disable beam sync, Open Frame meter, or Fraps.

Measure the FPS and refresh rate of an AVID Plug-In with UI graphics similar to your Plug-In for reference.

Measure your Plug-In with the same tool under the same circumstances (the same session, playback engine and settings).

Expected behavior: FPS and redrawing time should be similar and there should be no unexpected delays.

Test 3.2: Shortcuts

1. CMD + OPT + CTRL + Click (Mac) or CTRL + ALT + START + Click (Win) on each parameter.

Expected behavior: This should reveal a pop-up automation menu.

2. Automate each parameter using its automation pop-up menu.

Expected behavior: Parameters are highlighted.

3. Check that the "Fine" control mode works when CMD (Mac) / CTRL (Win) clicking to modify a parameter value.

4. OPT (Mac) / ALT (Win) + Click, sets parameter value to default.

5. CMD + CTRL (Mac) or CTRL + START (Win) + Click on an automation enabled parameter to display the lane in the timeline.

SHIFT + Click on a parameter to temporarily link it between channels and apply the new value to both channels.

6. CMD + CTRL (Mac) or CTRL + START (Win) + Click on an automation enabled parameter to display the lane in the timeline.

7. If a Plug-In is part of a tracks group and the parameters are linked:

CTRL (Mac) / START (Win) + Click to temporarily unlink and modify parameter value.



Test 3.3: Save and re-open session functionality

1. Insert Plug-In.

2. Save, close and re-open the session.

Perform this with the Plug-In UI open.

Perform this with Plug-In UI closed.

Perform this with AAX DSP and AAX Native versions (if Plug-In is available in both formats).

Expected behavior: DSP usage is released and reallocated (AAX DSP only).

3. Start playback after re-opening session.

Expected behavior: Plug-In passes and processes audio as expected.

4. Compare parameters values and processed signal sound before and after re-opening session.

Expected behavior: Parameter changes and the processed signal should remain consistent when re-opening the session.

5. Verify that saved settings remain selected and active.

Expected behavior: A saved/selected preset should not be in italics.

An altered preset will show in italics.



Test 4.1: Master Bypass Transparency

Designed to test if the Plug-In Bypass is a 100% true bypass, also tests DSP delay reporting.

1. Turn ON "Delay Compensation" in the Options menu.

2. Create audio track and import audio. Make sure the track has an active output bus assigned.

3. Duplicate track.

4. Insert AAX Native version of Plug-In on Track 1.

Select Bypass on Plug-In.

5. Insert an AAX Native Plug-In with Phase Invert functionality in the second track. (For example, EQ3 1-Band).

Select Phase button on Plug-In.

6. Start playback.

Expected behavior: No audio should be heard (note: volume and pan settings should be identical).

7. Replace AAX Native version of Plug-In with AAX DSP version.

8. Replace EQ-3 1-Band with Time Adjuster ( DSP ) as well.

9. COM (Mac) or CTL (Win) click the "actual" volume displays.

This function rotates between 3 displays ((Volume, Peak, and DSP delay).

10. Set the adjuster on Track B to match the delay on Track A's display.

Note: you may need to de-activate/re-activate the Time Adjuster in order for the changes to reflect Track B's display.

11. Verify the Phase button on the Time Adjuster is selected.

12. Start playback.

Expected behavior: No audio should be heard (note: volume and pan settings should be identical).

Warning: Filtering audio can be expected when testing Modulation or Spatial Plug-Ins.

*If Validator test tool is available, a cancellation test can be used to test bypass transparency.

Test 4.2: Does the Plug-In sound as expected

1. As outlined by the Plug-In’s specification, does the Plug-In "sound" like it supposed to?

2. Do specific controls "do what they are supposed to"?

3. For newer Plug-Ins, it may be necessary to compare output or performance against known data (real world HW, example files, or marketing spec).

4. For Version updates, does the newer revision perform the same as earlier releases?



Test 4.3: Live Input Monitoring

1. Instantiate the Plug-In on a record enabled track with a live Input.

2. Record audio signal and then play back the recorded track.

3. Instantiate the Plug-In on an audio track, turn on Input Monitoring and feed that track a live signal.

Expected behavior: You should hear the signal being processed by the Plug-In both when monitoring the Input and while recording and playing back afterwards.

Test 4.4: Bounce

1. Instantiate the Plug-In on an Audio Track with an audio clip, modify Plug-In parameters and perform a Real-Time Bounce.

Import the Bounced track back to the session.

Verify that the Bounced audio matches the original audio with the Plug-In, and that there are no unexpected clicks or pops.

2. Repeat the previous step but perform an Offline Bounce instead.

3. Compare the Real-Time Bounce and the Offline Bounce clips to make sure they sound as close as possible.

*Slight differences could be expected depending on the Plug-In specs.

Test 4.5: Commit

1. Verify that the Plug-In is correctly rendered into a new track when performing a Commit operation.

Expected Behavior: New track should contain the processed audio clip reflecting the Plug-In settings. There should be no unexpected glitches or noises.

2. Perform Commit on:

- Audio Track

- Instrument track

- Aux Track

3. Perform Commit operations on the following track widths:

- Mono

- Stereo

- 5.1 (if applicable)

3. On Instrument tracks, perform Commit operations by both menu/contextual menu option and Drag and Drop into an audio track.

Expected Behavior: Both operations should render the same results.

4. If Plug-In supports Multiple Output Functionality, verify that the Commit operation works for all Plug-In Aux Outputs assigned.

Expected Behavior: Each track which receives its input from one of the Plug-In's Aux Outputs should be rendered into a new track.



Test 4.6: Track Freeze

1. Perform a Freeze operation on a track with the Plug-In instantiated.

Expected Behavior: The Plug-In should be remain inactive, GUI inaccessible and the frozen audio on the clip should play back the processed audio

matching the parameters set up at the moment of freezing.

2. Perform Freeze on:

- Audio Track

- Instrument track

- Aux Track

Expected Behavior: All tracks should render the same result.

3. Perform Freeze operations on the following track widths:

- Mono

- Stereo


4. Insert 2 instances of the same Plug-In on an audio track with an audio clip.

Right click on the first instance of the Plug-In and select "Freeze up to this Insert".

Expected Behavior: The track should be frozen. The first instance of the Plug-In should be frozen as well, being inaccessible. The second instance

of the Plug-In should be accessible and allow changes. The audio should be affected by the Plug-In.



Test 5.1: Settings

1. Insert Plug-In.

2. Factory Default should be listed in Plug-In Setting Manager (assuming you start with fresh session and prefs).

3. Adjust some parameter controls.

Expected behavior: Factory Default setting name should change to italic.

4. Save (& rename) setting file.

5. Toggle between default and saved setting and any "provided" settings.

Verify that Plug-In settings change accordingly.

Expected behavior: Each setting is displayed in "standard font (no italic).

6. Copy setting from one instance and paste to another.

7. Import a setting:

First, locate the Plug-In settings folder.

...User/Documents/Pro Tools/Plug-In Settings.

Drag one of the setting for the selected Plug-In to the desktop.

Return to the Plug-In and select "Import setting".

Navigate to desktop and import the setting.

Expected behavior: Imported setting should be loaded and the setting should be present in the presets list.

8. With preset or setting selected, save, close, and reopen the session.

Expected behavior: Setting is still selected and shows up as expected.

9. Instantiate 2nd instance.

10. Adjust settings but do not save it as a "setting".

A. *Open session at different sample rate.

B. *Open that session on a different OS (OSX vs. Windows).

C. *Open that session of a different Pro Tools platform (HD vs. Non-HD).

Expected result: Settings should be consistent across all of these changes.

Test 5.2: Parameter Accuracy

1. Move each Plug-In control.

Expected behavior: The parameters should allow to be adjusted through the FULL range - as stated in the design spec.

2. Check that the parameters "value" (ms, vol, freq, etc.) is correct (Ex. 1.34 kHz is better than 1340 hz).



Test 5.3: Compare Functionality

The "Compare light" behaves like a A/B switch to toggle between the last recalled / "saved" setting and the current status of the controls.

1.Insert Plug-In.

Expected behavior: Plug-In should be at "factory default" or User setting.

Compare Light should be UN-lit.

Name of Preset/setting should be in normal text.

2.Make any change to any control on the Plug-In.

Expected behavior: The Compare Light should light up. The name of the Preset/Setting should now be italicized.

3.With the Compare light ON and the preset name italicized:

Click the Compare light.

Click it again.

Expected behavior: The Plug-In parameters toggle between the "saved" preset setting and the altered "compare" state.



Test 6.1: Automation

1. Insert Plug-In.

2. Auto-enable all Plug-In parameters:

CTL + OPT + COM (Mac) or CTL + START + ALT (Win) + click the AUTO button.

Verify that the controls also show up (& can be added/removed) from the AUTO enable window (AUTO button, next to SAFE).

3. Put track into automation Write, Touch, or Latch mode.

4. Start playback.

5. Make automation pass, "touching" all controls.

6. Stop and Re-start playback.

Expected behavior: The controls follow the automation moves you made during the previous pass.

7. Repeat with 2nd instance of Plug-In.

Expected behavior: The automation from one Plug-In does not affect the other during playback.

8. Disable the automation parameters:


Expected behavior: A Dialog box pops up asking: "Are you sure? You will lose all automation", etc.

9. Re-enable the automation parameters:


10. Make another pass of automation:

Make long, slow, FULL RANGE automation moves.

Test all applicable controls.

11. View the automation playlist for each control in the Edit Window.

Expected behavior: There should be no "stepping" and the movement should be smooth.

The value or name of the viewed playlist should be correct when touched manually.

12. Create some automation moves manually from the playlist (Edit window).

Make some aggressive automation changes as well (hint: use the Free Hand Pencil Tool).

Expected behavior: These adjustments should be reflected in the Plug-In GUI.

13. OPT Copy the automated Plug-In to another insert.

Open both plug ins side by side (target mode) to view automation.

Expected behavior: The automation should be the same for both inserts.

14. Remove the 2nd (OPT copied) instance.

Click "OK" when asked "Are you sure?".

Expected behavior: The original instance's automation is unaffected.



15. Reveal the Plug-In's delay compensation settings in the Pro Tools Mix or Edit window.

While playback is stopped, edit every parameter in the Plug-In and observe whether it affects the Plug-In's latency.

Test edits to each such parameter during playback and verify that changing these parameters during playback does not change the Plug-In's latency

until playback is stopped. This verification must be done using a bus to a separate record track; the delay compensation displayed by Pro Tools will not update during playback,

so visual confirmation using this display is not possible.

Each parameter that affects the Plug-In's latency must not do so during playback. However, the Plug-In may erroneously change its algorithm

in a way that impacts its latency.

Automating parameters that affect the Plug-In's latency is strongly discouraged. It is legal for such parameters to be automatable, but special

care must be taken with automatable parameters to ensure that they do not impact the Plug-In's latency during playback

Test 6.2: Automation Cancellation

1. Create 2 audio tracks and place an audio clip in the first one.

2. Instantiate the Plug-In in the first track.

3. Enable automation for all parameters and manually write automation (you can use the pencil tool).

4. Route the first track Output to the second track Input.

5. Do a record pass.

Expected behavior: Recorded audio on the second track has the processed signal from first track.

6. Route both tracks outputs to Monitoring output.

7. Instantiate the EQIII Plug-In on the second track and invert phase.

8. Start playback.

Expected behavior: Expected behavior: Signals should cancel and no audio should play back.

Test 6.3: MIDI Mapping (if applicable)

If the Plug-In allows MIDI mapping for external controllers:

1. Instantiate the Plug-In on any track.

2. Create a MIDI track and assign the MIDI output to the instantiated Plug-In.

3. Right click (or CTRL + Click on Mac) on each parameter of the Plug-In, and select "Learn" to map to the controller's knobs/faders/keys.

Modify parameters with the controller and write automation.

Expected behavior: You should be able to effectively control the full range of the parameter mapped.



Test 7: AudioSuite

AudioSuite tests should be performed on both short and long clips in order to ensure correct functionality.

1. Verify that the Plug-In is available in the AudioSuite (AS) Menu.

2. Make an audio selection (mono or stereo).

3. Open the AudioSuite Plug-In.

4. Select Preview (you should hear the selected audio).

5. Make adjustments to the Plug-In parameters.

Note: In general, parameter changes in AS take a bit longer to take affect that in standard Plug-Ins.

6. Select Bypass (next to Preview).

Verify that the changes are bypassed.

Let the bypassed preview loop more than once to ensure bypass remains active.

7. Select any factory or user presets.

Expected behavior: The preset changes the Plug-In settings.

8. Select Process.

Expected behavior: If Use in Playlist is highlighted (it is by default), the processed file should be placed at your selection location.

9. Play the new file using the Pro Tools transport.

Expected behavior: The processed signal should have been correctly rendered.

10. Verify that the Plug-In specific Suffix was added to the processed file.

Example: Audio 1 is now called "Audio 1-01 EQ7", etc.

11. For Reverb and Delay Plug-Ins:

Verify that the Reverse function processes the signal accordingly.

12. Process a clip with the Handles value set to 0.0.

Undo and repeat the process with Handles set to different values.

Expected behavior: Processed signal should correspond the original one (signal should not offset or stretch depending on Handle values).

13. Trim out the clip sides out left and right as much as possible after processing the signal with different Handles values.

Expected behavior: Clip Handles length matches Handles value set in AudioSuite window and expected audio is present in the Handle regions;

no unexpected silence gaps at beginning or end of the handles.

14. If available, apply the Reverse function with different Handle values.

Trim out the clip sides out left and right as much as possible.

Expected behavior: Clip Handles length matches Handles value set in AudioSuite window and expected audio is present in the Handle regions;

no unexpected silence gaps at beginning or end of the handles.



Test 8.1: Auto Delay Comp (ADC) 1

Auto Delay Compensation can be turned on/off in the Options menu.

1. Turn on "Delay Compensation" in the Options menu.

2. Make sure to have the ADC window showing in the Mix window:

View > Mix Window > Delay Compensation.

3. Create 2 Audio, 2 Aux, 1 Master fader (track).

Expected behavior: In the Mix window, tracks should display 3 lines for delay compensation (Master track should display only 1 line):

Top line: Delay on that track

Mid line: Manual Adjustment

Bottom line: Auto Delay

The ADC window in each track should show:

Audio Tracks: 3 zeros

AUX tracks: 3 zeros

Master fader: 1 zero

4. OPT + CMD (Mac) or CTL + ALT (Win) click the Volume display ONCE.

Expected behavior: All of the tracks should now show "O" (DSP delay) instead of "0.0" (volume).

5. Add a Plug-In to one of the Audio tracks and look at the ADC window for the track with the Plug-In.

Expected behavior: The amount of samples of delay are displayed in first line (dly) and zero is displayed in the last line (cmp).

6. Look at the other audio tracks.

Expected behavior: First line (dly) should display a value of zero and the last line (cmp) should have the same value as the "dly" on the track with the Plug-In.

Aux tracks should show the same results as well. Master track should display zero for "dly".

7. Add some additional instances to the track with the Plug-In.

Expected behavior: "cmp" values for the other track should make up for additional "dly".

8. If the DSP delay on the track (or any single Plug-In) exceeds the maximum of the ADC setting:

Expected behavior: The numbers in the ADC track display will turn red.

9. Bypass the Plug-In.

Expected behavior: Delay compensation should not change. Plug-Ins should have the same delay when they are bypassed.

Note: The Delay Compensation value at the bottom line could be slightly different than the amount of Delay in the track with the Plug-In.



Test 8.2: Auto Delay Comp (ADC) 2

1. Create a session, import an audio clip and instantiate the Plug-In.

2. Map the output of the track to a new audio track and record a few bars with Delay Compensation OFF.

3. Repeat the step and record into a new track with Delay Compensation ON.

Expected behavior: The signal recorded with Delay Compensation ON, aligns with the original signal. Zoom in to verify the waveforms align.

The signal recorded with Delay Comp off, should be offset by the amount of samples displayed in the Delay Compensation window in the Mix Window.

4. Instantiate EQ3 1-Band on the track that recorded the audio, invert phase and start playback.

Expected behavior: Signal should be cancelled and no audio should be heard.

5. Repeat the process using sends to new tracks instead of mapping the output.

6. Repeat the process using chained sends (Aux tracks to Audio tracks).



Test 9.1: Virtual Instruments Instantiation (if applicable)

The tests listed below are specific to Virtual Instruments only. These tests are complementary to tests included in other pages.

Please refer to the following pages to cover the remaining testing areas:

GUI & Save, "Audio Integrity" (Test 2 and Multiple Output Functionality test), "Settings", "Automation", "Rewire", "Real World", "Session Xchange" and "Control Surfaces".

The following test should be covered on all track formats supported by the Virtual Instrument.

Verify that VI is not available on tracks with formats that are not supported.

1. Instantiate the Virtual Instrument on an Instrument Track.

Enable Instrument view on either the Mix or Edit window.

Verify that the MIDI Output is automatically assigned to the VI Plug-In.

Import a MIDI clip into the Instrument Track and playback to verify that audio can be heard.

2. Instantiate the Virtual Instrument on an Aux track.

Create a MIDI track.

Verify that the Virtual Instrument can be selected in the MIDI track Output.

Import a MIDI clip into the MIDI Track and playback to verify that audio can be heard.

3. If the Virtual Instrument uses a Samples Library:

Upon instantiating the VI, manually check that Plug-In is looking for the Sample at the correct location.

Move the Samples library to a new location.

Back in Pro Tools, update the VI settings to look for the Samples Library in the new location.

Verify that the samples are playing back in the new location.

Test 9.2: MIDI Recording and Playback (if applicable)

1. With a MIDI controller plugged to your system, create an instrument track and instantiate the VI.

2. With MIDI Thru enabled, play some notes.

Audio should be playing back.

3. Record enable the track and record a few bars.

4. Play back the recorded bars.

5. Record a few more bars and change some parameters during the recording.

When playing back, notes and parameter changes recorded previously, should play back.

6. Right click on parameters, select "Learn MIDI CC" and assign that parameter to a specific fader/knob.

Verify that it's possible to perform changes to that parameter with the corresponding fader/knob.



Test 9.3: Virtual Instrument Bounce (if applicable)

1. Perform a Real-Time Bounce of an Instrument Track with a clip and the instantiated VI.


Verify that the Bounce audio matches the Instrument Track MIDI clip and there are no unexpected clicks or pops.

2. Perform a Real-Time Bounce of a MIDI track with a clip, routed to an Aux track with the VI instantiated.


Verify that the Bounce audio matches the MIDI clip and there are no unexpected clicks or pops.

3. Repeat steps 1 and 2 performing an Offline bounce instead.

4. Compare the Real-Time Bounce and the Offline Bounce clips to make sure they are as close as possible.

* Slight differences could be expected depending on the Virtual Instrument specs.

* Track Bounce, Commit and Freeze functionality listed in section 4.5 should also apply to Virtual Instruments.

Test 9.4: Multiple Output Functionality (if applicable)

Intended to test the "Multiple Aux output' functionality included with synth/sample plug ins.

1. Insert Plug-In on Instrument Track (this is our "Source").

2. Load sounds, banks, etc. into the Plug-In.

3. Assign individual sounds, etc. to the plug in's AUX outputs.

4. Create X amount of Aux tracks in Pro Tools.

The number is determined by the # of Aux outputs the Plug-In contains.

Example: Strike has 8 stereo outputs or 16 mono, so I would create 8 stereo Aux or 16 mono Aux.

5. Set the Aux track inputs to the Plug-In outputs listed in the pull-down menu.

6. Write or play in MIDI notes to the Source Instrument track.

7. Play back MIDI.

Expected results: The sounds routed to each Plug-In Aux output should input to the corresponding Aux input track.



Test 10: Real world processing (Recommended)

The goal is to put the Plug-In in real world situations, preferably in a 'heavy processing' session.

There is no set test procedure here. The goal is to tax the system and the Plug-In.

If you do not have a sufficient "real world" session, one example might be:

1. Open a session with 10 mono and 5 stereo tracks.

2. Insert a mono and stereo version of the Plug-Ins.

3. Write significant amount of Plug-In automation for each.

4. OPT-Copy the automated plug ins to the other inserts on the tracks.

5. Repeat until 75% of the system DSP is used. You can check this in the System Usage window (HDX Systems Only).

6. Repeat until CPU usage is approx. 50% during playback.

7. Add volume, mute, and pan automation.

8. Save, close, and re-open the session.

Expected behavior:

Audio in the session should be playing back correctly.

The automation/processing of the Plug-In is accurate (audio is processed as expected and Plug-In GUI presents no issues).

There should not be unexpected CPU errors (For example: -9128 error, 6031 error, etc.).



Test 11.1: Multi-OS, Machine, and Session Interchange (Recommended)

1. Install, insert, and open the Plug-In on all possible platforms:

OSX (Mountain Lion, Mavericks, Yosemite).

Windows (7, 8, 8.1).

Pro Tools HD/Non-HD (on HDX and Native systems).

2. Plug-In display matches Design Spec for the specified OS, etc.

Channel widths / Surround options.

DSP usage.

AAX DSP, AAX Native, AudioSuite versions.

Expected behavior: Versioning, Plug-In presets, and sample library locations follow Design Spec.

3. Using a Mac system, instantiate the Plug-In on a session and save.

Open the same session on a Windows system and continue using the Plug-In (modify parameters, start playback, bypass, make inactive, etc.).

Repeat the test starting a session in Windows and re-opening it on Mac.

Expected behavior: Session should open and the Plug-In should work without problems.

If the Plug-In is available in both AAX DSP and AAX Native, repeat the previous test, instantiating the AAX DSP version on one system and re-opening

it on a different OS with only the AAX Native version installed.

Expected behavior: Session should open and the Plug-In's AAX Native version should be active and working as expected.

Test 11.2: Session Interchange (Recommended)

For these tests, we will assume you have sessions already created, either from tests/scenarios in this grid or Real World sessions.

1. Be sure to have multiple channel widths and versions of the Plug-In:

AAX Native &/or AAX DSP.

Mono, stereo, 5.0, etc.

2. Within the session, be sure to have:

Saved presets.

Plug ins Setting (not saved to presets).

Automation of Plug-In parameters.

Inactive and Active instances of the Plug-In.

3. Save and close the session.

4. Transfer the session to another system and open.

Expected behavior: Session opens on different systems and all areas mentioned on steps 1 and 2 behave the same as in the original session.



Test 12: Control Surfaces (Recommended)

The Control Surfaces tests will depend on what hardware you have available.

The test listed below are general but they are common to all control surfaces and they should allow to cover essential functionality:

1. Instantiate Plug-In from the Control Surface (if supported).

Expected behavior: OLED (touch-screen display) should update with the instantiated Plug-In.

Plug In name and parameters labels should be correctly displayed/abbreviated.

2. Instantiate Plug-In from Pro Tools and check that the control surface updates.

Expected behavior: OLED should update with instantiated Plug-In.

Plug In name and parameters labels should be correctly displayed/abbreviated.

3. Make the Plug-In inactive from the Control Surface.

Expected behavior: OLED should update with current Plug-In status.

4. Make the Plug-In inactive inside Pro Tools.

Expected behavior: Control Surface OLED should update with current Plug-In status.

5. Using the encoders, set params values to minimum and maximum.

Expected behavior: Encoders should allow to set any value and it should be reflected in both Pro Tools and the Control Surface OLED.

6. Write smooth automation for parameters using the Control Surface.

Expected behavior: Automation is captured without abrupt jumps and reflects the user changes.

Please refer to AVID Plug-In SDK documentation for more information on Page Tables requirements and how to verify their content from within Pro Tools:

- AAX SDK documentation: Manual > Page Table Guide

- TDM/RTAS SDK documentation: PlugInSDKDocs_9_0.pdf Chapter 6: Control Surfaces and Page Tables (pp. 59-92)



Test 13: Accessibility

Avid encourages rich Apple VoiceOver support for visually impaired users of your AAX Plug-Ins. In 2015, we plan to include Accessibility among the

user-generated Plug-In ratings. VoiceOver support is not required for Plug-In certification or participation in Avid Marketplace at this time.

AAX Plug-In is rated from 1 to 5 with 5 representing “strong agreement” for the following criteria:

A. Plug-In can be installed and its license authorized without sighted assistance.

B. Plug-In can be registered without sighted assistance.

C. Plug-In supports Pro Tools standard methodology for save/load of presets or employs a proprietary substitute that supports VoiceOver.

D. All user-controllable parameters are speakable with VoiceOver.

E. Plug-In contains accurate page tables for Avid control surfaces compatible with Pro Tools 11 or higher.

F. Solutions Partner makes customer-facing statement in support of accessibility and provides contact information for inquiries relating to accessibility.

Using Screen Curtain for Accessibility Testing:

1. To enable VoiceOver, select Accessibility from the System Preferences, Select VoiceOver from the left hand sidebar, and check “Enable VoiceOver.”

A button at the bottom of this window activates VoiceOver training, which is highly recommended

2. To experience your Plug-In as a blind user would, you can make your Mac OS X monitor black in VoiceOver mode but pressing the keys

SHIFT + OPT + CMD + F11

For more information about Apple Accessibility development guidelines, please refer to the following links:

Apple Accessibility Development Guidelines: https://developer.apple.com/accessibility/

Google Group on Pro Tools Accessibility: https://groups.google.com/forum/#!forum/ptaccess



Test 14: Rewire (if applicable)

1. Be sure a ReWire Application is installed (Reason, Live Lite, Uno Essential, etc.).

Note: Certain Rewire apps require you to launch them in standalone mode prior to using them as a rewire Plug-In.

2. Verify that the DigiReWire.aaxplugin is installed (should be installed with Pro Tools) in the following location:

/Library/Application Support/Avid/Plug Ins/ (Mac)

/Program Files/Avid/Pro Tools/System Plug-Ins/ (Win)

3. Launch Pro Tools.

4. Create Instrument, Aux, or Audio track.

5. Insert ReWire Plug-In of choice, most likely from the Instruments category in the Insert selector.

Expected behavior: The ReWire Plug-In should allow you to set the output.

Mono ReWire Plug-Ins should let you choose either Left or Right.

6. Instantiate the ReWire app by instantiating it inside Pro Tools (if applicable).

Expected behavior: Rewire app launches (this only works with certain apps).

7. Initiate a 2nd (multiple) ReWire Application.

Insert different application on new track.

Expected behavior: Several instances of Rewire apps can co-exist in the same session.



Media Composer

The following matrix details the tests required for Media Composer coverage:

Effects Plug-Ins and others Virtual Instruments

Test 1: AudioSuite Required N/A

Test 2: Track Effect Required N/A

The tests in the Pro Tools section above cover all general Plug-In operation and usage. The tests in this

section are meant to complement the full Pro Tools test suite with additional tests of workflows which are

specific to Media Composer. A Plug-In must be tested with the full set of Pro Tools tests listed above, or their

equivalent tests in Media Composer, in addition to the specific Media Composer tests listed here, before it is

determined to be compatible with Media Composer.



Test 1.1: AudioSuite – GUI

Prerequisite: Start with a sequence with at least four audio tracks; one Mono, one Stereo, one 5.1 and one 7.1.

Load corresponding audio onto all four tracks.

If you have imported polyphonic media that is not the correct type, you can adapt the source clips to the track type with the "modify clip" command

in the bin menu.

1. Verify Plug-In name appears correctly in the "Audio Clip" column of the effect pane of the project window (Requires MC 8.5 or later).

2. Open AudioSuite Plug-In window from the Tools menu.

Activate Selected Plug-In (To Open Plug-In Properties Window).

Expected Behavior: Plug-In GUI display conforms to design specs. The Plug-In title is the correct one.

3. Following step 1, adjust the Plug-In settings.

Expected Behavior: GUI responds to changes as expected without any display errors.

4. Open and close the Plug-In window repeatedly (several times).

Expected Behavior: Plug-In window redraws as expected displaying the same graphics and settings as when closed.

5. Click and drag the Plug-In window through the screen.

Expected Behavior: There should be no unexpected UI inconsistencies or display errors. Plug-In window and GUI should follow the mouse movement.

6. If applicable, verify that the TAB order and Keyboard shortcut control works as expected.

7. If applicable, verify that the text entry works as expected.

Expected Behavior: Text entry does not return display issues and the font size and type matches the rest of the GUI.

Test 1.2: AudioSuite - Functionality Plug-In Window

1. Open the AudioSuite Plug-In window.

Verify that the following buttons are responsive and perform the expected actions:

- OK

Expected behavior: Closes the window without errors, and if a render was requested, renders the effect to the timeline.

- Preview

Expected behavior: Effect plays with best effort to real time. Verify all channels of a multi-channel clip are present in meters or other dynamic

displays.

- Bypass

Expected Behavior: When previewing, if Bypass is activated, the audio should not be affected by the Plug-In processing.

- Cancel. Change effect parameters, cancel and re-open the effect

Expected Behavior: The effect parameters should return to their pre-edit values.



- Render

- Plug-In Status Text

Expected behavior: Each button should perform the expected action without unexpected errors or strange behavior.

2. Media Composer presents one custom button, labeled "Optional" if not used. If used, verify that it is correctly labeled and work as expected.

Test 1.3: AudioSuite Tool Window

1. Drag Effect Icon button to Bin.

Expected Behavior: Bin effect preset should be created.

2. Drag icon from bin to another clip.

Expected Behavior: Verify that all effects parameters are carried across from the saved preset.

2. Render effect.

Expected Behavior: Effect should Render without any unexpected noises.

3. Verify the following Fast Menu options work without problems:

- Set Audio suite Plug-Ins –Global

- Render Audio suite Plug-Ins on Track - Global

- Remove Audio suite on Track - Global

4. Set up Plug-In with non-default settings for all parameters, drag effect icon to bin, move bin to opposite platform

(Windows to Mac or Mac to Windows), apply the preset to a new clip on the new platform.

Expected Behavior: Parameters settings should be kept between platforms and audio should be processed accordingly.

Test 1.4: AudioSuite – Render

1. Verify that AudioSuite Render works correctly on:

- Mono clips

- Stereo clips

- 5.1 clips

- 7.1 clips

Change the project sample rate (in audio project settings) and repeat the render test at each of 44.1kHz, 48kHz, 88.2kHz, and 96khz sample rates.

Expected Behavior: Plug-In should use correct Sample Rate for rendering. Effects should be rendered accordingly.

* Note: Testing at 88.2 and 96Khz requires Mojo DX or Nitris DX hardware, or capable OpenIO hardware. "Software Only" media composer will not

operate at 96Khz, even if using audio hardware that is 96Khz capable

* Note: Pay particular attention to delays duration and frequencies affected by Plug-In.

* Note: Even though Media Composer supports 32kHz, AAX Plug-Ins do NOT and no testing is required with that sample rate.



Test 1.5: AudioSuite – Timeline

1. Verify render from timeline commands "Render at Position..." and "Expert Render at Position..."

Between each render, clear the render with the "Clear Renders At Position..." command (Timeline/Render menu) .

Verify that the effect rendered can be cleared and re-rendered by using the AudioSuite Fast Menu, without the need to open the effects UI

Expected behavior: Audio should re-render identical to the first render.

If audio cannot be re-rendered identically, you should disclaim support for AudioSuite clip effects in Media Composer.

Test 1.6: AudioSuite - Hosted Presets

1. Verify on a clean install that the factory presets are accessible.

2. Verify that Plug-In presets load correctly.

3. Verify that changing presets during loop playback doesn’t cause errors (Playback may stop).

4. Verify that loaded presets play back and render correctly:

- AudioSuite Export with Plug-In Effects

- Export to WAV

5. Verify that the exported AAF sequence can be re-imported on a different system.

Expected Behavior: The AudioSuite Plug-In and its' parameters settings should remain intact.

Test 1.7: AudioSuite - Master Clip Mode

1. Drag and drop an audio clip from a bin into the Plug-In AudioSuite window. Verify it works with:

- Mono source clips

- Stereo source clips

2. Verify that width-changing effects are rendered to the correct width on output (only mono, stereo, 5.1, and 7.1 are supported).

Expected Behavior: Rendered clip width should change to the correct output width.

3. Verify that duration-changing effects render correct output durations.

Expected Behavior: Rendered clip duration should adjust to reflect the rendered effect duration.

* Note: Width-changing AudioSuite effects (such as down-mixers) will only function in Master Clip Mode; these effects cannot operate using the

standard AudioSuite Tool. Also, effects that cannot re-render from their preset values will only function correctly in Master Clip mode.

* Note: Effects that change clip length to a shorter duration should come with warning that they are best used in Master Clip Mode because the user

of a "consolidate" operation on such effects may not preserve enough of the source clip to re-render, should a re-render be needed.



Test 2.1: Track Effect UI - AAX Tool Window

1. Verify that the Plug-In can be inserted in Select Plug-In menu.

2. If real-time use is allowed, make sure the effect name appears in the "Audio Track" column of the effect pane of the project window, and in the correct category.

If real-time use is not allowed, be sure the effect name does NOT appear there.

3. Verify that the Plug-In can be switched for another in the Select Plug-In menu.

4. Verify the correct display of the inserted Plug-In.

5. Verify that Plug-In settings can be modified as per specs.

6. Verify the correct behavior of TAB order and Keyboard shortcut control (if applicable).

7. Verify text entry fields for Plug-In works as per specs (if applicable).

8. Verify the correct display of the Plug-In GUI by closing and reopening the Plug-In window repeatedly.

9. Verify the correct display of the Plug-In GUI when dragging the window across the screen.

10. Verify the correct creation of a Plug-In template by using the Plug-In template button.

Test 2.2: Track Effect UI - Timeline Track Control Panel

1. Insert a Plug-In on a track and change all Plug-In parameters. There should be no default settings.

In the Mix Tool, drag the effect to another track.

Expected Behavior: The parameters should remain intact.

2. In the Mix Tool, Option/ALT Drag the Plug-In to clone it onto another track.

Expected Behavior: The Plug-In should be cloned and the parameters should remain intact.

3. In the Timeline Track Control Panel, drag the Plug-In to another track.

Expected Behavior: The Plug-In should be moved and the parameters should remain intact.

Test 2.3: Track Effect - Playback Performance

1. Verify that there are no audio issues during playback with patched Plug-In.

2. Verify that there are no audio issues when performing JKL scrubbing with patched Plug-In.

3. Verify that there are no audio issues when performing Caps Lock mouse scrubbing with patched Plug-In.

4. Verify that Plug-In parameters can be modified during playback and that there are no audio issues in the process.

5. Verify that Plug-In can be bypassed and unbypassed during playback .



6. Verify tests 1 to 5 on the following track widths:

- Mono

- Stereo



7. If Plug-In can change the width of a track, try the permitted combinations and make sure Media Composer changes the track width accordingly.

Only mono, stereo, 5.1, and 7.1 formats are supported.

8. Verify that there are no playback issues when having different track widths with the Plug-In patched to each type in the timeline.

9. Verify that delay compensation is correctly applied:

- Up to 16K samples at 48Khz

- Up to 32K samples at 88.2/96Khz

* Note: Customers should be warned of possible A/V sync issues if more than 16K (32K) of delay compensation is required.

Test 2.4: Track Effect - Presets

1. Verify that Plug-In Factory Presets are available on a clean install.

2. Verify that Plug-In Factory Presets load correctly.

3. Create new presets in the preset menu, and make sure they can be applied to a new effect instance.

4. Verify that both Plug-In Factory Presets and User Presets can be rendered without problems.

5. Verify that it is possible to change Plug-In presets during playback (Playback can stop when doing so).

6. Drag the effect icon to a bin, and verify that it can be applied to a new effect instance by being dragged from the bin to a track in the timeline,

or to a slot in the mix tool.

7. Save the bin on one platform (Mac or Win) and re-open that bin on the other platform (Win or Mac).

Expected Behavior: The parameters of effects on tracks, or stored in bins, should carry over unchanged.

Test 2.5: Track Effect - Audio Mixdown

1. Mixdown a sequence with an AAX instance of the Plug-In into different track widths and verify that the Plug-In is rendered into the resulting

mixdown.

2. Mixdown a combination of track types with multiple instances of the Plug-In, and verify that the Plug-In is rendered into the mixdown

accordingly.

3. Verify that both AudioSuite and track insert instances of Plug-In can be applied to the same track.

To do this, you should have a clip with the AudioSuite version of the Plug-In on a track with the AAX instance of the same Plug-In.



Test 2.6: Track Effect - Export

1. Verify that a sequence including one or more AAX instances of the Plug-In can be exported as WAV.

2. Export a sequence containing one or more instances of the AAX Plug-In through AAF, and re-import. Verify that the Plug-In parameters are kept

upon import.

3. Export as AAF, and re-import into a different system type (Mac to Win, or Win to Mac). Verify that the Plug-In parameters are kept upon import.

4. Export as AAF and import into Pro Tools. Verify that the Plug-In parameters are kept upon import in Pro Tools.

© Avid Technology, Inc. 2015. All rights reserved.