I took the C++ discid code and ported it to C with libcdio's routines. This
has now been checked into libcdio's "example" directory in git
https://savannah.gnu.org/git/?group=libcdio

The code in libcdio is just as short (if not shorter) and about just as
quick.

On Fri, Nov 4, 2011 at 8:43 AM, Stef Bon <[email protected]> wrote:

> 2011/11/4 Leon Merten Lohse <[email protected]>:
>
> >> I've found an utility which reads various important data very quickly:
> >>
> >> http://discid.sourceforge.net/
> >
> > This utility gives you the cddb disc id. It is not only possible to do
> > this with libcdio, it is already implemented in cd-info. cd-info uses
> > that string to query the freedb/cddb server.
> > Compare cd-info output line beginng with `Disc ID'.
> >
> > It get the information it needs from the toc (table of content) located
> in
> > the discs lead-in area.
> > I cannot think of a faster method but normally that is very fast.
>
> Hi Leon,
>
> I've seen in the the ouput of cd-info this disc id.
>
> But my issue is that the command cd-info takes a long time (some
> seconds) to finish.
>
> Now I use the output of cd-info  to generate an unique id for an audio cd.
>
> But has to be done before the fs is mounted, causing extra delay.
>
> I been looking for such an id (previous message on this list some
> months ago), till I found this discid yesterday, and it's exactly what
> I want. It generates an unique id, which has also some sense in the
> cddb world, and this utility does it very fast!
>
> So the point is, can cd-info give the same output, and also that fast as
> discid?
>
> (the information is thus not only the hexnumber, but also, the number
> of tracks, and the startsectors.. and total number of seconds)
>
> Stef
>
> _______________________________________________
> Libcdio-help mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/libcdio-help
>
_______________________________________________
Libcdio-help mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/libcdio-help

Reply via email to