Re: jack midi drivers

On Sat, 2007-03-10 at 23:07 +0300, Dmitry Baikov wrote:
> On 3/10/07, Paul Davis <paullinuxaudiosystems.com>
wrote:
> > i fully support this idea, specifically translated
as 'dmitry should
> > have write access and should create a branch to
hold the work".
> >
> > dmitry, send me an ssh public key and i'll give
you write access to the
> > repository.
> 
> Great.
> Sent.

Nice.

Would it be easy enough to include this code in Jack in such
a way that
it can be built as both drivers and bridge clients?  If all
the choices
can be built by default (depending on available API) and the
driver
chosen via cmd line option, everybody's happy (ie no more
API debates).

Larsl's direct /dev file driver looks like it should work on
BSD without
too much (if any) trouble.  Anyone want to do OSX and
Windoh's? 

Also, this is going to force the issue of driver
"client" names.  We
can't have MIDI ports showing up on alsa_pcm...

-DR-


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jackit-devel mailing list
Jackit-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el

On 3/10/07, Dave Robillard <drobillaconnect.carleton.ca> wrote:
> Would it be easy enough to include this code in Jack in
such a way that
> it can be built as both drivers and bridge clients?
It is possible, but I don't see what for.

> If all the choices
> can be built by default (depending on available API)
If you are talking about jack-time.patch, it is not needed
anymore.

> and the driver
> chosen via cmd line option, everybody's happy (ie no
more API debates).
cmdline option is the best solution so far.

> Larsl's direct /dev file driver looks like it should
work on BSD without
> too much (if any) trouble.  Anyone want to do OSX and
Windoh's? 
In case if Larsl's driver has any problems and/or Larsl does
not want
to support it, alsaraw driver can be refactored into three
parts:
common, alsa and oss.

I have no access to OSX and no time/desire to write a wnd
driver.

What to do with PortAudio (read PortMidi) one?
I looked into the API, and seems it will need one thread per
midiport.
Not very good.

> Also, this is going to force the issue of driver
"client" names.  We
> can't have MIDI ports showing up on alsa_pcm...
Right!

Dmitry.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jackit-devel mailing list
Jackit-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el

On Sat, Mar 10, 2007 at 03:35:45PM -0500, Dave Robillard
wrote:
> On Sat, 2007-03-10 at 23:07 +0300, Dmitry Baikov
wrote:
> > On 3/10/07, Paul Davis <paullinuxaudiosystems.com> wrote:
> Nice.
> 
> Would it be easy enough to include this code in Jack in
such a way that
> it can be built as both drivers and bridge clients?  If
all the choices
> can be built by default (depending on available API)
and the driver
> chosen via cmd line option, everybody's happy (ie no
more API debates).
> 
> Larsl's direct /dev file driver looks like it should
work on BSD without
> too much (if any) trouble.  Anyone want to do OSX and
Windoh's? 
> 
> Also, this is going to force the issue of driver
"client" names.  We
> can't have MIDI ports showing up on alsa_pcm...

Right now they are showing up as alsa_midi*. iirc, Paul
wanted something
more generic since alsa is linux only.

Another thing I wondered ... can/should the spaces be taken
out of the
midi device portion of port names? It might be nicer for
commandline
client users.

-Eric Rz.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jackit-devel mailing list
Jackit-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el