Fluidsynth exits when it finds a EOF, so you have to keep the standard input open; try this: $ (cat filename.sh; cat ) | fluidsynth -m alsa_seq ~/gerrit.sf2 that will leave the fluidsynth shell ready for inputs after the commands in filename.sh have been sent to it. HTH, HAND Il sab, 2004-01-31 alle 02:00, Gerrit Niestijl ha scritto: > Hi, > > > I think fluidsynth has a special option to force interactive mode, but I'm > > not sure. Just try fluidsynth --help | less. > > Well, there is a -i or --no-shell parameter, it suggests the > opposite, but does not work at all: > > $ fluidsynth -i -m alsa_seq ~/gerrit.sf2 > cca_open_socket: error connecting to destination 'localhost:14541': Connection refused > cca_comm_connect_to_server: could not create server connection > cca_init: could not connect to server 'localhost:14541' - disabling ladcca > ** Using format s16, rw, interleaved > $ > > That's it, fluidsynth only displays some messages and then quits. I am > not even trying to send commands! > > Maybe it's some shell | pipe magic i don't know about? > > Is there anyone on this list who has some more experience with sending > commands from a file to fluidsynth? > > -- > gerrit -- Linux User #153639 RoLug Member - http://rovigo.linux.it GnuPG id:E88F9363 keyserver.linux.it Jabber id:cava@xxxxxxxxxxxxxxx -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata Url : http://music.columbia.edu/pipermail/linux-audio-user/attachments/20040201/ca5e1ce5/attachment-0001.bin
