IPB

Welcome Guest ( Log In | Register )

6 Pages V  « < 3 4 5 6 >  
Reply to this topicStart new topic
Opus 1.1-beta, Officially released
jmvalin
post Nov 27 2013, 06:46
Post #101


Xiph.org Speex developer


Group: Developer
Posts: 479
Joined: 21-August 02
Member No.: 3134



QUOTE (LithosZA @ Nov 27 2013, 00:43) *
Yes, I am still having the same issue.
Is there somebody here who can build opus-tools with GCC instead? smile.gif


Actually, I would still like to investigate what's going on with that build. I have been able to compare your Opus file with one on my machine and they diverge only after 10 frames, then converge again when the encoder switches to CELT. So I'd like to make sure that it's not a bug in Opus that only affects some compilers. That's why I'd need more information on the compiler, compile options, ...
Go to the top of the page
+Quote Post
Anakunda
post Nov 27 2013, 09:33
Post #102





Group: Members
Posts: 458
Joined: 24-November 08
Member No.: 63072



QUOTE (jmvalin @ Nov 27 2013, 02:50) *
If so, Anakunda can you give more info on your build.


I don't know about anything except extended floating point precision. Now I'm to make a build with standard floating point and only minimum optimizations (those -O... and no Intel advanced optimizations like elevated architecture features or interprocedural things).
If this produces the same issues then I can't do anything more with that (or is a bug of codec self)
Attached File(s)
Attached File  opus-1.1rc-noopt.rar ( 2.79MB ) Number of downloads: 67
 
Go to the top of the page
+Quote Post
o-l-a-v
post Nov 27 2013, 11:02
Post #103





Group: Members
Posts: 127
Joined: 18-July 12
From: Norway
Member No.: 101545



QUOTE (Anakunda @ Nov 27 2013, 10:33) *
QUOTE (jmvalin @ Nov 27 2013, 02:50) *
If so, Anakunda can you give more info on your build.


I don't know about anything except extended floating point precision. Now I'm to make a build with standard floating point and only minimum optimizations (those -O... and no Intel advanced optimizations like elevated architecture features or interprocedural things).
If this produces the same issues then I can't do anything more with that (or is a bug of codec self)


My god. The quality at just 100kbps is amazing.
I've found no bugs yet.
Go to the top of the page
+Quote Post
Ajaja
post Nov 27 2013, 11:37
Post #104





Group: Members
Posts: 4
Joined: 27-November 13
Member No.: 112638



QUOTE (LithosZA @ Nov 27 2013, 07:43) *
Is there somebody here who can build opus-tools with GCC instead? smile.gif


Attached File(s)
Attached File  opus_1.1-rc.gcc.rar ( 310.81K ) Number of downloads: 66
 
Go to the top of the page
+Quote Post
LithosZA
post Nov 27 2013, 12:02
Post #105





Group: Members
Posts: 195
Joined: 26-February 11
Member No.: 88525



I am at work now and tested both Anakunda's and Ajaja's builds. Both seem to work except Anakunda couldn't accept FLAC input.
I will test again when I get home on the laptop that gave problems.

It still will be useful to know what compiler options + the exact compiler that was used that caused the issue. Just to determine if something can be changed in the code to be more friendly with that compiler.
Go to the top of the page
+Quote Post
Case
post Nov 27 2013, 16:04
Post #106





Group: Developer (Donating)
Posts: 2214
Joined: 19-October 01
From: Finland
Member No.: 322



GCC 4.82 compile: Attached File  opus-1.1-rc-gcc482.zip ( 367.41K ) Number of downloads: 67

MSVC 2013 compile: Attached File  opus-1.1-rc-msvc2013.zip ( 565.34K ) Number of downloads: 128

MSVC version seems quite a bit faster here. It requires SSE2 support from the processor.
Go to the top of the page
+Quote Post
LithosZA
post Nov 27 2013, 17:29
Post #107





Group: Members
Posts: 195
Joined: 26-February 11
Member No.: 88525



Ok, I have tested the new builds from Anakunda, Ajaja and Case and they all seem to work correctly.
EDIT: Ajaja and Case's builds support FLAC input. Had to use WAV input for Anakunda's build.

This post has been edited by LithosZA: Nov 27 2013, 17:39
Go to the top of the page
+Quote Post
eahm
post Nov 27 2013, 17:58
Post #108





Group: Members
Posts: 1062
Joined: 11-February 12
Member No.: 97076



Thank you Case. Testing ASAP.

This post has been edited by eahm: Nov 27 2013, 17:58


