Very Computer

Quote:> play sound.au

I've tried recompiling the kernel multiple times, using all possible
buffer sizes, but I always get that same error message.  As I haven't
seen this problem mentioned by anyone else, I figured I'd better post
it.  Anyone else having this problem?  Any solutions?

    ///////////////////////////////////////////////////////////////////////
   //  Michael Holl      "Now next Friday I didn't have the rent...     //

 //              http://www.students.uiuc.edu./~m-holl/               //
///////////////////////////////////////////////////////////////////////

] > play sound.au
] Invalid audio buffers size 1024
]
] I've tried recompiling the kernel multiple times, using all possible
] buffer sizes, but I always get that same error message.  As I haven't
] seen this problem mentioned by anyone else, I figured I'd better post
] it.  Anyone else having this problem?  Any solutions?

Yes, the play application needs to be fixed:

*** recplay.c~  Thu Feb 15 06:58:50 1996
--- recplay.c   Sun Feb 18 08:01:13 1996
***************
*** 188,190 ****
        ioctl(audio, SNDCTL_DSP_GETBLKSIZE, &abuf_size);
!       if (abuf_size < 4096 || abuf_size > 65536) {
                close(audio);
--- 188,190 ----
        ioctl(audio, SNDCTL_DSP_GETBLKSIZE, &abuf_size);
!       if (abuf_size < 1 || abuf_size > 65536) {
                close(audio);
--
David Fox          http://found.cs.nyu.edu/fox          xoF divaD
NYU Media Research Lab                     baL hcraeseR aideM UYN

    ///////////////////////////////////////////////////////////////////////
   //  Michael Holl      "Now next Friday I didn't have the rent...     //

 //              http://www.students.uiuc.edu./~m-holl/               //
///////////////////////////////////////////////////////////////////////

Quote:>I'd been having extremely good luck with all of the 1.3 kernels until
>1.3.63 was released.  Starting with this kernel, whenever I try to
>play a sound file through /dev/dsp (using sox or wavplay), I get an
>error message similar to the following:

>> play sound.au
>Invalid audio buffers size 1024

>I've tried recompiling the kernel multiple times, using all possible
>buffer sizes, but I always get that same error message.  As I haven't
>seen this problem mentioned by anyone else, I figured I'd better post
>it.  Anyone else having this problem?  Any solutions?

--
Steve McIntyre, CURS Secretary      "Can't keep my eyes from the circling sky,"

Churchill College    <a href=http://www2.eng.cam.ac.uk/~93sam/>my home page</a>
Cambridge, UK     <a href=http://www2.eng.cam.ac.uk/~93sam/comp/>My PC page</a>

(http://personal.eunet.fi/pp/voxware)

if you visit this site, it explains that the new sound driver (3.5-beta3)
breaks sound utils such as sox, etc.  and that there are some new sound
utils available at that same site (vplay, and maybe others, I just checked
back and got this info)

actually, the new sound stuff is at
ftp://ftp.best.com/pub/front/tasd/snd-util-3.5.tar.gz

this should fix the vplay, but sox remains broken, as far as I can tell

hope this helps!  

--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT/E/S d-(---) s: a-- C++ ULSV+ P+ L+++ E---- W N+ w-- O- M- V-- PS+ PE
Y+ PGP+ t+ 5- X+ tv+ DI+++ D+ G+ e++>++++ h*(---) r+++ y+++**
------END GEEK CODE BLOCK------

Quote:>I'd been having extremely good luck with all of the 1.3 kernels until
>1.3.63 was released.  Starting with this kernel, whenever I try to
>play a sound file through /dev/dsp (using sox or wavplay), I get an
>error message similar to the following:

>> play sound.au
>Invalid audio buffers size 1024

  Peter

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Peter "Pit" Suetterlin                  http://www.kis.uni-freiburg.de/~ps
Kiepenheuer Institut fuer Sonnenphysik

 -- * -- * ...-- * -- * ...-- * -- * ...-- * -- * ...-- * -- * ...-- * --
Come and see the stars!             http://www.kis.uni-freiburg.de/~ps/SFB
Sternfreunde Breisgau e.V.
Tel.: +49 761 73571 or 278588
__________________________________________________________________________

Quote:>in the /usr/src/linux/drivers/sound/Readme file there is a URL which gives
>the current status of the sound driver.

>(http://personal.eunet.fi/pp/voxware)

>if you visit this site, it explains that the new sound driver
>(3.5-beta3) breaks sound utils such as sox, etc.  and that there are
>some new sound utils available at that same site (vplay, and maybe
>others, I just checked back and got this info)

 Peter

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Peter "Pit" Suetterlin                  http://www.kis.uni-freiburg.de/~ps
Kiepenheuer Institut fuer Sonnenphysik

 -- * -- * ...-- * -- * ...-- * -- * ...-- * -- * ...-- * -- * ...-- * --
Come and see the stars!             http://www.kis.uni-freiburg.de/~ps/SFB
Sternfreunde Breisgau e.V.
Tel.: +49 761 73571 or 278588
__________________________________________________________________________

Quote:>Same here (Soundblaster Pro). Furthermore many aplications hang:
>xanim (2.703) only manages one run of the audio-stream of an
>AVI-file.  xanim doesn't really quit after exiting the program but
>stays around blocking the audio devices. Same for Maelstrom wich will
>just hang. This is up to 1.3.65 at least. (Haven't tried more recent
>ones).

     Shawn McHorse

     An Austin NorthCross-Dresser

]
] >in the /usr/src/linux/drivers/sound/Readme file there is a URL which gives
] >the current status of the sound driver.
] >
] >(http://personal.eunet.fi/pp/voxware)
] >
] >if you visit this site, it explains that the new sound driver
] >(3.5-beta3) breaks sound utils such as sox, etc.  and that there are
] >some new sound utils available at that same site (vplay, and maybe
] >others, I just checked back and got this info)
]
] Uuh, and why that kind of strong incompatibility in that phase
] (Thought we are in the feature freeze)? This will also break many
] (most?) of the aplications using sound devices.  You will have to
] recompile (even worse, patch!) all of them.  What about comercial
] programs w/o sources ?

The feature freeze you are referring to is an informal one.  IMHO.
The real feature freeze comes when Linus declares version 2.0.  At
that point sellers of commericial programs without sources will have
to work out their own solutions.
--
David Fox          http://found.cs.nyu.edu/fox          xoF divaD
NYU Media Research Lab                     baL hcraeseR aideM UYN

Markus

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface

iQCVAgUBMSr3OxqJqDLErwMxAQEkiwQArZMhzy9rRp9w4CIPi8Nry5meS/Q7Ql0d
Otrc8nkTyT6LCsE+y5ur6CrKl334QypgY7mB0ySUz9RY4BqQoRNIMmHO8bJ0Tnsb
pomAw3HzlEu6TjMzTz8wdrmLs940tvgxcjJ0bzwy3GiCMLbReC042QcFzwTIu5Um
Zndx5M4N6QU=
=5Usq
-----END PGP SIGNATURE-----