Mixer control display makes no sense

Description

With 4a we have virtual controls what make the list long but also gives us the opportunity to get some unification for user and App rather that to stupidly map the name reported by the platform.

Currently we have the worse of both world:

 - the list is too long
 - the name are meaningless (list of output ##)

Please get a look at the attached screen photo.

Environment

None

Attachments

3

relates to

Activity

Walt Miner 
July 2, 2018 at 12:02 AM

Close for FF RC1

Loïc Collignon [ IoT.bzh ] 
March 27, 2018 at 1:03 PM

Mixer now use app-template and allow you to specify which HAL you want using the cmake's command line.

Loïc Collignon [ IoT.bzh ] 
March 13, 2018 at 1:31 PM

I made a hack that use alsacore and hals, in which I expose only 2 sliders (master and microphone).

More should come later, but at least it's simple.

It's available on a sandbox for testing: https://gerrit.automotivelinux.org/gerrit/gitweb?p=apps/mixer.git;a=commit;h=373f6cc2117d296abd8bc8bbd0e3b1392b834506

This should work on M3 board only. To make it work on other hardware, you have to edit the config.xml to import your HALs.

If you import an HAL which is not available on your board, mixer app won't start.

This should be fixed in the future to make it more portable with no manual edit.

Dominig ar Foll 
January 4, 2018 at 10:46 AM

It's far better but I still do not understand why we need to have Ouput #0 till #5 in front of the name of the control.

See photo attached.

Matt Ranostay 
January 3, 2018 at 7:16 PM

Still an issue? Or can you close?

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Affects versions

Priority

Created December 15, 2017 at 5:52 AM
Updated July 2, 2018 at 12:02 AM
Resolved June 28, 2018 at 2:01 PM