Age | Commit message (Collapse) | Author | Files | Lines |
|
Most of the stuff in bootstrap.sh seemed to reimplement autoreconf,
badly. I don't understand the wisdom behind the run_versioned
trickery. configure.ac states that we require Automake 1.11, so
apparently the VERSION variable in bootstrap.sh was out of date.
Instead of bumping the version number, I replaced the cruft with
an autoreconf call.
|
|
|
|
|
|
The changelog generation script is not maintained, not installed on most
devs' systems, and the from-git changelog is mostly not useful.
|
|
|
|
There's no reason to present this for all S/PDIF and HDMI cases. The
user can select it when required.
|
|
We don't want to flood users with this option, let's just leave it
closed by default for those who need it.
|
|
|
|
If we know if a certain port is available/unavailable, we can print
that out, as a help to the user (and as debugging for ourselves).
A profile is also available/unavailable if all ports which have that
profile are available/unavailable.
Credit goes to David Henningson for the original idea and some of the code.
|
|
The prepareMenu() call can change the active profile selection, which
in turn will cause a "set card profile" command to be sent to the
server if the "updating" flag is not set, so the "updating" flag needs
to be set when calling prepareMenu() from updateCard().
This caused a problem with disconnecting bluetooth headsets: as part
of the disconnection procedure, module-bluetooth-device sets the card
profile to "off". At that point module-card-restore doesn't do
anything, because the change is marked as "don't save". But the
profile change event is then sent to pavucontrol, which updates its
view, and pavucontrol sends the new profile ("off") back to
pulseaudio, and this time the profile change iss marked as "please
save", so module-card-restore restores the "off" profile when the
device is connected again, even though the user never requested the
"off" profile to be chosen.
|
|
|
|
|
|
This change adds the ability to change the latency offset of a port with
pavucontrol.
|
|
This is a minor cleanup that moves the index of the sink/source and the
card_index from the sink/source widget to the device widget.
|
|
The cardwidget should cache all the relevant data for the ports.
This change introduces a new port class which holds the port info for
the card.
|
|
|
|
|
|
As a developper, I find it annoying to restart pavucontrol everytime I restart
pulseaudio, moreover the error dialog sometimes needs an additional click
before restarting.
Add it as a command line option so that default behavior is not changed.
|
|
We need to set the visible_window property to ensure
the theme background colour shines through.
https://bugzilla.gnome.org/show_bug.cgi?id=655635
|
|
|
|
3.2) and distribute .xz files.
We will drop .gz support after 1.0
Also bumped automake version to 1.11 to match PA itself
and for the dist-xz option
|
|
|
|
This makes sure we inhibit autosuspend only for network sources (which
was the main purpose of adding autosuspend, since constantly monitoring
those is network heavy).
|
|
|
|
|
|
|
|
The server now signals when a sink supports setting formats, so we don't
have to rely on the profile name.
|
|
digitial sink
|
|
|
|
This only seemed to affect GTK3 and it seems to introduce
a GTK warning relating to 'gtk_widget_size_allocate' similar
to those fixed in the previous commit, but nothing seems to
be the worse for it.
|
|
|
|
|
|
volumes.
The setting of the channel map triggers the display of the actual volume sliders
so it is essential that we do not set it when we don't want to.
|
|
|
|
|
|
Spotted by spm_Draget via IRC
|
|
* Use ctrl+w or ctrl+q or esc to quit.
* Uset ctrl+1-5 to change tabs.
|
|
As pavucontrol is often used for debugging PA, it should
be quite robust and not popup messages etc. under 'normal'
testing conditions. This adds quite a verbose message under
some specific conditions that do crop up from time to time.
|
|
Pass --disable-gtk3 to configure to build against gtk2
|
|
Refs #804
|
|
The number of volume steps doesn't really affect our scale, so there
is little value in setting it.
|
|
This allows us to set volumes up to ~153% aka +11dB.
Also show the current dB value in the UI - as pavucontrol is a bit more
developer-friendly than other volume UIs displaying this by default makes
sense.
|
|
displayed rather than real text)
|
|
|
|
|
|
|
|
mute and lock channels buttons
|
|
|
|
Refs: http://pulseaudio.org/ticket/768
|
|
|