Macros discussion page

From Audacity Wiki
Revision as of 18:22, 21 March 2018 by PeterSampson (talk | contribs) (James' Notes: removed "* {{todo}} Import/Export buttons to become functional" - James already has this - OOPS)
Jump to: navigation, search
This page is intended for gathering together issues and discussions regarding the transition to Macros from Chains for 2.3.0

James' Notes

  • ToDo.png Create / Add some more built in Macros in time for the May 12th Preview version.
  • ToDo.png Implement Import and Export (can be after the Preview)
  • ToDo.png (Paul?) Drag-and-drop too, for Import.
  • ToDo.png Edit button to work for commands with no parameters, so we can see their script id and type.
  • ToDo.png (Aspirational) Find-command entry box in Select Command dialog.
  • Done.png Custom names for All None etc.


IDPStatusSummary (14 tasks) ID
1854P1RESOLVEDUn-warned export file overwrite danger in 2.2.2 Chains and 2.3.0 Macros1854
549P3NEWEnh: Add missing export formats to Macros549
1709P3NEWIdentically-named effects cannot be differentiated in the Select Command dialog in Macro editing1709
548P3NEWEnh: Add export format options and export sample rate to Macro parameters548
901P3REOPENEDEnh: Macros: Noise Reduction and Noise Removal do not store parameters in a Macro901
878P3RESOLVEDBuilt in Generators don't work correctly in Chains878
876P3RESOLVEDWindows: Macros: LV2 plug-in effects only save default parameters.876
526P4RESOLVEDWindows: Chains: Select Command sets width of all columns by width of longest command526
1742P4RESOLVEDBuilt-in Macro name "MP3 Conversion" does not translate1742
1793P4RESOLVEDAutomatic zoom to fit of imported audio does not work in Chains1793
1237P4RESOLVEDMacros: Inconsistent per-platform behaviour cancelling in-progress Macro applied to project.1237
1745P4RESOLVEDNames of commands in Chains do not translate, and the English uses ugly CamelCase1745
1807P4RESOLVEDNyquist Prompt Scripting command is not functional1807
1238P4RESOLVEDChains: Non-interactive "Apply Chain" window obscured.1238

Mac crash on second evocation of Tools > Macro

I don't think this is yet logged on Bugzilla

A second related instance is reported on the Forum Bug: Audacity 2.3.0 crashes on second entry to Manage Macros

Regression testing Macros versus Chains

As outlined in recent email on Quality - germane points to be summarized here.

Macros and Chains behave differently on Export

We need to decide what is desired-behavior on Export from Macros.

Bug: nested "cleaned" folders

Not only do we get the regression of interrupting the automated process with requests for user input - we also get the bug of the nested "cleaned" folders. This bug is not yet logged on Bugzilla pending discussions on desired behaviors.

Export as M4A(AAC) and AIFF

These commands to be added to the available commands for Macros.

Parameter setting for "Export as ..." in Macros

There is no ability to set parameters for the "Export as ..." commands in Chains

Bill wrote: I seem to recall we’ve been bitten by the “use the last settings made by the user for this command” before. That is, the user sets up a chain containing an effect, later uses the effect with new settings, then finds that the chain uses these new settings rather than the ones in effect when the chain was created/edited. I think it is much safer to explicitly save the settings in the macro step.

Persistence of Manage Macros and Macros Palette dialogs

James has fixed this so that the Manage Macros and Macros Palette dialogs remain on-screen while a Macro is being applied to the current project.

The Manage Macros and Macros Palette dialogs are temporarily removed from the screen while a Macro is being applied to a file,

These are desired and intended behaviors

Bug 1854 - Un-warned export file overwrite danger in 2.2.2 Chains

Apply Chain can silently overwrite an existing file of the same name in the "cleaned" folder - and this is done with no warning to the user (as one would normally expect with potential file over-writes.

The current behavior of 2.3.0 alpha Macros side-steps this issue with its user interrupts for file locations - and goes on to issue an overwrite warning if the user does not change the filename - but the overwrite is allowable of course. The current 2.3.0 is probably a regression (discussed elsewhere) - hence this bug stands.

"Cleaned" versus "cleaned" folder name

Peter (and Connie) would prefer the "cleaned" folder to be capitalized - or Peter would prefer it be renamed to "Macro Output"

No export in Macros for files

Bill has proposed, that since it makes no sense to run a Macro on a file where the Macro does not have a export step, we block running a Macro on file(s) if the Macro has no Export step. Peter supports this.

Macros file overwrites

Any potential file overwrite by a Macro either applied top project or to file(s) should issue a warning to the user and pause for OK/NO before proceeding.