28 Jan
2019
28 Jan
'19
6:30 p.m.
On Mon, Jan 28, 2019, 7:52 PM Ralf Mardorf <ralf.mardorf(a)alice-dsl.net
wrote:
How does your script find out to what card it assigned
the aliases?
it takes some info for the group and a pattern string to match against
ports, you'd need to determine manually which ports belong to which device
and supply them. from there one of the devices ports would possess
predictable and unique names to restore connections against. the script and
patch were written with grouping audio in mind, but it could be used to
somewhat solve this I suppose
Have you ever used two or more identical PCI cards as
MIDI interface?
I've not.
On Mon, Jan 28, 2019, 7:52 PM Ralf Mardorf <ralf.mardorf(a)alice-dsl.net
wrote:
On Mon, 28 Jan 2019 12:01:56 -0500, Sunset Tech
wrote:
On Mon, Jan 28, 2019, 11:15 AM Ralf Mardorf
wrote:
How does your script find out to what card it assigned the aliases?
Have you ever used two or more identical PCI cards as MIDI interface?
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
FWIW apart from jack audio, there are also jack
and ALSA midi
available. AFAIK when for example using two TerraTec EWX 24/96 PCI
cards as MIDI interfaces, there is no way at all to restore MIDI
connections automatically. The only way is to do all MIDI IO
connections with those cards manually. Even changing the name of at
least one card, does only affect audio, the MIDI names of identical
PCI cards are always the same.
I'll admit i am not sure what your general
thought here is? depending
on the method used to restore connections, with the script I wrote one
of these devices could be oneshot assigned group aliases for its midi
ports, and then connections restored from there