All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Paul Davis <pbd@op.net>
Cc: "jackit-devel@lists.sourceforge.net"
	<jackit-devel@lists.sourceforge.net>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [Jackit-devel] Multiple cards.
Date: Wed, 12 Jun 2002 22:23:37 +0900	[thread overview]
Message-ID: <3D074B59.6030602@boosthardware.com> (raw)
In-Reply-To: 200206121243.g5CChIP04283@post2.fast.net

Paul Davis wrote:

>>I can hear Paul now saying you have no desire to make this happen 
>>because you do not work with consumer devices. Unless someone paid you 
>>to do it.
> 
> 
> That's correct. Consumer devices are just that. People trying to do
> multichannel work by ganging such devices are engaged in a strategy I
> don't want to support with my own time.
> 

Not even if the reason is to allow cueing of a track. I think it may 
even be possible to allow this to work in sample sync if alsaplayer is 
the app used to play the file.

Eg1. I could cue the file using my headphones channel on a consumer card 
and then click a switch in alsaplayer to allow the file to stream 
through my pro card. As long as the file was paused between switching 
channels it should retain sample sync because alsaplayer is sample accurate.

Eg2. I could set up three channels in ardour mixer for each alsaplayer 
gui and then I just fade them in/out depending on what channel I want to 
hear the file through. This would definitely loose sample sync but could 
allow for some interesting time effects. Do you fancy the idea of 
"ardour dub sessions"?

> 
>>If it is possible to do and the code was written would it be included in 
>>JACK?
> 
> 
> Its possible, and if it was reasonably written, it would be included
> in JACK.
> 

That's good to know.


> 
>>If it is possible to do how much would it cost to have it implemented?
> 
> 
> I don't know. Somebody else would have to do it.
> 

Is there anything that would entice you into whipping it out?

I can send you a sticker if it helps :)



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/

  reply	other threads:[~2002-06-12 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.1020609234513.20161B-100000@planck.clarku.edu>
     [not found] ` <E17HH98-0005Ai-00@usw-sf-list1.sourceforge.net>
     [not found]   ` <20020610155238.E6051@ecs.soton.ac.uk>
     [not found]     ` <3D06E569.6080305@boosthardware.com>
     [not found]       ` <3D06F382.ED7BCC17@folkwang-hochschule.de>
     [not found]         ` <3D070D18.4050505@boosthardware.com>
     [not found]           ` <3D071681.D0F07B00@folkwang-hochschule.de>
2002-06-12 12:03             ` [Jackit-devel] Multiple cards Patrick Shirkey
2002-06-12 12:45               ` Paul Davis
2002-06-12 13:23                 ` Patrick Shirkey [this message]
2002-06-12 13:43                   ` Paul Davis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D074B59.6030602@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jackit-devel@lists.sourceforge.net \
    --cc=pbd@op.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.