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: Winamp - OGG Plugin - Argh! (Read 7991 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Winamp - OGG Plugin - Argh!

I've been using Winamp 2.9 with the build in (?) ogg Plugin in order to Tag my files.
Now I've discovered that all of my ogg files seemed to be Vorbis release candidate 3, although I've been coding them with oggdrop to 1.0 or since mid of Oct to 1.0.1

First i didn't know if I did sth wrong but now I know what was the reason for it: Winamp edits also some technical data fields in the Vorbis header.

Now my 2 Questions: the sound quality is not affected by this AFAIK. Am I right?
Can I fix the incorrect data with a tagger (foobar?)?

THX

Winamp - OGG Plugin - Argh!

Reply #1 –
Quote
First i didn't know if I did sth wrong but now I know what was the reason for it: Winamp edits also some technical data fields in the Vorbis header.

Now my 2 Questions: the sound quality is not affected by this AFAIK. Am I right?
Can I fix the incorrect data with a tagger (foobar?)?

No, you didn't do anything wrong.

Yes, that's a known bug in one of the older winamp plugins. The newer versions do not have this bug.

You are correct, the sound quality is not affected.

No, you can't fix it with foobar. In fact, I don't know of any program that will change the vendor string for you.

Winamp - OGG Plugin - Argh!

Reply #2 –
Quote
Yes, that's a known bug in one of the older winamp plugins. The newer versions do not have this bug.

Which newer versions? I know the plugin coming with winamp 2.91 has the bug.
BTW is really only the libvorbis number changed or anything else along?

Winamp - OGG Plugin - Argh!

Reply #5 –
As far as I recall, Peter updated this plugin to a Vorbis Post-1.0 CVS state. Another tagging/seeking issue was also fixed.

Winamp - OGG Plugin - Argh!

Reply #6 –
And isn't there any possibility to fix the header?AFAIK all fields (also the 'tech info') could be edited with a tool like tag!? I don't know how to use it and if it either possible.

Winamp - OGG Plugin - Argh!

Reply #7 –
I would also be interested by such a tool as I would use it to correct
Xiphophorus libVorbis I 20011217 = V1.0 RC3 Win32 Platform ==> Bad RC3 Vendor String
to
Xiphophorus libVorbis I 20011231 = V1.0 RC3 Not-Win32 Platforms ==> Good RC3 Vendor String
I use VorbisExt so I see this bad Vendor String directly in Windows Explorer which slowly begins to annoy me  specially as the bad RC3 Vendor String date ends by a "17" like the official 1.00 version  (20011217 VS 20020717) I already mistaken RC3 for V1.0 when I was doing quick VorbisExt check

So if anyone is aware of a piece of software that can do that ... I join myself to Der_Iltis to ask for any info

Winamp - OGG Plugin - Argh!

Reply #8 –
I would also be interested in a way of fixing these vendor tags that Wianmp 2.91 screwed up!  I'm on "in_vorbis.dll" version 1.35 now and went back, manually editing all the files I touched with version 1.32 to remove the "padding", but the "vendor" field doesn't get fixed.  :(

Ideas or solutions?  Anyone?