This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
using:command_line_usage [2012/11/11 08:51] 127.0.0.1 external edit |
using:command_line_usage [2016/06/20 10:42] mean |
||
---|---|---|---|
Line 5: | Line 5: | ||
Avidemux may be called with many arguments. The most obvious is //avidemux(nbsp)myFile.avi//, that will load myFile.avi. | Avidemux may be called with many arguments. The most obvious is //avidemux(nbsp)myFile.avi//, that will load myFile.avi. | ||
- | You can also provide other commands, each one of them beginning by(nbsp)(ndash) to invoke an action. You won't have the full capabilities of the GUI though. | + | You can also provide other commands, each one of them beginning by "--" to invoke an action. You won't have the full capabilities of the GUI though. |
**Warning**: When in command line mode, all alert boxes will be skipped and questions will be automatically set to NO. | **Warning**: When in command line mode, all alert boxes will be skipped and questions will be automatically set to NO. | ||
- | |||
- | **Warning**: It is very important to note that indexes are not saved. For example, if you do //avidemux2(nbsp)file.nuv// you won't be prompted to save the index. | ||
The arguments are evaluated from left to right and processed one at a time. The command line is far from bullet proof as most of the checks are inside the GUI. | The arguments are evaluated from left to right and processed one at a time. The command line is far from bullet proof as most of the checks are inside the GUI. | ||
- | A workbench file is a project file. The term workbench refers to the currently active video and settings in the program. When you save a workbench you are really saving it to a project file. | + | A project file is a file containing all settings and loaded files. It is a "snapshot" of avidemux state at the point it was saved. |
===== Commands ===== | ===== Commands ===== |