From: Igor Gueths <igueths@comcast.net>
To: speakup@braille.uwo.ca
Subject: Re: problem playing ogg files
Date: Sun, 3 Aug 2003 22:08:42 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308032208140.17575-100000@igueths> (raw)
In-Reply-To: <20030804014940.GA368@lnx3.holmesgrown.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hmm. Thanks for the pointer Steve. I didn't know Zinf was still actively
being developed. From what I saw there wasn't a lot of activity, however
it seems I am wrong on this.
On Sun, 3 Aug 2003, Steve Holmes wrote:
> I just received an anouncement this evening that zinf 2.2.4 was
> released on sourceforge. I haven't tried it yet but will later on.
>
> On Sun, Aug 03, 2003 at 08:07:22PM -0400, Igor Gueths wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > There's always zinf. Just make sure to get zinf-2.2.1, the 2.2.2 version I
> > couldn't get to build. Problem is that fast forwarding through vorbis
> > files doesn't work properly. I think it might have something to do with
> > time indexing i.e., time elapsed vs. time remaining.
>
> --
> Make sure your E-mail can be read by everyone!
> http://www.betips.net/etc/evilmail.html
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6
iD8DBQE/LcAtGT7f58lCbH0RAtEyAKCF+k7prdebJq8hXGt3s45LBnOfFQCeNypn
1aKVSt9aVztrwRNABiNgdfc=
=k1cy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Adam Myrow
` Thomas Stivers
` Igor Gueths
` Steve Holmes
` Igor Gueths [this message]
` jude dashiell
` Buddy Brannan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0308032208140.17575-100000@igueths \
--to=igueths@comcast.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).