Software other might not know, but which are really useful!!

[studio32]

Hi,

There are many many (little) apps in linux audio music world. It's hard to come to know the good and usable ones...

Maybe you use or know a app which other SHOULD know! Post it here!

[studio32]

TAPSTART

http://www.arnoldarts.de/drupal/?q=TapStart

[studio32]

JACK_MIXER

To manage volume of rezound and my guitar...

http://home.gna.org/jackmixer/

EDIT: nice feature: LASH support to save settings :)

[studio32]

MIDINGSOLO:

This project aims to do a real-time audio note recognition software for monophonic signals (like solos).
The input must be a monophonic wave signal (only one voice, with one melodic instrument). The result are MIDI events launched trough the ALSA sequencer. (recognized notes are printed to the standard output too)

http://home.gna.org/midingsolo/index.html

I didn't use it yet, just a tip....

[studio32]

Psychosynth

Kind of like a ReacTable without the projector, DV camera, and cubes of cardboard.

Bjork has used something like it on her tour


http://www.psychosynth.com/doku.php

[thorgal]

ecasound : http://ecasound.seul.org/ecasound/

command line tool, extremely powerful! it can be used as simply as

ecasound -i /dev/dsp -o somefile.whatever (OSS input)
or
ecasound -i jack:some port -o whatever

or
ecasound -c for interactive session.

This is a really cool tool if you won't want to have GUIs all around. It can be used from non X sessions. But it also has a lot of frontends (ecamegapedal for guitar effects, emacs bindings, etc).

[studio32]

LASH-wrap - A small LASH wrapper

http://lists.linuxaudio.org/pipermail/l ... 19502.html

http://lists.linuxaudio.org/pipermail/l ... 19503.html

Lash-Wrap

-- ABOUT:

Lash-Wrap is a small helper application that serves as a "proxy" between an un-LASH'ified app and the LASH system.

LASH is the LASH Audio Session Handler, a server/client solution to storing and restoring whole music sessions ("session" as a collection of interconnected JACK and ALSA programs).

Sadly not all (pretty much none) of the vast amount of cool linux audio and music apps are LASH'ified. Which makes using LASH pretty pointless at the time being. This little app tries to provide a suboptimal solution which should at least alleviate the user from writing an individual shell script for starting up every single music project.

-- USAGE:

The general commandline syntax is:

lash_wrap [lash_wrap arguments] -- [commandline to start app]

-- EXAMPLE:

An example is sometimes worth more than 100 lines of docs, so here you go:

lash_wrap --jack-name ardour --alsa-name ardour -- ardour2 /media/sound/ardour/foo/foo.ardour

As you can see you have to tell the app in question what file to load its state from. In this case we tell ardour2 to load an ardour file called

/media/sound/ardour/foo/foo.ardour

The user is responsible to save the ardour file before closing the LASH project. This way, the next time when the LASH session gets restored, ardour will be started with the exact same commandline again, thus loading its own session file. At which point the user then can happily continue working on his project.

We also have to tell lash_wrap the jack client and alsa port names of the propgram we want to run if we want our connections to be restored. The --alsa-name option is a bit dirty. It works by searching for the exact client name and then getting its ID. An alternative way would be to specify the client ID if its known beforehand. E.g. a client might allow the client ID itself to be specified:

lash_wrap --alsa-id 64 --jack-name some_app -- some_app --seq-client-id 64

I can't think of any apps that provide this option though at this moment. So i just left it in, because it was easy to implement.

-- PROBING FOR PARAMETERS:

It's also possible to probe the alsa and jack client names. This can be done with the "-p" parameter which starts the wrapped application, waits for a certain period of time listening to new jack and alsa clients before automatically exiting. During the probe a new command line is printed with the probed client names.

An example of a probe command for a soft synth named Phasex:
lash_wrap --probe-client-name -- phasex

Result of the probe:
[Lash-Wrap]: ******************************************************
[Lash-Wrap]: * probed startup command:
[Lash-Wrap]: * lash_wrap -l phasex -j "phasex" -a "PHASEX Synthesizer" -- phasex
[Lash-Wrap]: ******************************************************


-- CAUTION!!!!! READ ON:

If you forget to save your work in the wrapped application it will very likely be lost [unless the app has some auto-save feature]. Once you close the LASH session, lash_wrapped apps will get killed by lash_wrap [first sending a SIGTERM, then a SIGKILL]. Depending on the specific implementation and version of jackd you are using this might have serious unwanted side effects. Be warned ;D

I suppose for some apps there might exist ways to tell them to save/load their state via some alternative way [e.g. by a shell script interface or something]. It might be possible to extend lash_wrap into this direction some time in the future. If you have suggestions, let me know.

F

The probing code the man page and some other changes have been generously provided by Jaakko Sipari.

I have no experience with is, someone else?

[studio32]

AlsaPlayer

A player which can handle jack connections very well!

http://www.alsaplayer.org/

[studio32]

WAON

'WaoN is a Wave-to-Notes transcriber, that is, the inverse of timidity by Tuukka Toivonen (and its descendants timidity++). ("WaoN" also has a meaning of harmony of notes or chord in Japanese!) My original intention is to pick up voicing of harmony from sound of my favorite pianists. (I have no talent to do so, but computer will But there is no functional application of this kind on Unix platform, as far as I know. So I began writing this WaoN by myself.'

http://www.kichiki.com/WAON/waon.html