| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The structure itself will contain various bits of info so exposing this fully to the client is a bad idea.
By keeping to a rename operation we keep what we do store abstracted from the clients.
Also fix some doxy comments.
|
|
|
|
|
|
|
|
|
|
| |
This allows clients to edit the priroity order. What is not yet in place is the initialisation of that priority list
when new devices are detected or the cleaning (remove holes) when devices are removed.
In order to keep the storage transparent I will likely remove the write functionality and replace it with a
simple rename method.
I also still need to expose the priority itself when reading the data.
|
|
|
|
| |
necessary
|
|
|
|
|
|
|
| |
device-priority routing.
The routing logic itself does not yet exist, but the command currently will unload/load module-stream-restore as approriate.
(module-stream-restore would conflict with the role-based priority-routing).
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
of devices.
This fixes a few bugs in the copy+pasted implementation of apply_entry()/get_name().
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is effectively copied from the stream restore extension.
|
|
|
|
|
|
|
|
|
|
| |
of various sinks.
This will be used as the basis for a queryable system for past and present devices, initially for use in KDE.
Currently all this module does is save lists of sinks/sources and their descriptions, so it needs to
gain a protocol extension to make this queryable.
As things stand it will save the device descriptions of all sinks and restore them if they differ from whats on record.
|
| |
|
| |
|
|
|
|
|
|
| |
Fixes an assert that is hit in somne niche cases:
https://bugzilla.redhat.com/show_bug.cgi?id=533482
|
|
|
|
| |
Use the correct sample rate for reporting about the timing.
|
|
|
|
|
|
| |
Original patch supplied by 'adi'
http://pulseaudio.org/ticket/669
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In virtual machines sound card clocks and OS scheduling tend to become
unreliable, adding various 'uneven' latencies. The adaptive algorithm
that handles drop-outs does not handle it this well: in contrast to
drop-outs on real machines that are evenly distributed, small and can
easily be encountered via the adpative algorithms, drop-outs in VMs tend
to happen abruptly, and massively, which is not easy to counter.
This patch simply disables timer based scheduling in VMs reverting to
classic IO based scheduling. This should help make PA perform better in
VMs.
https://bugzilla.redhat.com/show_bug.cgi?id=532775
|
| |
|
| |
|
| |
|
|
|
|
| |
http://pulseaudio.org/ticket/702
|
|
|
|
|
|
|
| |
On some cards line-out is independant of Sepaker and it is a good idea
to cover that so that they can independantly be activated.
https://bugzilla.redhat.com/show_bug.cgi?id=520884
|
| |
|
| |
|
|
|
|
|
|
| |
As seen on some HDA chips:
https://bugzilla.redhat.com/attachment.cgi?id=359804
|
|
|
|
|
|
| |
As seen on some drivers:
https://bugzilla.redhat.com/show_bug.cgi?id=498612
|
|
|
|
|
|
| |
As used by some HDA devices:
https://bugzilla.redhat.com/attachment.cgi?id=365290
|
|
|
|
|
|
| |
As used by some HDA chips:
https://bugzilla.redhat.com/attachment.cgi?id=366816
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lennart,
Apparently I was debugging this at the same time as you. I can't figure out
why my Fedora 11 install with glibc-2.10 has a glibc realpath that doesn't
match the gnu documentation and returns null. But it does.
Your commit aa8ce5bb9b159abb2ffb0f43996340566fc2e9c6 almost fixed my
problem, but it needs a tweak.
Thanks,
David Yoder
|
| |
|
| |
|
|
|
|
| |
user input
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This was reported as Gentoo bug #287391 by Torsten Kaiser, and the fix was
suggested by Mike Frysinger.
|
| |
|
| |
|
|
|
|
|
| |
I checked the source code, and latency_msec is missing from the list
of valid module arguments. Attaching a patch to add it.
|
| |
|
|
|
|
|
| |
We need to sign extend the lower part of the multiplication before adding it to
the higher part. Makes -1 * 0xffff work again.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are multiple package management systems out there which implement
packages using symlinks. The recent (otherwise useful) check to ensure that
a re-executed pulseaudio is actually reexecuting itself unfortunately breaks
in the presence of all these packaging systems, because PA_BINARY refers
to its installed location (e.g. /usr/local/bin/pulseaudio), which is a
symlink to the binary (e.g. /usr/local/stow/pulseaudio-0.9.18/bin/pulseaudio),
because /proc/self/exe always contains the canonical path of the executable,
with all symlinks resolved.
(At least one distribution uses a symlink-based packaging system, so
will be forced to apply this locally in any case.)
The fix is simple: canonicalize PA_BINARY before equality-testing. (This
should be completely safe, because the OS does just that when PA_BINARY
is executed.)
The patch is against 0.9.18, but applies without fuzz to current master.
|
|
|
|
| |
sessions does not create spew in syslog
|
|
|
|
|
|
| |
Tweak the constraints a little so that register starved 32bit systems
can select a stack variable for the channel paramter instead of reusing one of
the registers we're using in the code.
|
|
|
|
| |
This avoids the need for ugly casting in client implementations.
|