IPB

Welcome Guest ( Log In | Register )

Opus 1.1a BABYEATER build
NullC
post Feb 11 2013, 21:51
Post #1





Group: Developer
Posts: 200
Joined: 8-July 03
Member No.: 7653



Ever mindful of the world's population problems, the Opus development team is excited to present a new highly experimental build of Opus which is expected to eat 100% more babies than prior editions. It is also expected have (potentially) improved transient handling performance:

https://people.xiph.org/~greg/opus-tools_ba...ater-deluxe.zip (Edit: replaced with updated version, see below)

What this does is adapts the frame-size dynamically based on transient analysis prior to encoding. Leave the opus-tools framesize knob alone (in this test build it controls the amount of look-ahead used for the analysis, and 60ms is the default and only tested value).

It would be super-helpful to compare this with the regular 1.1 alpha at various rates and point us to any interesting results you find (e.g. where it does obviously worse or better, or where it catches fire and/or eats household pets instead of babies). Obviously you shouldn't be encoding your music archives with this stuff yet.

This post has been edited by NullC: Feb 13 2013, 01:07
Go to the top of the page
+Quote Post
 
Start new topic
Replies
jensend
post Apr 8 2013, 17:16
Post #2





Group: Members
Posts: 149
Joined: 21-May 05
Member No.: 22191



I can't reproduce your problem on mainline builds. Haven't tried with the babyeater build.

jmvalin has asked that people now use mainstream pre-1.1 builds and not the babyeater build. The Babyeater builds were an experiment in variable frame sizes; jmvalin and NullC needed some feedback on their experiment, people responded, some major issues were found, and there's a good bit of work to be done before they ask people to test that again. In the meantime there are plenty of other innovations etc in the master builds that need more testing.

This again highlights the need for very visible instructions and warnings for prospective testers and an up-to-date link to builds (and possibly source snapshots/git revision numbers) the Opus devs would prefer people use for testing. I've proposed before that this be done with a sticky in the Opus subforum- indeed that's one of the main reasons I pushed for having a dedicated Opus subforum. When those instructions and warnings aren't very visible, we all have to keep correcting misconceptions. When people who want to help test don't know which builds to test, they may be wasting their time, and responding to their reports may waste developers' time. Simple steps to improve communication can go a long way to help.
Go to the top of the page
+Quote Post
jmvalin
post Apr 8 2013, 18:20
Post #3


Xiph.org Speex developer


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



QUOTE (jensend @ Apr 8 2013, 12:16) *
jmvalin has asked that people now use mainstream pre-1.1 builds and not the babyeater build. The Babyeater builds were an experiment in variable frame sizes; jmvalin and NullC needed some feedback on their experiment, people responded, some major issues were found, and there's a good bit of work to be done before they ask people to test that again. In the meantime there are plenty of other innovations etc in the master builds that need more testing.


Actually, I recommended that people stop testing babyeater, but testing of 1.1-alpha and git is still very appreciated. The more testing we get, the quicker we can get to a final 1.1 release. We're interested in cases where 1.1 performs poorly, but what's even more useful is when 1.1 performs worse than 1.0.x, i.e. regressions.
Go to the top of the page
+Quote Post
jensend
post Apr 8 2013, 22:41
Post #4





Group: Members
Posts: 149
Joined: 21-May 05
Member No.: 22191



QUOTE (jmvalin @ Apr 8 2013, 11:20) *
Actually, I recommended that people stop testing babyeater, but testing of 1.1-alpha and git is still very appreciated.
I'm confused. By starting with 'Actually,' you give the impression that I said something false which you're correcting, but you apparently go on to repeat what I just said. Maybe by "pre-1.1" you thought I meant "1.0.x"? I meant "development versions leading up to 1.1," as could be seen from my mention of the innovations in git master.

QUOTE (Gainless @ Apr 8 2013, 11:39) *
Regularly updated builds would indeed be great, though.
Sure, it would, but that's not quite what I was asking for, and perhaps I didn't do well at making that clear.

Regardless of how frequent/up-to-date the builds are, the link needs to be up-to-date. In other words, whether they set up a Jenkins windows build artifact and prefer that testers use those bleeding edge builds or whether they only sporadically provide "blessed" builds for testers every few months, they need to communicate clearly about which builds prospective testers should use.

Right now, the most up-to-date advice on which build to test is quite frequently buried in some thread somewhere or stated in the (ephemeral, no public logs) IRC channel. In other words, it's effectively invisible to most people. This puts prospective testers, especially those on platforms like Windows where setting up a build environment takes knowledge and effort, at a real disadvantage. It is an unnecessary barrier, and it causes confusion, frustration, and useless bug reports.
Go to the top of the page
+Quote Post
jmvalin
post Apr 9 2013, 03:21
Post #5


Xiph.org Speex developer


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