--------------------
/lwAsIimz
Go to the top of the page
+Quote Post
jmvalin
post Nov 27 2013, 20:35
Post #109


Xiph.org Speex developer


Group: Developer
Posts: 479
Joined: 21-August 02
Member No.: 3134



QUOTE (Anakunda @ Nov 27 2013, 03:33) *
I don't know about anything except extended floating point precision. Now I'm to make a build with standard floating point and only minimum optimizations (those -O... and no Intel advanced optimizations like elevated architecture features or interprocedural things).
If this produces the same issues then I can't do anything more with that (or is a bug of codec self)


Any way you can isolate which option was causing the problem using LithosZA's test? Also, could you try reproducing the original bad build and removing the following lines in celt/pitch.h:

#if defined(__SSE__) && !defined(FIXED_POINT)
#include "x86/pitch_sse.h"
#endif

That would help verifying that there's no issue with the SSE optimizations.
Go to the top of the page
+Quote Post
Anakunda
post Nov 28 2013, 00:12
Post #110





Group: Members
Posts: 458
Joined: 24-November 08
Member No.: 63072



QUOTE (jmvalin @ Nov 27 2013, 20:35) *
Any way you can isolate which option was causing the problem using LithosZA's test?

I'd like to isolate it, can LithosZA give me some information how to reproduce the bug? and possibly upload the sample somewhere...
Go to the top of the page
+Quote Post
jmvalin
post Nov 28 2013, 00:35
Post #111


Xiph.org Speex developer


Group: Developer
Posts: 479
Joined: 21-August 02
Member No.: 3134



QUOTE (Anakunda @ Nov 27 2013, 18:12) *
QUOTE (jmvalin @ Nov 27 2013, 20:35) *
Any way you can isolate which option was causing the problem using LithosZA's test?

I'd like to isolate it, can LithosZA give me some information how to reproduce the bug? and possibly upload the sample somewhere...


So you can get the sample here. Then, run the command line:
opusenc --save-range range.txt --bitrate 24 smallProblem.flac output.opus

You can then compare the range.txt output. This is the broken range that LithosZA was generating, and here's the working range that I get on my machine. You can see that the two differ between lines 10 and 38.
Go to the top of the page
+Quote Post
lithoc
post Nov 28 2013, 09:42
Post #112





Group: Members
Posts: 49
Joined: 9-January 02
Member No.: 963



hold your horses .... rc2 just released

This post has been edited by lithoc: Nov 28 2013, 09:42
Go to the top of the page
+Quote Post
zerowalker
post Nov 28 2013, 10:38
Post #113





Group: Members
Posts: 266
Joined: 6-August 11
Member No.: 92828



Are there any tests on how Opus competes against other codecs in overall with newer releases?

I doubt as it will probably wait till 1.1 is completed, but it seems to be fairly more active now which makes things interesting:)
Go to the top of the page
+Quote Post
jmvalin
post Nov 28 2013, 12:11
Post #114


Xiph.org Speex developer


Group: Developer
Posts: 479
Joined: 21-August 02
Member No.: 3134



QUOTE (lithoc @ Nov 28 2013, 03:42) *
hold your horses .... rc2 just released


rc2 is fixing issues with ARM assembly. For x86, there's absolutely no change compared to rc1.
Go to the top of the page
+Quote Post
darkbyte
post Nov 28 2013, 17:24
Post #115





Group: Members
Posts: 151
Joined: 14-June 11
Member No.: 91517



I wonder if this release fixes the IS stereo to mono downmix problem where channels cancels each other? Or this is entirely depends on the decoder being used?


--------------------
Wavpack -b450x1c
Go to the top of the page
+Quote Post
Anakunda
post Nov 29 2013, 01:14
Post #116





Group: Members
Posts: 458
Joined: 24-November 08
Member No.: 63072



Here's rc2 build, hopefully the issues are gone

cool.gif
Attached File(s)
Attached File  opus-1.1rc2.rar ( 5.8MB ) Number of downloads: 93
 
Go to the top of the page
+Quote Post
jmvalin
post Nov 29 2013, 01:44
Post #117


Xiph.org Speex developer


Group: Developer
Posts: 479
Joined: 21-August 02
Member No.: 3134



QUOTE (Anakunda @ Nov 28 2013, 19:14) *
Here's rc2 build, hopefully the issues are gone


I don't have a Windows machine to test, but that would be surprising since the only thing that changed in rc2 compared to rc1 is ARM assembly.
Go to the top of the page
+Quote Post
the_weirdo
post Nov 29 2013, 07:45
Post #118





