Click sound at the end of play-out

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
Sox-users mailing list
Sox-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

Click sound at the end of play-out

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
Sox-users mailing list
Sox-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

Problems compiling Sox 14.0

I cannot compile sox 14.0, and I'm too inexperienced to fix this problem.

I'm running a Slackware 11.0 system, but with a 2.6.13 kernel.

Make seems to indicate problems with ogg-vorbis.  I disabled ogg support 
and make finished without errors.  Installation commenced without errors.

But the new version of sox cannot read wav files. It says it cannot find 
the data chunk. So I've gone back to version 13.0.

I note in config.log that there are several instances where 
ac_nonexistent.h is not found. In addition, there are tons of "warning: 
function declaration isn't a prototype." I noticed the same thing wi Sox 
13.0, which compiles and installs just fine.

Mike Keithley

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: Problems compiling Sox 14.0

Please attach your config.log which would help us help you...

-Pascal

On 11/1/07, Mike Keithley <mkeithley <at> pobox.com> wrote:
> I cannot compile sox 14.0, and I'm too inexperienced to fix this problem.
>
> I'm running a Slackware 11.0 system, but with a 2.6.13 kernel.
>
> Make seems to indicate problems with ogg-vorbis.  I disabled ogg support
> and make finished without errors.  Installation commenced without errors.
>
> But the new version of sox cannot read wav files. It says it cannot find
> the data chunk. So I've gone back to version 13.0.
>
> I note in config.log that there are several instances where
> ac_nonexistent.h is not found. In addition, there are tons of "warning:
> function declaration isn't a prototype." I noticed the same thing wi Sox
> 13.0, which compiles and installs just fine.
>
>
> Mike Keithley
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Sox-users mailing list
> Sox-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
>

--

-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: SoX v14.0.0 WAV file issues...

John Magliacane wrote:
> I've been using SoX successfully for quite a number of years, but version 14
> brings with it problems never seen before.
>
> I'm running several different Slackware Linux machines -- some with the default
> gcc 3 compiler, while others have gcc 4 that I've compiled and installed
> myself.
>
>
>   

> However, once compiled, SoX cannot read or play .wav files.  The program exits
> with a "Could not find data chunk" error.
>
> I tried commenting out the data chunk "if" check on or about line 816 in
> src/wav.c.  This allowed SoX to read the file and display data size
> information, but the program quickly exits after this without reading the file
> any further.
>
> So, the error trap appears to be working properly, but the "len" or the
> "dwDataLength" variables might be incorrectly computed.
>
>   

Thanks for trying to debug this some... Could you also add a "-V4" to 
your command line when running SoX?  It should print out some extra 
information like about chunks it finds:

/sox -V4 monkey.wav -e
/usr/local/bin/sox: SoX v14.0.1
/usr/local/bin/sox auto: Detected file format type: wav
/usr/local/bin/sox wav: WAV Chunk fmt
/usr/local/bin/sox wav: WAV Chunk fact
/usr/local/bin/sox wav: WAV Chunk data

That should helps us pinpoint how early in reading the WAV file its 
failing.  The data chunk should be the last thing it starts reading.

Also, is this *all* WAV files that fail or just some?  Can you try the 
monkey.wav that comes with SoX?  If it works with that one then we will 
need a sample WAV that doesn't work and can probably debug it pretty fast.

Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: Click sound at the end of play-out

Its not a bug I'm aware of. It could be a SoX bug but in my experience 
its usually an ALSA bug.

Do you have any other data points to help pinpoint it? Did it work on in 
SoX pre-14.0.0? Do other ALSA audio programs not have the problem? What 
is your sound driver?

I guess SoX team should at least check with ALSA team... I'm not aware 
of any requirements to send a complete buffer (padded with silence) even 
on the last buffer. Maybe the ALSA driver is playing random data from 
previous buffers to make up for it.

If you like, write a bug report on SoX's bug tracker.

Chris

Frank Fang wrote:
>
> Hi,
>
> I am using “play” to play sound clips. The version number is v14.0.0. 
> At the end of the playout, I can hear a small click artifact. After I 
> use “—buffer 1024” (by default, it is 8192), the click artifacts are 
> gone.
>
> Is this a known bug?
>
> Thanks,
>
> Zheng
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: Problems compiling Sox 14.0

Pascal Giard wrote:
> Please attach your config.log which would help us help you...
>
> -Pascal
>
> On 11/1/07, Mike Keithley <mkeithley <at> pobox.com> wrote:
>   
>> I cannot compile sox 14.0, and I'm too inexperienced to fix this problem.
>>
>> I'm running a Slackware 11.0 system, but with a 2.6.13 kernel.
>>
>> Make seems to indicate problems with ogg-vorbis.  I disabled ogg support
>> and make finished without errors.  Installation commenced without errors.
>>
>> But the new version of sox cannot read wav files. It says it cannot find
>> the data chunk. So I've gone back to version 13.0.
>>
>> I note in config.log that there are several instances where
>> ac_nonexistent.h is not found. In addition, there are tons of "warning:
>> function declaration isn't a prototype." I noticed the same thing wi Sox
>> 13.0, which compiles and installs just fine.
>>
>>
>> Mike Keithley
>>     

Any history you can provide on these WAV files would also help (were 
they created with earlier version of SoX or another application?).  Can 
you read the monkey.wav file that comes with SoX source code?

Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: Using sox as a library

robs wrote:
>
> I'm afraid the SoX lib API is still poorly documented
> and somewhat fluid.
>   
This is probably going to be my next big update to SoX.  I'm going to 
work out a real API for effects and document them.

It probably won't be until December before I can do this though.

Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: Installing SoX

Yes, I agree with if SoX can not completely find all needed items then 
it should disable it.  If you can, please write a bug report on our bug 
tracker for each item that find that doesn't work as you described.  
Then we can fix it as time permits.

BTW, the following is my expected behavior for this.

It must find usable libraries and headers in normal case or disable the 
feature.

If user specifies --enable-blah and it can not find both libraries and 
headers then configure should stop executing at that point instead of of 
just disabling the feature.

I don't think we work like that consistently right now but its the ideal 
way for distribution packages so that they can know when the package 
they built doesn't have the feature they force-enabled.

Chris

Michael Chapman wrote:
> Just a comment.
>
> If one has 'something' the "./configure" detects it.
> One then runs "make" and it fails if you do not have the development 
> library/header files.
>
> E.g. for 'something' = mad/lame/  
>
> So one can run " ./configure --without-mad --without-lame"
> (or install the missing files).
>
> No problem.
>
> But a couple of years ago I would not have understood the output of make and 
> would have just given up. A pity as SoX is wonderful.
>
> For a more naïve user base, it would be good if configure not only checked 
> whether lame, mad, etc. were present but also whether they were usable. (Also 
> configure runs quicker than (as well as before) make on my ancient machine 
> ;
>
> Just a thought ... if, anyway, it is a practicable thought? 
>
> 	Michael Chapman
>
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Sox-users mailing list
Sox-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

Re: Problems compiling Sox 14.0

-Any history you can provide on these WAV files would also help (were 
-they created with earlier version of SoX or another application?).  Can 
-you read the monkey.wav file that comes with SoX source code?
-
-Chris
-
The wav files I tested were made by sox 13.0.  Monkey.wav would not play.  It
gives

"sox soxio: Failed reading rc/monkey.wav': Could not find data chunk."

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/