Re: [pulseaudio-discuss] [PATCH] M-audio fasttrack pro: fix input device string
David Henningsson launchpad@epost.diwic.se writes: On 2010-05-25 01:26, Lennart Poettering wrote: On Wed, 19.05.10 01:00, David Henningsson (launchpad@epost.diwic.se) wrote: Heya, Sometimes the input device shows up at device ID 0, and sometimes device ID 1, so try both. Humpf. Why is that so? The driver authors presumably have a reason for this assignment, and before we merge something like this we should figure out what's going on and how we should label this. We currently label that mapping Analog Streo Channel A. It appears to me that that mapping label might not be accurate anymore after such a change. AFAIK this sound card is just using the standard USB Audio drivers. I don't have access to this particular hardware either, so I'm not in a position to debug the drivers ATM. So I can't answer your question and my guess is that it varies between hardware revisions. Perhaps David Kågedal, who wrote the initial profile, knows more about this? I haven't seen it switch between device IDs, so I have no idea. But I didn't really use it a lot with my linux machine, so the testing has been light. But it worked without problem. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Does pulseaudio require alsa/oss
Colin Guthrie gm...@colin.guthr.ie writes: 'Twas brillig, and Nix at 23/04/10 00:43 did gyre and gimble: Fedora, at least, doesn't use ck-launch-session: it uses ck-xinit-session, which is not in upstream console-kit at all; it's in the RH-specific xinit package. Can you say which pacakge provides that file? It doesn't seem to be part of the main ConsoleKit spec (i.e. with a patch). I'd like to look at this file but without knowing what package it's in, it's hard to comment. It's derived from ck-launch-session but does some incomprehensible-to-non-dbus-hackers and uncommented thrashing about with dbus first. It too appears to run a shell and then exit, so how it does what it does is equally mysterious to me. Of course, it, also, has no documentation whatsoever. Maybe it's not ready for upstream yet? Fedora tends to be a testing ground for a lot of new things, so this is not overly uncommon. I love the new Linux world. :/ Would you prefer some completely unknown and mysterious system to one you actually can poke about with and figure out? Honestly, if this bothers you, do something about it - speak to the people involved and help write the docs. Moaning solve precisely nothing. I don't think that's what he meant. There are upsides and downsides to how Linux works and is developed. I have felt the same frustration about these kinds of new subsystems that lack documentation. Most recently it was udev that has no description about its properties, not even in the source code. Of course we have to moan, otherwise will never document anything they do. And asking people who know absolutely nothing about something quite complex and obscure to write the documentation soves precisely nothing. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Does pulseaudio require alsa/oss
David Kågedal dav...@lysator.liu.se writes: Of course we have to moan, otherwise will never document anything they do. And asking people who know absolutely nothing about something quite complex and obscure to write the documentation soves precisely nothing. Or, put another way: Complaining about missing or poor documentation is a bug report just like copmlaining about missing or broken functionality. Just like any bug report, it can be fixed by someone who knows how it works, or by someone who doesnt (with much greater effort). And no, I'm not asking for big manuals presenting everything in perfect style. But I'm asking developers to add some notes about how stuff actually works. I think that Lennart is good at this, for example. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Saving stream volumes per physical output
Tanu Kaskinen ta...@iki.fi writes: to, 2010-01-14 kello 21:54 +0100, Lennart Poettering kirjoitti: On Wed, 06.01.10 05:18, Tanu Kaskinen (ta...@iki.fi) wrote: Then at some point I switch back to the headphones. m-d-r restores the sink reference volume to 0 dB and m-s-r doesn't do anything. Now the music stream has also absolute volume 0 dB, which is 10 dB more than what I want the headphones to have. When I changed the volume while using the speakers, it shouldn't have affected the volume that I get when using the headphones. Yes, but that is expected. If you change the stream volume you change the stream volume. if you change the device volume you change the device volume. But it's so tempting to use the volume slider in Rhythmbox ;) Now that you have convinced me to some degree about that the device volume should be the usual volume to adjust, I guess my biggest problem are the volume sliders in individual applications. I believe they cause problems/inconveniences for many users (I'm going here solely by my own intuition; I don't remember hearing any actual complaints). Do you possibly have the opinion that applications should get rid of the volume sliders, or make them control the device volume? That wouldn't make sense. If I pull the volume slider in Rhythmbox, I expect it to only affect the sound coming from Rhythmbox. I'm not sure I understood what the problem was. If you move a stream to a device with the volume cranked up, you shouldn't be surprised that it gets louder. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Stream volumes as the universal volume adjustment method
Lennart Poettering lenn...@poettering.net writes: By the way, with the per-output stream restoring it might make sense to also include the sink name in the onscreen display that shows the stream name. So instead of just Music, it would show Music via M-Audio FastTrack Pro (Headphones). That would again provide more hints about what really happens (but I guess it would really be too much information). I thought about this too. It might make sense to show the device string in the streams line iff there is more than one device. In that case it is useful and otherwise the information is redundant. There is a related case that I mentioned a long time ago. I had a Creative X-mod USB card (I sold it, so I can no longer test this). It has a big round volume knob that I thought would be nice to use to control the volume of the sound coming from the device. But no, the volume knob doesn't do that. I simply acts as a keyboard and sends increase-volume/decrease-volume keystrokes. This means that it would usually (depending on how I configure things) not control what comes out of the Xmod, but instead control the main volume (which are the internal laptop speakers or headphones. The workaround was of course to make the Xmod the main device, and use the internal card as a secondary. But I was really annoyed by this misdesign. Could this be solved in PA somehow? -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] M-Audio FastTrack Pro
Lennart Poettering lenn...@poettering.net writes: On Fri, 15.01.10 10:41, David Kågedal (dav...@lysator.liu.se) wrote: udev actually sets two props: ID_MODEL and ID_MODEL_ENC. The former has all special chars (including spaces) replaced by underscore. The latter has them escape in a \x20 like notation. I have now modified PA to use ID_MODEL_ENC and undo the encoding. You should now get the USB supplied names without underscores. Wonderful! I didn't get any response to my question on linux-hotplug. Have you seen any kind of documentation about these properties anywhere, by the way? Nah. But it helps being friends with the udev maintainer... Then you could perhaps give him a gentle nudge to at least write a comment in the source code... -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Saving stream volumes per physical output
Lennart Poettering lenn...@poettering.net writes: Oh, two hearts beat in my chest. On one hand I think yes, the apps too should show the device volume since that is mroe likely what people want to change. But then on the other I think if we show something at all, we probably should show something that is not completely redundant and that amkes sense for someone who did understand the idea of stream and device volumes. If we'd show the devcie volume in the apps this would be redundant, since the usual volume hotkeys/notification icon handle/show that anyway, and it is kinda surprising if an in-app volume changes the other volumes too. So, I guess in the end I am a little bit more leaning to the side that the apps should show per-stream volumes. We (you) need to think of what the mental model for the user interface is. I see the applications on the screen in a similar way as gadgets on my real desk, it would seem strange if when I turned down the volume on the radio in the desk corner, it also turned down the volume of the alarm clock in the other corner. The device volume is not always interesting at all, since I might have sent the audio to an amp with a hardware volume knob. Then it really doesn't make sens to control anything else than stream volumes (or application volumes as the user sees it) from the computer screen. The rules would of course be very different if I was using an N900 or something similar. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] M-Audio FastTrack Pro
Lennart Poettering lenn...@poettering.net writes: On Thu, 07.01.10 17:31, David Kågedal (dav...@lysator.liu.se) wrote: Sure, I will do that. But I'm still not sure I understand why we aren't using then perfectly good name M-Audio FastTrack Pro that apparently is reported by ALSA in /proc/asound/cards. See Lennart's point 3 above. In *your* case it's nice, but apparently in the majority of cases it's not nice and totally generic which is no use to anyone. Yes, the USB information is nice for me. But PA shows a broken string that it seems to have invented itself. So far, nobody has been able to explain why it does that (until you gave a suggestion below). If it had simply used the USB information, I would have been happy. You maybe., most others not. It is a simple fact that most manufacturers dont give teh USB descriptor data the love it deserves, e.g. very seldomly the USB serial id is actually useful. Sure. But I'm just complaining that someone (perhaps udev) is making it deliberately worse, so that it isn't usefule even if the manufacturer gets its act together. The USB descriptor data is available via sysfs (/sys/bus/usb/devices/*-*/manufacturer and /sys/bus/usb/devices/*-*/product). If you check that you will notice that very often the data in those fields is not exactly useful if it is available at all (in which case those files wont exist) All of them look pretty good on my system: krank% cat /sys/bus/usb/devices/*/product PS2 to USB Converter Microsoft 5-Button Mouse with IntelliEye(TM) FastTrack Pro USB2.0 Hub Controller O2Micro CCID SC Reader EHCI Host Controller EHCI Host Controller UHCI Host Controller UHCI Host Controller UHCI Host Controller UHCI Host Controller UHCI Host Controller These two ultimately come from UDEV: udev_device_get_property_value(card, ID_MODEL_FROM_DATABASE) and udev_device_get_property_value(card, ID_SERIAL) So I guess udev puts the underscores in. Thank you. Finally a pointing finger. So why is udev giving us a mangled name? And why is PA using that, rather than using the information it obviously can get from the device? Because we trust udev. And we want to keep the bus-specific code in PA at a minimum. That sounds sensible. And udevadm info --path=/sys/bus/usb/devices/2-4.4 --query=property | grep ID_MODEL does show the broken name (and there is no ID_MODEL_FROM_DATABASE). I guess I'll move my complaints to the udev people (or possibly the Ubuntu people) and see what emerges. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] M-Audio FastTrack Pro
Lennart Poettering lenn...@poettering.net writes: And another thing: The sinks appear as FastTrack_Pro ..., with an underscore instead of a space for some reason. That's data read from the USB device itself. PA uses that only if no prettier device string is available in the usb.ids database (which is the same one that is used by lsusb). But that is the strange part. There is no underscore in any ALSA output I found. This is from /proc/asound/cards, for instance: 1 [Pro]: USB-Audio - FastTrack Pro M-Audio FastTrack Pro at usb-:00:1d.7-4.4, full speed It has USB ID 0763:2012, but I don't even see it listed in http://www.linux-usb.org/usb.ids In /proc/asound/card1/id it is simply described as Pro. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] M-Audio FastTrack Pro
Lennart Poettering lenn...@poettering.net writes: On Thu, 07.01.10 15:08, David Kågedal (dav...@lysator.liu.se) wrote: Lennart Poettering lenn...@poettering.net writes: And another thing: The sinks appear as FastTrack_Pro ..., with an underscore instead of a space for some reason. That's data read from the USB device itself. PA uses that only if no prettier device string is available in the usb.ids database (which is the same one that is used by lsusb). But that is the strange part. There is no underscore in any ALSA output I found. This is from /proc/asound/cards, for instance: ALSA includes its own string database in the drivers. On most devices ALSA usually uses only a string like USB Audio which is why we use that as last resort only, if the USB descriptor does not include s string. 1 [Pro]: USB-Audio - FastTrack Pro M-Audio FastTrack Pro at usb-:00:1d.7-4.4, full speed It has USB ID 0763:2012, but I don't even see it listed in http://www.linux-usb.org/usb.ids Yes, that's precisely the reason why PA falls back to that string that is read from the USB device itself: if there was an entry in the db it would take precedence. That's why I asked you to submit an entry with a pretty string. But the string read from the USB device itself has no underscore, as far as I can tell. In /proc/asound/card1/id it is simply described as Pro. Yes, that is just a logical string that is used do situingish it from the other cards in the system, it is a string similar to how network interfaces are called eth0 or wlan0. Here's the order how we look for a name: 1) use the usb.ids name if there is one in the db 2) use the usb device string read from the device itself is there is one 3) fallback to the descriptive name alsa uses for it which often enough is very generic, such as USB Audio. And I asked you to add a pretty string to usb.ids and submit that to the official database so that everyone can enjoy a nicer string. Sure, I will do that. But I'm still not sure I understand why we aren't using then perfectly good name M-Audio FastTrack Pro that apparently is reported by ALSA in /proc/asound/cards. In 2) in your list, are you saying that PA reads FastTrack_Pro from somewhere? lsusb -v also lists the name without underscore. Here is part of the output from pacmd list: index: 39 name: alsa_output.usb-M-Audio_FastTrack_Pro-00.analog-stereo-a-output driver: module-alsa-card.c [...] properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = USB Audio alsa.id = USB Audio alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 1 alsa.card_name = FastTrack Pro alsa.long_card_name = M-Audio FastTrack Pro at usb-:00:1d.7-4.4, full speed alsa.driver_name = snd_usb_audio device.bus_path = pci-:00:1d.7-usb-0:4.4:1.0 sysfs.path = /devices/pci:00/:00:1d.7/usb2/2-4/2-4.4/2-4.4:1.0/sound/card1 udev.id = usb-M-Audio_FastTrack_Pro-00 device.bus = usb device.vendor.id = 0763 device.vendor.name = Midiman device.product.id = 2012 device.product.name = FastTrack_Pro device.serial = M-Audio_FastTrack_Pro device.string = hw:1,0,0 device.buffering.buffer_size = 352800 device.buffering.fragment_size = 176400 device.access_mode = mmap+timer device.profile.name = analog-stereo-a-output device.profile.description = Analog Stereo Channel A device.description = FastTrack_Pro Analog Stereo Channel A alsa.mixer_name = USB Mixer alsa.components = USB0763:2012 module-udev-detect.discovered = 1 device.icon_name = audio-card-usb What shows up in pavucontrol is device.description, as far as I can tell. How is that formed? Does it use device.product.name? I tried digging through the sources, but I didn't really manage to get to the source of it. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] M-Audio FastTrack Pro
Colin Guthrie gm...@colin.guthr.ie writes: 'Twas brillig, and David Kågedal at 07/01/10 15:52 did gyre and gimble: Lennart Poettering lenn...@poettering.net writes: 3) fallback to the descriptive name alsa uses for it which often enough is very generic, such as USB Audio. And I asked you to add a pretty string to usb.ids and submit that to the official database so that everyone can enjoy a nicer string. Sure, I will do that. But I'm still not sure I understand why we aren't using then perfectly good name M-Audio FastTrack Pro that apparently is reported by ALSA in /proc/asound/cards. See Lennart's point 3 above. In *your* case it's nice, but apparently in the majority of cases it's not nice and totally generic which is no use to anyone. Yes, the USB information is nice for me. But PA shows a broken string that it seems to have invented itself. So far, nobody has been able to explain why it does that (until you gave a suggestion below). If it had simply used the USB information, I would have been happy. Cheking your product, it does indeed look like it's missing from the usb ids database: https://usb-ids.gowdy.us/read/UD/0763 (as 2012 is missing). Yes, I already wrote that in my mail. In 2) in your list, are you saying that PA reads FastTrack_Pro from somewhere? lsusb -v also lists the name without underscore. device.product.name = FastTrack_Pro device.serial = M-Audio_FastTrack_Pro These two ultimately come from UDEV: udev_device_get_property_value(card, ID_MODEL_FROM_DATABASE) and udev_device_get_property_value(card, ID_SERIAL) So I guess udev puts the underscores in. Thank you. Finally a pointing finger. So why is udev giving us a mangled name? And why is PA using that, rather than using the information it obviously can get from the device? Col PS FWIW, I have a similar issue wiht my USB speakers. I put mine in the database a while back, but it should be able to get it without this info anyway. I can do that too, but I think that when M-Audio actually manages to include useful USB descriptions, we should be able to use that in PA. Good information from the source (the vendor) should be encouraged. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] How to disable pulseaudio daemon
Burkhard Stubert burkhard.stub...@googlemail.com writes: Hi, I would like to disable the pulseaudio daemon temporarily. PA runs per user session. How do I do this? You are not very specific about what you want to do, but perhaps pasuspender is what you are looking for? Run pasuspender otherprogram to run otherprogram with pulseaudio temporarily disabled (no longer using the audio devices). When it finished, pulsaudio will be enabled again. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] M-Audio FastTrack Pro
I created a mixer profile for my M-Audio FastTrack Pro USB card that
allows both stereo output channels to be used.
I should probably add a profile that allows the input channels to appear
as two mono sources, as well as the current stereo source, but I don't
have a microphone around to test it (and I'm lazy).
This was simple, since it is similar to the Native Instruments Audio 4
DJ profile file that was included, but not identical (only two channels
input e.g.)
I wonder, shouldn't ALSA/PulseAudio be able to somehow guess the profile
so that the two stereo channels appear automatically?
And another thing: The sinks appear as FastTrack_Pro ..., with an
underscore instead of a space for some reason.
I created a file /etc/udev/rules.d/91-pulseaudio.rules with the
following contents:
SUBSYSTEM!=sound, GOTO=pulseaudio_x_end
ACTION!=change, GOTO=pulseaudio_x_end
KERNEL!=card*, GOTO=pulseaudio_x_end
SUBSYSTEMS==usb, ATTRS{idVendor}==0763, ATTRS{idProduct}==2012,
ENV{PULSE_PROFILE_SET}=maudio-fasttrack-pro.conf
LABEL=pulseaudio_x_end
and the attached file maudio-fasttrack-pro.conf was placed in
/usr/share/pulseaudio/alsa-mixer/profile-sets/
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
; M-Audio FastTrack Pro
;
; This card has one duplex stereo channel called A and an additional
; stereo output channel called B.
;
; We knowingly only define a subset of the theoretically possible
; mapping combinations as profiles here.
;
; See default.conf for an explanation on the directives used here.
[General]
auto-profiles = no
[Mapping analog-stereo-a-output]
description = Analog Stereo Channel A
device-strings = hw:%f,0,0
channel-map = left,right
direction = output
[Mapping analog-stereo-a-input]
description = Analog Stereo Channel A
device-strings = hw:%f,0,0
channel-map = left,right
direction = input
[Mapping analog-stereo-b-output]
description = Analog Stereo Channel B
device-strings = hw:%f,1,0
channel-map = left,right
direction = output
[Profile output:analog-stereo-all+input:analog-stereo-all]
description = Analog Stereo Duplex Channel A, Analog Stereo output Channel B
output-mappings = analog-stereo-a-output analog-stereo-b-output
input-mappings = analog-stereo-a-input
priority = 100
skip-probe = yes
[Profile output:analog-stereo-a-output+input:analog-stereo-a-input]
description = Analog Stereo Duplex Channel A
output-mappings = analog-stereo-a-output
input-mappings = analog-stereo-a-input
priority = 40
skip-probe = yes
[Profile output:analog-stereo-b+input:analog-stereo-b]
description = Analog Stereo Output Channel B
output-mappings = analog-stereo-b-output
input-mappings =
priority = 50
skip-probe = yes
[Profile output:analog-stereo-a]
description = Analog Stereo Output Channel A
output-mappings = analog-stereo-a-output
priority = 5
skip-probe = yes
[Profile output:analog-stereo-b]
description = Analog Stereo Output Channel B
output-mappings = analog-stereo-b-output
priority = 6
skip-probe = yes
[Profile input:analog-stereo-a]
description = Analog Stereo Input Channel A
input-mappings = analog-stereo-a-input
priority = 2
skip-probe = yes
--
David Kågedal
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] setting a volume on a short lived stream
Lennart Poettering lenn...@poettering.net writes: On Fri, 30.10.09 08:15, Brian J. Murrell (br...@interlinx.bc.ca) wrote: On Fri, 2009-10-30 at 02:11 +0100, Lennart Poettering wrote: This is admittedly a problem, but I kinda hope that it will fix itself by applications tagging event sounds properly. I'm sceptical. I certainly would make sense to allow volume changes shortly after a stream died. The low-level technology in PA allows that, it's just that g-v-c and pavucontrol currently do not make use of this. In the meanwhile, is there anything I can do manually to effect this? Command line is just fine with me in the interim. You can just tag your streams properly via env vars, as already pointed out, and then use the system sound slider: $ PULSE_PROP='media.role=event' metacity The code on http://pulseaudio.org/wiki/ApplicationProperties seems to set this instead: $ PULSE_PROP_media.role=event metacity Does both work, or am I just confused? -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] setting a volume on a short lived stream
David Kågedal dav...@lysator.liu.se writes: Lennart Poettering lenn...@poettering.net writes: On Fri, 30.10.09 08:15, Brian J. Murrell (br...@interlinx.bc.ca) wrote: On Fri, 2009-10-30 at 02:11 +0100, Lennart Poettering wrote: This is admittedly a problem, but I kinda hope that it will fix itself by applications tagging event sounds properly. I'm sceptical. I certainly would make sense to allow volume changes shortly after a stream died. The low-level technology in PA allows that, it's just that g-v-c and pavucontrol currently do not make use of this. In the meanwhile, is there anything I can do manually to effect this? Command line is just fine with me in the interim. You can just tag your streams properly via env vars, as already pointed out, and then use the system sound slider: $ PULSE_PROP='media.role=event' metacity The code on http://pulseaudio.org/wiki/ApplicationProperties seems to set this instead: $ PULSE_PROP_media.role=event metacity Does both work, or am I just confused? And by the way, neither is mentioned in http://pulseaudio.org/wiki/FAQ#WhatenvironmentvariablesdoesPulseAudiocareabout -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] setting a volume on a short lived stream
Colin Guthrie gm...@colin.guthr.ie writes: And by the way, neither is mentioned in http://pulseaudio.org/wiki/FAQ#WhatenvironmentvariablesdoesPulseAudiocareabout Indeed, that should be updated. Feel free to make the changes :) Done. But since I don't really know anything I couldn't write anything really useful. Please, someone who knows how PULSE_PROP is interpreted, fill it with more complete information. Like, can you put more than one property in it? -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio elusive
Colin Guthrie [EMAIL PROTECTED] writes: 'Twas brillig, and David Kågedal at 08/12/08 10:29 did gyre and gimble: Colin Guthrie [EMAIL PROTECTED] writes: 'Twas brillig, and Luke Yelavich at 07/12/08 20:34 did gyre and gimble: Pavucontrol hasn't yet been included in Ubuntu, pavucontrol isn't included in Ubuntu??!!?? This cannot be true surely? It's main app to control pulseaudio... sure, it's has UI problems, but talk about cutting of your nose to spite your face. It's in the pavucontrol package, un the universe section. Phew! Note that universe is disabled by default, so you really have to know how to look for it. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio elusive
Colin Guthrie [EMAIL PROTECTED] writes: 'Twas brillig, and Luke Yelavich at 07/12/08 20:34 did gyre and gimble: Pavucontrol hasn't yet been included in Ubuntu, pavucontrol isn't included in Ubuntu??!!?? This cannot be true surely? It's main app to control pulseaudio... sure, it's has UI problems, but talk about cutting of your nose to spite your face. It's in the pavucontrol package, un the universe section. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio elusive
Sean McNamara [EMAIL PROTECTED] writes: Universe hasn't been disabled by default for... years. If the first command you run after a vanilla install of Ubuntu 8.04 or 8.10 is sudo aptitude install pavucontrol, it will work. Not sure when universe was first enabled by default, but it was a _long_ time ago... anyone still using an Ubuntu release that old shouldn't expect any meaningful functionality out of the PulseAudio version shipped with that. It was probably still called polypaudio! Sorry for the misinformation. I guess I don't do fresh installs often enough. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] How to PA - PA
Colin Guthrie [EMAIL PROTECTED] writes: Hi, First of all, I'm a bit confused by your setup. Am I right in saying that you want to *run* applications on you your server but have the display *and* sound come out on the X client? This is what I'd guess as being the typical setup and should work out of the box without any manual tweaking: You sound confused. Remember that the X terminal machine runs the X server. And the X client runs on the server machine. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pavucontrol -- server selection?
Paul Fox [EMAIL PROTECTED] writes: matthew wrote: I believe you can just specify the environment variables and then run the app. So try this: export PULSE_SERVER=xxx.xxx.xxx.xxx Another variable option is PULSE_SINK. I forget where I found this little tidbit, but it works for me! Matt well, i was about to point out that i'd already tried PULSE_SERVER, but i tried it again, and now it works. dammit. :-) i have no idea why it didn't work before. i found the command in my shell history to re-run it, so it wasn't a typo. i've used pulse to listen to some music in the meantime, but i'd be surprised if that affected how pavucontrol works. :-/ well wait. it now works remotely, but not locally. okay. i'm confused. It sounds like you need to show us exactly the commands you run. Starting from a fresh shell. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Volume controller redirection
Lennart Poettering [EMAIL PROTECTED] writes: 2) When I control the volume of the Xmod, the volume jumps up and down rather erratically, and loses synch between the right and left channel. But this happens when using ALSA directly, so it's not related to PA. Probably some fuckup in the gnome volume mixer applet? Please try this again and close all mixer windows and remove the applet from your panel. I tried to remove the applet, but it didn't seem to help. I'm not certain there isn't something else still left, though. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Volume controller redirection
This might not really be something for PA to handle, but since it's related, I thought I'd ask here anyway. I bought a Creative Xmod to use with my laptop when I'm at the desk. It is a USB soundcard with a line out that I connect to the speakers. It also has a larg volume knob, but for some reason that knob isn't a hardware volume controller, but sends messages over USB and lets the software handle it. I run GNOME/Ubuntu 7.10, and the knob actually works without any configuration. But there are two problems: 1) The volume knob will control the main mixer in the GNOME settings, i.e. the same as the volume buttons on the laptop. This means that unless I reconfigure it, it will control the volume of the internal speakers instead of the external speakers that are connected to it. I can reconfigure gnome so that both volume controllers control the Xmod volume instead. Does anyone know if there is a way to make each volume controller control different mixers? 2) When I control the volume of the Xmod, the volume jumps up and down rather erratically, and loses synch between the right and left channel. But this happens when using ALSA directly, so it's not related to PA. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] priority logic in main seems broken
the following log message:
W: core-util.c: setpriority(): Permission denied
I suspect that since the -11 nice value breaks a resource limit, we
should have called setrlimit to change it before dropping CAP_SYS_RESOURCE.
if (suid_root) {
pa_bool_t drop;
drop = conf-cmd != PA_CMD_DAEMON || !conf-realtime_scheduling;
#ifdef RLIMIT_RTPRIO
if (!drop) {
/* At this point we still have CAP_NICE if we were loaded
* SUID root. If possible let's acquire RLIMIT_RTPRIO
* instead and give CAP_NICE up. */
const pa_rlimit rl = { 9, TRUE };
if (set_one_rlimit(rl, RLIMIT_RTPRIO, RLIMIT_RTPRIO) = 0) {
pa_log_info(Successfully increased RLIMIT_RTPRIO, giving up
CAP_NICE.);
drop = TRUE;
} else
pa_log_warn(RLIMIT_RTPRIO failed: %s, pa_cstrerror(errno));
}
#endif
if (drop) {
pa_drop_caps();
pa_drop_root();
suid_root = real_root = FALSE;
}
}
--
David Kågedal
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Lennart Poettering [EMAIL PROTECTED] writes: I know that Gentoo sets up PA this way. This is against my recommendation. The only use case for running PA as system-wide instance is thin clients, where the users using PA are not local. If that's the only focus of Gentoo than great. But the last time I looked this wasn't quite the only focus of Gentoo. ;-) My use case is that I connected the good speakers to my closet server that has no console login. I then want to be able to redirect my laptop streams to the speakers, either using multicast or a tunnel. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
