From: Andy Lo A Foe <andy@alsa-project.org>
To: linux-sound@vger.kernel.org
Subject: Re: mp3 seeking
Date: Wed, 27 Oct 1999 14:02:22 +0000 [thread overview]
Message-ID: <marc-linux-sound-94103418715603@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94096104300746@msgid-missing>
On Tue, 26 Oct 1999 est@hyperreal.org wrote:
> First, I must thank you for alsaplayer since I'm using an adaptation
> of your adaptation of the mpg123 code in the next major release of
> oolaboola. I'm encapsulating it in a separate process (called
> mp3serv) to get re-entrancy. I may move to the xing decoder but the
> process interface will remain the same.
Very interesting. I'm thinking about a similar solution for doing
reentrancy with plugins that don't support it, something like a proxy
plugin interface with IPC and shared memory. Where can I get the latest
version of oolaboola?
> My understanding was that it *may* take more than 3 frames of priming
> to resynchronize. One of the xing/freemap people got me the logic but
> I haven't implemented it yet.
I'm using 3 right now. You need a bit more for lower bitrates it seems.
I've never really looked into the encoding algorithm so... :)
> Another issue is how to find a given frame in the first place. Given
> that each frame may have an extra byte of padding, a multiplication is
> (audibly!) unreliable. I've implemented a table-of-contents mechanism
> to deal with this.
Yes, if you want 100% correct seeking the best thing you can do is to
store the frame start positions while decoding. It is a bit slow though.
Is that what you're doing? (for VBR encoded files I don't see any other
(simple) method to support seeking BTW)...
Regs,
Andy
--
AlsaPlayer, http://www.alsa-project.org/~andy/
prev parent reply other threads:[~1999-10-27 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 17:20 mp3 seeking est
1999-10-27 14:02 ` Andy Lo A Foe [this message]
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=marc-linux-sound-94103418715603@msgid-missing \
--to=andy@alsa-project.org \
--cc=linux-sound@vger.kernel.org \
/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