public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: pulseaudio.exe never have a sound
Date: Fri, 08 Mar 2019 19:10:00 -0000	[thread overview]
Message-ID: <87pnr15gim.fsf@Rainer.invalid> (raw)
In-Reply-To: <1552002839127-0.post@n5.nabble.com> (Bobone's message of "Thu, 7	Mar 2019 16:53:59 -0700 (MST)")

Bobone writes:
> Corinna Vinschen-2 wrote
>> Is anybody here interested in removing these limitations?  One problem is
>> that Cygwin only recogizes a single audio device, the current default
>> device.  It would be cool if somebody with a bit of knowledge in Windows
>> audio could update Cygwin's /dev/dsp code a bit.
>
> Is it so that no matter what library, e.g. OSS or libdao, it is not possible
> to address other sound devices?

Cygwin only has one audio device, namely /dev/dsp -- and that device is
the current default device in Windows.  So no, it doesn#t matter which
library you are using, they will all have to use the same single device.
Corinna was asking for someone to provide code so that any other sound
devices Windows knows about show up under /dev as well.  Only then would
it become possible for libraries to address "other devices".


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2019-03-08 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 11:58 rexdf Rexdf
2015-03-20 21:56 ` Yaakov Selkowitz
2015-03-21  8:04   ` Rexdf
2015-03-21 13:50     ` Mark Geisert
2015-03-23 10:08   ` Corinna Vinschen
2019-03-07 23:59     ` Bobone
2019-03-08 15:39       ` jwang
2019-03-08 19:10       ` Achim Gratz [this message]
2019-03-08 21:41         ` Bobone
2019-03-09 15:41           ` Corinna Vinschen

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=87pnr15gim.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).