homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gward
Recipients
Date 2006年06月11日.16:54:43
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=14422
Brett -- I'm not sure why I put 3.1 sec in there. It's
probably just what popped out the first time I ran this test
on my machine. Anyways, simple math reveals that the
theoretical running time of the test file is ~2.93 sec:
 (23493 bytes) / (1 byte/sample) / (8000 samples/sec) =
2.93 sec
which of course ignores the overhead of the file header, but
that seems to pretty small. "sox" agrees:
$ time /usr/bin/play Lib/test/audiotest.au
Input Filename : Lib/test/audiotest.au
Sample Size : 8-bits
Sample Encoding: u-law
Channels : 1
Sample Rate : 8000
Time: 00:02.93 [00:00.00] of 00:02.93 ( 100.0%) Output
Buffer: 23.46K
Done.
/usr/bin/play Lib/test/audiotest.au 0.03s user 0.02s system
1% cpu 3.127 total
Can you try that on your machine and put the output here?
Anyways, the likely culprits are 1) faster hardware (less
overhead opening audio device, reading file, etc) and 2)
variations in sound chip frequency (8000 Hz is not always
exactly 8000 Hz). I'll try to fix the test so it's a little
fuzzier.
History
Date User Action Args
2007年08月23日 14:40:25adminlinkissue1501330 messages
2007年08月23日 14:40:25admincreate

AltStyle によって変換されたページ (->オリジナル) /