Group: Members
Posts: 4
Joined: 8-September 10
From: Southeast Asia
Member No.: 83705



I tested those builds by Case, Ajaja and Anakunda with command line posted by jmvalin here, and they all produce different results (and they are different from "working range").

I also tested with my build and it produces same results as "working range". I've attached my build in case someone want to try it out.
Attached File  Opus-1.1-rc2.7z ( 477.45K ) Number of downloads: 105


This post has been edited by the_weirdo: Nov 29 2013, 07:52
Go to the top of the page
+Quote Post
Brazil2
post Nov 29 2013, 11:08
Post #119





Group: Members
Posts: 149
Joined: 9-May 10
Member No.: 80499



QUOTE (the_weirdo @ Nov 29 2013, 07:45) *
I tested those builds by Case, Ajaja and Anakunda with command line posted by jmvalin here, and they all produce different results

A quick test encoding the same WAV 453 MB file on two 'old' Core2Duo has shown that not only Case's GCC build is always slower than Ajaja's GCC build but it also writes 1 byte more:

Ajaja's:
CODE
       Encoded: 44 minutes and 53.6 seconds
       Runtime: 1 minute and 43 seconds
                (26.15x realtime)
         Wrote: 43510600 bytes, 134680 packets, 2696 pages


Case's:
CODE
       Encoded: 44 minutes and 53.6 seconds
       Runtime: 1 minute and 47 seconds
                (25.17x realtime)
         Wrote: 43510601 bytes, 134680 packets, 2696 pages
Go to the top of the page
+Quote Post
eahm
post Dec 2 2013, 06:59
Post #120





Group: Members
Posts: 1062
Joined: 11-February 12
Member No.: 97076



Thanks the_weirdo, using yours.

This post has been edited by eahm: Dec 2 2013, 07:00


--------------------
/lwAsIimz
Go to the top of the page
+Quote Post
Anakunda
post Dec 3 2013, 23:21
Post #121





Group: Members
Posts: 458
Joined: 24-November 08
Member No.: 63072



Last RC is released, some bugfixes here:

QUOTE
3 December, 2013

This is the third and likely last release candidate for 1.1. It fixes several bugs in the fixed-point build. Floating point is unaffected.



Attached File(s)
Attached File  opus-1.1rc3.rar ( 5.8MB ) Number of downloads: 71
 
Go to the top of the page
+Quote Post
eahm
post Dec 3 2013, 23:44
Post #122





Group: Members
Posts: 1062
Joined: 11-February 12
Member No.: 97076



Thanks Anakunda, could you also create a build with just opusenc.exe or explain to me please why your way is better?

This post has been edited by eahm: Dec 3 2013, 23:44


--------------------
/lwAsIimz
Go to the top of the page
+Quote Post
Anakunda
post Dec 3 2013, 23:56
Post #123





Group: Members
Posts: 458
Joined: 24-November 08
Member No.: 63072



Oh yes, I can, but dont be worried it's up to pair to single file, so it's no better nor worse. I'm just tried to convert same song using the same encoder on two PCs with two different processors and the result is not same which proves that for different CPUs different level of optimizations is used which affects the resulting audio data in some way. I can't say if these changes affect the quality also or even produce hearable artifacts.

This post has been edited by Anakunda: Dec 3 2013, 23:58
Go to the top of the page
+Quote Post
eahm
post Dec 4 2013, 00:10
Post #124





Group: Members
Posts: 1062
Joined: 11-February 12
Member No.: 97076



Also ~5 MB (your x86 or x64 pack) vs ~450 kB (standard single build).

This post has been edited by eahm: Dec 4 2013, 00:13


--------------------
/lwAsIimz
Go to the top of the page
+Quote Post
jmvalin
post Dec 4 2013, 04:24
Post #125


Xiph.org Speex developer


Group: Developer
Posts: 479
Joined: 21-August 02
Member No.: 3134



QUOTE (Anakunda @ Dec 3 2013, 17:56) *
Oh yes, I can, but dont be worried it's up to pair to single file, so it's no better nor worse. I'm just tried to convert same song using the same encoder on two PCs with two different processors and the result is not same which proves that for different CPUs different level of optimizations is used which affects the resulting audio data in some way. I can't say if these changes affect the quality also or even produce hearable artifacts.


Be careful what you compare. The file has a stream ID which is chosen randomly by the encoder. So it's normal for Opus files to not be identical. You'd have to either compare the decoded output or look at the output of --save-range.
Go to the top of the page
+Quote Post

6 Pages V  « < 3 4 5 6 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 29th August 2014 - 22:10