Re: [ecasound] -i:jack, client misconnects when client has midi ports

This is a minor issue, considering jack_multi provides
an alternative for those rare cases.

Thanks, with friendly greetings :)

On Fri, Feb 01, 2019 at 09:13:50AM -1000, Joel Roth wrote:
> This is based on a report I received.
>
> Here is these relevant jack_lsp output:
>
> effect_0:lv2_events_in
> properties: input,
> 8 bit raw midi
> effect_0:lv2_midi_out
> properties: output,
> 8 bit raw midi
> effect_0:lv2_audio_in_1
> properties: input,
> 32 bit float mono audio
> effect_0:lv2_audio_in_2
> properties: input,
> 32 bit float mono audio
> effect_0:lv2_audio_out_1
> properties: output,
> 32 bit float mono audio
> effect_0:lv2_audio_out_2
> properties: output,
> 32 bit float mono audio
>
> When using -f:s32_le,1,48000 -i:jack,effect_0 in a chain setup,
> the connection goes to port effect_0:lv2_events_in.
>
> I think Ecasound was developed before JACK had midi.
> Looks like it needs patched to skip midi ports.
>
> Regards,
>
> Joel
>
> --
> Joel Roth
>
>
>
>
> _______________________________________________
> Ecasound-list mailing list
> Ecasound-list@email-addr-hidden
> https://lists.sourceforge.net/lists/listinfo/ecasound-list

-- 
Joel Roth
  
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list