On Wednesday, February 22, 2012 11:42:13 AM joerg-cyril.hoe...@t-systems.com
wrote:
> That's why I'll repeat once more and say that DSound's resampler should
> become that one.
>
> My little knowledge about DSound's 3 initialisation modes (WRITE_PRIMARY
> etc.) tells me it's compatible with such
Hi,
Chris Robinson wrote:
>> You forgot AUDCLNT_STREAMFLAGS_RATEADJUST since w7.
>Interestingly, this flag seems to only have an effect for already-initialized
>streams. ALSA would need a way to adjust the rate of an opened device for this
>to work.
My view on it is this: given that it's said t
Andrew Eikum writes:
> I agree with this analysis. Here's a patch. It uses pipes to separate
> device names, since I know commas are meaningful in ALSA. Perhaps
> that's not enough, and we need to do quoting?
The right way would be to use a MULTI_SZ string.
--
Alexandre Julliard
julli...@wineh
> I agree with this analysis. Here's a patch. It uses pipes to separate
> device names, since I know commas are meaningful in ALSA. Perhaps
> that's not enough, and we need to do quoting?
>
> In any case, this patch ought to be enough to satisfy users for 1.4.
> Any thoughts, anyone?
AFAIK, pipes
On Mon, Feb 13, 2012 at 12:08:57PM -0800, Chris Robinson wrote:
> For now, I think snd_card_next, with registry options for custom prefixes and
> an additional set of devices, is the best way to go. There's simply too much
> junk with snd_ctl_name_hint.
>
I agree with this analysis. Here's a pa
On Monday, February 13, 2012 10:31:06 PM Нискородов Серёжа wrote:
> Ok, I agree, many "junk devices", bad enumeration methods, okay. But
> why you are against a registry parameter? I'm a power user, I know
> WHAT I do, I want to see all ALSA devices, even "junk". Why I can't do
> that?
Mainly beca
2012/2/13 Chris Robinson :
> On Monday, February 13, 2012 8:37:42 PM Нискородов Серёжа wrote:
>> Chris Robinson wrote:
>> > It's not something normal users do, but for "power users" I don't see a
>> > problem with asking them to tell Wine about it.
>>
>> I'm a power user, but for what I have to wro
On Monday, February 13, 2012 8:37:42 PM Нискородов Серёжа wrote:
> Chris Robinson wrote:
> > It's not something normal users do, but for "power users" I don't see a
> > problem with asking them to tell Wine about it.
>
> I'm a power user, but for what I have to wrote device name in regedit,
> if I
>>Because if tomorrow I will add a new device to .asoundrc, I will also
>>have to add it to the WINE registry?
> Registry or winecfg, is there such a difference?
Difference is that I have to describe the device in wine while this
device is already described in .asoundrc.
> Elaborated approach:
>
On Monday, February 13, 2012 6:12:00 PM Нискородов Серёжа wrote:
> >> Here is another trouble with snd_ctl_open. Not all devices in alsa
> >> configuration files have a predefined ctl. Especially defined by user,
> >> for example I don't always define a ctls for all my devices in
> >> .asoundconf
>
Hi,
Нискородов Серёжа wrote:
>I really don't understand you. Why to write "plug:dmix" in wine,
>while you can configure ALSA devices natively via .asoundrc ?
plug:dmix is 9 characters, .asoundrc not well documented, with
features that even people who've been writing them for long can
learn any da
On Monday, February 13, 2012 2:17:13 PM joerg-cyril.hoe...@t-systems.com
wrote:
> Chris Robinson wrote:
> >Plain mmdevapi can't do rate conversions
> You forgot AUDCLNT_STREAMFLAGS_RATEADJUST since w7.
Interestingly, this flag seems to only have an effect for already-initialized
streams. ALSA wo
On Monday, February 13, 2012 10:07:45 AM Andrew Eikum wrote:
> On Sat, Feb 11, 2012 at 06:24:08AM -0800, Chris Robinson wrote:
> > Hmm, actually it seems winealsa already does this enumerating. Except it
> > hardcodes the plughw: prefix for the device string, uses the card index
> > instead of the
> Here's a stupid registry entry patch. The paths are:
> HKCU\Software\Wine\Drivers\winealsa.drv\ALSAOutputDevice
> HKCU\Software\Wine\Drivers\winealsa.drv\ALSAInputDevice
>
> If we can't reach a sensible consensus about device enumeration
> sometime this week, I'll submit this to fix 1.4.
I do no
> snd_ctl_name_hint() and friends:
> +Includes user-specified, non-hw devices as well as true hw devices, but:
> -Misses devices without 'hint' configs (Arch had this problem until a few
> weeks ago, other distros?)
In my Ubuntu 11.04 snd_ctl_name_hint() lists all my devices, that I
described in
>> Here is another trouble with snd_ctl_open. Not all devices in alsa
>> configuration files have a predefined ctl. Especially defined by user,
>> for example I don't always define a ctls for all my devices in
>> .asoundconf
>
> You can use the "hw:" prefix for snd_ctl_open. All you need it for is
On Mon, Feb 13, 2012 at 02:12:02PM +0100, joerg-cyril.hoe...@t-systems.com
wrote:
> Bottom line IMHO:
> 1. Wine-1.4 MUST have a means to select something
>other than "default" without recompiling.
> 2. Via registry or winecfg, I don't mind.
>
> A stupid registry entry would be fine with me.
On Sat, Feb 11, 2012 at 06:24:08AM -0800, Chris Robinson wrote:
> On Saturday, February 11, 2012 2:05:18 PM Нискородов Серёжа wrote:
> > Here is another trouble with snd_ctl_open. Not all devices in alsa
> > configuration files have a predefined ctl. Especially defined by user,
> > for example I do
> Bottom line IMHO:
> 1. Wine-1.4 MUST have a means to select something
> other than "default" without recompiling.
> 2. Via registry or winecfg, I don't mind.
>
> A stupid registry entry would be fine with me. At least, winecfg
> would remain void of GUI logic that's valid for winealsa only. U
Hi,
Нискородов Серёжа wrote:
>Do you can play wav mono 11025Hz directly to your dmix51 device?
>Without "plug:" wrapper? With my soundcard I can't.
>So I can enumerate dmix*: devices to, I even can enumerate all
>devices, but I see almost no sence in this.
My Ubuntu dmix can't either.
All it acce
Hi,
Chris Robinson wrote:
>All but "dmix51:CARD=NVidia,DEV=0" is completely useless, and except for
>iec958, null, and the very bottom one, they all describe the same device
Now we've done a full circle. My feeling past bug #28723 comment #110
http://bugs.winehq.org/show_bug.cgi?id=28723#c110
w
On Saturday, February 11, 2012 2:05:18 PM Нискородов Серёжа wrote:
> > Nope, it won't open in a rate other than 48000hz without plug:. But again,
> > that's fine for mmdevapi as it doesn't support rate conversion by default.
>
> Hmm... Ok. But how it works in Windows? Does you mean that
> applicat
> As I mentioned, native mmdevapi doesn't do samplerate conversion or channel
> remixing. For shared mode, the device only opens with a pre-defined, user-
> selected rate and channel config. The only thing the default native mmdevapi
> will do is accept different sample depths/type (prefering float
On Friday, February 10, 2012 10:50:33 PM Нискородов Серёжа wrote:
> Not only sample type, but sample rate to. For example, dmix plugin
> have predefined samplerate for mixing, so if WINE send other
> samplerate to it without "plug:" wrapper, in best case you will get
> error message and no sound.
> The only thing "plug:" would do that mmdevapi would need is sample type
> conversion.
Not only sample type, but sample rate to. For example, dmix plugin
have predefined samplerate for mixing, so if WINE send other
samplerate to it without "plug:" wrapper, in best case you will get
error message
On Friday, February 10, 2012 5:09:05 PM Нискородов Серёжа wrote:
> > There's no $HOME/.asoundrc on any of my systems, yet I'd like to
> > use "plug:dmix" with Wine, e.g. on systems with PulseAudio installed.
> > I can use speaker-test -Dplug:dmix with no trouble.
> > Will your patch make that appea
> There's no $HOME/.asoundrc on any of my systems, yet I'd like to
> use "plug:dmix" with Wine, e.g. on systems with PulseAudio installed.
> I can use speaker-test -Dplug:dmix with no trouble.
> Will your patch make that appear in the list?
The devices that I can add to the list can be seen in out
Hi,
There's no $HOME/.asoundrc on any of my systems, yet I'd like to
use "plug:dmix" with Wine, e.g. on systems with PulseAudio installed.
I can use speaker-test -Dplug:dmix with no trouble.
Will your patch make that appear in the list?
Нискородов Серёжа wrote:
>To check whether the device is a h
> The trouble is that to be completely correct, you have to Free the
> values you Allocated into previous members of the ids and keys arrays,
> as well as the arrays themselves. That means a for-loop over only the
> valid members of those arrays, and it turns into quite a lot of code
> for an erro
On Thu, Feb 09, 2012 at 10:08:39PM +0200, Нискородов Серёжа wrote:
> > Thanks, I've been wanting to do this for a while. I've been hesitating
> > because ALSA doesn't document the format of their device names. If a
> > device name contains a colon, is it _always_ a hardware device that
> > will be
> Thanks, I've been wanting to do this for a while. I've been hesitating
> because ALSA doesn't document the format of their device names. If a
> device name contains a colon, is it _always_ a hardware device that
> will be returned by the snd_card_* family? Who knows...
To check whether the devic
On Tue, Feb 07, 2012 at 11:32:34PM +0200, Нискородов Серёжа wrote:
> Perhaps the code is not so clear and beautiful, but it works for me,
> and maybe someone wants to send it to the repository, or to correct
> and send a corrected.
One more thing, this messes up the default device selection, which
On Tue, Feb 07, 2012 at 11:32:34PM +0200, Нискородов Серёжа wrote:
> I'm not so good at programming. I just was looking for a way to
> make possible play sound from WINE to ALSA software device other than
> "default".
>
> I wrote a patch that allows you to select the ALSA software device
> from co
Hi, all.
I'm not so good at programming. I just was looking for a way to
make possible play sound from WINE to ALSA software device other than
"default".
I wrote a patch that allows you to select the ALSA software device
from control panel, along with the hardware devices.
Perhaps the code is no
34 matches
Mail list logo
