[pulseaudio-tickets] [PulseAudio] #804: Locked sliders don't snap to grab points if dragging slider Front left
#804: Locked sliders don't snap to grab points if dragging slider Front left +--- Reporter: onox| Owner: lennart Type: defect | Status: new Milestone: | Component: pavucontrol Keywords: | +--- I have an output device and an input device which both have two sliders: Front Left and Front Right. If the channels are locked together and I start to drag the lower slower (Front Right) then both sliders snap to the grab points Silence, Base, and Max. If I start dragging the upper slider (Front Left), then the sliders don't seem to snap to the three points. If I unlock the channels, then the lower Front Right slider will snap to the grab points, but the upper Front Left not. -- Ticket URL: http://pulseaudio.org/ticket/804 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #804: Front left slider doesn't snap to grab points (was: Locked sliders don't snap to grab points if dragging slider Front left)
#804: Front left slider doesn't snap to grab points -+-- Reporter: onox| Owner: lennart Type: defect | Status: new Milestone: | Component: pavucontrol Resolution: |Keywords: -+-- -- Ticket URL: http://pulseaudio.org/ticket/804#comment:1 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #804: Front left slider doesn't snap to grab points
#804: Front left slider doesn't snap to grab points -+-- Reporter: onox| Owner: lennart Type: defect | Status: new Milestone: | Component: pavucontrol Resolution: |Keywords: -+-- Comment(by onox): s/lower slower/lower slider/ -- Ticket URL: http://pulseaudio.org/ticket/804#comment:2 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #804: Front Left slider doesn't snap to grab points (was: Front left slider doesn't snap to grab points)
#804: Front Left slider doesn't snap to grab points -+-- Reporter: onox| Owner: lennart Type: defect | Status: new Milestone: | Component: pavucontrol Resolution: |Keywords: -+-- -- Ticket URL: http://pulseaudio.org/ticket/804#comment:3 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #802: Status on Arch Linux | Splitting into Library and Application
#802: Status on Arch Linux | Splitting into Library and Application -+-- Reporter: Xavion | Owner: lennart Type: enhancement | Status: closed Milestone: | Component: build-system Resolution: distrospecific |Keywords: -+-- Comment(by coling): Lennart has already said that if the patch is clean he will likely apply it. That said, as a packager myself, I find it absolutely astounding that the Arch build system requires that you build and install a given source multiple times in order to package it. Every other distro I know of splits the PA package into separate binary packages, but they only need to build it once and the definition of which files go to which binary package is left up to the packager to specify, not the upstream project. To me, this requirement by the Arch build system is in no way indicative of a relatively advanced package management system - it's totally backwards :s A source tarball should be built once, and once only when creating binary packages. If you do just built it once then run the make install-xxx multiple times with different values of xxx, then this is slightly more sensible but pushing your Arch specific policy into upstream packages seems rather narrow minded anyway. I know, for example, that the library packaging policy is different in Mandriva than it is in RedHat and I know that Ubuntu do things differently still. This kind of split should definitely be left to the packaging system IMO. That's my €0.02 -- Ticket URL: http://pulseaudio.org/ticket/802#comment:8 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #580: pulseaudio master volume is scaled differently as alsa master
#580: pulseaudio master volume is scaled differently as alsa master -+-- Reporter: yelo3 | Owner: lennart Type: defect | Status: reopened Milestone: | Component: module-alsa-* Resolution: |Keywords: -+-- Changes (by yelo3): * status: closed = reopened * resolution: elsewhere = Comment: I opened a bug to alsa, and someone answered that this might be a problem in pulseaudio. Here's a link to the bug, so you can read the comments: https://bugtrack .alsa-project.org/alsa-bug/view.php?id=4956 -- Ticket URL: http://pulseaudio.org/ticket/580#comment:7 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
