summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* alsa: fix minor sampling rate deviations before adjusting the buffer sizeLennart Poettering2009-11-231-7/+9
|
* alsa: fix log output when the audio device refuses to give us again the same ↵Lennart Poettering2009-11-232-2/+2
| | | | period settings we had before
* pulse: ask for timing updates both *before* and *after* triggering a stream ↵Lennart Poettering2009-11-231-2/+36
| | | | state change so that in the STARTED/UNDERFLOW callbacks we accurate transport latency information
* pulse: delay smoother update only when unpausing, not when pausing, since we ↵Lennart Poettering2009-11-231-17/+19
| | | | don't want the timer to advance when we are supposedly already paused
* pulse: try to fix inaccuracy with uncork timing for streams that are created ↵Lennart Poettering2009-11-231-1/+16
| | | | in corked state
* daemon: complain if user passes too many argumentsLennart Poettering2009-11-231-0/+37
|
* Merge branch '0.9.20-stable' into stable-queueColin Guthrie2009-11-202-50/+61
|\ | | | | | | | | Conflicts: src/Makefile.am
| * rygel: fix itemCount property for sources0.9.20-stableLennart Poettering2009-11-181-11/+34
| | | | | | | | Fixes http://pulseaudio.org/ticket/721
| * build-sys: Fix missing trailing slash in 14eaf2Colin Guthrie2009-11-161-1/+1
| |
| * build-sys: Make sure all alsa path config files are installedSjoerd Simons2009-11-161-37/+25
| | | | | | | | | | While all alsa path configuration files were in EXTRA_DIST not all of them were in in alsapaths_DATA. Fixed by only defining the list in one place
* | device-manager: Update docs version -> 0.9.20Colin Guthrie2009-11-111-12/+12
| | | | | | | | Third time is a charm... maybe.
* | device-manager: Update docs version -> 0.9.20Colin Guthrie2009-11-111-12/+12
| |
* | device-manager: Fix compiler warning.Colin Guthrie2009-11-111-4/+4
| | | | | | | | Do not use a variable called 'index' as it clashes with string.h
* | device-manager: Rather than flagging the device as available, just include ↵Colin Guthrie2009-11-113-9/+6
| | | | | | | | the sink/source index with PA_INVALID_INDEX meaning unavailable
* | device-manager: Play nice with module-stream-restore.Colin Guthrie2009-11-111-37/+47
| | | | | | | | | | | | If m-s-r sets the device we let it do so. Otherwise we handle the routing. We run before module-intended-roles as the priority list will likely be configured appropriately to do the same job, albeit with manual setup.
* | device-manager: Make use of PA_IDXSET_FOREACH when applying entries.Colin Guthrie2009-11-111-12/+12
| |
* | device-manager: Keep track as to whether or not the user specifically ↵Colin Guthrie2009-11-111-9/+40
| | | | | | | | | | | | | | | | | | | | | | renamed the device. If the user has not (via our protocol extension) renamed a device, but it happens to now have a different name (e.g. module-combine automatically updating the description for us or udev-db getting better etc.) then make sure we update our cache with this updated version. If the user has set a name, enforce it's use, even if the description is updated by some other means (e.g. the user manually editing the proplist or another module doing it for them).
* | device-manager: No need to check the version after calling read_entry()Colin Guthrie2009-11-111-4/+4
| |
* | device-manager: Fix typo in module loading script.Colin Guthrie2009-11-111-1/+1
| |
* | device-manager: Add some scripts that are only run under KDE to ↵Colin Guthrie2009-11-113-3/+52
| | | | | | | | load/initialise module-device-manager with routing turned on.
* | device-manager: Misc fixes to co-exist with other stream management/routing ↵Colin Guthrie2009-11-111-40/+30
| | | | | | | | | | | | | | modules. * Do not read or set the save_sink/save_source flags. This seems to be for module-stream-restore only... * Even if a sink is already set by an earlier module, still move it to the sink we dictate.
* | device-manager: Misc fixes.Colin Guthrie2009-11-111-37/+47
| | | | | | | | | | | | | | | | | | | | * Fix a s/sink/source/ copy paste issue when dumping the database. * Only show priority list when routing is enabled (as the list is not updated if not) * Fix a memory access issue when finding the highest priority sinks/sources * key name->device name efficiency fix. * Silence noisy debug on reorder - it seems to work :) * Reroute after reordering. * Initialise preferred lists to PA_INVALID_INDEX
* | device-manager: Fix the writing of the database when priority doesn't change.Colin Guthrie2009-11-111-1/+3
| |
* | device-manager: Add extra debug messagesColin Guthrie2009-11-111-1/+19
| |
* | device-manager: Change the prefer/defer options to a single 'reorder' command.Colin Guthrie2009-11-114-136/+154
| | | | | | | | | | | | We put in the devices from the wire into a hashmap and then add all like type device in the database and then order them based on priority (with the ones specified on the wire always being in that order at the top of the list.
* | device-manager: Don't notify clients on every subscription (it happens all ↵Colin Guthrie2009-11-111-6/+18
| | | | | | | | | | | | the time). Also compare the entries fully before saving.
* | device-manager: Save icon and report current availability over protocol.Colin Guthrie2009-11-111-17/+53
| | | | | | | | | | This also ensures we let clients know whenver a sink changes in some capacity. Also correct some debug code.
* | device-manager: Expose the priority lists in the protocol extension.Colin Guthrie2009-11-113-38/+86
| | | | | | | | Also leave space for 'icon' and 'available' details too, althought currently this info is dummy.
* | device-manager: Add a function to dump the database which we do whenever we ↵Colin Guthrie2009-11-111-15/+107
| | | | | | | | save it (and on startup)
* | device-manager: Reroute streams when they change allowing the media.role to ↵Colin Guthrie2009-11-111-212/+243
| | | | | | | | | | | | | | be updated mid-stream. We do not handle the _EVENT_NEW subscription here as the PA_CORE_HOOK_SINK_INPUT_NEW/PA_CORE_HOOK_SOURCE_OUTPUT_NEW hook should handle the initial routing.
* | device-manager: Refactor the routing method to allow the routing of a single ↵Colin Guthrie2009-11-111-65/+80
| | | | | | | | stream
* | device-manager: More sensible names for internal functionsColin Guthrie2009-11-111-10/+8
| |
* | device-manager: Reroute the streams on startup and update our cache on enable.Colin Guthrie2009-11-111-10/+8
| |
* | device-manager: Keep a cache of the highest priority devices for each role.Colin Guthrie2009-11-111-47/+52
| | | | | | | | Rather than querying our database on every new stream, we keep a cache and only update it when a sink/source is added/removed.
* | device-manager: Fix the database write modeColin Guthrie2009-11-111-3/+3
| |
* | device-manager: Update exportsColin Guthrie2009-11-111-1/+4
| |
* | device-manager: Some efficiency and safety tweaksColin Guthrie2009-11-111-4/+9
| |
* | device-manager: Allow the routing component to be turned on via a module ↵Colin Guthrie2009-11-111-12/+14
| | | | | | | | argument as well as via protocol extn.
* | device-manager: Remove unused variablesColin Guthrie2009-11-111-3/+0
| |
* | device-manager: Set the most appropriate sink/source when new streams are ↵Colin Guthrie2009-11-111-16/+50
| | | | | | | | created
* | device-manager: Add routing functions that are triggered when sinks/soruces ↵Colin Guthrie2009-11-111-61/+136
| | | | | | | | are added/removed.
* | device-manager: Add a function to get a list of the highest priority device ↵Colin Guthrie2009-11-111-0/+81
| | | | | | | | indexes for each role.
* | device-manager: Remove unneeded logic for checking for and (un)loading ↵Colin Guthrie2009-11-111-35/+0
| | | | | | | | module-stream-restore. We can co-exist
* | device-manager: Rough framework (slots etc.) for handling routing.Colin Guthrie2009-11-111-5/+201
| | | | | | | | | | | | | | | | This is incomplete, it just adds the slots in question and assigns noops to them. Some minor cleanup of types. Due to the priority of the hooks, it seems we can actually coexist with module-stream restore so the code to detect and unload it will be removed shortly.
* | device-manager: debug and commentsColin Guthrie2009-11-111-1/+2
| |
* | device-manager: Fix the freeing of the datum on prefer/defer.Colin Guthrie2009-11-111-5/+4
| | | | | | | | Also fix a log typo
* | device-manager: When a new device is encountered, initialise the priority ↵Colin Guthrie2009-11-111-4/+56
| | | | | | | | list to an appropriate value
* | device-manager: Let subscribed clients know when something changes.Colin Guthrie2009-11-111-0/+16
| |
* | device-manager: Change the write function to a rename function.Colin Guthrie2009-11-113-75/+44
| | | | | | | | | | | | | | 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.
* | device-manager: Provide a method for prefering/defering a device.Colin Guthrie2009-11-113-0/+238
| | | | | | | | | | | | | | | | | | | | 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.