osmocom-bb.git branch fixeria/audio created. osmocon_v0.0.0-1895-g0ed60f68

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.

gitosis at osmocom.org gitosis at osmocom.org
Wed Dec 13 00:15:54 UTC 2017


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The Open Source GSM Base Band stack".

The branch, fixeria/audio has been created
        at  0ed60f68b86b47417e2ec587320e27c84737695b (commit)

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmocom-bb/commit/?id=0ed60f68b86b47417e2ec587320e27c84737695b

commit 0ed60f68b86b47417e2ec587320e27c84737695b
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Tue Dec 12 19:14:13 2017 +0700

    mobile: integrate GAPK based audio I/O back-end
    
    This change introduces a new feature of mobile application - audio
    I/O support, which allows to speak right from PC running mobile
    through its ordinary mic and speakers.
    
    The audio I/O is based on GAPK library, which relays on ALSA sound
    framework. The API of GAPK implies to use the processing queues
    (chains), which basically consist of a source block, several
    processing blocks, and a sink block. So, there are two voice
    processing chains:
    
      - 'pq_audio_source' (voice capture -> frame encoding),
      - 'pq_audio_sink' (frame decoding -> voice playback).
    
    Both of them exchange frames from two dedicated buffers:
    
      - 'tch_fb_ul' - a buffer for to be played DL TCH frames,
      - 'tch_fb_dl' - a buffer for encoded UL TCH frames.
    
    In its turn, both buffers are served by a new gapk_io_dequeue()
    function, which is being called within the mobile_work() loop.
    
    Current limitations:
    
      - Both processing chains are being initialized on MS init
        mobile_init() and being destroyed on mobile_exit(). Thus,
        some part of memory is occupied during all MS work cycle,
        even when there is no an active call. Would be better to
        keep both chains in memory during a voice call only.
    
      - TCF/FR codec support only. Despite the both chains are
        codec independent, they are being initialized with FR.
        Should be resolved together with the first issue.
    
      - Missing ECU (Error Concealment Unit). If the BTS signal is
        weak and some TCH frames were lost, the voice playback may
        contain some unpleasant audio drops. This will be resolved
        as soon as ECU is implemented as a part of libosmocodec.
    
    Change-Id: Ib86b0746606c191573cc773f01172afbb52f33a9

http://cgit.osmocom.org/osmocom-bb/commit/?id=be594d8afbf031ff03b73bee07d61ce1b5cc9bb8

commit be594d8afbf031ff03b73bee07d61ce1b5cc9bb8
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Tue Dec 12 19:08:17 2017 +0700

    mobile/gsm48_rr.c: set audio mode according to configuration
    
    In the prevoius change a new configuration option was introduced
    as a part of new 'audio' node - 'io-target'. This change makes it
    to take an effect, instructing the L1 to use one of the following
    possible TCH frame I/O targets:
    
      - gapk - build-in (WIP) GAPK-based audio back-end (default);
      - hardware - L1 hardware (e.g. Calypso DSP);
      - socket - External MNCC application (e.g. LCR).
    
    Change-Id: I2a36d9c30da6746995dcea3a33cb13e0d2f6549a

http://cgit.osmocom.org/osmocom-bb/commit/?id=b929c39eea0aba5e223deb1260d32c1b6df59ecc

commit b929c39eea0aba5e223deb1260d32c1b6df59ecc
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Tue Dec 12 03:49:43 2017 +0700

    mobile/vty_interface.c: add new 'audio' section
    
    This change introduces a new node named 'AUDIO', which is intended
    to organize some audio related settings, such as:
    
      - io-target - TCH frame I/O back-end (e.g. gapk, hardware);
      - alsa-output-dev - ALSA playback (i.e. speakers) device name;
      - alsa-input-dev - ALSA recording (i.e. mic) device name.
    
    The last two are actual when 'io-target' is set to 'gapk'.
    For now, all introduced parameters don't affect anything.
    
    Change-Id: I62cd5ef22ca2290fcafe65c78537ddbcb39fb8c6

http://cgit.osmocom.org/osmocom-bb/commit/?id=ef167cdb6368bb721aacc4af1b9c7081678a6702

commit ef167cdb6368bb721aacc4af1b9c7081678a6702
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Sep 8 15:54:39 2017 +0300

    host/layer23: add a new logging category for GAPK
    
    Change-Id: I5c3e8553f9bca2ca2e1bf17ee5934e04bd12f605

http://cgit.osmocom.org/osmocom-bb/commit/?id=ab6eebadccb6400c30e4a10efb37aeca7d8436f9

commit ab6eebadccb6400c30e4a10efb37aeca7d8436f9
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Sep 8 00:45:29 2017 +0300

    mobile: link the binary against libosmogapk
    
    Since GAPK became a library - libosmogapk, one could be used for
    the audio capture / playback directly on the host side. This
    change adds the library as a dependency, and links the mobile
    against it.
    
    Change-Id: I47054f32fec6780bdbe6f73b82aa446c4c7c1df4

http://cgit.osmocom.org/osmocom-bb/commit/?id=6a3321363296d4671c8053668966c4ffa46bd608

commit 6a3321363296d4671c8053668966c4ffa46bd608
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Sep 8 00:40:27 2017 +0300

    mobile/Makefile.am: consistently format variables
    
    Change-Id: I309d94c4a381c21486e5b424c9504ea6d272af05

http://cgit.osmocom.org/osmocom-bb/commit/?id=bed3ac314145d4685fa1cc508121db05e350e731

commit bed3ac314145d4685fa1cc508121db05e350e731
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Mon Dec 11 04:26:12 2017 +0700

    mobile: add MNCC handler selection to settings
    
    Since the mobile application is patentionally able to work with
    multiple MS instances, it's better to have a possibility to
    choose an MNCC (Call Control) handler per each MS separately.
    
    This change cleans up the code, removing a dedicated command-line
    option '-m' intended for enabling extarnal MNCC. Now it's possible
    to set an MNCC-handler for each MS via VTY interface and settings.
    
    The following MNCC-handlers are available:
    
      - mobile - build-in MNCC-handler (default);
      - socket - external MNCC-handler via UNIX-socket (e.g. LCR);
      - dummy - dummy handler without CC support.
    
    Change-Id: I2df91c7a79ba5c39bc6ceae900ef649129dd0346

http://cgit.osmocom.org/osmocom-bb/commit/?id=4f5746ada980e3beb7deaee9d0ae0bbf7db45aa5

commit 4f5746ada980e3beb7deaee9d0ae0bbf7db45aa5
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Sep 8 18:51:53 2017 +0300

    mobile: add MNCC socket path to settings
    
    Previously the MNCC socket path was generated automatically,
    using concatenation of the '/tmp/ms_mncc_' prefix and MS name.
    Let's allow user to specify this manually, keeping a similar
    generation method for default value.
    
    Change-Id: I643356ac579bc5e765f668265ec803b22a73739c

-----------------------------------------------------------------------


hooks/post-receive
-- 
The Open Source GSM Base Band stack



More information about the osmocom-commitlog mailing list