Ralf Mardorf wrote: > Christian wrote: > >> Hi Ralf, >> I have just installed Jconv and it seem to be working fine. >> However there seems to be some problem wiht my sound card. For some reason >> the microphone input or the line input doesn't seem to work. It works fine >> in Windows. >> I am new to this so I apologize if the question sounds a little stupid, but >> how do I use ecasound to connect to jack and play a sound file using this >> reverb? >> I tried something like the following: >> ecasound -i test.wav -o jack >> But it didn't work. >> Best regards and many thanks for all your help, >> Christian >> > > Hi Christian :) > > oops, we shouldn't write again to Fons too. He's the coder of Jconv. > > I never used ecasound. > > "*JACK input/outputs* > > JACK is a low-latency audio server that can be used to connect > multiple independent audio application to each other. It is > different from other audio server efforts in that it has been > designed from the ground up to be suitable for low-latency > professional audio work. > > Ecasound provides multiple ways to communicate with JACK servers. To > directly input or output to soundcard, use *-i jack_alsa* and *-o > jack_alsa*. To communicate with other apps, use > *jack_auto,remote_clientname*. To just create ports without making > any automatic connections, there are *jack* and > *jack_generic,local_portprefix*. > > Additionally global JACK options can be set using > *-G:jack,client_name,operation_mode*. 'client_name' is the name used > when registering ecasound to the JACK system. If 'operation_mode' is > "notransport", ecasound will ignore any transport state changes in > the JACK-system; in mode "send" it will send all start, stop and > position-change events to other JACK clients; in mode "recv" > ecasound will follow JACK start, stop and position-change events; > and mode "sendrecv" (the default) which is a combination of the two > previous modes. > > More details about ecasound's JACK support can be found from > ecasound user's guide." >
http://www.eca.cx/ecasound/Documentation/ecasound_manpage.html You should try to run man ecasound and ecasound -h or ecasound --help Don't forget, you are not using Windows. There are a lot of Linux only users, me too, that think that some ideas for Linux audio are obscure. If you know any FOSS OS better for audio than Linux, please let me know soon. I will change to this OS immediately. Windows and MacOS are the better systems to make music, but they aren't FOSS. You have to learn by trial and error. > Okay, I guess you will have this chain: > > Sound card in -> Jconv in / Jconv out -> Ecasound in / Ecasound out -> > Sound card out > > "- o jack_alsa" seems to do the job for the output to the sound card. > Ooops ;) "-o jack_alsa" > Maybe "-i jack_auto,remote_TEST" or "-i jack_auto,remote_Test:Out-1 > jack_auto,remote_Test:Out-2" will be fine. > I guess it's "-i jack_auto,remote_TEST" because "TEST" is the client name and "Out-1" and "Out-2" seems to be the local portprefixes. > Than depending to the HOWTO > http://lists.64studio.com/pipermail/64studio-users/2008-October/001922.html, > the scrip for jack_snapshot must be changed from > > system:capture_1 > TEST:In-1 > TEST:Out-1 > system:playback_1 > TEST:Out-2 > system:playback_2 > > to > > system:capture_1 > TEST:In-1 > > Maybe there is a shell command so that you don't need to connect > "system:capture_1" to "TEST:In-1" by jack_snapshot, but than you have to do > it by the shell command: > > unknown-shell-command -from-port system:capture_1 -to-port TEST:In-1 > > Cheers, > Ralf >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
