On Sat, 2011-04-23 at 11:52 +0200, immanuel litzroth wrote:
>
>
>
> Well, hang on... can't you force a client to take a particular
> ID? You
> can do that with the hardware addresses by specifying it in
> asound.conf
> so your MIDI
>
>
>
> Well, hang on... can't you force a client to take a particular ID? You
> can do that with the hardware addresses by specifying it in asound.conf
> so your MIDI interfaces stay in the same place across reboots (otherwise
> it's a race to see which interface initialises first).
>
> I managed
On Fri, 2011-04-22 at 19:22 -0400, Paul Davis wrote:
> > But surely, the client IDs are a moving target. I want to connect
> > to a specific instance of ZynaddsubFX, not to the program that was
> > the second one to get an ALSA ID...
> >
> > Am I missing something?
>
> i don't think so. but since
On Fri, Apr 22, 2011 at 07:55:33PM -0400, David Robillard wrote:
> Why do you know the names of the required ports but not the numbers?
The names are lust 'Launchpad', the numbers are not fixed AFAIK.
> P.S. The direct USB interface to the launchpad is pretty simple, I'm
> driving mine without
On Fri, 2011-04-22 at 22:30 +, Fons Adriaensen wrote:
> On Fri, Apr 22, 2011 at 06:06:54PM -0400, David Robillard wrote:
>
> > Alsa sequencer names aren't unique or intended for use as identifiers,
> > you probably don't want to do this if it's at all possible to avoid...
>
> If that's true,
On Fri, Apr 22, 2011 at 07:22:59PM -0400, Paul Davis wrote:
> i don't think so. but since, as dave pointed out, there is no
> particular mapping between client IDs and names, there's really no way
> to do this. i think. like i said, i consider the whole design totally
> FUBAR'ed. if you use numer
On Fri, Apr 22, 2011 at 7:22 PM, Fons Adriaensen wrote:
> It seems that sending the OSC command /ardour/transport_play
> a second time has the effect of locating back to the previous
> start position and resuming play from there. Could be useful,
> but is this intentional ? The 'Start' widget doe
On Fri, Apr 22, 2011 at 7:18 PM, Lieven Moors wrote:
> On Fri, Apr 22, 2011 at 07:09:24PM -0400, Paul Davis wrote:
>> On Fri, Apr 22, 2011 at 7:05 PM, Lieven Moors wrote:
>>
>> > I had a similar problem in my studio when I wanted to restore
>> > connections with multiple ZynaddsubFX instances. Al
On Fri, Apr 22, 2011 at 06:55:18PM -0400, Paul Davis wrote:
> for myself, i think its reasonable accurate to say that ALSA's
> identification of MIDI ports is totally FUBAR'ed. this doesn't help
> much.
:-) or mayby :-(
> i'm not quite sure what you mean about ardour (2's) behaviour, but its
>
On Fri, Apr 22, 2011 at 07:09:24PM -0400, Paul Davis wrote:
> On Fri, Apr 22, 2011 at 7:05 PM, Lieven Moors wrote:
>
> > I had a similar problem in my studio when I wanted to restore
> > connections with multiple ZynaddsubFX instances. All the port names
> > were the same, so I had no way of know
On Fri, Apr 22, 2011 at 7:05 PM, Lieven Moors wrote:
> I had a similar problem in my studio when I wanted to restore
> connections with multiple ZynaddsubFX instances. All the port names
> were the same, so I had no way of knowing which was which.
> And the client ID is not much help either, beca
On Fri, Apr 22, 2011 at 10:30:55PM +, Fons Adriaensen wrote:
> On Fri, Apr 22, 2011 at 06:06:54PM -0400, David Robillard wrote:
>
> > Alsa sequencer names aren't unique or intended for use as identifiers,
> > you probably don't want to do this if it's at all possible to avoid...
>
> If that'
On Fri, Apr 22, 2011 at 6:30 PM, Fons Adriaensen wrote:
> On Fri, Apr 22, 2011 at 06:06:54PM -0400, David Robillard wrote:
>
>> Alsa sequencer names aren't unique or intended for use as identifiers,
>> you probably don't want to do this if it's at all possible to avoid...
>
> If that's true, what
On Fri, Apr 22, 2011 at 06:06:54PM -0400, David Robillard wrote:
> Alsa sequencer names aren't unique or intended for use as identifiers,
> you probably don't want to do this if it's at all possible to avoid...
If that's true, what purpose do they have at all ?
In this concrete case, I have Pyt
On Fri, 2011-04-22 at 21:10 +, Fons Adriaensen wrote:
> On Fri, Apr 22, 2011 at 04:51:53PM -0400, Paul Davis wrote:
> > On Fri, Apr 22, 2011 at 4:45 PM, Fons Adriaensen
> > wrote:
> > > Hello all,
> > >
> > > after reading ASLA docs for some hours I've not found an
> > > answer to the followi
On Fri, Apr 22, 2011 at 11:24:47PM +0200, Dominic Sacré wrote:
> On Friday 22 April 2011 22:45:34 Fons Adriaensen wrote:
> > after reading ASLA docs for some hours I've not found an
> > answer to the following:
> >
> > Given the ALSA sequencer client and port _names_, find the
> > numbers required
On Friday 22 April 2011 22:45:34 Fons Adriaensen wrote:
> after reading ASLA docs for some hours I've not found an
> answer to the following:
>
> Given the ALSA sequencer client and port _names_, find the
> numbers required to set up a connection (a 'subscription'
> in ALSA lingo).
ALSA client an
On Fri, Apr 22, 2011 at 04:51:53PM -0400, Paul Davis wrote:
> On Fri, Apr 22, 2011 at 4:45 PM, Fons Adriaensen wrote:
> > Hello all,
> >
> > after reading ASLA docs for some hours I've not found an
> > answer to the following:
> >
> > Given the ALSA sequencer client and port _names_, find the
> >
On Fri, Apr 22, 2011 at 4:45 PM, Fons Adriaensen wrote:
> Hello all,
>
> after reading ASLA docs for some hours I've not found an
> answer to the following:
>
> Given the ALSA sequencer client and port _names_, find the
> numbers required to set up a connection (a 'subscription'
> in ALSA lingo).
Hello all,
after reading ASLA docs for some hours I've not found an
answer to the following:
Given the ALSA sequencer client and port _names_, find the
numbers required to set up a connection (a 'subscription'
in ALSA lingo).
Anyone knows how to do this ?
Ciao,
--
FA
_
20 matches
Mail list logo
