Disclaimer: I am not a professional programmer. Also, I am a great admirer of the Audacity project and the leaders here.
The present post isn’t to provoke, but to invite discussion on a minor aspect that crossed my notice.
Steps followed:
I click open a new blank Audacity window from the Application Menu Icon → Sound & Video → Audacity from my Debian system’s Start Menu.
Upon the system’s drawing of the Audacity window I go to the window menu View → History. The History window opens.
I now import an audio file. The History panel shows the path and file name. All the operations on the audio file is recorded by the History window, except the Save Project or Export step.
Then when I close the file, the History window also gets closed, while the Audacity window remains open.
Had this History window not closed this History record could be the origin for a set of batch commands to be executed automatically.
I would have greatly been helped by recording this regularly used set of commands to be run automatically henceforth.
My leaders, I am certain that you will overcome this drawback and have the batch command facility be made available to us users.
There is already a “batch command facility” available in Audacity - it is called Macros.
You have to build them manually though, you cannot record actions that you do to be made into a macro (one of the ex-developers had plans to do that a few years ago, but sadly that never materialized).
The History window shows the history of actions applied to the current project within the current session.
When a project is closed, the current project window closes, and a new project window opens. This typically occurs so quickly that it can be difficult to see that the window was closed.
If you open more than one project window at a time (Example: “File menu > New”), then each project has its own History, and you can open the History window for both projects at the same time (two separate History windows, one for each project).
Your observations are consistent with how the History window works.
Mr. Steve, my teacher, my leader,
Thank you for your reply, explaining the present framework with History.
Now please allow me to push my perspective with humility: Ideally, I would have thought that the History window recorded everything ( that would both have suited my purpose and my expectation of rationality). But the reality is a bit off-beat. Even, when I export or save the project it doesn’t record the step.
Please observe my earlier lines. I again try for a greater clarity: . . . Before opening a project the History window, when clicked open, is Blank, as expected. Then when I import a project and run operations, the Historywindow is populated.
Ideally, the window should have recorded everything, including Saving the final Project. It doesn’t.
Ideally, I would have the History window to be/remain outside the domain of a Project, monitoring operations upon an audio file from that other, outside domain. When the file is closed, the History window should have remained open, with the File and Project closureoperation included in its recorder/report.
Further, I would have required a button that would’ve allowed me to save all the detailed steps recorded by the History window, no steps excluded.
The expectation has real-world implications for designing batch files (or macros, as stated by Mr. Waxcylinder).
The History window is a log of the project’s “Undo” history.
Exporting and Saving do not modify the project in any way, so they are not recorded in the project’s Undo history. It is not possible to “Undo” an Export or a Save.
It seems that what you are suggesting is to get rid of the project’s Undo history, and replace it with a “Session history” window. This would be a big change, and a lot of time and effort would need to be spent on ensuring that multi-project histories are handled correctly. In particular, it would be necessary to ensure that selecting “Undo” in one project is able to find the correct action to Undo, as it may be below actions done in other projects. Working with multiple projects at the same time would create complex histories that interleave actions from each project. If you want to persuade the developers that this would be a good change, then you will need to present a strong and clear case for the practical benefits of such a change.
At present I see no practical benefit in the change that you are proposing.
I assure you, no, Mr. Steve. Have them both. But from outside the domain of editing of a particular project. Let the History window record everything, from opening to closing, of projects, with all Undo history data. What isn’t possible to “Undo” needn’t be undone.
You needn’t waste your precious time setting off in the direction immediately.
But Mr. Steve, I had observed in the earlier versions two windows of audacity for two different projects, with different history windows.
I have planted a note, an inkling of an idea. It is for you leaders to consider its future without keeping me in the loop.
Just to let you know, I am no longer part of the Audacity development team. Audacity was acquired by Muse Group in 2021. I’m just a regular user these days.
Yes, you had informed earlier too in another post to me.
Actually, I had addressed the team, not specifically you. I addressed both my leaders, guides and the developers who make improvements.
To me, once a developer, always a developer. The unique insight isn’t lost. One just gets bored by repetitive tasks, that’s all.
Actually, I believe that away from the regular pressure of meeting objectives one is in fact freer to let the mind be relaxed to continue seeking solutions.
Those who are in positions to listen and act will surely be listening, I am assured, to keep Audacity improving.