From silverbacknet at gmail.com Wed Apr 1 06:12:02 2020 From: silverbacknet at gmail.com (Emily Bowman) Date: Tue, 31 Mar 2020 23:12:02 -0700 Subject: [opus] opus-codec.org/comparison: Mono or Stereo? In-Reply-To: References: Message-ID: When it comes to the specific file mentioned from that page, the original caption was also "Quality vs Bit-rate. - The figure below illustrates the quality of various codecs as a function of the bit-rate. It attempts to summarize results from a collection of listening tests and (when no data exists) show anecdotal evidence. It is overall fairly representative, but attempting to extract any exact value at a particular bitrate is certainly not recommended." Plus it's from 2012, and likely isn't fully representative of the Opus and alternative codec advancements since. Emily B On Tue, Mar 31, 2020 at 1:54 PM Orestes Zoupanos < oresteszoupanos at hotmail.com> wrote: > Paul, > > you may find the following page has more useful/accurate numbers than that > diagram: > > https://wiki.xiph.org/Opus_Recommended_Settings > > > ------------------------------ > *From:* opus on behalf of Paul Marks < > pmarks at google.com> > *Sent:* Thursday, February 13, 2020 6:31:39 PM > *To:* opus at xiph.org > *Subject:* [opus] opus-codec.org/comparison: Mono or Stereo? > > Looking at the Opus comparison page[1], I can't figure out whether the > Opus/AAC/Vorbis/MP3 lines are meant to imply a mono or stereo > encoding. Could someone please update the caption to clarify this? > > The single dot for G.711 is clearly mono, but for stereo music, are > the codecs at the top meant to converge near 128 kbps, or 256 kbps? > > [1] http://opus-codec.org/comparison/ > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.jackson at sonocent.com Wed Apr 1 16:08:32 2020 From: simon.jackson at sonocent.com (Simon Jackson) Date: Wed, 1 Apr 2020 17:08:32 +0100 Subject: [opus] Opusfile CMake build Message-ID: Hi, Would you be interested in a patch to add CMake support to Opusfile? Opus already seems to have it, but I had to roll my own for Opusfile. I've attached a patch if you're interested, I've been using for a while now and it does what I need, it may not be exhaustive enough for wider distribution though. Hope it helps, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: opusfile_cmake.patch Type: application/octet-stream Size: 2315 bytes Desc: not available URL: From simon.jackson at sonocent.com Tue Apr 7 10:47:21 2020 From: simon.jackson at sonocent.com (Simon Jackson) Date: Tue, 7 Apr 2020 11:47:21 +0100 Subject: [opus] CMake patches In-Reply-To: References: <329af864-b621-413b-32fe-3a1209d8854b@jmvalin.ca> Message-ID: Did the patch 5 split / AVX fix work get merged at all, I didn't see any more mails about it? Thanks! On Tue, 14 Jan 2020 at 21:34, Marcus Asteborg wrote: > Awesome thanks! Good comments. > > Please apply patch 1-4 and I prepare another iteration on patch 5 for you > too look at. > > //Marcus > ------------------------------ > *From:* Jean-Marc Valin > *Sent:* Tuesday, January 14, 2020 08:24 > *To:* Marcus Asteborg > *Cc:* Simon Jackson > *Subject:* Re: [opus] CMake patches > > Hi Marcus, > > So I looked at the patches and have no issue with patches 1-4. For > patches 5 I have a few comments/questions. > > - The patch should probably be split in 3 (alloca, fast-math, and > SSE/AVX) to be clearer and easier to bisect if something goes wrong. > - About the alloca part, I'm not sure I understand what's happening but > it looks like alloca gets enabled only with MSVC and not gcc? That's > fine if gcc gets VAR_ARRAYS instead, but otherwise it's suboptimal and > may lead to problems. > - About FLOAT_APPROX, this is not the same as -ffast-math. FLOAT_APPROX > means that the code will approximate functions like exp() and log() by > directly playing with the bits *assuming* that the float data is in IEEE > 754 format. That's the case for x86 and ARM, but there are odd > architectures that implement non-754 float. Enabling FLOAT_APPROX on > those would break Opus badly. So it would be best to only enable > FLOAT_APPROX on archs that are known to have 754 float. > - About SSE/AVX, I read the post about why MAY_HAVE could break with > MSVC. Note that the Opus codebase uses static for every function defined > in header files, so that part shouldn't be a problem. OTOH, the math.h > problem may still be there. If you have a way to solve the math.h > problem, cpu detection on MSVC might be an option though. > > Cheers, > > Jean-Marc > > > On 1/9/20 12:48 AM, Marcus Asteborg wrote: > > Ping @Jean-Marc Valin > ! > > ------------------------------------------------------------------------ > > *From:* Simon Jackson > > *Sent:* Wednesday, January 8, 2020 09:54 > > *To:* Marcus Asteborg > > *Cc:* opus at xiph.org ; Jean-Marc Valin > > > *Subject:* Re: [opus] CMake patches > > Hi, > > > > This is great! I've literally run into the SSE/AVX issue over the past > > two days and was about to start putting together a PR myself. When using > > libopus compiled with the CMake toolchain on the Google Android > > emulator, `-mavx` causes SIGILL because it's vectorising the variadic > > function parameters and the emulator doesn't support AVX. I'd really > > appreciate if these make their way into master quickly because this has > > been causing me a bit of a headache. > > > > Thanks! > > > > On Wed, 18 Dec 2019 at 00:00, Marcus Asteborg > >> wrote: > > > > Hi all, > > > > With some downtime it's time for some CMake fixes. > > > > Most critically is the SSE fixes to avoid crashes that is described > > in 154 and 132 in github. Patch 5 should address this and also > > adding APPROX-FLOAT option. > > Hopefully this can give some gains for those of us running on > > Windows servers.j > > > > I went through the pull request and picked out a few that will ease > > up integration for consumers of Opus. Those patches are also added > > here with the original authors as commiters. > > > > I will go through the rest of the CMake related pull requests as > > well later this week. > > > > It would be nice to setup a CI-Pipeline with CMake builds whoever > > owns that on feel free to reach out to me and I can do the work > needed. > > > > //Marcus > > _______________________________________________ > > opus mailing list > > opus at xiph.org > > > > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7Cc15671b24d8e491dc19508d7990e4df7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637146159020540767&sdata=GdeehvmtVJ2EIjN9ZbfFBhVVfQHR4jaOoQoqeHhhZAY%3D&reserved=0 > > < > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7Cc15671b24d8e491dc19508d7990e4df7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637146159020540767&sdata=GdeehvmtVJ2EIjN9ZbfFBhVVfQHR4jaOoQoqeHhhZAY%3D&reserved=0 > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ulrich.Windl at rz.uni-regensburg.de Tue Apr 7 12:49:24 2020 From: Ulrich.Windl at rz.uni-regensburg.de (Ulrich Windl) Date: Tue, 07 Apr 2020 14:49:24 +0200 Subject: [opus] Container-less use of speex codec?? Message-ID: <5E8C76D4020000A10003822E@gwsmtp.uni-regensburg.de> Hi! >From what I learned is that the popular AVM "Fritz!Box" (www.avm.de) uses container-less speex for saving voice data (like from the answering machine). I have no idea why they decided to do so, but it's a matter of fact. The format is still the same in the current firmware. There are hacks out that allow the tools to process files without the Ogg header, and I wonder how hard it would be to provide some options in the opustools to be able to use the standard instead of some hacks. Try Googling for "speex-1.2beta3-fritzboxtam-beta1-src.tar.bz2. Regards, Ulrich " From xnorpx at outlook.com Tue Apr 7 15:27:51 2020 From: xnorpx at outlook.com (Marcus Asteborg) Date: Tue, 7 Apr 2020 15:27:51 +0000 Subject: [opus] CMake patches In-Reply-To: References: <329af864-b621-413b-32fe-3a1209d8854b@jmvalin.ca> , Message-ID: Not yet, Haven't got time to finalize it. But hopefully next month or so. Here is devbranch: https://github.com/xnorpx/opus/tree/dev/cmakefixes2 ________________________________ From: Simon Jackson Sent: Tuesday, April 7, 2020 03:47 To: Marcus Asteborg ; opus at xiph.org Cc: Jean-Marc Valin Subject: Re: [opus] CMake patches Did the patch 5 split / AVX fix work get merged at all, I didn't see any more mails about it? Thanks! On Tue, 14 Jan 2020 at 21:34, Marcus Asteborg > wrote: Awesome thanks! Good comments. Please apply patch 1-4 and I prepare another iteration on patch 5 for you too look at. //Marcus ________________________________ From: Jean-Marc Valin > Sent: Tuesday, January 14, 2020 08:24 To: Marcus Asteborg > Cc: Simon Jackson > Subject: Re: [opus] CMake patches Hi Marcus, So I looked at the patches and have no issue with patches 1-4. For patches 5 I have a few comments/questions. - The patch should probably be split in 3 (alloca, fast-math, and SSE/AVX) to be clearer and easier to bisect if something goes wrong. - About the alloca part, I'm not sure I understand what's happening but it looks like alloca gets enabled only with MSVC and not gcc? That's fine if gcc gets VAR_ARRAYS instead, but otherwise it's suboptimal and may lead to problems. - About FLOAT_APPROX, this is not the same as -ffast-math. FLOAT_APPROX means that the code will approximate functions like exp() and log() by directly playing with the bits *assuming* that the float data is in IEEE 754 format. That's the case for x86 and ARM, but there are odd architectures that implement non-754 float. Enabling FLOAT_APPROX on those would break Opus badly. So it would be best to only enable FLOAT_APPROX on archs that are known to have 754 float. - About SSE/AVX, I read the post about why MAY_HAVE could break with MSVC. Note that the Opus codebase uses static for every function defined in header files, so that part shouldn't be a problem. OTOH, the math.h problem may still be there. If you have a way to solve the math.h problem, cpu detection on MSVC might be an option though. Cheers, Jean-Marc On 1/9/20 12:48 AM, Marcus Asteborg wrote: > Ping @Jean-Marc Valin ! > ------------------------------------------------------------------------ > *From:* Simon Jackson > > *Sent:* Wednesday, January 8, 2020 09:54 > *To:* Marcus Asteborg > > *Cc:* opus at xiph.org >; Jean-Marc Valin > > *Subject:* Re: [opus] CMake patches > Hi, > > This is great! I've literally run into the SSE/AVX issue over the past > two days and was about to start putting together a PR myself. When using > libopus compiled with the CMake toolchain on the Google Android > emulator, `-mavx` causes SIGILL because it's vectorising the variadic > function parameters and the emulator doesn't support AVX. I'd really > appreciate if these make their way into master quickly because this has > been causing me a bit of a headache. > > Thanks! > > On Wed, 18 Dec 2019 at 00:00, Marcus Asteborg > > wrote: > > Hi all, > > With some downtime it's time for some CMake fixes. > > Most critically is the SSE fixes to avoid crashes that is described > in 154 and 132 in github. Patch 5 should address this and also > adding APPROX-FLOAT option. > Hopefully this can give some gains for those of us running on > Windows servers.j > > I went through the pull request and picked out a few that will ease > up integration for consumers of Opus. Those patches are also added > here with the original authors as commiters. > > I will go through the rest of the CMake related pull requests as > well later this week. > > It would be nice to setup a CI-Pipeline with CMake builds whoever > owns that on feel free to reach out to me and I can do the work needed. > > //Marcus > _______________________________________________ > opus mailing list > opus at xiph.org > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7Cc15671b24d8e491dc19508d7990e4df7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637146159020540767&sdata=GdeehvmtVJ2EIjN9ZbfFBhVVfQHR4jaOoQoqeHhhZAY%3D&reserved=0 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.jackson at sonocent.com Thu Apr 9 15:59:54 2020 From: simon.jackson at sonocent.com (Simon Jackson) Date: Thu, 9 Apr 2020 16:59:54 +0100 Subject: [opus] Opus CMake build support for Apple frameworks Message-ID: Hi, I've put together a patch which adds support to the CMake build for building Apple frameworks, as much as I dislike them. Is this something you'd like to integrate? Thanks, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: opus_cmake_frameworks.patch Type: application/octet-stream Size: 2793 bytes Desc: not available URL: From xnorpx at outlook.com Fri Apr 10 17:31:56 2020 From: xnorpx at outlook.com (Marcus Asteborg) Date: Fri, 10 Apr 2020 17:31:56 +0000 Subject: [opus] Opus CMake build support for Apple frameworks In-Reply-To: References: Message-ID: Hi Simon, CMake 3.14 add support for crosscompiling iOS, tvOS and watchOS https://cmake.org/cmake/help/v3.14/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos Can you clarify what your patch does? //Marcus cmake-toolchains(7) — CMake 3.14.7 Documentation The CMAKE_SYSTEM_NAME is the CMake-identifier of the target platform to build for.. The CMAKE_SYSTEM_PROCESSOR is the CMake-identifier of the target architecture to build for.. The CMAKE_SYSROOT is optional, and may be specified if a sysroot is available.. The CMAKE_STAGING_PREFIX is also optional. It may be used to specify a path on the host to install to. The CMAKE_INSTALL_PREFIX is always ... cmake.org ________________________________ From: opus on behalf of opus-request at xiph.org Sent: Friday, April 10, 2020 05:00 To: opus at xiph.org Subject: opus Digest, Vol 132, Issue 5 Send opus mailing list submissions to opus at xiph.org To subscribe or unsubscribe via the World Wide Web, visit https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 or, via email, send a message with subject or body 'help' to opus-request at xiph.org You can reach the person managing the list at opus-owner at xiph.org When replying, please edit your Subject line so it is more specific than "Re: Contents of opus digest..." Today's Topics: 1. Opus CMake build support for Apple frameworks (Simon Jackson) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Apr 2020 16:59:54 +0100 From: Simon Jackson To: opus at xiph.org Subject: [opus] Opus CMake build support for Apple frameworks Message-ID: Content-Type: text/plain; charset="utf-8" Hi, I've put together a patch which adds support to the CMake build for building Apple frameworks, as much as I dislike them. Is this something you'd like to integrate? Thanks, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: opus_cmake_frameworks.patch Type: application/octet-stream Size: 2793 bytes Desc: not available URL: ------------------------------ Subject: Digest Footer _______________________________________________ opus mailing list opus at xiph.org https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 ------------------------------ End of opus Digest, Vol 132, Issue 5 ************************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.jackson at sonocent.com Tue Apr 14 09:12:23 2020 From: simon.jackson at sonocent.com (Simon Jackson) Date: Tue, 14 Apr 2020 10:12:23 +0100 Subject: [opus] Opus CMake build support for Apple frameworks In-Reply-To: References: Message-ID: Hi Marcus, When building shared libraries for macOS / iOS /tvOS, by default `.dylib` shared libraries will be generated. With this patch `BUILD_FRAMEWORK` is exposed as an option allowing the user to specify that a `.framework` bundle should be built instead of a standalone `.dylib` file. Enabling the option sets the necessary target properties to instruct CMake to do this. The Ogg CMake build already has this functionality, this patch should be consistent with how frameworks are handled there. Simon On Fri, 10 Apr 2020 at 18:32, Marcus Asteborg wrote: > Hi Simon, > > CMake 3.14 add support for crosscompiling iOS, tvOS and watchOS > > > https://cmake.org/cmake/help/v3.14/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos > > Can you clarify what your patch does? > > //Marcus > cmake-toolchains(7) — CMake 3.14.7 Documentation > > The CMAKE_SYSTEM_NAME is the CMake-identifier of the target platform to > build for.. The CMAKE_SYSTEM_PROCESSOR is the CMake-identifier of the > target architecture to build for.. The CMAKE_SYSROOT is optional, and may > be specified if a sysroot is available.. The CMAKE_STAGING_PREFIX is also > optional. It may be used to specify a path on the host to install to. The > CMAKE_INSTALL_PREFIX is always ... > cmake.org > > > ------------------------------ > *From:* opus on behalf of opus-request at xiph.org < > opus-request at xiph.org> > *Sent:* Friday, April 10, 2020 05:00 > *To:* opus at xiph.org > *Subject:* opus Digest, Vol 132, Issue 5 > > Send opus mailing list submissions to > opus at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 > or, via email, send a message with subject or body 'help' to > opus-request at xiph.org > > You can reach the person managing the list at > opus-owner at xiph.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of opus digest..." > > > Today's Topics: > > 1. Opus CMake build support for Apple frameworks (Simon Jackson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Apr 2020 16:59:54 +0100 > From: Simon Jackson > To: opus at xiph.org > Subject: [opus] Opus CMake build support for Apple frameworks > Message-ID: > U-LcAOZmSK_1phySrTRWGG9UhcMDWjf5Txw at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > I've put together a patch which adds support to the CMake build for > building Apple frameworks, as much as I dislike them. Is this something > you'd like to integrate? > > Thanks, > Simon > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fpipermail%2Fopus%2Fattachments%2F20200409%2Fa281ca94%2Fattachment-0001.html&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=nIeHaWLowLksYl9QQvV1y2Rkd3zvUGiuqfIUYHknHnw%3D&reserved=0 > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: opus_cmake_frameworks.patch > Type: application/octet-stream > Size: 2793 bytes > Desc: not available > URL: < > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fpipermail%2Fopus%2Fattachments%2F20200409%2Fa281ca94%2Fattachment-0001.obj&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=d5V%2BTOGF3Onv6FJiFXlksuCLdf2Q5XKhqpQ8VsANw%2BU%3D&reserved=0 > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > opus mailing list > opus at xiph.org > > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 > > > ------------------------------ > > End of opus Digest, Vol 132, Issue 5 > ************************************ > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.jackson at sonocent.com Tue Apr 14 14:30:59 2020 From: simon.jackson at sonocent.com (Simon Jackson) Date: Tue, 14 Apr 2020 15:30:59 +0100 Subject: [opus] Opusfile CMake build In-Reply-To: References: Message-ID: I've updated the patch with support for building Apple frameworks. New patch attached, the old one can be ignored / discarded. Simon On Wed, 1 Apr 2020 at 17:08, Simon Jackson wrote: > Hi, > > Would you be interested in a patch to add CMake support to Opusfile? Opus > already seems to have it, but I had to roll my own for Opusfile. I've > attached a patch if you're interested, I've been using for a while now and > it does what I need, it may not be exhaustive enough for wider distribution > though. > > Hope it helps, > Simon > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: opusfile_cmake_frameworks.patch Type: application/octet-stream Size: 2616 bytes Desc: not available URL: From xnorpx at outlook.com Tue Apr 14 14:49:52 2020 From: xnorpx at outlook.com (Marcus Asteborg) Date: Tue, 14 Apr 2020 14:49:52 +0000 Subject: [opus] Opus CMake build support for Apple frameworks In-Reply-To: References: , Message-ID: Hi Simon, Please create a pull request here: https://github.com/xnorpx/opus/pulls Also please add a buildconfig here that exercise the BUILD_FRAMEWORK option: https://github.com/xnorpx/opus/blob/master/.github/workflows/build.yml [https://avatars2.githubusercontent.com/u/302709?s=400&v=4] xnorpx/opus Modern audio compression for the internet. Contribute to xnorpx/opus development by creating an account on GitHub. github.com That way we can ensure the patch work as expected and doesn't break any exciting behavior. Best Regards Marcus ________________________________ From: Simon Jackson Sent: Tuesday, April 14, 2020 02:12 To: Marcus Asteborg Cc: opus at xiph.org Subject: Re: [opus] Opus CMake build support for Apple frameworks Hi Marcus, When building shared libraries for macOS / iOS /tvOS, by default `.dylib` shared libraries will be generated. With this patch `BUILD_FRAMEWORK` is exposed as an option allowing the user to specify that a `.framework` bundle should be built instead of a standalone `.dylib` file. Enabling the option sets the necessary target properties to instruct CMake to do this. The Ogg CMake build already has this functionality, this patch should be consistent with how frameworks are handled there. Simon On Fri, 10 Apr 2020 at 18:32, Marcus Asteborg > wrote: Hi Simon, CMake 3.14 add support for crosscompiling iOS, tvOS and watchOS https://cmake.org/cmake/help/v3.14/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos Can you clarify what your patch does? //Marcus cmake-toolchains(7) — CMake 3.14.7 Documentation The CMAKE_SYSTEM_NAME is the CMake-identifier of the target platform to build for.. The CMAKE_SYSTEM_PROCESSOR is the CMake-identifier of the target architecture to build for.. The CMAKE_SYSROOT is optional, and may be specified if a sysroot is available.. The CMAKE_STAGING_PREFIX is also optional. It may be used to specify a path on the host to install to. The CMAKE_INSTALL_PREFIX is always ... cmake.org ________________________________ From: opus > on behalf of opus-request at xiph.org > Sent: Friday, April 10, 2020 05:00 To: opus at xiph.org > Subject: opus Digest, Vol 132, Issue 5 Send opus mailing list submissions to opus at xiph.org To subscribe or unsubscribe via the World Wide Web, visit https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 or, via email, send a message with subject or body 'help' to opus-request at xiph.org You can reach the person managing the list at opus-owner at xiph.org When replying, please edit your Subject line so it is more specific than "Re: Contents of opus digest..." Today's Topics: 1. Opus CMake build support for Apple frameworks (Simon Jackson) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Apr 2020 16:59:54 +0100 From: Simon Jackson > To: opus at xiph.org Subject: [opus] Opus CMake build support for Apple frameworks Message-ID: > Content-Type: text/plain; charset="utf-8" Hi, I've put together a patch which adds support to the CMake build for building Apple frameworks, as much as I dislike them. Is this something you'd like to integrate? Thanks, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: > -------------- next part -------------- A non-text attachment was scrubbed... Name: opus_cmake_frameworks.patch Type: application/octet-stream Size: 2793 bytes Desc: not available URL: > ------------------------------ Subject: Digest Footer _______________________________________________ opus mailing list opus at xiph.org https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 ------------------------------ End of opus Digest, Vol 132, Issue 5 ************************************ _______________________________________________ opus mailing list opus at xiph.org http://lists.xiph.org/mailman/listinfo/opus -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.jackson at sonocent.com Wed Apr 15 15:14:49 2020 From: simon.jackson at sonocent.com (Simon Jackson) Date: Wed, 15 Apr 2020 16:14:49 +0100 Subject: [opus] Opus CMake build support for Apple frameworks In-Reply-To: References: Message-ID: Hi Marcus, Just letting you know that I've opened the PR, in case you don't get notified. Regards, Simon On Tue, 14 Apr 2020 at 15:49, Marcus Asteborg wrote: > Hi Simon, > > Please create a pull request here: https://github.com/xnorpx/opus/pulls > Also please add a buildconfig here that exercise the BUILD_FRAMEWORK > option: > https://github.com/xnorpx/opus/blob/master/.github/workflows/build.yml > > xnorpx/opus > > Modern audio compression for the internet. Contribute to xnorpx/opus > development by creating an account on GitHub. > github.com > That way we can ensure the patch work as expected and doesn't break any > exciting behavior. > > Best Regards Marcus > > ------------------------------ > *From:* Simon Jackson > *Sent:* Tuesday, April 14, 2020 02:12 > *To:* Marcus Asteborg > *Cc:* opus at xiph.org > *Subject:* Re: [opus] Opus CMake build support for Apple frameworks > > Hi Marcus, > > When building shared libraries for macOS / iOS /tvOS, by default `.dylib` > shared libraries will be generated. With this patch `BUILD_FRAMEWORK` is > exposed as an option allowing the user to specify that a `.framework` > bundle should be built instead of a standalone `.dylib` file. Enabling the > option sets the necessary target properties to instruct CMake to do this. > > The Ogg CMake build already has this functionality, this patch should be > consistent with how frameworks are handled there. > > Simon > > On Fri, 10 Apr 2020 at 18:32, Marcus Asteborg wrote: > > Hi Simon, > > CMake 3.14 add support for crosscompiling iOS, tvOS and watchOS > > > https://cmake.org/cmake/help/v3.14/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos > > > Can you clarify what your patch does? > > //Marcus > cmake-toolchains(7) — CMake 3.14.7 Documentation > > The CMAKE_SYSTEM_NAME is the CMake-identifier of the target platform to > build for.. The CMAKE_SYSTEM_PROCESSOR is the CMake-identifier of the > target architecture to build for.. The CMAKE_SYSROOT is optional, and may > be specified if a sysroot is available.. The CMAKE_STAGING_PREFIX is also > optional. It may be used to specify a path on the host to install to. The > CMAKE_INSTALL_PREFIX is always ... > cmake.org > > > > ------------------------------ > *From:* opus on behalf of opus-request at xiph.org < > opus-request at xiph.org> > *Sent:* Friday, April 10, 2020 05:00 > *To:* opus at xiph.org > *Subject:* opus Digest, Vol 132, Issue 5 > > Send opus mailing list submissions to > opus at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 > > or, via email, send a message with subject or body 'help' to > opus-request at xiph.org > > You can reach the person managing the list at > opus-owner at xiph.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of opus digest..." > > > Today's Topics: > > 1. Opus CMake build support for Apple frameworks (Simon Jackson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Apr 2020 16:59:54 +0100 > From: Simon Jackson > To: opus at xiph.org > Subject: [opus] Opus CMake build support for Apple frameworks > Message-ID: > U-LcAOZmSK_1phySrTRWGG9UhcMDWjf5Txw at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > I've put together a patch which adds support to the CMake build for > building Apple frameworks, as much as I dislike them. Is this something > you'd like to integrate? > > Thanks, > Simon > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fpipermail%2Fopus%2Fattachments%2F20200409%2Fa281ca94%2Fattachment-0001.html&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=nIeHaWLowLksYl9QQvV1y2Rkd3zvUGiuqfIUYHknHnw%3D&reserved=0 > > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: opus_cmake_frameworks.patch > Type: application/octet-stream > Size: 2793 bytes > Desc: not available > URL: < > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fpipermail%2Fopus%2Fattachments%2F20200409%2Fa281ca94%2Fattachment-0001.obj&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=d5V%2BTOGF3Onv6FJiFXlksuCLdf2Q5XKhqpQ8VsANw%2BU%3D&reserved=0 > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > opus mailing list > opus at xiph.org > > https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xiph.org%2Fmailman%2Flistinfo%2Fopus&data=02%7C01%7C%7C5129a9bc55174fda492008d7dd46b6df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221168091429699&sdata=bYVdG80m0eaYyGgYyrclvfFOXjJicH2525zzf62HtNY%3D&reserved=0 > > > > ------------------------------ > > End of opus Digest, Vol 132, Issue 5 > ************************************ > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefancknoll at gmail.com Sat Apr 18 14:55:54 2020 From: stefancknoll at gmail.com (Stefan Knoll) Date: Sat, 18 Apr 2020 14:55:54 -0000 Subject: [opus] Opus Compile Message-ID: Hi. I am currently failing to cross compile opus. I would really appreciate if anyone with gcc experience could put me on the right track. I am attempting to compile opus 1.3.1 on for an ARMv7 single point hardware target. My command that I am using: ./configure --host=arm-none-eabi --build=x86_64-pc-linux-gnu --target=arm-none-eabi CFLAGS=-mthumb -mcpu=cortex-m4 -mfloat-abi=hard Please see attached config.log. Any assistance would be greatly appreciated Regard, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log Type: text/x-log Size: 11770 bytes Desc: not available URL: From terence.eden at gmail.com Sun Apr 19 10:48:34 2020 From: terence.eden at gmail.com (Terence Eden) Date: Sun, 19 Apr 2020 10:48:34 -0000 Subject: [opus] Stop opusenc from generating any comments? Message-ID: The opusenc tool automatically adds metadata - even if you don't specify any. For example, these tags are created by default on my files: ENCODER=opusenc from opus-tools 0.2 ENCODER_OPTIONS=--bitrate 6 --comp 10 --framesize 60 --padding 0 I've tried using `--discard-comments` but that has no effect. I've tried using `--comment ENCODER=` but that adds a duplicate tag. My limited knowledge of C suggests that the following lines in opusenc.c are where the magic happens: https://github.com/xiph/opus-tools/blob/master/src/opusenc.c#L480 https://github.com/xiph/opus-tools/blob/master/src/opusenc.c#L800 So, would it be possible to add a `--no-metada` option to completely suppress any metadata from being written? I realise this is a niche requirement! I'm trying to create tiny audio files where every byte saved is important. I can use Mutagen to remove the metadata, but I'd like a way not to add it in the first place. Thanks Terence -------------- next part -------------- An HTML attachment was scrubbed... URL: