similar to: renaming list to opus

陈伟旭 wrote: > So part of the wiki is out of date? Beside Opus-tools, I also concern > about the spec, optimization and future work in wiki. Could you tell me > about if they are out of date? > On 08/28/2019 00:08, Ralph Giles <mailto:giles at thaumas.net> wrote: For the Spec section: There is a Matroska mapping, and it has been implemented in Firefox and FFmpeg (and Chrome

hi,All, I want to know whether Opus has AEC features like Speex? Thanks 2012/10/17 <opus-request at xiph.org> > Send opus mailing list submissions to > opus at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xiph.org/mailman/listinfo/opus > or, via email, send a message with subject or body 'help' to

Hi Ralph, I have pushed patches to enable radix 3 and radix 5. Github: https://github.com/projectNe10/Ne10/releases/tag/v1.2.0 Best Regards, Phil Wang > Date: Thu, 11 Dec 2014 10:46:50 -0800 > From: Ralph Giles <giles at thaumas.net> > Subject: Re: [opus] [ARM][FFT][NEON] Integrate Ne10 into Opus? > To: opus at xiph.org > Message-ID: <5489E69A.5000305 at thaumas.net>

Hi, I had found a Opus TODO list in https://wiki.xiph.org/index.php?title=OpusTodo&mobileaction=toggle_view_desktop . The item "Opus-tools" interest me. And here is my question about "Port opusdec to libopusfile/libopusurl": 1. Does this function have achieved? On one hand, I think not literally. On the other hand, after briefly reviewing opusdec.c of opus-tools, I found

1. If you're building in CCS, I hope you have created new projects and imported the source and header files. 2. Then right click on project you want to build -> Build Properties -> Under C600 Compiler, click on Basic Options -> Change Optimization level On Fri, Sep 6, 2013 at 12:30 AM, <opus-request at xiph.org> wrote: > Send opus mailing list submissions to >

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

Yes, that's a start. Ultimately, though, I'm hoping to reduce the 80ms requirement, and am trying to get a handle on what state in the decoder must converge and what complications I might be up against. I'm also only considering CELT-based encodings if that simplifies things. I know that Opus can do inter-frame energy envelope prediction, but that dependency can be eliminated by

On 23/02/15 10:30 AM, Tony wrote: > I __think__ opus-tools' opusenc has code which can be used as a > template/sample for how to create an .Ogg file with Opus content. As > expected, it makes use of libopus and libogg. Sadly that's the best option currently. As you say it's a bit complicated, although oggenc has a lot of extra support for controlling encoder options you

<div id="contentDescription" style="line-height:1.5;text-align:justify;text-justify:inter-ideograph"> <div>Thanks to your reply.</div><div><br></div><div>So part of the wiki is out of date? Beside Opus-tools, I also concern about the spec, optimization and future work in wiki. Could you tell me about if they are out

Hi, While testing the Opus Decoder we came across the following: If the decoder encounters an 'Invalid Payload Length' the decoding of the stream is stopped. Also, when the decoder encounters 'Range coder state mismatch', the decoding of the stream is stopped. I believe that it should reject the erroneous payload and start decoding the next payload for it to work properly in a

Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the

Hi, I have application, where I am reciving the RTP packets, which has OPUS payload. >From the RTP packets I got following information: (12 byes Header) tells about the version, payload time, time stamp, srsc, etc. The rest of the packet is OPUS payload (raw format), The TOC byte from OPUS payload tells its 20ms frame, even the time stamp different of 960 means 20 msec frame. Questions: 1)

Dear Christian van Bijleveld, You can use any of the below DSPs of Texas Instruments 1. TMS320C674x - This supports floating point implementation of opus 2. TMS320C66x - This supports both floating and fixed point implementations 3. TMS320C64x - This supports only fixed point implementation Regards, Mahantesh On Mon, May 13, 2013 at 10:12 PM, <opus-request at xiph.org> wrote: >

Sorry about that, let me check the correct version for the intrin0.h include guard. //Marcus ________________________________ From: Ralph Giles <giles at thaumas.net> Sent: Thursday, June 11, 2020 19:31 To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org> Subject: Re: [opus] Misc patches Speaking of needing more complete ci feedback, the intrin0.h

Hi, I've been studying the Opus code and documentation for a while and have seen it mentioned several times that Opus uses pre-skip to allow the codec to converge. What convergence are they referring to? Rate control? Energy envelope prediction after seeking? Is there a discussion of this somewhere? Also, I'm also interested in the seeking behaviour of the decoder. If, say, I want to

Hi Ralph, I am using Http Progressive download technique to download the opus audio in chunks. So I am not sure if the Opusfile seek API will work in this case. Please correct me if I am wrong. Is there anyway to get or calculate the byte offset corresponding to the PCM time position? Then I can ask the server to serve the file from that byte onwards. Regards, Deepak. On Tue, Nov 8, 2016 at

Verified that intrin0.h was available in 1910, by building it locally on VS2017 version 15.0 MSVC++ 14.1 _MSC_VER == 1910 (Visual Studio 2017 version 15.0) https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B //Marcus ________________________________ From: Marcus Asteborg <xnorpx at outlook.com> Sent: Thursday, June 11, 2020 20:15 To: Ralph Giles <giles at thaumas.net>; opus at

FYI, the Ogg Opus encapsulation is now RFC 7845: https://tools.ietf.org/html/rfc7845 -------- Forwarded Message -------- Subject: [codec] RFC 7845 on Ogg Encapsulation for the Opus Audio Codec Date: Fri, 29 Apr 2016 19:47:28 -0700 (PDT) From: rfc-editor at rfc-editor.org To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org CC: drafts-update-ref at iana.org, codec at ietf.org, rfc-editor at

Hi Amit, I'm not sure what you're trying to ask, but the reserved space in the header is an optional thing. Encoders are free to do it, but are not required to do so. Jean-Marc On 05/11/2016 01:32 PM, Amit Ashara wrote: > Hello Jean-Marc, > > So for the moment we can assume that this method is also OK to use? > > On Embedded Systems, both SRAM and Flash can be a

All, Just a heads up that the IETF codec working group has issued a last call on the draft Opus specification. This means we think the draft adequately documents the format, and that we're willing to live with whatever bugs are present in the reference implementation, if they can't be fixed without breaking decodes. In turn, this means we could really use some feedback from implementers.