QUOTE (jensend @ Apr 8 2013, 17:41) *
QUOTE (jmvalin @ Apr 8 2013, 11:20) *
Actually, I recommended that people stop testing babyeater, but testing of 1.1-alpha and git is still very appreciated.
I'm confused. By starting with 'Actually,' you give the impression that I said something false which you're correcting, but you apparently go on to repeat what I just said. Maybe by "pre-1.1" you thought I meant "1.0.x"? I meant "development versions leading up to 1.1," as could be seen from my mention of the innovations in git master.


Yeah, I thought you meant 1.0.x. Sorry for the confusion.
Go to the top of the page
+Quote Post

Posts in this topic
- NullC   Opus 1.1a BABYEATER build   Feb 11 2013, 21:51
- - C.R.Helmrich   QUOTE (NullC @ Feb 11 2013, 21:51) What t...   Feb 11 2013, 22:57
|- - jmvalin   QUOTE (C.R.Helmrich @ Feb 11 2013, 16:57)...   Feb 11 2013, 23:24
|- - NullC   QUOTE (jmvalin @ Feb 11 2013, 14:24) (unl...   Feb 12 2013, 00:46
- - IgorC   eig sample has the issue. _http://depositfiles.or...   Feb 12 2013, 09:45
- - Gainless   At 192 kbps it does slightly better at this sample...   Feb 12 2013, 12:52
|- - NullC   QUOTE (Gainless @ Feb 12 2013, 03:52) The...   Feb 13 2013, 01:16
|- - Gainless   QUOTE (jmvalin @ Feb 12 2013, 23:23) OK, ...   Feb 13 2013, 21:54
|- - jmvalin   QUOTE (Gainless @ Feb 13 2013, 15:54) 192...   Feb 13 2013, 22:17
|- - Gainless   QUOTE (jmvalin @ Feb 13 2013, 22:17) QUOT...   Feb 14 2013, 13:35
|- - jmvalin   QUOTE (Gainless @ Feb 14 2013, 07:35) Sur...   Feb 14 2013, 20:00
|- - Gainless   QUOTE (jmvalin @ Feb 14 2013, 20:00) That...   Feb 15 2013, 20:42
|- - jmvalin   QUOTE (Gainless @ Feb 15 2013, 14:42) It...   Feb 16 2013, 04:58
|- - Gainless   QUOTE (jmvalin @ Feb 16 2013, 04:58) QUOT...   Feb 16 2013, 11:56
|- - jmvalin   QUOTE (Gainless @ Feb 16 2013, 05:56) QUO...   Feb 16 2013, 19:42
- - jmvalin   OK, I was able to identify at least one bug. See i...   Feb 12 2013, 23:23
- - IgorC   It's getting better http://pastebin.com/KGLCy...   Feb 12 2013, 23:51
- - Gainless   That's nice to hear, would be great if it coul...   Feb 16 2013, 20:40
|- - jmvalin   QUOTE (Gainless @ Feb 16 2013, 14:40) Tha...   Feb 18 2013, 06:43
- - Gainless   Sound both pretty transparent, thanks for the effo...   Feb 18 2013, 22:12
|- - jmvalin   QUOTE (Gainless @ Feb 18 2013, 16:12) Sou...   Feb 18 2013, 23:53
- - Omicron   Hello! I have some files: original wav 16khz u...   Feb 21 2013, 13:01
- - RobertM   QUOTE (Omicron @ Feb 21 2013, 22:01) Hell...   Feb 25 2013, 11:21
- - RobertM   I'm not a listening expert. However, I was int...   Feb 25 2013, 12:13
|- - RobertM   The samples encoded with the latest Opus version a...   Feb 26 2013, 06:55
- - Omicron   QUOTE what kind of problems did you hear? It soun...   Feb 26 2013, 23:10
- - RobertM   I think I've noticed a minor issue in the enco...   Feb 28 2013, 09:36
- - Gainless   Another sample making issues: DWK Sample A sweepin...   Apr 8 2013, 14:14
- - jensend   I can't reproduce your problem on mainline bui...   Apr 8 2013, 17:16
|- - jmvalin   QUOTE (jensend @ Apr 8 2013, 12:16) jmval...   Apr 8 2013, 18:20
||- - jensend   QUOTE (jmvalin @ Apr 8 2013, 11:20) Actua...   Apr 8 2013, 22:41
||- - jmvalin   QUOTE (jensend @ Apr 8 2013, 17:41) QUOTE...   Apr 9 2013, 03:21
|- - Gainless   QUOTE (jensend @ Apr 8 2013, 18:16) I can...   Apr 8 2013, 18:39
- - db1989   The above post has been moved from the associated ...   Apr 8 2013, 17:32
- - IgorC   The version 1.1a is the last testing build that wo...   Apr 8 2013, 19:05


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: 28th December 2014 - 12:01