Useful Console Commands

A subset of console commands (P) = Persistent, (NP) = Non-Persistent.

A detailed description of some useful console commands is available below.  Help Commands - List all console commands.

1. To write the full list out to a file, use:
   Log <filename>
   Help Commands
   Log

AcplGpuEffects true - displays current state of ACPL GPU effects processing and if installed graphics card is qualified to do so.
                                
BackRevCC - Allows Nitris and Adrenaline (ver 2.x) Color Correction effects in the currently
loaded sequence to be saved in a format compatible with Meridien (NP)
                                
CheckSequences - Checks all sequences for internal inconsistencies
                               
DumpFXSummary - Effects contained in a sequence are printed to the Console, new in MC3
                                
DumpSourceSummary - Sources contained in a sequence are printed to the Console, new in
MC v3  Edo any/acplcpu/acplgpu/hw/sw - "Effect Domain Override" forces effects processing to
occur in the specified domain.  Any = default. (NP)
                                
RepairSequences - Attempts to repair sequences with internal inconsistencies
                                
Subsys monpane debug - Allows precomputes to be loaded into source window (NP)
                                
ToggleHWDecode - Disables the hardware codecs (NP)
                                
WatchSequence - Continually check the sequence in the timeline for internal inconsistencies,
popping up a message the moment one is detected.

Very nice list. Thank you 'O mystery evangelist!

One more ...

How about adding 

setresizetype

To change the quality of 2D resizing

1.   Press Ctrl+6 (Windows) or ⌘+6 (Macintosh) to open the Console.

2.   Enter the following command into the Console and press return:

setresizetype 9

This Command changes the resize rendering method to polyphase interpolation. This is a high-quality rendering method that dramatically increases the quality of all 2D resizes (including the Picture-in-Picture effect, all the 2D keyers, and the “letterbox” Reformat effects). As this scaling algorithm takes slightly longer to process you will notice a reduction in the number of simultaneous real-time effects that are possible.

3.   To change back to anti-aliased bilinear interpolation, enter the following command into the Console:

setresizetype 8

The quality will also reset to anti-aliased bilinear interpolation when you quit and relaunch the application.

AND    TCBreakTolerance

The console is opened via the Tools menu or by doing a CMD-6 on Mac or CTRL-6 on a PC. Once the console is open:

• type: TCBreakTolerance 3
  • Where 3 is the value of the frame detection (2-12)
• Then the user hits:  ENTER
  
  

This should be entered each time the application is started up as it does not stick. The supported values are 2-12. Users who have tested this feature have found that “3” provided excellent results.

“1” is not allowed as it will return timecode breaks where there are none as it is too sensitive a setting. Users may find that “2” or “4” will work better for their tapes, but the user now has control over that setting.

AND IgnoreQTRate

Type 'IgnoreQTRate true' into the console. Avid then ignores the frame rate of the Quicktime file on import, and brings it in frame-for-frame.  This setting resets to False on a restart of Avid.

 Cool.  Keep your favorites coming, and they can be added to the list.

Um...define "internal inconsistencies".  I have no idea what that term means.

"... define "internal inconsistencies" ..."

One example would be taking a sequence backward, to an older system.  Some elements of the newer sequence might be nonsense to teh older system.  RepairSequences will strip those out, or make them workable.

I've been trying to save a text file of the full list of console commands, but the top of the list always gets truncated in the console window. Thus, when I save the log, I'm always missing commands A-F. I tried typing the following into the console, but couldn't get it to work:

To write the full list out to a file, use: 
Log <filename> 
Help Commands 
Log 

Can anyone explain how to do this? Thanks!

Randall L Rike:

"... define "internal inconsistencies" ..."

One example would be taking a sequence backward, to an older system.  Some elements of the newer sequence might be nonsense to the older system.

I've noticed that Newscutter 7.1.3.2 when right clicking on a sequence, has a new option "Create compatible copy..." which is intended to make sequences fully compatible with older versions of the application.

From the Avid Knowledge Base

How could I list all console commands?[243109]
http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243109

"... Create compatible copy ..."

Finally, a formal version of "repairsequences"

There´s any way to make a command automaticly run at startup?

For example to have ForceHDTranscode active from the beginning of the session.

The Precompute command is awesome (why isn't that default?)

:)

*Bump*

What a great thread!

RE: How could I list all console commands?[243109]
http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243109

This did not work for me, the file was blank. However, from another thread is a way to list and save all Console commands that definitely works in v.6:

http://community.avid.com/forums/t/8805.aspx

"Go to Console fast menu and select "Open log file". Select where you want your logfile stored. In the commandline type "help commands" and when the scrolling is over go to fast menu and select "Close log file" and bingo you have a copy of all console commands (nearly). There is a good document by Paul Samsons describing some of the most used commands . It can be found here. Bet regards. Beent"