ogg dev - Jan 2010 - Using vorbis-java to read an existing file?

Hi All

I was hoping to be able to use the vorbis-java library to read the 
comments attached to an ogg vorbis audio file.

The snag is that I can't see how to work with an existing file, only to 
create new ones. The encoding example only writes, doesn't read. The 
javadocs don't appear to tell you what you need to do. I tried to follow 
the C examples, but the APIs just seem to be too different :(

Could anyone point me at an example / some documentation on how to use 
vorbis-tools to read an existing file?

(I want to use vorbis-tools rather than some of the other java ogg 
libraries out there, as I'm after something under BSD or Apache licenses, 
and all the other things I found were GPL/LGPL)

Cheers
Nick

On Tue, 26 Jan 2010, Nick Burch wrote:
> The snag is that I can't see how to work with an existing file, only to
> create new ones. The encoding example only writes, doesn't read. The 
> javadocs don't appear to tell you what you need to do. I tried to
follow
> the C examples, but the APIs just seem to be too different :(
Having looked at the Java code some more, and at the original C code, it 
seems to me that the read support is missing from the vorbis-java port. I 
can see the various write related parts from the C coded in their Java 
equivalents, but the read bits seem to be missing :/

Can someone confirm if that's the case?

Assuming so, I'm trying to decide if it's likely to be better to port
the
missing read parts from C to Java, or start again with something with a 
more "Java like" api. Having read rfc 3533, I don't think doing a 
read-only ogg layer api using Java conventions should be too hard to 
implement....

Nick

> Assuming so, I'm trying to decide if it's likely to be better to
port the
> missing read parts from C to Java, or start again with something with a
> more "Java like" api. Having read rfc 3533, I don't think
doing a
> read-only ogg layer api using Java conventions should be too hard to
> implement....
There is the jogg and jorbis combination (used in Cortado) which sound
like what you want.

On Thu, 28 Jan 2010, Nick Burch wrote:
> Assuming so, I'm trying to decide if it's likely to be better to
port
> the missing read parts from C to Java, or start again with something 
> with a more "Java like" api. Having read rfc 3533, I don't
think doing a
> read-only ogg layer api using Java conventions should be too hard to 
> implement....
I've decided to go for the "write something java-like from
scratch"
option. I've done an ogg layer (with unit tests!) that's able to read, 
write, and round-trip without change existing files. The vorbis layer is 
almost there for info/header/setup in read/write, but there's no encoding 
or decoding of the audio data.

Would there be any interest in hosting this alongside the current 
(definately write-only) java library?

Nick