xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Boutsioukis <gboutsioukis@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: PV Audio GSoC Project
Date: Thu, 5 May 2011 22:32:53 +0300	[thread overview]
Message-ID: <BANLkTinzqUhFksgY_JoNqj6VKGPZP7_fiA@mail.gmail.com> (raw)
In-Reply-To: <20110505140016.GC4386@dumpdata.com>

> Those are the two examples. I know very little about the audio systems
> under Linux and Windows so I don't know how well they could mesh
> together and what problems could be expected. I guess I'll have to wait
> and see what design you come up with before I can comment :)

The only thing I can safely say right now is that sound interfaces
seem to be more hardware-oriented than OS-oriented, so maybe there
won't be any similar issues in this case.

> I've just looked up what PulseAudio actually is, and it appears that it
> already runs under Windows although that may not be in a useful way for
> your project.

I don't think that there's any hope that this port would help in any
way. One of the reasons of using PulseAudio is to keep the backend
from becoming subsystem specific, as it would for example with an ALSA
frontend. But much of the frontend code is still going to be
OS-specific anyway.

In the particular case of Windows, it would probably waste way more
effort to implement this frontend on top of anything but the standard
(Port Class?) driver model. Especially because, at least from what
I've seen so far, the backend code for audio is relatively trivial
compared to the frontend.

  parent reply	other threads:[~2011-05-05 19:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 12:02 PV Audio GSoC Project George Boutsioukis
2011-05-05 12:36 ` James Harper
2011-05-05 14:00   ` Konrad Rzeszutek Wilk
2011-05-05 14:26     ` James Harper
2011-05-05 19:32     ` George Boutsioukis [this message]
2011-05-05 20:58       ` Konrad Rzeszutek Wilk

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=BANLkTinzqUhFksgY_JoNqj6VKGPZP7_fiA@mail.gmail.com \
    --to=gboutsioukis@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).