similar to: Opus Major Version Benchmarks on Raspberry Pi

Hi All, What would be interesting would be a plot of complexity versus subjective or object audio quality. I've not had a chance to look at the new analysis code in 1.1 so maybe in the case of a 6kbps compression you could clarify what decisions would it be making that would justify the extra complexity? Best Regards Cliff Parris -----Original Message----- From: opus-request at

I have run a few more test at different bitrates and 1.1 is looking even worse in terms of speed compared to previous versions. I have shared a google sheet which has the raw data and charts for 6,16 and 32 kbps. Unfortunately you cannot show proper error bars on Google sheets but the standard deviation is in the data if you want to look. You can see that the profile for 1.1 is a lot different

Christian, I will give 64kbit/s a try and post the figures. My own project is voice only and requires low bitrate so was hoping that it was just the way I was compiling and not an actual regression in speed for SILK. The raspberry PI is quite a cheap and handy reference platform though the ARM side is fairly underpowered but has a great GPU. It also has no audio in which is a pain for playing

I have to admit that I am impressed by your results -- making 1.1 look slower than 1.0 is by no means an easy task. On the other hand, it's a great tutorial on how not to use Opus, so for the benefit of everyone, this is a summary of what we learned in this exercise: 1) When running on ARM, the fixed-point build is usually faster than floating point. This is true on the majority of ARM archs

It might be good to use the (uncompressed) samples on the opus page, as a common starting point? http://www.opus-codec.org/examples/ On Dec 21, 2013, at 9:43 AMEST, Stuart Marsden wrote: > I have run a few more test at different bitrates and 1.1 is looking even worse in terms of speed compared to previous versions. > > I have shared a google sheet which has the raw data and charts for

Cliff, Yes it would be good, but very hard to get a figure for the quality. At 6kbps I assume it does not bother trying to figure what mode to use as at that rate it can only use SILK. When I run some other bitrates it may get a bit slower trying to decide whether it is voice or music. I started with low bit rate because I am only really interested in Voice and very low bit rate. I think there

I have just started trying Opus with a view to using it in a project. I am interested in embedded hardware and tried it on the Raspberry Pi using the raspbian distro. The version of libopus in the repos is 0.9.14. I installed this and tried encoding 2 minutes of speech from a librevox recording. It managed this at a respectable pace for complexity 10: Skipping chunk of type "LIST",

Resampling to 48khz speeds them both up but the disparity is about the same: 2.609 to 3.69. Best Regards, Stuart Marsden On 17 December 2013 17:04, Stuart Marsden <stuartmarsden at finmars.co.uk>wrote: > Christian, > > Complexity 0, 6kbps: > > 0.9.14 Speed 5.204 > 1.1 Speed 5.218 > > A slight win on that run but they vary enough to say about the same. At >

On Mon, Dec 16, 2013 at 5:03 AM, Stuart Marsden <stuartmarsden at finmars.co.uk> wrote: > I have just started trying Opus with a view to using it in a project. I am > interested in embedded hardware and tried it on the Raspberry Pi using the > raspbian distro. > > The version of libopus in the repos is 0.9.14. I installed this and tried > encoding 2 minutes of speech from a

Hi Stuart, you are compressing it at 6kbit/s. Then, then SILK mode is probability used and the Silk mode is much faster than CELT. Do you also some figures at 64kbit/s? It is strange that Opus 1.1 got slower in the Silk mode - may the speech/voice selection adds some overhead. I would be interested in seeing the performance of the 64 kbit/s in both Opus 1.0 and Opus 1.1. With best

I thought I would run the same benchmarks on my PC that I have been running on my Pi. This is a very different beast as it is a i7-4770 with 4 cores (8 with hyperthreading) and 16GB RAM. This is a bit academic as any x86 PC in the last 10 years can encode very quickly and unless you are converting a huge catalogue you will not notice a small change in speed. That being said I wanted to see if

Hi Everyone, I have a question regarding the construction of 3D graphs in 'R', BUT these graphs also need to illustrate movement (with time) of the prostate gland (using radiological techniques). I am not sure how to do this in 'R' although I'm sure there is some way of doing it. Below, I have copied and pasted some of the data with which I'm working on. The data

Jean-Marc, I can try both of the things you suggested. Maybe this coming weekend. I installed the Raspbian libopus-dev package instead of building it myself and that's been working great. Do I use --disable-intrinsics on ./configure, or on make? On Thu, May 25, 2017 at 9:28 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Hi Samuel, > > Can you see if this commit fixes

Hello, I'm following the directions that 'make check' gave me: to e-mail you log files. I'm attempting to build opus on a raspberry pi zero w, which I think has more or less the original hardware as an original raspberry pi + WiFi. I'm running a clean install of the latest version of raspbian lite. Note that lite has no gui, but also has less packages in general, so it

Dear R-users, These days, I have been struggling to install the package sna on my Ubuntu 8.04 laptop. My R version is currently R 2.7.2. And I had no trouble installing any other packages (including network). However when I run 'install.packages("sna")', compilation of C codes is ok, but a syntax error is reported when building help pages and sna does not want to install. I

Raspberry Pi 1 and Zero use the arm1176jzf-s chip which AFAIK doesn't support NEON intrinsics. This may be a bug with the configure script because it appears to be compiling with NEON enabled. Lifeng can you comment? Is there a way to override the CPU detection in this case? Samuel, as a workaround you can download and compile an older version of the library. I think 1.1.2 predated the NEON

Targetting the raspberry pi, what triple/flags should I set? I tried triple: armv4t-unknown-linux-gnueabi and ld fails with: a.out uses VFP register arguments if i set hardfloat (using optdata.FloatABIType = FloatABI::Hard), ld fails with an assertion: 2.22 assertion fail ../../bfd/elf32-arm.c:11477 what am I missing?

It depends, of course, what operating system you have installed on the RPi, but given that it's an ARM1176JZFS (ARMv6) chip, I would expect to see armv6, not armv4t, in the CPU part of the triple. It has a VFP unit, so I'd assume that you'd want to set hardfp (unless you installed an OS that doesn't support hardfp in its standard library), but if ld is complaining then you almost

Hi. I'm an italian user. I have a nome ups, AROS Spring RT1500. I would like connect it by usb on my server raspberry pi. Someone knows a simple tutorial to send me? I did some test without success..... Thanks Flavio

On Sep 8, 2014, at 2:26 AM, Flavio.Boschiggia at infineon.com wrote: > Hi. > I'm an italian user. > I have a nome ups, AROS Spring RT1500. > I would like connect it by usb on my server raspberry pi. > Someone knows a simple tutorial to send me? I did some test without success..... > Thanks > Flavio We try to collect tutorial links here: