On Sun, 22 Feb 2009 15:30:31 -0800, Tom wrote:
I found a "workaround" for the tags (using your suggestion
of 'taglib')...
The following sequence seems to "fix" the tags produced by audacity,
making them "understood" by id3info/id3v2/rhythmbox:
taginfo FileFromAudacity >/tmp/tag
source /tmp/tag
id3v2 -a "$ARTIST" -t "$TITLE" -g "$GENRE"
"$FILE"
[Of course, some quoting of the tag info is needed if there are
quotes/etc. in the text. And more tags could be used....]
Some code changes would probably "fix" this, but do you think this is
an issue with audacity (or the libraries it calls) or "the rest of the
world"? Would like to BZ this to keep track of it. Any thoughts
where?
The Audacity project has a bug tracking system, but they prefer
problem reports via mail:
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Although rewriting the tags with a different library (libid3 vs. taglib)
may work for you, it remains to be seen whether the resulting files are
more compatible with "the rest of the world" as tested by the Audacity
developers.