Ogg Vorbis Release 9 Beta 1

[Spoon]

Made a few changes, so far they are:

Added 48Kbps
Improved ABR setup
CBR now returns correct bitrate in dAP
Writes Date tag instead of year

Download:

http://www.dbpoweramp.com/beta/dBpowerAMP-codec-Ogg.exe

427KB

[edgarde]

48Kbps setting encodes to 64Kbps :/

Items ripped at the "48Kbps" setting seem to be coming out 64, as evinced by file size (same as made at "64Kbps" setting) and "nominal bitrate" reading in Winamp.

I ripped a coupla CD's and converted a .WAV, each to a few different bitrates -- no crashes, and seemingly good files (playing random selections). However, late in the day I find I'm not getting "-1" quality.

Year is put under DATE as expected. I might suggest keeping the YEAR tag with duplicate info.

date & year tag trivia

A while ago I was gonna suggest "Year" in the DATE tag, but DATE (according to the Vorbis spec) and YEAR (not a Vorbis standard, but specfied in ID3 and freeDB) were supposedly different, like so:

DATE (Vorbis): any human-readable date of recording
YEAR (ID3 & freeDB): 4-digit number for year of release

... thus Rolling Stones Beggar's Banquet could have (only) 2 different YEAR's (either the original 1986 CD issue or the 2002 remaster) but just one DATE (which unfortunately could be written any way the user likes, and individual tracks might more correctly be dated to different sessions, so really many possible entries...).

Incidentally, FreeDB users often incorrectly submit recording (or, more likely, album original release) date as YEAR, even tho freeDB.org specifies "year ... in which the CD was released".

Musing on the vorbis-dev list came up with the following suggestions for DATE, all prior to v1.0, none made official:

* "a lot of people are already just putting in the year"
* RFC-822 : 1982-06-20
* ISO 8601 : 20 Jun 82 (very strongly advocated for)
* "... For the DATE header, we do suggest that you use the ISO format, or at least spell out the month (or the day of week) to remove ambiguity. But to demand standardized, machine parseable data misses the point; the spec clearly indicates the vorbis comment header is intended for simple human-readable data only."

Relevant threads:

http://www.xiph.org/archives/vorbis-dev/200010/0103.html

http://www.xiph.org/archives/vorbis-dev/200108/0169.html

I've been using RFC-style dates, which YEAR is compatible with, tho not always accurate. I doubt it breaks anything.

I bow to your Vorbis support.

Es.

[Amadablam]

The DATE/YEAR thing was bugging me too, and while I like the flexibility of the Vorbis commenting system, this is one area where it might have paid to be more specific. I found some interesting comments here:

http://reactor-core.org/ogg-tag-standard.html

I don't think there is anything official about this page, but their suggestion to always start the date field with the four digit year, regardless of any other included date information, is probably a good idea in light of the current specs. Since I'm really only worrying about the year anyway, I guess it's good enough for me.

And thanks to Spoon, it looks like I finally have a player that will read Vorbis dates properly!

[totalXSive]

According to ISO 8601, yyyy-mm-dd is the preferred, internationally-agreed format for dates, so it'd make sense to use it here.

[Rnergy]

Really....48Kbps setting encodes to 64Kbps

Spoon...48Kbps setting encodes to 64Kbps ! Small bug here...?

[Spoon]

Indeed it wasn't, atleast on VBR, here is Beta 2:

http://www.dbpoweramp.com/beta/dBpowerAMP-codec-Ogg.exe

[Spoon]

Beta closed, now released.