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.
Topic: aoTuV pre-beta 5 released! (Read 113849 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

aoTuV pre-beta 5 released!

Reply #125
Aoyumi, I read a rather new posting somewhere, people are shying from your tunings because they see it as "beta" so in their mind it's "unstable/test version" or something. The poster recommended you drop the "beta" word.

I just report it to you; if others can show the posting I'd be glad. I can't seem to find it again...

Before, I considered stopping the beta notation. However, since this kind of software always needs to be tested, I am continuing the beta notation in the symbolic meaning. 

aoTuV pre-beta 5 released!

Reply #126
*most* "open source" software keeps the 'beta' title forever. Wine has been out for over 10 years, and they *just* adopted the beta title. MPlayer is still 'prerelease', even though they are in their 8th prerelease and are always adding new features. I believe a different methodology needs to be adopted as a whole for all open source software, but that's not aoyumi's responsibility. I'd look at AoTuV as release 4.51, not beta 4.51.. It's confusing to some people, but for something like aoyumi's tunings, being done as a hobby, I'd never feel comfortable giving it a 'version' number mysql (edit: why did I put mysql? I meant MYSELF). Although I do think you should adopt a 'release' number instead. You could call the next release 'release 5' instead of 'beta 5', it wont shy people away, the number stays, and you can wiggle around calling it 'stable'.. Releasing it under 'version' scheme would say 'its stable' to most people, but I think calling it a 'release' would leave room for people to make up their own minds about how stable it is, which is an ideal middle ground for what you're doing.

My 2 cents
q4 AoTuV Vorbis is my friend.

aoTuV pre-beta 5 released!

Reply #127
I get the impression that most who are not familiar with the open source community shy away from beta as something other people test and they start using when beta becomes release or final. Perhaps a useful middle way are other terms like "release candidate" as that suggests there are no bugs in it in the sense of broken features and it just needs testing. In the strict sense of the word everything that is publically available is "released".

I don't like the -stable title as that suggests it's otherwise unstable, probably shying more people away from it...

I'm not a programmer, let alone one of aoyumi's caliber, but i would assume those who really test aotuv and give meaningful feedback will do so regardless of the presence beta tag.

Another idea would be to include the beta status only as a b in the version number, ie: "aotuv release b4.51"
Veni Vidi Vorbis.

aoTuV pre-beta 5 released!

Reply #128
or you can just manipulate your mind a bit and use those voices in your head to call it: 'stable enough for me, there was no beta included release' or something....
PANIC: CPU 1: Cache Error (unrecoverable - dcache data) Eframe = 0x90000000208cf3b8
NOTICE - cpu 0 didn't dump TLB, may be hung

aoTuV pre-beta 5 released!

Reply #129
The Linux versioning system is quite good actually.

aoTuV pre-beta 5 released!

Reply #130
I considered the version and performed it as follows. 

aoTuV page



aoTuV pre-beta 5 released!

Reply #133
I considered the version and performed it as follows. 

aoTuV page

Correct me if I'm wrong, but the only thing that's changed here is the designation isn't it? ie., the vendor string in info.c. There are no other code changes that I can see, are there?

aoTuV pre-beta 5 released!

Reply #134
A new version is due to become a "beta" again. If it is fully tested by people and it is satisfactory, it will become a next release version. 


I considered the version and performed it as follows. 

aoTuV page

Correct me if I'm wrong, but the only thing that's changed here is the designation isn't it? ie., the vendor string in info.c. There are no other code changes that I can see, are there?

A difference is not in output. 
(based on libvorbis 1.1.2 )

aoTuV pre-beta 5 released!

Reply #135
I think that more people that might have been "on the fence" with using AoTuV when it was in beta will be much more likely to use this "release" version (even if the internal workings between beta 4.51 and the release are almost negligible).

Good job, and keep up the wonderful work, Aoyumi. 

aoTuV pre-beta 5 released!

Reply #136
I'll wait for John33's OggDropXPd and oggenc before I update the wiki page


aoTuV pre-beta 5 released!

Reply #138
I considered the version and performed it as follows. 

aoTuV page


Some minor suggestions:
1) in the file aoTuV_technical.txt there is the changelog for aoTuV beta4.5, for aoTuV beta4a (this should be the same release of beta4.5) and this last one has the same changelog of the next version, that should be beta4 (apart from "and noise compander parameters"). - I think that the paragraph of beta4a should be removed.
2) in the file aoTuV_technical.txt in the aoTuV beta4.5 paragraph, before 2. and 3. there are two strange characters (should be replaced with spaces);
3) the filename should be libvorbis-aotuv_r1.tar.gz , without the extra tgz .
4) some file (configure , autogen.sh , ...) are missing the executable "x" flag on unix.
5) would be nice to provide a patch against libvorbis-1.1.2 (useful for unix users and distributions, I can provide that if you want).

