generating messages

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Tue, Dec 15, 1998 at 10:14:51PM +0100, Daniel Doering wrote:
> if i include the pvfspeed (necessary to feed the dato to pvftormd)
> into the pipe: 
> 
> > wavtopvf eddie.wav | pvfspeed -s 9600 | pvftowav | play
> 
>   Reading Wave file: Microsoft PCM format, 2 channels, 44100 samp/sec
>   176400 byte/sec, 4 block align, 16 bits/samp, 2119152 data bytes
>   Writing Wave file: Microsoft PCM format, 1 channel, 9600 samp/sec 9600
>   byte/sec, 1 block align, 8 bits/samp
>   Playing: stdin (full-song)
> 
> it comes out in slow-motion (about factor two - twice the time, half the
> frequencies) ... no matter what speed i specify or without any -s option
> at all.

Looks to me as if "pvfspeed" doesn't correctly pass the information "hey,
this is stereo" to the output file.  Sounds like a bug to me.

Any volunteers to check the PVF code?  Marc E. has no time, neither have 
I (I'm busy doing modem/firmware tests for ELSA).

> to me it seem that the *pvfspeed* really is the program that gets confused
> with stereo input. 

Yes.

> btw, pvftowav produces nothing but noise when given the -16 (produce 16
> bit output) swich. - no matter what the sampling depth of the pvf input
> is. 

Which mgetty/vgetty version is this?  (Are you sure you're using pvftowav
from 1.1.19, not some earlier version still on your hard disk?) - I
remember that there was some problem with pvftowav and "kaput" output in
some earlier versions, but can't remember which versions were affected, or
what the exact symptoms have been.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de