Nama - digital audio workstation
nama [options] [project_name]
Nama performs multitrack recording, effects processing, editing, mixing, mastering, live performance and general-purpose audio processing, using the Ecasound realtime audio engine.
Audio projects may be developed using tracks, buses, effects, sends, inserts, marks, regions, fades, sequences and edits. Each track may contain one or more WAV files, which may be recorded or imported.
Effects processing by LADSPA, LV2 and Ecasound plugins may be performed in realtime, or cached (e.g. frozen) to a file. The user may toggle between cached and dynamic processing for a track. Audio regions may be altered, duplicated, time-shifted or replaced.
Nama supports MIDI functionality via midish.
To facilitate reuse, a track's plugins and inserts can be stored as an effect chain. Effect profiles and project templates provide templating for groups of tracks and entire projects, respectively.
Audio IO is via JACK or ALSA. Soundcard IO is normally routed to JACK with transparent fallback to ALSA.
Project data parameters related to audio configuration are serialized as JSON and tracked using Git when available. The entire project history is retained and may be managed using branches and tags.
Nama supports Ladish Level 1 session handling.
Nama has fully featured terminal command prompt, a Tk GUI, and experimental OSC and remote-command modes.
The command prompt accepts Nama commands, Ecasound interactive-mode commands, shell commands and perl code.
It has command history and autocompletion. The help system provides documentation and keyword search covering Nama commands and effects.
The hotkey mode provides a convenient way to select, view, and modify effect parameters.
By default, Nama displays a graphic user interface while the command processor runs in a terminal window.
Start Nama in GUI mode
Start Nama in text mode
Specify configuration file (default: ~/.namarc)
Specify project root directory
Create project if it doesn't exist
Use Ecasound's Net-ECI interface
Use Ecasound's libecasoundc interface
Save/restore alsa state with project data
This help display
Debugging options:
Don't load effects data
Don't load project state
Bypass effects data cache
Regenerate the effects data cache
Don't automatically configure engine
Emit debugging information
Simulate JACK environment
Simulate ALSA environment
Don't spawn Ecasound process
Supply a command to execute
The Ecasound audio engine is configured through use of chain setups that specify the signal processing network.
Nama serves as an intermediary, taking high-level commands from the user, generating appropriate chain setups for user tasks such as recording, playback, mixing, etc., and running the audio engine.
Configuration commands affect future runs of the audio engine. For example, rec, play, mon and off determine whether the current track will get its audio stream from an external (e.g. live) source, whether an existing WAV file will be played back, and whether a new WAV file will be recorded. Nama responds to these commands by reconfiguring the engine and displaying the updated track status. See 'man ::ChainSetup' for details on how the chain setup created.
Once a chain setup is loaded and the engine is launched, commands can be issued to control the realtime behavior of the audio processing engine. These commands include transport start and stop, playback repositioning commands such forward, rewind and setpos. Effects may be added, modified or removed while the engine is running.
start
stop
forward
rewind
setpos
General configuration of sound devices and program options is performed by editing the .namarc file. On Nama's first run, a default version of .namarc is usually placed in the user's home directory.
Invoked by default if Tk is installed, this interface provides a subset of Nama's functionality on two windows:
The top section has buttons for creating, loading and saving projects, adding tracks, adding effects to tracks. In short, for setup.
Below are buttons for controlling the transport (start, stop and friends) and for setting marks.
The GUI project name bar and time display change color to indicate whether the upcoming operation will include live recording (red), mixdown (yellow) or playback (green).
The effects window provides sliders for each effect parameter of each track. Parameter range, defaults, and log/linear scaling hints are automatically detected. Text-entry widgets are used to enter parameters values for plugins without hinted ranges. Any parameter label can be clicked to add a parameter controller.
The command prompt is available in the terminal window during GUI operation. Text commands are used to access Nama's more advanced functions.
Press the Enter key if necessary to get the command prompt, which will look something like this:
nama sax ('h' for help)>
In this instance, 'sax' is the current track.
When using buses, the bus is indicated before the track:
nama Strings/violin ('h' for help)>
At the prompt, you can enter Nama and Ecasound commands, Perl code preceded by eval or shell code preceded by !.
eval
!
Multiple commands on a single line are allowed if delimited by semicolons. Usually the lines are split on semicolons and the parts are executed sequentially, however if the line begins with eval or ! the entire line (up to double semicolons ';;' if present) will be given to the corresponding interpreter.
You can access command history using up-arrow/down-arrow.
Type help for general help, help command for help with command, help foo for help with commands containing the string foo. help_effect foo bar lists all plugins/presets/controller containing both foo and bar. Tab-completion is provided for Nama commands, Ecasound-iam commands, plugin/preset/controller names, and project names.
help
help command
command
help foo
foo
help_effect foo bar
Many effects have abbreviations, such as 'afx' for 'add_effect'.
Each track has a descriptive name (i.e. vocal) and an integer track-number assigned when the track is created. New user tracks initially belong to the Main bus.
Track output signals are usually mixed and pass through the Master track on the way to soundcard for monitoring.
The following sections describes track attributes and their effects.
Specifying 'mono' means the track has one input channel, which will be recorded as a mono WAV file. Mono track signals are automatically duplicated to stereo and a pan effect is provided.
Specifying 'stereo' for a track means that two channels of audio input will be recorded as an interleaved stereo WAV file. You can also use a 'stereo' declaration to avoid the automatic channel copy usually applied to single-channel sources.
Specifying N channels for a track ('set width N') means N successive input channels will be recorded as an N-channel interleaved WAV file.
Each track, including Master and Mixdown, has its own REC/MON/PLAY/OFF setting.
The MON setting means that the track source is connected to the track input, and the track output is supplied for monitoring by the Main bus and other submixes if any.
The REC setting prepares the track is ready to record a WAV file.
The PLAY setting enqueues an audio file for playback from disk as the track source.
REC and PLAY settings also create the monitoring routes associated with MON status.
OFF setting tells Nama to remove the track from the audio network. OFF status also results when no audio source is available. A track with no recorded WAV files will show OFF status, even if set to PLAY.
Buses can force the status of their member tracks to OFF. Nama provides MON and OFF settings for buses. OFF (set by bus_off) removes all member tracks from the chain setup, MON (set by bus_mon restores them.
bus_off
bus_mon
The mixplay command sets the Mixdown track to PLAY and the Main bus to OFF.
Multiple WAV files ("takes") can be recorded for each track. These are distinguished by a version number that increments with each recording run, i.e. sax_1.wav, sax_2.wav, etc. All WAV files recorded in the same run have the same version numbers.
The version numbers of files for playback can be selected at the bus or track level. By setting the bus version to 5, you can play back version 5 of several tracks at once. Version 5 could signify the fifth take of a song, or the fifth song of a live recording session.
The track version setting, if present, overrides the bus setting. Setting the track version to zero restores control of the version number to the bus.
The Main bus version setting does not currently propagate to other buses.
Marks in Nama are similar to those in other audio editing software. One limitation is that mark positions are relative to the beginning of an Ecasound chain setup. If your project involves a single track, and you will be shortening the stream by setting a region to play, set any marks you need after defining the region.
The region command allows you to define endpoints for a portion of an audio file. You can then use the shift command to move the region to the desired time position.
region
shift
Each track can have one region definition. To create multiple regions, the new_region command takes a pair of marks to create a read-only copy of the current track with the specified region definition.
new_region
You can control this region as you would any other other track, applying effects, adjusting volume, etc.
Currently, regions are not clipped out of their host track. This feature may be implemented in future.
The link_track clones a read-only track from another track, which may belong to a different project.
link_track
Each track gets volume and pan effects by default. New effects added using add_effect are applied before pan volume controls. You can position effects anywhere you choose using insert_effect or position_effect.
add_effect
insert_effect
position_effect
Nama allows you to place fades on any track. Fades are defined by mark position and duration. An additional volume operator, -eadb, is applied to each track to host the envelope controller that implements fades.
The send command can route a track's post-fader output to a soundcard channel or JACK client in addition to the normal mixer input. Nama currently allows one aux send per track.
send
The add_insert command configures a pre- or post-fader send-and-return to soundcard channels or JACK clients. Wet and dry signal paths are provided, with a default setting of 100% wet.
add_insert
Each track can have one pre-fader and one post-fader insert.
A bunch is just a list of track names. Bunch names are used with the keyword for to apply one or more commands to several tracks at once. A bunch can be created with the new_bunch command. Any bus name can also be treated as a bunch. Finally, several system defined bunches are available:
for
new_bunch
All tracks with the corresponding setting in the current bus
Buses enable multiple tracks to be routed through a single mix track before feeding the Main mixer bus (or possibly, another bus.)
The following commands create a bus and assign three tracks to it. The mix track takes the name of the bus and is stereo by default.
# create a bus named Strings with a same-named mix track add_bus Strings # create tracks for the bus add_tracks violin cello bass # move the tracks from the Main bus (default) to the Strings bus for violin cello bass; move_to_bus Strings # use the mix track to control bus output volume Strings vol - 10
Submixes are a type of bus used to provide instrument monitors, or to send the outputs from multiple user tracks to an external program such as jconverter.
While Nama can address tracks by either name and track number, the chain setups use the track number exclusively.
The Master track (mixer output control) is always chain 1, the Mixdown track is always chain 2.
In single-engine mode, Nama uses Ecasound loop devices where necessary to connect two tracks, or to allow one track to have multiple inputs or outputs. Each loop device adds one buffer, which increases latency. In dual-engine mode, JACK ports are used for interconnections instead of loop devices.
The following diagrams apply to Nama's single-engine, mode. (The same topology is used in dual-engine mode.)
Let's examine the signal flow from track 3, the first available user track. Assume track 3 is named "sax".
We will divide the signal flow into track and mixer sections. Parentheses show the track number/name.
The stereo outputs of each user track terminate at Master_in, a loop device at the mixer input.
Sound device --+---(3)----> Master_in /JACK client | +---(R3)---> sax_1.wav
REC status indicates that the source of the signal is the soundcard or JACK client. The input signal will be written directly to a file except in the special preview and doodle modes, or if rec_disable is issued.
rec_disable
sax_1.wav ------(3)----> Master_in
In the second part of the flow graph, the mixed signal is delivered to an output device through the Master chain, which can host effects. Usually the Master track provides final control before audio output or mixdown.
Master_in --(1)--> Master_out --+--------> Sound device | +-->(2)--> Mixdown_1.wav
In mastering mode (invoked by master_on and released master_off) the following network, receives the Master track signal as input and provides an output to the soundcard or WAV file.
master_on
master_off
+- Low -+ | | Master_in --- Eq --+- Mid -+--- Boost -> soundcard/wav_out | | +- High +
The Eq track hosts an equalizer.
The Low, Mid and High tracks each apply a bandpass filter, a compressor and a spatialiser.
The Boost track applies gain and a limiter.
These effects and their default parameters are defined in the configuration file .namarc.
The mixdown command configures Nama for mixdown. The Mixdown track is set to REC (equivalent to Mixdown rec) and the audio monitoring output is turned off (equivalent to Master off).
mixdown
Mixdown rec
Master off
Mixdown proceeds after you start the transport.
As a convenience, Mixdown_nn.wav will be symlinked to <branch_name_nn.wav> in the project directory. (If git is disabled or not available <project_name_nn.wav> is used instead.) Corresponding encoded files are created if the "mixdown_encodings" option is set. Acceptable values are a space-separated list. The default is "mixdown_encodings: ogg mp3".
These non-recording modes, invoked by preview and doodle commands tweak the routing rules for special purposes. Preview mode disables recording of WAV files to disk. Doodle mode disables PLAY inputs while excluding any tracks with the same source as a currently routed track. The arm command releases both preview and doodle modes.
preview
doodle
arm
The eager setting causes the engine to start immediately following a reconfiguration.
These modes are unnecessary in Nama's dual-engine mode.
The save command is the usual way to preserve your work.
save
When you type save, Settings related to the state of the project are saved in the file State.json in the current project directory. State.json is tracked by git.
save updates several other data files as well:
Aux.json, in the current project directory, contains data that is part of the project (such as command history, track comments, and current operating modes) but with no direct effect on the project audio.
global_effect_chains.json, in the project root directory, contains system and user defined effect chains.
save somename.json will save project state to a file of that name. Similarly get somename.json will load the corresponding file. The .json suffix may be omitted if "use_git: 0" is set in .namarc.
save somename.json
get somename.json
When git is installed, Nama uses it to store snapshots of every step in the history of your project.
While you can continue using the same save and get with snapshots, the underlying version control gives them huge advantages over files: (1) they can sprout branches, (2) they retain their history and (3) they are never overwritten.
get
When you type save initial-mix, the latest snapshot is tagged with the name "initial-mix", which you can recall later with the command get initial-mix.
save initial-mix
get initial-mix
You can include a comment with the snapshot:
save initial-mix "sounds good enough to send to the front office"
Nama lets you create new branches, starting at any snapshot.
To start a new branch called compressed-mix starting at a snapshot called initial-mix you would say:
new_branch compressed-mix initial-mix
If you want to go back to working on the master branch, use branch master.
branch master
You can also issue native git commands at the Nama prompt.
All projects begin on the "master" branch. Because this is the default branch, it is not displayed in the prompt. Otherwise "master" is not special in any way.
In the graphs below, the letters indicate named snapshots.
create test-project ... save a ... save b ... save c ---a---b---c (master) get a ... save d ... save e ... save f d---e---f (a-branch) / -----a----b---c (master)
Now, you want to go back to try something different at "c":
get c ... save g d---e---f (a-branch) / ----a----b---c (master) \ g (c-branch CURRENT HEAD)
You could also go back to master, and restart from there:
get master ... save h ... save i d---e---f (a-branch) / ----a----b---c---h---i (master CURRENT HEAD) \ g (c-branch)
While the merging of branches may be possible, the function has not been tested.
When you type quit Nama will automatically save your work to State.json. If you don't want this behavior, use Ctrl-C to exit Nama.
quit
Use source filename.ports to ask Nama to connect multiple JACK ports listed in a file filename.ports to the input port(s) of that track.
If the track is stereo, ports from the list are alternately connected to left and right channels.
An edit consists of audio clips and data structures associated with a particular track and version. The edit replaces part of the original WAV file, allowing you to fix wrong notes, or substitute one phrase for another.
Each track can host multiple edits. Edits are non-destructive; they are achieved by using Ecasound's ability to crossfade and sequence.
Select the track to be edited and the correct version.
Before creating the edit, you will now need to create three marks:
play start point =item * rec start point =item * rec end point
The edit will replace the audio between the rec start and rec end points.
There are two ways to set these points.
Position the playback head a few seconds before the edit. Enter the set_edit_points command. This will start the engine. Hit the P key three times to designate the playback start, punch-in and punch-out positions.
Position the playback head at the position you want playback for the edit to start. Enter the set_play_start_mark command.
Use the same procedure to set the rec start and rec end positions using the set_rec_start_mark and set_rec_end_mark commands.
Type new_edit play_start_mark rec_start_mark rec_end_mark.)
Enter the new_edit command to create the necessary tracks and data structures.
Use preview_edit to confirm the edit positions. The engine will run and you will hear the host track with the target region removed. Playback will be restricted to the edit region. You may use preview_out to hear the clip to be removed.
Use list_marks to see the edit marks and modify_mark to nudge them into perfect position.
Once you are satisfied with the mark positions, you are ready to record your edit.
Enter start_edit. Playback will begin at first mark. The replacement clip will be recorded from the source specified in the original track.
Each start_edit command will record an additional version on the edit track. redo_edit will delete (destructively) the most recent audio clip and begin recording anew.
You may specify another range for editing and use the editing procedure again as many times as you like. Edits may not overlap.
merge_edits will recursively merge all edits applied to the current track and version, creating a new version.
I recommend that you merge edits when you are satisfied, with the results to protect your edits against an accidental change in mark, region or version settings.
restore_edits acts on a merged version of the current track, selecting the prior unmerged version with all edits and region definitions in "live" form. You may continue to create new edits. TO BE IMPLEMENTED
list_edits will label the edits by index and time.
end_edit_mode will restore normal playback mode
destroy_edit Behind the scenes, the host track becomes the mix track to a bus. Sources for the bus are the original audio track, and zero or more edits, each represented by one track object.
You can send now send commands from a remote process, and also get information back. Understand that this code opens a remote execution hole.
In .namarc you need something like:
remote_control_port: 57000
Then Nama will set up a listener for remote commands.
The usual return value will be a single newline.
However, if you send an 'eval' command followed by perl code, the return value will be the result of the perl code executed with a newline appended. If the result is a list, the items will be joined by spaces into a single string.
If the result is an object or data structure, it will be returned in a serialized form.
For example, if you send this string:
eval $this_track->name
The return value will be the name of the current track.
help [ <integer:help_topic_index> | <string:help_topic_name> | <string:command_name> ]
help marks # display the help category marks and all commands containing marks help 6 # display help on the effects category help mfx # display help on modify_effect - shortcut mfx
help_effect <string:label> | <integer:unique_id>
help_effect 1970 # display help on Fons Adriaensen's parametric EQ (LADSPA) help_effect etd # prints a short message to consult Ecasound manpage, # where the etd chain operator is documented. hfx lv2-vocProc # display detailed help on the LV2 VocProc effect
find_effect <string:keyword1> [ <string:keyword2>... ]
find_effect compressor # List all effects containing "compressor" in their name or parameters fe feedback # List all effects matching "feedback" # (for example a delay with a feedback parameter)
exit
memoize
unmemoize
rec # prepare the curent track to be recorded. start # Start the engine/transport rolling (play now!) stop # Stop the engine, cleanup, prepare to review
getpos
start # Start the engine. gp # Get the current position of the playhead. Where am I?
setpos <float:position_seconds>
setpos 65.5
forward <float:increment_seconds>
fw 23.7
rewind <float:decrement_seconds>
rewind 6.5
to_start
to_end
ecasound_start
ecasound_stop
restart_ecasound
rec # Set the current track to record from its source. preview # Enter the preview mode. start # Playback begins. You can play live, adjust effects, # forward, rewind, etc. stop # Stop the engine/transport. arm # Restore to normal recording/playback mode.
doodle # Switch into doodle mode. start # start the engine/transport running. (fool around) stop # Stop the engine. arm # Return to normal mode, allowing play and record to disk
mixdown # Enter mixdown mode start # Start the transport. The mix will be recorded by the # Mixdown track. The engine will run until the # longest track ends. (After mixdown Nama places # a symlink to the WAV file and possibly ogg/mp3 # encoded versions in the project directory.) mixoff # Return to the normal mode.
mixplay
mixplay # Enter the Mixdown play mode. start # Play the Mixdown track. stop # Stop playback. mixoff # Return to normal mode.
mixoff
automix
mr # Turn on master mode. start # Start the playback. # Now you can adjust the Boost or global EQ. stop # Stop the engine.
add_track <string:name>
add_track clarinet # create a mono track called clarinet with input # from soundcard channel 1.
add_tracks <string:name1> [ <string:name2>... ]
add_tracks violin viola contra_bass
add_midi_track <string:name>
link_track [<string:project_name>] <string:track_name> <string:link_name>
link my_song_part1 Mixdown part_1 # Create a read-only track "part_1" in the current project # using files from track "Mixdown" in project "my_song_part_1". # link_track compressed_piano piano # Create a read-only track "compressed_piano" using files from # track "piano". This is one way to provide wet and dry # (processed and unprocessed) versions of same source. # Another way would be to use inserts.
import_audio <string:full_path_to_file> [ <integer:frequency> ]
import /home/samples/bells.flac # import the file bells.flac to the current track import /home/music/song.mp3 44100 # import song.mp3, specifying the frequency
set_track <string:track_field> <value>
record
rec # Set the current track to record. start # A new version (take) will be written to disk, # creating a file such as sax_1.wav. Other tracks # may be recording or playing back as well. stop # Stop the recording/playback, automatically enter playback mode
play
mon
off
source <integer:soundcard_channel> | <string:jack_client_name> | <string:jack_port_name> <string:jack_ports_list> | | <string:track_name> | <string:loop_id> | 'jack' | 'null'
source 3 # Take input from soundcard channel 3 (3/4 if track is stereo) # source null # Track's input is silence. This is useful for when an effect such # as a metronome or signal generator provides a source. # source LinuxSampler # Record input from the JACK client named LinuxSampler. # source synth:output_3 # record from the JACK client synth, using the # port output_3 (see he jackd and jack_lsp manpages # for more information). # source jack # This leaves the track input exposed as JACK ports # such as Nama:sax_in_1 for manual connection. # source kit.ports # The JACK ports listed in the file kit.ports (if it exists) # will be connected to the track input. # # Ports are listed pairwise in the .ports files for stereo tracks. # This is convenient for use with the Hydrogen drumkit, # whose outputs use one JACK port per voice.
send <integer:soundcard_channel> | <string:jack_client_name> | <string:loop_id>
send 3 # Send the track output to soundcard channel 3. send jconvolver # Send the track output to the jconvolver JACK client.
remove_send
stereo
mono
set_version <integer:version_number>
piano # Select the piano track. version 2 # Select the second recorded version sh # Display information about the current track
destroy_current_wav
list_versions
list_versions # May print something like: 1 2 5 7 9 # The other versions might have been deleted earlier by you.
vol [ [ + | - | / | * ] <float:volume> ]
vol * 1.5 # Multiply the current volume by 1.5 vol 75 # Set the current volume to 75 # Depending on your namarc configuration, this means # either 75% of full volume (-ea) or 75 dB (-eadb). vol - 5.7 # Decrease current volume by 5.7 (percent or dB) vol # Display the volume setting of the current track.
mute
unmute
unity
vol 55 # Set volume to 55 unity # Set volume to the unity value. vol # Display the current volume (should be 100 or 0, # depending on your settings in namarc.)
solo [ <strack_name_1> | <string:bunch_name_1> ] [ <string:track_name_2 | <string:bunch_name_2> ] ...
solo # Mute all tracks but the current track. nosolo # Unmute all tracks, restoring prior state. solo piano bass Drums # Mute everything but piano, bass and Drums.
nosolo
all
piano # Select track piano mute # Mute the piano track. sax # Select the track sax. solo # Mute other tracks nosolo # Unmute other tracks (piano is still muted) all # all tracks play
pan [ <float:pan_position_in_percent> ]
pan 75 # Pan the track to a position between centre and hard right p 50 # Move the current track to the centre. pan # Show the current position of teh track in the stereo panorama.
pan_right
pan_left
pan_center
pan_back
show_tracks
show_tracks_all
show_bus_tracks
show_track
show_mode
show_track_latency
show_latency_all
set_region <string:start_mark_name> <string:end_mark_name>
sax # Select "sax" as the current track. setpos 2.5 # Move the playhead to 2.5 seconds. mark sax_start # Create a mark sp 120.5 # Move playhead to 120.5 seconds. mark sax_end # Create another mark set_region sax_start sax_end # Play only the audio from 2.5 to 120.5 seconds.
add_region <string:start_mark_name> | <float:start_time> <string:end_mark_name> | <float:end_time> [ <string:region_name> ]
sax # Select "sax" as the current track. add_region sax_start 66.7 trimmed_sax # Create "trimmed_sax", a copy of "sax" with a region defined # from mark "sax_start" to 66.7 seconds.
remove_region
shift_track <string:start_mark_name> | <integer:start_mark_index | <float:start_seconds>
piano # Select "piano" as current track. shift 6.7 # Move the start of track to 6.7 seconds.
unshift_track
modifiers [ Audio file sequencing parameters ]
modifiers select 5 15.2 # Apply Ecasound's select modifier to the current track. # The usual way to accomplish this is with a region definition.
nomodifiers
normalize
fixdc
autofix_tracks
remove_track
bus_version
add_bunch <string:bunch_name> [ <string:track_name_1> | <integer:track_index_1> ] ...
add_bunch strings violin cello bass # Create a bunch "strings" with tracks violin, cello and bass. for strings; mute # Mute all tracks in the strings bunch. for strings; vol * 0.8 # Lower the volume of all tracks in bunch "strings" by a # a factor of 0.8.
list_bunches
remove_bunch <string:bunch_name> [ <string:bunch_name> ] ...
add_to_bunch <string:bunch_name> <string:track1> [ <string:track2> ] ...
add_to_bunch woodwind oboe sax flute
commit <string:message>
tag <string:tag_name> [<string:message>]
branch <string:branch_name>
list_branches
new_branch <string:new_branch_name> [<string:existing_branch_name>]
save_state [ <string:settings_target> [ <string:message> ] ]
get_state <string:settings_target>
list_projects
new_project <string:new_project_name>
create jam
load_project <string:existing_project_name>
load my_old_song
project_name
new_project_template <string:template_name> [ <string:template_description> ]
new_project_template my_band_setup "tracks and busses for bass, drums and me"
use_project_template <string:template_name>
apt my_band_setup # Will add all the tracks for your basic band setup.
list_project_templates
destroy_project_template <string:template_name1> [ <string:template_name2> ] ...
generate
arm_start
connect
disconnect
show_chain_setup
loop <string:start_mark_name> | <integer:start_mark_index> | <float:start_time_in_secs> <string:end_mark_name> | <integer:end_mark_index> | <float:end_time_in_secs>
loop 1.5 10.0 # Loop between 1.5 and 10.0 seconds. loop 1 5 # Loop between marks with indeices 1 and 5, see list_marks. loop sax_start 12.6 # Loop between mark sax_start and 12.6 seconds.
noloop
add_controller [ <string:operator_id> ] <string:effect_code> [ <float:param1> <float:param2> ] ...
add_effect etd 100 2 2 50 50 # Add a stero delay of 100ms. # the delay will get the effect ID E . # Now we want to slowly change the delay to 200ms. acl E klg 1 100 200 2 0 100 15 200 # Change the delay time linearly (klg)
add_effect [ (before <fx_alias> | first | last ) ] <fx_alias> [ <float:param1> <float:param2>... ] "before", "first" and "last" can be abbreviated "b", "f" and "l", respectively.
We want to add the decimator effect (a LADSPA plugin). help_effect decimator # Print help about its paramters/controls. # We see two input controls: bitrate and samplerate afx decimator 12 22050 # prints "Added GO (Decimator)" # We have added the decimator with 12bits and a sample rate of 22050Hz. # GO is the effect ID, which you will need to modify it.
add_effect_last <fx_alias> [ <float:param1> <float:param2>... ]
add_effect_first <fx_alias> [ <float:param1> <float:param2>... ]
add_effect_before <fx_alias> <fx_alias> [ <float:param1> <float:param2>... ]
modify_effect [ <fx_alias> ] <integer:parameter> [ + | - | * | / ] <float:value> fx_alias can be: a position, effect ID, nickname or effect code
To change the roomsize of our reverb effect to 62 lfx # We see that reverb has unique effect ID AF and roomsize is the # first parameter. mfx AF 1 62 # mfx AF,BG 1 75 # Change the first parameter of both AF and BG to 75. # mfx CE 6,10 -3 # Change parameters 6 and 10 of effect CE to -3 # mfx D 4 + 10 # Increase the fourth parameter of effect D by 10. # mfx A,B,C 3,6 * 5 # Adjust parameters 3 and 6 of effect A, B and C by a factor of 5.
remove_effect <fx_alias1> [ <fx_alias2> ] ...
position_effect <string:id_to_move> <string:position_id>
position_effect G F # Move effecit with unique ID G before F.
show_effect [ <string:effect_id1> ] [ <string:effect_id2> ] ...
sfx # Print name, unique ID and parameters/controls of the current effect. sfx H # Print out all information about effect with unique ID H.
dump_effect
list_effects
hotkeys
hotkeys_always
hotkeys_off
add_insert External: ( pre | post ) <string:send_id> [ <string:return_id> ] Local wet/dry: local
add_insert pre jconvolver # Add a prefader insert. The current track signal is sent # to jconvolver and returned to the vol/pan controls. add_insert post jconvolver csound # Send the current track postfader signal (after vol/pan # controls) to jconvolver, getting the return from csound. guitar # Select the guitar track ain local # Create a local insert guitar-1-wet # Select the wet arm afx G2reverb 50 5.0 0.6 0.5 0 -16 -20 # add a reverb afx etc 6 100 45 2.5 # add a chorus effect on the reverbed signal guitar # Change back to the main guitar track wet 25 # Set the balance between wet/dry track to 25% wet, 75% dry.
set_insert_wetness [ pre | post ] <n_wetness>
wet pre 50 # Set the prefader insert to be balanced 50/50 wet/dry. wet 100 # Simpler if there's only one insert
remove_insert [ pre | post ]
rin # If there is only one insert on the current track, remove it. remove_insert post # Remove the postfader insert from the current track.
ctrl_register
preset_register
ladspa_register
list_marks
to_mark <string:mark_name> | <integer:mark_index>
to_mark sax_start # Jump to the position marked by sax_mark. tmk 2 # Move to the mark with the index 2.
add_mark [ <string:mark_id> ]
mark start # Create a mark named "start" at the current position.
remove_mark [ <string:mark_name> | <integer:mark_index> ]
remove_mark start # remove the mark named start rmk 16 # Remove the mark with the index 16. rmk # Remove the current mark
next_mark
previous_mark
name_mark <string:mark_name>
modify_mark [ + | - ] <float:seconds>
move_mark + 2.3 # Move the current mark 2.3 seconds forward from its mmk 16.8 # Move the current mark to 16.8 seconds, no matter, where it is now.
engine_status
dump_track
dump_group
dump_all
dump_io
list_history
add_submix_cooked <string:name> <destination>
add_submix_cooked front_of_house 7 # send a custom mix named "front_of_house" # to soundcard channels 7/8
add_submix_raw <string:name> <destination>
asbr Reverb jconv # Add a raw send bus called Reverb, with its output
add_bus <string:name> [ <string:track_name> | <string:jack_client> | <integer:soundcard_channel> ]
abs Brass # Add a bus, "Brass", routed to the Main bus (e.g. mixer) abs special csound # Add a bus, "special" routed to JACK client "csound"
update_submix <string:name>
update_submix Reverb
remove_bus <string:bus_name>
list_buses
set_bus <string:busname> <key> <value>
overwrite_effect_chain Same as for new_effect_chain
new_effect_chain <string:name> [ <effect_id_1> <effect_id_2>... ]
new_effect_chain my_piano # Create a new effect chain, "my_piano", storing all # effects and their settings from the current track # except the fader (vol/pan) settings. nec my_guitar A C F G H # Create a new effect chain, "my_guitar", # storing the effects with IDs A, C, F, G, H and # their respective settings.
delete_effect_chain <string:effect_chain_name>
find_effect_chains [ <string:key_1> <string:value_1> ] ...
fec # List all effect chains with their effects.
find_user_effect_chains [ <string:key_1> <string:value_1> ] ...
bypass_effects [ <string:effect_id_1> <string:effect_id_2>... | 'all' ]
bypass all # Bypass all effects on the current track, except vol and pan. bypass AF # Only bypass the effect with the unique ID AF.
bring_back_effects [ <string:effect_id_1> <string:effect_id_2> ... | 'all' ]
bbfx # Restore the current effect. restore_effect AF # Restore the effect with the unique ID AF. bring_back_effects all # Restore all effects.
new_effect_profile <string:bunch_name> [ <string:effect_profile_name> ]
add_bunch Drums snare toms kick # Create a buch called Drums. nep Drums my_drum_effects # Create an effect profile, call my_drum_effects
apply_effect_profile <string:effect_profile_name>
destroy_effect_profile <string:effect_profile_name>
list_effect_profiles
show_effect_profiles
full_effect_profiles
cache_track [ <float:additional_processing_time> ]
cache 10 # Cache the curent track and append 10 seconds extra time,
uncache_track
do_script <string:filename>
do prepare_my_drums # Execute the script prepare_my_drums.
scan
add_fade ( in | out ) marks/times (see examples)
fade in mark1 # Fade in,starting at mark1 and using the # default fade time of 0.5 seconds. fade out mark2 2 # Fade out over 2 seconds, starting at mark2 . fade out 2 mark2 # Fade out over 2 seconds, ending at mark2 . fade in mark1 mark2 # Fade in starting at mark1, ending at mark2 .
remove_fade <integer:fade_index_1> [ <integer:fade_index_2> ] ...
list_fade # Print a list of all fades and their tracks. rfd 2 # Remove the fade with the index (n) 2.
list_fade
add_comment <string:comment>
ac "Guitar, treble on 50%"
remove_comment
show_comment
show_comments
add_version_comment <string:comment>
avc "The good take with the clear 6/8"
remove_version_comment
show_version_comment
show_version_comments_all
set_system_version_comment <string:comment>
midish_command <string:command_text>
m tracknew my_midi_track
midish_mode_on
midish_mode_off
midish_mode_off_ready_to_play
midish_mode_off_ready_to_record
new_edit
set_edit_points
list_edits
select_edit <integer:edit_index>
end_edit_mode
destroy_edit [ <integer:edit_index> ]
preview_edit_in
preview_edit_out
play_edit
record_edit
edit_track
host_track_alias
host_track
version_mix_track
play_start_mark
rec_start_mark
rec_end_mark
set_play_start_mark
set_rec_start_mark
set_rec_end_mark
disable_edits
merge_edits
explode_track
move_to_bus <string:bus_name>
asub Drums # Create a new sub bus, called Drums. snare # Make snare the current track. mtb Drums # Move the snare track into the sub bus Drums.
promote_version_to_track <integer:version_number>
read_user_customizations
limit_run_time [ <float:additional_seconds> ]
limit_run_time_off
offset_run <string:mark_name>
offset_run_off
view_waveform
edit_waveform
rerecord
for piano guitar;rec # Set piano and guitar track to record. # do your recording and ilstening. # You want to record another version of both piano and guitar: rerec # Sets piano and guitar to record again.
analyze_level
for <string:track_name_1> [ <string:track_name_2>} ... ; <string:commands>
for piano guitar; vol - 3; pan 75 # reduce volume and pan right for snare kick toms cymbals; mtb Drums # move tracks to bus Drums
git <string:command_name> [arguments]
edit_rec_setup_hook
edit_rec_cleanup_hook
remove_fader_effect vol | pan | fader
rename_track <string:old_track> <string:new_track>
new_sequence <string:name> <track1, track2,...>
select_sequence
list_sequences
show_sequence
append_to_sequence [<string:name1>,...]
asq chorus # append chorus track to current sequence asq # append current track to current sequence
insert_in_sequence <string:name1> [<string:name2>,...] <integer:index>
remove_from_sequence <integer:index1> [<integer:index2>,...]
delete_sequence <string:sequence>
add_spacer <float:duration> [<integer:position>]
convert_to_sequence
merge_sequence
snip <mark_pair1> [<mark_pair2>...]
snip cut1-start cut1-end cut2-start cut2-end This removes cut1 and cut2 regions from the current track by creating a sequence.
compose <string:sequence_name> <string:trackname> <mark_pair1> [<mark_pair2>...]
compose speeches conference-audio speaker1-start speaker1-end speaker2-start speaker2-end This creates a "speeches" sequence with two clips for speaker1 and speaker2.
undo
redo
show_head_commit
eager on | off
new_engine <string:engine_name> <integer:port>
select_engine <string:engine_name>
set_track_engine_group <string:engine_name>
set_bus_engine_group <string:engine_name>
select_submix <string:submix_name>
trim_submix
# reduce vol of current track in in_ear_monitor by 3dB select_submix in_ear_monitor trim vol - 3
nickname_effect <lower_case_string:nickname>
add_track guitar afx Plate nick reverb # current effect gets name "reverb1" mfx reverb1 1 0.05 # modify first reverb effect on current track mfx reverb 1 2 # works, because current track has one effect named "reverb" afx reverb # add another Plate effect, gets name "reverb2" rfx reverb # Error, multiple reverb effects are present on this # track. Please use a numerical suffix. mfx reverb2 1 3 # modify second reverb effect rfx reverb1 # removes reverb1 ifx reverb2 reverb # insert another reverb effect (reverb3) before reverb2 rfx reverb3 # remove reverb3 rfx reverb # removes reverb2, as it is the sole remain reverb effect
delete_nickname_definition
afx Plate # add Plate effect nick reverb # name it "reverb", and create a nickname for Plate dnd reverb # removes nickname definition afx reverb # error
remove_nickname
afx Plate nick reverb mfx reverb 1 3 rnick mfx reverb 1 3 # Error: effect named "reverb" not found on current track
list_nickname_definitions
set_effect_name <string:name>
set_effect_surname <string:surname>
remove_effect_name
remove_effect_surname
Nama selects realtime or nonrealtime parameters based on the realtime_profile, ecasound_buffersize and ecasound_globals fields in .namarc. You can optionally specify the buffersizes as a multiple of the JACK period size. Note that for best realtime operation under JACK you will have to configure jackd appropriately as well.
The realtime and auto profiles are useful when using Nama/Ecasound for live fx processing or live monitoring.
The realtime profile sets a small buffersize and other low latency settings whenever a soundcard or JACK client is connected.
The nonrealtime profile uses a bigger buffer, providing extended margins for stable operation. It is suitable for post-processing, or for recording without live monitoring responsibilities.
The auto profile defaults to nonrealtime settings. It switches to realtime, low-latency settings when a track has a live input.
On any change in setup, the GUI display updates and show_tracks command is executed automatically showing what to expect the next time the engine is started.
You can use the chains command to verify the Ecasound chain setup. (The Ecasound command cs-save-as mysetup.ecs will additionally store all engine data, effects as well as routing.)
chains
cs-save-as mysetup.ecs
The dump command displays data for the current track. The dumpall command shows all state that would be saved.
dump
dumpall
This is the same output that is written to the State.yml file when you issue the save command.
No latency compensation across signal paths is provided at present. This feature is under development.
If you are using Nama with the NetECI interface (i.e. if Audio::Ecasound is not installed) you should block TCP port 2868 if your computer is exposed to the Internet.
The following commands, available on Unixlike systems with Perl installed, will pull in Nama and other Perl libraries required for text mode operation:
cpanm Audio::Nama -or- PERL_MM_USE_DEFAULT=1 cpan Audio::Nama
cpanm Audio::Nama
PERL_MM_USE_DEFAULT=1 cpan Audio::Nama
To use the GUI, you will need to install Tk:
cpanm Tk
You may want to install Audio::Ecasound if you prefer not to run Ecasound in server mode:
cpanm Audio::Ecasound
You can pull the source code as follows:
git clone git://github.com/bolangi/nama.git
Consult the BUILD file for build instructions.
The Nama mailing list is a suitable forum for questions regarding Nama installation, usage, bugs, feature requests, etc.
http://www.freelists.org/list/nama
For questions and discussion related to Ecasound
https://lists.sourceforge.net/lists/listinfo/ecasound-list
The modules that make up this application are the preprocessed output from several source files. Patches against these source files are preferred.
Joel Roth, <joelz@pobox.com>
Alex Stone Brett McCoy Dubphil F. Silvain ++ Joy Bausch Julien Claassen ++ Kevin Utter Lars Bjørndal Philippe Schelté Philipp Überbacher Raphaël Mouneyres ++ Rusty Perez S. Massy ++
Copyright (c) 2009-2013 by Joel Roth.
This is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, Version 3.
1 POD Error
The following errors were encountered while parsing the POD:
Non-ASCII character seen before =encoding in 'Bjørndal'. Assuming UTF-8
To install Audio::Nama, copy and paste the appropriate command in to your terminal.
cpanm
CPAN shell
perl -MCPAN -e shell install Audio::Nama
For more information on module installation, please visit the detailed CPAN module installation guide.