Anyway, thanks for the release 




aoTuV pre-beta 5 released!

Reply #142
but there are not Win32 reference binary ?

aoTuV pre-beta 5 released!

Reply #143
r1 has a high compression ratio: all files are 1 byte smaller than beta 4.51 : the string of r1 is on byte smaller:
Code: [Select]
AO; aoTuV r1 [20051117] (based on Xiph.Org's libVorbis)
AO; aoTuV b4b [20051117] (based on Xiph.Org's libVorbis)

aoTuV pre-beta 5 released!

Reply #144
Some minor suggestions:
1) in the file aoTuV_technical.txt there is the changelog for aoTuV beta4.5, for aoTuV beta4a (this should be the same release of beta4.5) and this last one has the same changelog of the next version, that should be beta4 (apart from "and noise compander parameters"). - I think that the paragraph of beta4a should be removed.
2) in the file aoTuV_technical.txt in the aoTuV beta4.5 paragraph, before 2. and 3. there are two strange characters (should be replaced with spaces);
3) the filename should be libvorbis-aotuv_r1.tar.gz , without the extra tgz .
4) some file (configure , autogen.sh , ...) are missing the executable "x" flag on unix.
5) would be nice to provide a patch against libvorbis-1.1.2 (useful for unix users and distributions, I can provide that if you want).

A1. A2.
I checked the above-mentioned problem. I will correct it. Thank you.

A4.
Those files are the same as libvorbis 1.1.2.  And I do not understand them...

A5.
I will prepare patch, after correcting the above-mentioned problem.



<<I updated the aoTuV page according to the above. >>

aoTuV pre-beta 5 released!

Reply #145
The Lancer/Blacksword notes don't suggest that a 2006 version of aoTuV is built into their August 24, 2006 build.
John33's P4 build in Rarewares ran mighty fast and well on this x64 AMD 3300+.
I converted Pimsleur Japanese learning audio CDs for playback on my Cowon JetAudio.  Though I'm trying to learn Japanese without romaji, jumpimg immediately to kana and kanji,  I do want to say to Aoyumisan:
Domo arigato gozaimasu!

aoTuV pre-beta 5 released!

Reply #146
The Lancer/Blacksword notes don't suggest that a 2006 version of aoTuV is built into their August 24, 2006 build.


Every single .ogg has the vendor tag that reveal the encoder.

Code: [Select]
tool = BS; Lancer(SSE2) [20060824] (based on aoTuV r1 [20051117])


And you can find detailed change log on this page.

aoTuV pre-beta 5 released!

Reply #147
^
haregoo:
I don't understand the references to both 20060824 and 20051117.
Is the fact that November 2005 is still cited because the newest codec tweaks only affect encoding at quality ratings under 1.0?

aoTuV pre-beta 5 released!

Reply #148
I don't understand the references to both 20060824 and 20051117.
Is the fact that November 2005 is still cited because the newest codec tweaks only affect encoding at quality ratings under 1.0?

aoTuV Release 1 is equal to aoTuV b4.51(20051117) quality-wise, and Lancer 20060824 is based on aoTuV Release 1(r1). In terms of quality, there are NO difference in these encoders.

