similar to: opus on TI55x

Hi all, I'm trying to build the celt package on the Texas TMS320VC5510 DSK. I think there are some #define for it in the code, but I'm doing something wrong. Is there any documentation about it? So far I'm building with the TI_C5X_ASM;CONFIG_TI_C55X #define. Any help? Thank you. Giovanni

Hello Giovanni, I am running both Opus Encoder and Decoder on a TI Cortex M4 core without any issues. What is the specific issue that you are facing? Can you explain? Regards Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20160105/0bc0bc2c/attachment.htm

Hi Amit, issues I'm facing now are int overflow and memory management. I'm working on it. I'm working on the tms320c5515 evm board. Best regards, Giovanni. On 5 January 2016 at 18:40, Amit Ashara <ashara.amit at gmail.com> wrote: > Hello Giovanni, > > I am running both Opus Encoder and Decoder on a TI Cortex M4 core without > any issues. What is the specific issue

Thanks Jean-Marc, I was able to get both encode and decode working the CC3220 device! But for bi-directional communication, I need decode and encode to occur in less time than the frame size I’m sending (20 ms). Currently decode takes 16~22 ms and encode is ~13 ms. What is the best way to try to reduce this time? Also, unsure why encode is taking less time than decode... I've also

Hello, for your consideration. The following patch moves the channel_pos() function from within the #if !defined(DISABLE_FLOAT_API). This change is required when compiling with FIXED_POINT and DISABLE_FLOAT_API defined. #### ### diff --git a/src/opus_multistream_encoder.c b/src/opus_multistream_encoder.c index 3efab53..6f3eb53 100644 --- a/src/opus_multistream_encoder.c +++

Gents, I am getting the following compile error on V11.1 "declaration may not appear after executable statement in block". This occurs in two places in celt.c. ============================================================================ ==================== #ifdef FIXED_POINT #ifndef DISABLE_FLOAT_API CELT_STATIC int celt_encode_with_ec_float(CELTEncoder * restrict st, const

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

Hi ! Can anybody point me how to compile speex for subj ? May be I'm doing something stupid.. I just took all files from /libspeex and added them to my project in Code Composer 2.1. Then I set global definitions CONFIG_TI_C55X, FIXED_POINT, DISABLE_WIDEBAND, RELEASE for entire project and edit arch.h and create speex_config_types.h. Then tried to compile it and run. Code seems to be hang in

Jean-Marc, Thanks for the response and the helpful info. I am trying to get the library to build without using the pseudostack define, and use either VAR_ARRAYS or ALLOC, but it seems the global stack is not defined. Where do can I define this in my example? VR -----Original Message----- From: Jean-Marc Valin [mailto:jmvalin at jmvalin.ca] Sent: Tuesday, February 20, 2018 5:40 PM To:

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi, I am working on trying to compile opus to be as small as possible. I have passed the FIXED_POINT and the DISABLE_FLOAT_API but I am looking into making this lib even smaller in size. Where can I find out about how to best strip this lib to only compile in what I need?

From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one

The security.evm extended attribute is fully owned by the Linux kernel and cannot be directly written from userspace. Therefore, we can always skip it. --- xattrs.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/xattrs.c b/xattrs.c index b105392..3b72e61 100644 --- a/xattrs.c +++ b/xattrs.c @@ -255,6 +255,9 @@ static int rsync_xal_get(const char *fname,

From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one

Marc Lindahl wrote: > Of course, I'm setting up a bunch of tests to evaluate these, what I was asking was more along the lines of, > If you set up the same exact, including the sample rate, do you get the same results (e.g. same code path, calculations, etc.?) If you configure a custom mode with the standard parameters (48 kHz sampling rate and a frame size of 120, 240, 480, or 960),

On 02/23/2018 10:47 AM, Rodriguez, Vince wrote: > Currently decode takes 16~22 ms and encode is ~13 ms. What is the best > way to try to reduce this time? Also, unsure why encode is taking less > time than decode... Tried running a profiler? > I've also noticed if I change my encoder to silk only, I get a Heap > overflow... I have dynamically allocated a heap for the codec,

Hi, I've attached a patch to fix use_dtx when building with DISABLE_FLOAT_API. Thanks, Felicia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20160720/4bcbab8d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-use_dtx-for-DISABLE_FLOAT_API.patch

Dear Opus family, we have implemented the Opus codec at a Texas Instruments DSP C6418. It is working fine! Does anyone has experience with the configuration of the codec for a speed optimized implementation on that DSP? At the moment, we use the following settings: #define NONTHREADSAFE_PSEUDOSTACK 1 #define FIXED_POINT

Hi Vince, Normally, Opus should work fine on the CC3220, though real-time encoding may be a bit tight depending on what configuration you choose. You'll probably want to configure with --enable-fixed-point and --disable-float-api (or define FIXED_POINT and DISABLE_FLOAT_API if you don't use autoconf). The encoder has a bunch of run-time settings that you may want to set, depending on