similar to: Building opus for android

Hello. I've developed VOIP android app. using speex codec, and it works very well. But I want to change to Opus codec, instead speex. Where can I find sample opus android.mk file ? I am a beginner of NDK. so I cannot make android.mk file myself. Please help me. tks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello. I'm trying to use opus-tools on Android to encode wav data but I couldn't build it. I need to resample my raw data so opusenc does its job. Is it possible to use opus-tools on Android? OPUS is the first citizen in my app but not sure which flags I need to add to build this. LOCAL_CFLAGS := -w -std=gnu99 -O2 -DNULL=0 -DSOCKLEN_T=socklen_t -DLOCALE_NOT_USED -D_LARGEFILE_SOURCE=1

I wanted to send out a little note to the Opus/Xiph list about my Kickstarter project for Cool Mic, an open source Icecast source client for Android (I hope it's not out of line that I do. I'm hoping to grab your attention for just a minute to tell you about it. For those also on the Icecast user list I apologize for the cross-post). Cool Mic is an open-source Icecast 2.x source client.

Hi! You probably know already, but recently there's "fobbar2000 mobile" available for Android (I think Windows and iOS, too), and it plays Opus even ol older Android (like 4.0). Ulrich

I integrated libopusenc(version 0.2.1) to Android platform. but I collected some crash when opus encode destory. error backstrace as following: 1 #00 pc 0006828e /system/lib/libc.so (je_huge_salloc+133) [armeabi-v7a] 2 #01 pc 0006d303 /system/lib/libc.so (ifree+274) [armeabi-v7a] 3 #02 pc 0006d65d /system/lib/libc.so (je_free+72) [armeabi-v7a] 4 #03 pc 000025ef libopusenc.so ope_encoder_destroy

Hi, We are rebasing our audio compression subsystem using OPUS rather than SPEEX. The platform is Android but this piece is written in C code: we need to support armv5/armv7/x86 architectures.... and we use the released opus-1.1beta package from here<http://downloads.xiph.org/releases/opus/opus-1.1-beta.tar.gz>. A lot of our OPUS build system + code to drive the audio compression has been

On 2019-04-14 9:35 a.m., zol wrote: > When trying to play vorbis or opus files that have large cover sizes > >1MB on android 8.0 built in player, they fail to play. Removing the > cover allows them to play. I didn't investigate very closely (and my android 8 device has always ignored opus files!) But I'd guess it's either a bug with re-assembling the larger metadata

Hi Ralph, Gentle reminder.. Regards, Rhishi -----Original Message----- From: Rhishikesh Agashe Sent: Friday, September 20, 2013 11:02 To: 'Ralph Giles' Subject: RE: [opus] Need info on optimizing Opus code for a particular core/processor Hi Ralph, Can you let me know how to submit my code for review? What is the procedure? Also, could you create an account for the same let me know

When trying to play vorbis or opus files that have large cover sizes >1MB on android 8.0 built in player, they fail to play. Removing the cover allows them to play.  Has anyone encountered this before or know if it is a known android or opus/vorbis bug?

Hi, Many car radios of today, don't support opus encoded files, but do support Android auto, and Apple car play. Are there any plans on making an opus app for Android auto, for the car (like one that works with my Ford)? Thanks! Herman -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'm not sure what you mean exactly by your question, but Opus should compile out-of-the-box on both Android and iOS. Now, AFAIK newer Android versions already include Opus as part of the platform, but I don't think iOS does at this point. Cheers, Jean-Marc On 09/12/16 09:51 AM, Chris Bohlin wrote: > Hello, I am trying to see if the codec is fully supported on Android and >

I'm trying to do a standalone build of Opus and I get the following messages when compiling for android arm64 using clang:   CC       silk/fixed/arm/warped_autocorrelation_FIX_neon_intr.lo silk/fixed/arm/warped_autocorrelation_FIX_neon_intr.c:43:37: warning: incompatible pointer types assigning to 'const long *' from 'long long *' [-Wincompatible-pointer-types]    

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

Hi folks sincere apologies if this is not meant to be posted here. I am the CEO at http://directi.com. One of our products http://talk.to is in the messaging space and we are planning to add voice support to our application and are currently investigating codecs (Opus, ilbc, isac, G.729, AMR etc). There are several variables and obviously Opus would be our preferred choice given its quality, VBR,

Hi folks sincere apologies if this is not meant to be posted here. I am the CEO at http://directi.com. One of our products http://talk.to is in the messaging space and we are planning to add voice support to our application and are currently investigating codecs (Opus, ilbc, isac, G.729, AMR etc). There are several variables and obviously Opus would be our preferred choice given its quality, VBR,

Hi, We have observed that the stack usage in Opus Encoder/Decoder is enormous(50-60Kb approx). As we all know, in embedded systems, high stack usage is discouraged. How are we planning to take care of that? One idea is to allocate the required memory on heap and pass it on as an argument to the main Opus API and allocate the internal buffers used by the internal modules on the allocated buffer.

Yeah I see the definition, but unlike USE_ALLOCA and VAR_ARRAYS, it has not been used/set anywhere in the code for allocating buffers! Regards, Rhishi -----Original Message----- From: Jean-Marc Valin [mailto:jmvalin at jmvalin.ca] Sent: Friday, September 20, 2013 12:00 To: Rhishikesh Agashe Cc: opus at xiph.org Subject: Re: [opus] Regarding stack usage in Opus Actually, the code already has

Actually, the code already has an option for using the heap rather than the stack, see NONTHREADSAFE_PSEUDOSTACK in the code. As the name implies, it's not thread-safe though. Cheers, Jean-Marc On 20/09/13 01:29 AM, Rhishikesh Agashe wrote: > Hi, > > > > We have observed that the stack usage in Opus Encoder/Decoder is > enormous(50-60Kb approx). As we all know, in

When trying to play vorbis or opus files that have large cover sizes >1MB on android 8.0 built in player, they fail to play. Removing the cover allows them to play. Has anyone encountered this before or know if it is a known android or opus/vorbis bug?

Hi All, I am brand new to CELT and have some questions about support on android. 1) When I play the CELT samples at http://www.celt-codec.org/samples/tasl/on my android Gingerbread (2.3.4) phone it works - does it mean that Android already has CELT built it? If yes, what version of the library is it using? 2) Is there any documentation I can refer to for support level on android? - thanks