similar to: libopus build environment assistance request

Hello all! I'm having trouble with a cross compiled libopus for an embedded application and would like some help. preamble: embedded details: processor: bf537 kernel: Linux release 3.0.8-ADI-2011R1-svn4693, build #2834 Fri Apr 22 12:35:34 ADT 2016 toolchain: bfin-linux-uclibc-gcc release gcc version 4.3.5 (ADI-2011R1-RC4) audio interface: ALSA

Jean-Marc, I'm an embedded systems designer and am in the process of selecting a hardware platform to run a Linux-Speex VoIP application. Being concerned with size and power consumption I must choose a processor with a minimal amount of computational power. To that end I've narrowed my search to number of different products that reference the popular "SiSoft Sandra(TM)"

Hello everyone, For a private project I would like to make a new Internet Intercom device (for my kids and me). At the moment I use a separate DSP with Ogg/Vorbis (VS1053) but I like a challenge ;-) Is a eg. ST32F10x (cortex m3) or a new ST32F40x (cortex m4) powerful enough to do encoding and decoding ? Any existing projects to learn from? Thanks for your time, Edwin van den Oetelaar

Hi, I'm working on porting libopus to some specific platforms. Due to some restrictions of the platform and to improve the performance I had to change a bit the accuracy of some functions (fft, mdct and so on). With a help of tools provided with the source code, I can check that my changes in the code are not the cause of serious damages during decoding, and all decoding tests are passed.

The libopus encoder's opus_encode() method is documented as "Encodes an Opus frame". Does that mean that it always produces a single Opus frame (i.e. the number of frames in the TOC byte will always be 0)? It's not clear from the documentation, but the fact that it cannot produce a 120ms Opus packet makes me wonder if that was the intention and any multi-frame Opus packets must

Hi, I'm looking for the description of possible combinations of libopus parameters. For instance in case of low bitrate encoding (voip application, SILK part) it does not have sense to set 2 channels. Audio applications (CELT part) widely use 2 channels. What about HYBRID mode? Is it closer to voip or audio applications? What is the typical number of channels? Can constant bitrate be used in

I just recently found that opus_multistream_encode_float is returning -1 (OPUS_BAD_ARG) with the libopus 1.1 build but works just fine with the libopus 1.0.1 and libopus 1.1-beta builds. I tried using opus_multistream_encoder_create and opus_multistream_surround_encoder_create. Tried with coupled and uncoupled quadraphonic and uncoupled stereo encodes. I'm dynamically loading the libopus

On 2014-06-02 11:51 PM, Alpha Thinktink wrote: > Have there been changes to the meaning or handling of the parameters > for either of the mentioned functions? Hmm. There shouldn't have been between 1.1-beta and release. I guess you can't tell us which argument is bad because the win32 binary is stipped. Have you tried compiling it yourself? -r

On 2014-06-04 12:47 PM, Alpha Thinktink wrote: > 1>------ Build started: Project: opus, Configuration: Release Win32 ------ > 1> fatal: Not a git repository: 'C:\My Documents\Opus\win32\..\.git' > 1> The syntax of the command is incorrect. > 1> The system cannot find the path specified. > 1>C:\Program

On 2014-06-04 1:25 PM, Alpha Thinktink wrote: > Ok, this seems contradictory to the output that the build log is > telling me. The log is showing a fatal error and the build doesn't > succeed. You're right. Doesn't work on the libopus-1.1 source tarball. Sorry about that! -r

Finally got it to compile and attach the MSVC debugger. It fails at the following: if ((!st->variable_duration && 400*frame_size != st->Fs && 200*frame_size != st->Fs && 100*frame_size != st->Fs && 50*frame_size != st->Fs && 25*frame_size != st->Fs && 50*frame_size != 3*st->Fs) || (400*frame_size <

Alpha Thinktink wrote: > max_data_bytes=-11 That value is passed in by you. I also don't think passing such a value would have worked in earlier releases. It indicates the size of the buffer you are passing to the encoder to receive the encoded output.

On Wed, Jun 4, 2014 at 4:41 PM, Alpha Thinktink <alphathinktink at gmail.com> wrote: > > >> max_data_bytes=-11 > This can happen with multistream cbr if the bitrate is set too low, to a value that would allow less than 4 bytes per stream, per packet. What bitrate are you using? Perhaps you set it to a value in kb/s instead of b/s. -------------- next part -------------- An

In debugging I saw: opus_multistream_encoder.c line 760 if(!vbr) max_data_bytes = IMIN(max_data_bytes, 3*st->bitrate_bps/(3*8*Fs/frame_size)); max_data_bytes after this code becomes -2 where as before it was 10200. I suspect it was because st->bitrate_bps was set to -1000 to indicate Auto bitrate. I imagine Max bitrate (-1) has a slightly similar effect. then in the same c file

Hi, I just checked in a fix for the bug you reported. Let me know if it works. Cheers, Jean-Marc On 05/06/14 12:41 AM, Alpha Thinktink wrote: > In debugging I saw: > opus_multistream_encoder.c > line 760 > if(!vbr) > max_data_bytes = IMIN(max_data_bytes, > 3*st->bitrate_bps/(3*8*Fs/frame_size)); > > max_data_bytes after this code becomes -2 where as

#2027: multistream_encode(_float) fails on hard cbr encodes in libopus v1.1 -----------------------------------------+------------------------------ Reporter: thinktink | Owner: jmvalin@? Type: defect | Status: closed Priority: P3 | Milestone: Component: Opus |

#2027: multistream_encode(_float) fails on hard cbr encodes in libopus v1.1 -----------------------------------------+------------------------------ Reporter: thinktink | Owner: jmvalin@? Type: defect | Status: closed Priority: P3 | Milestone: Component: Opus |

I am developing an arm based application which is soon to be released. I noticed on this list mention of neon instruction optimisations in the git version of libopus (which I will be testing shortly) whose speed improvements I would very much like to benefit from in my application. However I would also very much like to be able to release my application based on an official libopus release,

Hello, you can compile opus with "--enable-fixed-point". That saves a cpu ressources. https://github.com/Studio -Link/PKGBUILDs_clean/blob/master/opus/PKGBUILD#L23 -- nice regards, Sebastian Reimers ------------------------------------------ IT-Service Sebastian Reimers Am blanken Boom 14 32369 Rahden Festnetz: 05776-3930000 Fax-Nummer: 05221-17242088 Skype: miete-admin E-Mail:

I was digging around and saw a bunch of different people have created ways of building libopus for android (even I did one back in the CELT days). Is there an official one somewhere that I missed? I even notice this is the Google sources, but it seems to be a touch long in tooth at this point: https://android.googlesource.com/platform/external/libopus/+/android-wear-5.1.1_r1 I am happy to build