Christian don't take care of this.
It's just a stupid thought that has no effect to the usage.
Ralf Mardorf wrote:
> Ralf Mardorf wrote:
>
>> *lol* I read something about jack_connect should be a "example" client,
>> I should have checked
>> jack_connect --help
>> usage: jack_connect <src_port> <dst_port>
>> The source port must be an output port of the source client.
>> The destination port must be an input port of the destination client.
>>
>>
>
> Maybe this is an example client?!, but without effect?!, it only has an
> input, no signal processing and an output?! or isn't it an client itself
> and just a command to connect clients?!
>
*?*
Is it a client because it's using jack headers, but without own ports?
So, it is a command to connect ports of other clients, that means it is
a client itself, but a client that connect ports of other clients
directly, without own ports?
I think I've got it.
_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users
Jconv should be part of the next 64 Studio release
