Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

SndBite 3.3 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News SndBite 3.3 (Default branch)
# 1  
Old 12-14-2008
SndBite 3.3 (Default branch)
Image SndBite is a specialized audio editor designed for breaking large recordings into smaller components with great efficiency. Its principal intended application is in linguistic research where it is often desirable to put each word or sentence into a separate file before further processing. It is also useful for measuring pause durations. Its features include multiple simultaneous views of the waveform at different resolutions, the ability to position window edges at transitions between sound and silence, automated setting of cut points at zero-crossings, automatic filename generation easily controlled by the user, and optional automatic playback on window motion. It is scriptable and may be run in batch mode without the GUI. License: GNU General Public License (GPL) Changes:
Numerous small improvements were made, especially in keyboard shortcuts. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

stg-publish

STG-PUBLISH(1)							   StGit Manual 						    STG-PUBLISH(1)

NAME

       stg-publish - Push the stack changes to a merge-friendly branch

SYNOPSIS

       stg publish [options] [branch]

DESCRIPTION

       This command commits a set of changes on a separate (called public) branch based on the modifications of the given or current stack. The
       history of the public branch is not re-written, making it merge-friendly and feasible for publishing. The heads of the stack and public
       branch may be different but the corresponding tree objects are always the same.

       If the trees of the stack and public branch are different (otherwise the command has no effect), StGit first checks for a rebase of the
       stack since the last publishing. If a rebase is detected, StGit creates a commit on the public branch corresponding to a merge between the
       new stack base and the latest public head.

       If no rebasing was detected, StGit checks for new patches that may have been created on top of the stack since the last publishing. If new
       patches are found and are not empty, they are checked into the public branch keeping the same commit information (e.g. log message, author,
       committer, date).

       If the above tests fail (e.g. patches modified or removed), StGit creates a new commit on the public branch having the same tree as the
       stack but the public head as its parent. The editor will be invoked if no "--message" option is given.

       It is recommended that stack modifications falling in different categories as described above are separated by a publish command in order
       to keep the public branch history cleaner (otherwise StGit would generate a big commit including several stack modifications).

       The public branch name can be set via the branch.<branch>.public configuration variable (defaulting to "<branch>.public").

OPTIONS

       -b BRANCH, --branch BRANCH
	   Use BRANCH instead of the default branch.

       --author "NAME <EMAIL>"
	   Set the author details.

       --authname NAME
	   Set the author name.

       --authemail EMAIL
	   Set the author email.

       --authdate DATE
	   Set the author date.

       -m MESSAGE, --message MESSAGE
	   Use MESSAGE instead of invoking the editor.

       -f FILE, --file FILE
	   Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)

       --sign
	   Add a "Signed-off-by:" to the end of the patch.

       --ack
	   Add an "Acked-by:" line to the end of the patch.

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							    STG-PUBLISH(1)