similar to: Витастади наука

Hi, Before I comment on the graphics you posted to visualize the difference between two audio signals, I'd like to ask for your help in evaluating my JPEG encoder. I've encoded an image with JPEG and then computed the difference with the original. I then converted the difference to sound. You can listen to the image difference on this clip: https://jmvalin.ca/misc_stuff/diff.wav Can you

Just to be clear, my goal here wasn't to make fun of anyone, but to drive the point that spectrograms should *never* be used to demonstrate quality. The only case where they can sometimes be useful is for diagnostic purposes. If you hear something and you're not sure what you're hearing exactly, then sometimes a spectrogram can help you figure out what it is. That's pretty much it.

Hello, you can find pure java version of Opus codec with java spi interface at my web-site: http://dmilvdv.narod.ru/Apps/opus.html   Text in Russian, but must be understandable. Best regards, Dmitriy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20160530/f400f322/attachment-0001.html>

Jean-Mark sarkasm. Jean-Markasm. (Bonus points for providing an actual noisy WAV! ^_^) On 30/10/2017 20:28, Jean-Marc Valin wrote: Hi, Before I comment on the graphics you posted to visualize the difference between two audio signals, I'd like to ask for your help in evaluating my JPEG encoder. I've encoded an image with JPEG and then computed the difference with the original. I then

Good morning. I've ran a test against MP3 format. Code: (first convert tested audio file to 16 bit 48khz with sox.exe if needed) lame.exe -b 320 48khzfilein.wav -o fileout.mp3 lame --decode fileout.mp3 -o fileout.mp3.wav opusenc.exe --bitrate 320 48khzfilein.wav fileout.opus opusdec.exe fileout.opus fileout.opus.wav wavdiff.exe 48khzfilein.wav fileout.mp3.wav -diff fileout.mp3.delta.wav

Still can't reproduce. What OS and compiler version? Jean-Marc On 21/04/15 02:48 AM, Suresh Thiriveedi wrote: > Hi, > > There is no change in the compiler flags. I'm using as it is from the > original code. No change in the Makefile and I believe it is using the > floating point only by default. > > We are using 8k samples and mono so the commands is as follows.

Hello! In file "src/mlp_train.c" was 6 memleaks. I fixed it. --- Best regards, Denis Tsekh Cel.phone: +7 904 891 13 10 E-mail: denis_andreevich at mail.ru Skype: hexus-2008 ICQ: 266669416 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20161215/95e5ab04/attachment.html> -------------- next part

Hi guys, as MP3 and Opus have very similar objectives, I think the original poster's question was a valid one: Why does Opus have more artefacts in the lower frequency ranges than MP3 has? The spontaneous suspect that lower frequency artefacts may be more noticeably than higher frequency artefacts seems plausible, also. Is it a matter of energy (which is higher for higher frequencies)? When

Hi Looks like 1.1 version is sensitive to the system architecture/compiler/kernel version. Below is my observation in various linux system I have. As you mentioned, you are not observed the crash in your system, can you please share your system details. And also please comment on the below table/observations. *Machine IP* *optimization flags* *RHEL version* *kernel version* *gcc version*

Hi, There is no change in the compiler flags. I'm using as it is from the original code. No change in the Makefile and I believe it is using the floating point only by default. We are using 8k samples and mono so the commands is as follows. [root at MEDIA opus-1.1]# ./opus_demo -d 8000 1 opus_encoded_crash.opus opus_encoded_crash.pcm *And segmentation is as below..*. ............ Calling

Hi, On Sat, Jan 28, 2017 at 2:04 AM, Raghavan, Karthik < karthikr at qti.qualcomm.com> wrote: > Hi > > > > I am not sure if this issue has been resolved, but on the latest opus > 1.1.4, > > · I downloaded the tarball, > > · ran ./configure followed by > > · make and then > > · make check > > > > Can you

Hi, I have downloaded the latest stable version *1.0.2 opus audio codec* from the following link: http://www.opus-codec.org/downloads/ *Details of OS & CPU:* OS : Microsoft Windows XP CPU : intel core 2 Duo cpu I am using Microsoft visual C++ 2010 Express to build the codec (opus.vcxproj available in the package downloaded). I am able to build it & could generate the application

Hi On the opus-codec web page here ---> http://www.opus-codec.org/development/ Underneath "Source code repository" there are options to download the gits. As well as the traditional "$ git clone git://git.opus-codec.org/opus.git" there are also Snapshots. opus-master.tar.gz opus-1.0.x-branch.tar.gz It's a great idea... To download HEAD the command can be like this...

Hi Max, cmake .. -G "Visual Studio 16 2019" -A ARM64 -DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=ON cmake --build . -j 10 Is building for me, but I don't have any Windows Arm64 device so cannot test it. Note that: Neon will not work on windows out of the box builds due renamed header:

Le 19-12-18 à 12 h 29, Marc Lavallée a écrit : > Hi Andrew, > > I suspect that the configure option should be enable-ambisonics > (instead of enable_ambisonics), but for each of opus, libopusenc, > opusfile and opus-tools git repos (on master branch), when I try > "./configure --enable-ambisonics", I get this error message: > > configure: WARNING: unrecognized

On 10/28/2013 01:37 PM, Antonio Juan wrote: > The problem is that for using this package I need to use all the libs > like ogg, even Speex?, You do not need Speex. You do need libogg because .opus files *are* Ogg files. > no, and also where i can find an easy example > like opus_demo.c to create the .opus file There's an easy example called opusenc in the opus-tools package :-)

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 >

Any luck reproducing the problem with opus_demo or opus-tools? Jean-Marc On 02/22/2018 10:14 PM, Stepan Salenikovich wrote: > > > On Thu, Feb 22, 2018 at 9:53 PM, Jean-Marc Valin <jmvalin at jmvalin.ca > <mailto:jmvalin at jmvalin.ca>> wrote: > > On 02/22/2018 09:34 PM, Stepan Salenikovich wrote: > > Its unexpected because the decoder continues to

Hi, We are able to reproduce the issue with the 1.1 opus_demo (sample file). We captured the frames in our server just before the opus_decode and fed the file to opus_demo (1.1) and it is crashing. Same file is tested with 1.1.1 and it is fine. So this is in line with our server testing observation and I think here we can conclude that the 1.1 library is crashing while handling a specific mode

ly or Hybrid frames for 40 or 60ms packet, respectively. That is based on = concatenating 20ms frames, right? Is 60ms the largest packet opus_encode() can generate? In order to get pac= kets of up to 120 ms by combining multiple frames as described in RFC6716 c= lause 2.1.4 one would need to use the "repacketizer". That is if I want to= have a 120 ms packet, I would need to take