summaryrefslogtreecommitdiffstats
path: root/plugins/alsa/alsa-api-mixer.c
AgeCommit message (Collapse)AuthorFilesLines
2018-09-07fixed crash upon misconfiguration of capture/playback devicesThierry Bultel1-6/+8
The null pcmplug case was not correctly handled in various places. Also fixed some typos in the log Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-08-31Added bluez sound playback supportThierry Bultel1-8/+56
This adds sound playback for incoming sound from connected bluetooth devices. In this version, the softmixer relies on a modified bluez-alsa version (https://github.com/iotbzh/bluez-alsa), that provides an ioplug PCM bluezalsa connection proxy. The softmixer api has a new verb to dynamically set the device to listen to: afb-client-demo ws://localhost:1234/api?token=\uuid=123 smixer bluezalsa_dev '{"interface":"hci0", "device":"F6:32:15:2A:80:70", "profile":"a2dp"}' In this way it is possible to switch from a bluezalsa audio source to another without any further configuration. For now, only interface hci0 is supported. This commit also migrates the softmixer binding to API v3 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-07-20rework the sound capture & playback modelThierry Bultel1-1/+1
Now uses two threads for in the playing loop The first one reads from the capture device (ie, a phys. capture, or snd_aloop) and writes data to a circular buffer. The second one gets data from the circular buffer and outputs it to the playback. This model solves a lot of correlated timing bugs between read & write tasks. The read tasks only wakes up the write task when the buffer is 80% full. The buffer size big enough to hold 2 seconds of sound. The mute implementation has also been simplified, since it has been found out that it was possible to recover from an interrupted read, by calling snd_pcm_start additionnally to snd_pcm_prepare. Thus, the mute code consists in listening to an extra file descriptor in the read loop. Reading from that descriptor gives the mute or unmute command sent at higher level (in the PCM control event callback). When a 'mute' order is get, the capture sound fd is simply backup and replaced by '-1' in the set of the poll of the read task. When a 'unmute' order is get, the fd is simply restored. The start threshold is only computed for capture, and hardcoded to 1 for playback. This removes most of the remaining EPIPE on playback. The stop threshold has been removed. It had bad side effects on the amount of writeable data returned by snd_pcm_avail_update (was returning too small chunks) Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-07-11stops the read/write loop when the stream is mutedThierry Bultel1-4/+5
when the stream is muted (due to the configuration, or due to a HAL request), the read/write loop is stopped. The benefit is that muting will work with capture devices that do not implement the mute in their driver. The inconvenient of stopping the read loop is that it has made appear an unexpected side-effect: the poll on capture does not trig for further incoming frames. The workaround is to completely close, then reopen and configure the capture PCM. Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-07-03Uses the APIv3 compatibility to vdynThierry Bultel1-12/+0
Uses the new compatibility for vdyn based on V3 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-06-22plugins: code & log cleanupThierry Bultel1-3/+3
2018-06-22alsa-api-mixer: code & log cleanupThierry Bultel1-14/+42
Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-06-11Correct issues when calling info verbJonathan Aillet1-7/+4
Correct issues when calling info verb : - Two 'AFB_ReqFail' was called when an error was detected on info call reqsuest json (generating an application framework error). - The error messages wasn't up to date. Change-Id: Ifbb94854bc8a9d13ddf702defa94eaa6cf87e9ba Signed-off-by: Jonathan Aillet <jonathan.aillet@iot.bzh>
2018-06-10Authorize new section at mixer initializationJonathan Aillet1-1/+2
Authorize the new section 'mixerapi' to be present into the json sent to initialize mixer. Change-Id: I7feed818f19f2d93566f6e1634933462828dbdf0 Signed-off-by: Jonathan Aillet <jonathan.aillet@iot.bzh>
2018-06-10Documentation/cleanupfulup1-1/+2
2018-06-10Added cardid+verb return for capture+playback sndcardfulup1-71/+263
2018-06-10Added stream/ramp return to fit HAL attach requestfulup1-88/+155
2018-06-10Cleanup and added return of previous volume when setting new valuefulup1-61/+201
2018-06-06Move smixer API create+attach into controller onload sectionfulup1-71/+9
2018-06-06Fixed the MixerInfoAction replyThierry Bultel1-7/+4
Make it robust to empty source, and set the source when input is a direct capture device. Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-06-05Fix alsa URI within attach responsefulup1-2/+3
2018-06-05Use attach info verb to build attach response.fulup1-6/+8
2018-06-05Update info command and move HTML5 to new APIfulup1-25/+101
2018-06-04Fixed compilation issues with gcc >= 7.2Thierry Bultel1-1/+1
Fixed some warnings about uninitialized variables
2018-06-04Move to Dynamic Mixer API (work in progress)Fulup Ar Foll1-145/+214
2018-05-18Added create/close mixer APIFulup Ar Foll1-27/+96
2018-05-18Implements volume rampingFulup Ar Foll1-4/+4
2018-05-17Implemented sub API for stream with volume/pause/toggle/...Fulup Ar Foll1-4/+56
2018-05-17Initial version with dynamic APIsFulup Ar Foll1-0/+150