Opened 12 years ago

Closed 11 years ago

#4428 closed defect (wontfix)

Mixer device does not accept spaces

Reported by: Paul Lambert <paul at planar.id.au> Owned by: danielk
Priority: trivial Milestone: unknown
Component: mythtv Version: head
Severity: low Keywords:
Cc: Ticket locked: no

Description

The setting in the settings table labelled "MixerControl?" does not accept spaces from the frontend. My machine, by default, doesn't appear to have either a PCM mixer or a Master volume control. All the useful controls in the alsa mixer (amixer) have spaces in their name.

When I update the database directly using the command: "update settings set data = "Analog Front" where value = 'MixerControl?' and host = 'myth';" then I can control the volume via mythfrontend.

I took a look through the code to see if I could make a change. The setting is configured in the file programs/mythfrontend/globalsettings.cpp. However, it is using a control entitled "HostComboBox?", which from the look of things by default doesn't accept spaces. A lot of different things also use HostComboBox?, so probably modifying it to accept spaces would be a bad idea. It wasn't clear whether there is already a solution to this for other areas that use HostComboBox?, or whether this is a new need that hasn't previously arisen.

Any ideas?

Change History (4)

comment:1 Changed 12 years ago by danielk

I think this is a new need. I've been meaning to write a better control for audio setup for years now. But we really should be able to detect the ALSA sound system control names and fill that combobox..

comment:2 Changed 12 years ago by paulh

If you are using trunk you can now use the popup keyboard which *does* allow you to enter spaces.

comment:3 Changed 12 years ago by danielk

Component: mythcontrolsmythtv
Owner: changed from Isaac Richards to danielk
Priority: minortrivial
Severity: mediumlow
Status: newassigned
Version: unknownhead

comment:4 Changed 11 years ago by danielk

Resolution: wontfix
Status: assignedclosed

work around exists & the code will be going away in the MythUI port... marking as wontfix

Note: See TracTickets for help on using tickets.