Audacity Forum

The mp3 can only be exported in 128 kbps in the batch mode, Why the mp3 export option in the edit chain is not configurable.

I didn't know Audacity has batch processing feature until i read it in a website, because the command "apply chain" "edit chains" is not easy to understand for a ordinary user so i suggest
the command "apply chain" should be renamed to "batch process" and "edit chains" should be renamed to "edit batch processing effects" this will be easy to understand for a ordinary user.

MP3 export in Chains will export with whatever encoding settings were used last. So, for example, if you want to use MP3 export with a bit rate of 256 kbps, then before you start the natch process, manually export a file as 256 kbps MP3. MP3 export will remain at 256 kbps until you change it.

Thank you for the feedback about the manual. The manual is constantly being updated to keep it in step with the current release version of Audacity and to improve it for users. The section about Chains was recently updated, so hopefully users of the next version of Audacity will find it easier to understand. The new version is here: http://manual.audacityteam.org/man/Chai ... automation (but note that the new version of the manual may not match exactly with the current release version of Audacity - it is for Audacity 2.0.4 which is yet to be released).

The mp3 export command in the edit chains should also be configurable like the other commands.

And i am requesting the commands in the file menu of Audicity "apply chain" should be renamed to "batch process" and "edit chains" should be renamed to "edit batch processing effects" this will be easy to understand for a ordinary user.

kolpotoru wrote:The mp3 export command in the edit chains should also be configurable like the other commands.

Thanks, I'll add your vote for this feature.

kolpotoru wrote:And i am requesting the commands in the file menu of Audicity "apply chain" should be renamed to "batch process" and "edit chains" should be renamed to "edit batch processing effects"

There is a problem in doing that. Chains are not only used for batch processing - they are also used for "Effects automation" (that is, automatically applying a sequence of effects in the current project). If Chains were called "Batch Process" then it would be completely misnamed in the context of applying a chain of effects to audio selected in the current project.
"Chains" are a general way of apply a "sequence of commands" (the "chain") to either a set of files (batch processing) or to a selection in the current project.

Then the "Apply Chain" may be renamed to "Batch Process Effects or Files" "Edit Chains" can be renamed to "Edit Effects List".

What i am trying to say is that this commands should be easy to understand for a non experienced user.

kolpotoru wrote:What i am trying to say is that this commands should be easy to understand for a non experienced user.

I agree totally, but we get all sorts of users. If we changed the name as you suggest then I would expect to see a lot more guitarists asking how to "daisy-chain" effects. What seems obvious to one user may not be the best thing for another user, so lots of compromises need to be made. Personally I think that "effect chains" and "batch processing" should have been kept separate, thus avoiding much of this confusion, but that is not the way that Audacity was developed.

The first time i was not able to figure out the batch processing feature of Audacity but now i know how to do it so it is not my problem i was only suggesting the changes for any new user who may be having the same confusion as i had. But since from your post I understand that it will not be possible, so i guss the new users will have to figure this out on their own.

steve wrote:Personally I think that "effect chains" and "batch processing" should have been kept separate, thus avoiding much of this confusion, but that is not the way that Audacity was developed.

May be in the future release the "effect chains" and "batch processing" will be separated to avid this confusion.