Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.

Poll

What do you think of aoTuV Beta 5?

Good enough to replace b4.51/R1 as the recommended version.
[ 47 ] (64.4%)
Still needs more peer-review.
[ 12 ] (16.4%)
I don't have an opinion.
[ 14 ] (19.2%)

Total Members Voted: 91

Topic: Recommended Vorbis - Update Now? (Read 8883 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Recommended Vorbis - Update Now?

Before voting, please read the following thread first:

http://www.hydrogenaudio.org/forums/index....showtopic=55371

Then, you can vote. Plus provide whatever reasoning you think below.

Note: The 2 questions of the poll are not really relevant to each other. Each question stands independently.

Additional Note: If you don't have any opinion for both questions above, please do not vote

Recommended Vorbis - Update Now?

Reply #1 –
Firstly, B5 should be "recommended".

Rather than recommending versions, why not use the developers recommended version? They will of done more testing and know the codec better than anyone else. So are in the best position to recommend what version to use.

Recommended Vorbis - Update Now?

Reply #2 –
Quote from: pepoluan on
Note: The 2 questions of the poll are not really relevant to each other. Each question stands independently.
If that's the case both questions should have a null vote option.  I can't really answer Q1, but I can have an opinion on Q2.

Quote from: madorangepanda on
Rather than recommending versions, why not use the developers recommended version? They will of done more testing and know the codec better than anyone else. So are in the best position to recommend what version to use.
Is this achievable with Vorbis?  Do Xiph recommend the aoTuV's builds?
I'm on a horse.

Recommended Vorbis - Update Now?

Reply #3 –
Monty has spoken:
http://lists.xiph.org/pipermail/vorbis/200...rch/025710.html
Quote
Make no mistake, AoTuV b3 is once again a solid, noticable improvement over the stock libvorbis.


http://www.hydrogenaudio.org/forums/index....st&p=491641
Quote
I've told anyone who's asked that AoTuV is the best of the Vorbis encoders out there that I know of. There is nothing dodgy or unofficial about it. I'm enjoying having a healthy third-party project advance the encoder.

Recommended Vorbis - Update Now?

Reply #4 –
Not exactly front-page news for noobs...
I'm on a horse.

Recommended Vorbis - Update Now?

Reply #5 –
As long as we have posters like guru and Synthetic Soul HA reccomendations should be kept.
WavPack 5.6.0 -b384hx6cmv / qaac64 2.79 -V 100

Recommended Vorbis - Update Now?

Reply #6 –
Testing is time consuming. Newbies should be pointed to current versions and not older versions like in most software. Likewise, Current users DON'T need to upgrade whenever a new version is out unless 'bleeding-edge' appeals to them.

So use latest versions for the clueless, do your own testing and decide for yourself for others. Exactly the same thing applies to lossless encoders minus sound quality issues. I think the rarewares vorbis page is perfect.
wavpack -b3.63hhcs.5

Recommended Vorbis - Update Now?

Reply #7 –
Quote from: Synthetic Soul on
Quote from: pepoluan on
Note: The 2 questions of the poll are not really relevant to each other. Each question stands independently.
If that's the case both questions should have a null vote option.  I can't really answer Q1, but I can have an opinion on Q2.
Yeah, I realized this approx. 10 seconds after posting ... 

Recommended Vorbis - Update Now?

Reply #8 –
Quote from: pepoluan on
Quote from: Synthetic Soul on
Quote from: pepoluan on
Note: The 2 questions of the poll are not really relevant to each other. Each question stands independently.
If that's the case both questions should have a null vote option.  I can't really answer Q1, but I can have an opinion on Q2.
Yeah, I realized this approx. 10 seconds after posting ... 
I was hoping for an explicit request, so I hope you don't mind, but I have now added null vote options.


Personally, given the confusion over Vorbis (i.e.: aoTuV and Lancer), and also some other codecs, I still think that there is a place for Hydrogen Audio recommendations.  New users often end up here when searching for information about codecs, and given the knowledge base that this board has, including the fact that many codec developers post here, I can't help thinking that if we don't, who will?  I agree that the recommended version will often be the latest, but on those occassions that it is not I think it is extremely important that new users are given some guidance.

It's an interesting poll.
I'm on a horse.

Recommended Vorbis - Update Now?

Reply #9 –
Quote from: Synthetic Soul on
Quote from: pepoluan on
Quote from: Synthetic Soul on
Quote from: pepoluan on
Note: The 2 questions of the poll are not really relevant to each other. Each question stands independently.
If that's the case both questions should have a null vote option.  I can't really answer Q1, but I can have an opinion on Q2.
Yeah, I realized this approx. 10 seconds after posting ... 
I was hoping for an explicit request, so I hope you don't mind, but I have now added null vote options.
Thanks! And sorry to those who have inadvertently voted with a no-null option.

Quote from: Synthetic Soul on
Personally, given the confusion over Vorbis (i.e.: aoTuV and Lancer), and also some other codecs, I still think that there is a place for Hydrogen Audio recommendations.  New users often end up here when searching for information about codecs, and given the knowledge base that this board has, including the fact that many codec developers post here, I can't help thinking that if we don't, who will?  I agree that the recommended version will often be the latest, but on those occassions that it is not I think it is extremely important that new users are given some guidance.
Ah, I suddenly have an idea: What if we recommend only the make of the encoder (e.g. aoTuV & Lancer), instead of the build of the encoder (e.g. R1, B5, etc.) ? For the build, maybe just put in a statement such as:

" You may safely use the latest version (v0.666) as peer-review has shown that the latest version is stable. "

Or something to that effect.

Recommended Vorbis - Update Now?

Reply #10 –
Voted.

Beta 5 is good enough IMO, I'm using it (lancer build) since it's out, and it rocks. Never had any problem with hundreds of tracks, and quality is excellent

For the HA recommended encoders, I can't make up my mind.

Edit : pepoluan, your idea is good

Recommended Vorbis - Update Now?

Reply #11 –
I have just voted.

I use Beta 5 and have not had any problems with it - judging by the general consensus I think it is suitable enough to become the next Recommended Encoder.

As for the relevance of the HA Recommended Encoders? - definitely keep. Just pointing to the "latest version" is not always the best option - the stability of new encoder version varies quite a lot, and may not be deemed suitable for "noobs" who just want a decent codec/audio file.

madorangepanda's idea about the Developer's Recommended Version is a reasonable idea - would give the user more freedom of choice. However, whether it is really necessary...  .

Recommended Vorbis - Update Now?

Reply #12 –
So, the current consensus heavily recommends b5 to dethrone R1 as the HA-recommended encoder.

As to whether we should keep this "recommendation", those who are 'for' outweighs those who are 'against' by a 50% margin.

So, the final verdict:
- The recommendation system stays.
- aoTuV beta 5 is now the HA-recommended encoder

Case closed. I will update the wiki shortly.

Edit: I have updated the 'history' section. Was about to edit the next section but realizes that RareWares has only 1 compile, and that is ICL compile... for what processor? Discussion continues in this thread.