Re: Writing WAV files through a pipe

From	Ilya Zakharevich <nospam-abuse@ilyaz.org>
Newsgroups	comp.os.os2.programmer.misc
Subject	Re: Writing WAV files through a pipe
Date	Wed, 30 Mar 2011 00:15:48 +0000 (UTC)
Organization	U.C. Berkeley Math. Department.
Lines	34
Message-ID	<slrnip4thk.6jv.nospam-abuse@powdermilk.math.berkeley.edu> (permalink)
References	<stfVq7QNr4pc-pn2-3WRfnSQgDzPo@localhost> <Bd1D8ggkpXsj-pn2-4j5b5WpNLPzO@Rudi6> <stfVq7QNr4pc-pn2-FevSC9tcSV0v@localhost> <Bd1D8ggkpXsj-pn2-DcwghRWdjFKB@Tobias> <stfVq7QNr4pc-pn2-0hDYlHUVbT2J@localhost> <Bd1D8ggkpXsj-pn2-yjXnODBdECR1@Tobias> <slrnim8ie9.t3d.nospam-abuse@powdermilk.math.berkeley.edu> <slrnim8m92.1cdt.abuse@news.pr.network> <slrnim9elu.u1i.nospam-abuse@powdermilk.math.berkeley.edu> <IU.D20110224.T081209.P54640.Q0@J.de.Boyne.Pollard.localhost> <slrnimj95r.m63.nospam-abuse@powdermilk.math.berkeley.edu> <slrnioubak.n0q.abuse@news.pr.network>
Injection-Date	Wed, 30 Mar 2011 00:15:48 +0000 (UTC)
Injection-Info	mx02.eternal-september.org; posting-host="LlLjF8LevGdIZWbTvv+SXA"; logging-data="23161"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+UHU5lRTJIGT2DA6zU4v2x"
User-Agent	slrn/0.9.8.1pl1 (Linux)
Cancel-Lock	sha1:dU4rwQaSTC+3lhYJT1s/rleeosU=
Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.stben.net!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
Xref	x330-a1.tempe.blueboxinc.net comp.os.os2.programmer.misc:125

Show key headers only | View raw

On 2011-03-27, Paul Ratcliffe <abuse@orac12.clara34.co56.uk78> wrote:
>> Get a clue!  Most of multimedia file formats are "defined" by the most
>> common implementations (even when formal specifications exist - which
>> I'm not absolutely sure was applicable to RIFF from the start).  And
>> this uint_32 would be immediately converted to off_t, which for more
>> than a decade would be just signed_int_32.

> Why would anybody in their right mind want to turn an unsigned length
> field to a signed offset?

I see.  You do not know the signature of the corresponding OS APIs...

> Well, I suppose you would, but then you seem to be deranged anyway.

Hmm, I wonder why I do not give a damn about what you think of me?
Really curious...

>> LOL!  If you think so, feel free to risk damage to your audio
>> equipment and/or your hearing by piping raw audio.
>
> More bullshit. How does piping data damage your audio equipment/hearing?
> And yes, I do know what you are really getting at.

So could not you decide whether you know or not before posting?  I
see, this would not give you a possiblity to demonstrate your rudeness
and lack of understanding of the issues involved...

> That's why it makes sense to tell the far end explicitly what it's
> receiving.

Yes.  And the only reliable way is to include it in the stream.

Yours,
Ilya

Back to comp.os.os2.programmer.misc | Previous | Next — Next in thread | Find similar

Thread

Re: Writing WAV files through a pipe Ilya Zakharevich <nospam-abuse@ilyaz.org> - 2011-03-30 00:15 +0000
  Re: Writing WAV files through a pipe Paul Ratcliffe <abuse@orac12.clara34.co56.uk78> - 2011-04-03 12:57 +0000

csiph-web