PDA

View Full Version : Nightlies have been rejecting OGGs



John Ellis
2003-12-26, 09:41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've noticed that for a weeks or so now the nightlies have been rejecting
Ogg files. Or at least mine. Whenever I fire up the SlimServer I get:

This is not an Ogg bitstream (no OggS header). at /home/jellis/Documents/
Applications/SlimServer_v2003-12-26/CPAN/Ogg/Vorbis/Header/PurePerl.pm
line 152.

And things just go downhill from there. It appears that _checkHeader in
CPAN/Ogg/Vorbis/Header/PurePerl.pm is looking at the first four bytes of
the Ogg file and looking for 'OggS' in the header. But if your first 4300
(or so) bytes are filled with ID3v2 info then you're screwed because the
byte offset is incorrect.

Known issue?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/7GSnRbpfi9ylWxoRAuDAAJ4in2E6+w+0Auw9KlZTrXQZgbjRRw CaAzbM
Ef0W4Ahy0CQqdX9gMnzEYnw=
=tEQZ
-----END PGP SIGNATURE-----

John Ellis
2003-12-26, 10:43
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I guess Vorbis considers ID3 tags to "corrupt" Ogg files (see the Ogg
Traffic for 12/15/02 at http://www.vorbis.com/ot/20021215.html), while
I'm more likely to consider ID3 tags an additional feature. I'm guessing
that the Perl module is taking the same stance - that ID3 tags just
corrupt an Ogg and should be stripped?

I guess that's the difference between using the Perl module to parse the
bytestream itself and using ogginfo to glean the correct information out
of the file and discard the rest.

Yes, I'm just talking to myself at this point. Just writing it down in
case it's of any use to anyone who has the same problem after the
ogginfo->PurePerl switch.

On Friday 26 December 2003 11:41 am, I wrote:
> I've noticed that for a weeks or so now the nightlies have been
> rejecting Ogg files. Or at least mine. Whenever I fire up the
> SlimServer I get:
>
> This is not an Ogg bitstream (no OggS header). at
> /home/jellis/Documents/
> Applications/SlimServer_v2003-12-26/CPAN/Ogg/Vorbis/Header/PurePerl.pm
> line 152.
>
> And things just go downhill from there. It appears that _checkHeader in
> CPAN/Ogg/Vorbis/Header/PurePerl.pm is looking at the first four bytes
> of the Ogg file and looking for 'OggS' in the header. But if your first
> 4300 (or so) bytes are filled with ID3v2 info then you're screwed
> because the byte offset is incorrect.
>
> Known issue?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/7HNJRbpfi9ylWxoRAuXsAKC3v/kKGz44TXhdi5OQOz0+29dHzACguZGJ
UyX2xAaSw2F62bbxppCXY5Q=
=1gf8
-----END PGP SIGNATURE-----

John Ellis
2003-12-26, 13:06
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've stripped all my Ogg's of both v1 and v2 ID3 tags and I no longer
receive the below error. However, no tagging works at all now (SlimServer
doesn't notice any album/artist/track info). Noatun and XMMS have no
problem reading tag info, however.

Are the nightlies in a bad way with Ogg right now?

On Friday 26 December 2003 11:41 am, you wrote:
> I've noticed that for a weeks or so now the nightlies have been
> rejecting Ogg files. Or at least mine. Whenever I fire up the
> SlimServer I get:
>
> This is not an Ogg bitstream (no OggS header). at
> /home/jellis/Documents/
> Applications/SlimServer_v2003-12-26/CPAN/Ogg/Vorbis/Header/PurePerl.pm
> line 152.
>
> And things just go downhill from there. It appears that _checkHeader in
> CPAN/Ogg/Vorbis/Header/PurePerl.pm is looking at the first four bytes
> of the Ogg file and looking for 'OggS' in the header. But if your first
> 4300 (or so) bytes are filled with ID3v2 info then you're screwed
> because the byte offset is incorrect.
>
> Known issue?

- --
John T. Ellis
Information Systems Experts, Inc.
http://www.ise-indy.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/7JTKRbpfi9ylWxoRArfKAJ4iqR0lLpbM1rw2Sj6mmvHSie7x9w Cgg/k0
PcQ3cWKvBMTX6bTgSq0NHEg=
=vpNP
-----END PGP SIGNATURE-----

Dan Sully
2003-12-26, 14:16
* John Ellis <john.ellis (AT) ise-indy (DOT) com> shaped the electrons to say...

> I've noticed that for a weeks or so now the nightlies have been rejecting
> Ogg files. Or at least mine. Whenever I fire up the SlimServer I get:
>
> This is not an Ogg bitstream (no OggS header). at /home/jellis/Documents/
> Applications/SlimServer_v2003-12-26/CPAN/Ogg/Vorbis/Header/PurePerl.pm
> line 152.
>
> And things just go downhill from there. It appears that _checkHeader in
> CPAN/Ogg/Vorbis/Header/PurePerl.pm is looking at the first four bytes of
> the Ogg file and looking for 'OggS' in the header. But if your first 4300
> (or so) bytes are filled with ID3v2 info then you're screwed because the
> byte offset is incorrect.

John - could you please email that .ogg file off-list? Thanks.

-D
--
Off the record, on the QT, and very hush-hush.

John Ellis
2003-12-30, 13:51
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For those in Vorbisland:

Evidentally the nightlies were in a bad way with Ogg's. But the current
12/30 nightly reads Ogg descriptions correctly. You still need to do the
- -R hack in convert.conf, but otherwise things get indexed/streamed just
fine.

CPU utilization... oddly enough... seems to be down as well. Considering
that it's still just piping raw decoded data to stdout and encoding raw
data to mp3 from stdin that's kinda weird.

On Friday 26 December 2003 03:06 pm, you wrote:
> I've stripped all my Ogg's of both v1 and v2 ID3 tags and I no longer
> receive the below error. However, no tagging works at all now
> (SlimServer doesn't notice any album/artist/track info). Noatun and
> XMMS have no problem reading tag info, however.
>
> Are the nightlies in a bad way with Ogg right now?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/8eVVRbpfi9ylWxoRAkjBAJ4kNikO5xURVbRjAK82cfdxBX9H+A Cfe5QV
dtWgRKph/y7AknH6yTksQEM=
=f59K
-----END PGP SIGNATURE-----