From: "Lloyd G. Rasmussen" <lras@loc.gov>
To: blinux-list@redhat.com
Subject: Re: Digital Talking Book Standard
Date: Mon, 19 Nov 2001 12:04:13 -0500 [thread overview]
Message-ID: <3.0.5.32.20011119120413.00874d50@sun8.LOC.GOV> (raw)
In-Reply-To: <20011119174322.D29158@stalin.acc.umu.se>
In the NISO standard, we're not allowing variable bit rate, for the reasons
outlined below. I haven't seen huge space savings for voice recordings.
At 05:43 PM 11/19/01 +0100, you wrote:
>On Mon, Nov 19, 2001 at 11:35:59AM -0500, Nicolas Pitre wrote:
>> On Mon, 19 Nov 2001, Peter Toneby wrote:
>>
>> > On Mon, Nov 19, 2001 at 11:14:39AM -0500, Janina Sajka wrote:
>> > > What about freeamp?
>> >
>> > It does not support searches on timecode (at least I didn't see anything
>> > about that while checking their pages, they only seem to have normal
>> > seek in files, which is not enough).
>>
>> Well... It is enough with some extra processing. You need to find out the
>> data bitrate, estimate the seek position in the audio file,
resynchronize on
>> a mpeg frame boundary, back a couple frames, compute the backed frames to
>> restabilize the mpeg windowing factors without actually playing them then
>> finally resume audio from the desired frame.
>
>The problem is VBR, I'm not sure how it works, but I suspect each frame
>have it's own bitrate in that case, and if the stream use that, you need
>to loop through all frames and calculate the current time :(, well, I'll
>have a closer look at mad and see if I can do something for fixed
>bitrates at least.
>
>/Peter
Braille is the solution to the digital divide.
Lloyd Rasmussen, Senior Staff Engineer
National Library Service f/t Blind and Physically Handicapped
Library of Congress (202) 707-0535 <lras@loc.gov>
<http://www.loc.gov/nls>
HOME: <lras@sprynet.com> <http://lras.home.sprynet.com>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin G. McCormick
` Saqib Shaikh
` Peter Toneby
` Janina Sajka
` Peter Toneby
` Nicolas Pitre
` Peter Toneby
` Lloyd G. Rasmussen [this message]
` Nicolas Pitre
` Nicolas Pitre
` Peter Toneby
` Janina Sajka
` Nicolas Pitre
` Janina Sajka
` Nicolas Pitre
` Brent Harding
` Nicolas Pitre
[not found] ` <Pine.LNX.4.33.0111191409370.3206-100000@toccata.grg.afb.ne t>
` Brent Harding
[not found] ` <Pine.LNX.4.33.0111191147560.2815-100000@toccata.grg.afb.ne t>
` Brent Harding
` Nicolas Pitre
` Joel Zimba
` Brent Harding
` Brent Harding
` Nicolas Pitre
` philwh
` Janina Sajka
` Brent Harding
` Buddy Brannan
` Brent Harding
[not found] ` <Pine.LNX.4.33.0111191114500.2815-100000@toccata.grg.afb.ne t>
` Brent Harding
` Luke Davis
` cbowman
` ssh A. R. Vener
` ssh cbowman
` ssh Luke Davis
` ssh Andor Demarteau
` ssh Luke Davis
` ssh Fredrik Larsson
` ssh Luke Davis
` ssh Fredrik Larsson
` ssh cbowman
` ssh A. R. Vener
` ssh A. R. Vener
` ssh Luke Davis
` Digital Talking Book Standard Brent Harding
` cbowman
` Luke Davis
` cbowman
` Janina Sajka
` Pratik Patel
` Brent Harding
-- strict thread matches above, loose matches on Subject: below --
Janina Sajka
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=3.0.5.32.20011119120413.00874d50@sun8.LOC.GOV \
--to=lras@loc.gov \
--cc=blinux-list@redhat.com \
/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).