Did I make myself clear?

aoTuV pre-beta 5 released!

Reply #149
aoTuV Release 1 is equal to aoTuV b4.51(20051117) quality-wise, and Lancer 20060824 is based on aoTuV Release 1(r1). In terms of quality, there are NO difference in these encoders.

Did I make myself clear?


Just to make sure to all that there are no difference in code between beta 4.51 and Release 1: this is the difference between libvorbis-1.1.2 patched with beta 4.51 and Release 1:
Code: [Select]
diff -purN libvorbis-1.1.2/COPYING aotuv-r1_20051117/COPYING
--- libvorbis-1.1.2/COPYING     2006-08-24 14:47:35.000000000 +0200
+++ aotuv-r1_20051117/COPYING   2006-08-23 14:56:14.000000000 +0200
@@ -1,4 +1,4 @@
-aoTuV - Copyright (c) 2003-2005 Aoyumi
+aoTuV - Copyright (c) 2003-2006 Aoyumi
libvorbis - Copyright (c) 2002-2005 Xiph.org Foundation

Redistribution and use in source and binary forms, with or without
diff -purN libvorbis-1.1.2/aoTuV_README-1st.txt aotuv-r1_20051117/aoTuV_README-1st.txt
--- libvorbis-1.1.2/aoTuV_README-1st.txt        2006-08-24 14:47:35.000000000 +0200
+++ aotuv-r1_20051117/aoTuV_README-1st.txt      2006-08-23 15:02:14.000000000 +0200
@@ -1,4 +1,4 @@
-aoTuV beta4.51 release note
+aoTuV Release 1

"aoTuV" tunes up Xiph.Org's libvorbis uniquely.
A license is taken as "BSD-style license" as well as original libvorbis.
@@ -9,16 +9,15 @@ A license is taken as "BSD-style license
   Manuke's patch is used for improvement in the speed of sort processing.
   When "#define OPT_SORT" of "lib/psy.h" is deleted, the conventional
   processing method is used.
+  Thanks! Manuke.

-
-Thanks! Manuke.
-
+  This version is the same contents as aoTuV beta4.51.


aoTuV based on <Xiph.Org libvorbis>

Copyright (c) 2002-2005 Xiph.Org Foundation
-Copyright (c) 2003-2005 Aoyumi
+Copyright (c) 2003-2006 Aoyumi


-AUTHOR : aoyumi <aoyumi at inter7.jp>
\ No newline at end of file
+AUTHOR : aoyumi <aoyumi at gmail.com>
diff -purN libvorbis-1.1.2/lib/info.c aotuv-r1_20051117/lib/info.c
--- libvorbis-1.1.2/lib/info.c  2006-08-24 14:47:35.000000000 +0200
+++ aotuv-r1_20051117/lib/info.c        2006-08-23 12:40:08.000000000 +0200
@@ -416,7 +416,7 @@ static int _vorbis_pack_info(oggpack_buf
}

static int _vorbis_pack_comment(oggpack_buffer *opb,vorbis_comment *vc){
-  char temp[]="AO; aoTuV b4b [20051117] (based on Xiph.Org's libVorbis)";
+  char temp[]="AO; aoTuV r1 [20051117] (based on Xiph.Org's libVorbis)";
   int bytes = strlen(temp);

   /* preamble */
diff -purN libvorbis-1.1.2/lib/psy.c aotuv-r1_20051117/lib/psy.c
--- libvorbis-1.1.2/lib/psy.c   2006-08-24 14:47:35.000000000 +0200
+++ aotuv-r1_20051117/lib/psy.c 2006-08-23 14:25:56.000000000 +0200
@@ -1066,7 +1066,6 @@ void _vp_offset_and_mix(vorbis_look_psy
     if(m4_val > 0){
        if(fmask && (m4_start<i)){
                mdct[i] *= m4_val;
-               //logmdct[i]=todB(mdct+i)  + .345; // + .345 is a hack
        }
     }