sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: SourceForge.net <noreply@sourceforge.net>
To: SourceForge.net <noreply@sourceforge.net>
Subject: [ sox-Bugs-2497902 ] Wave files from SoX Rate Converter in 24bits can't be read
Date: Mon, 18 Feb 2013 16:54:45 -0800	[thread overview]
Message-ID: <E1U7bTr-0001vK-UV@sfs-ml-2.v29.ch3.sourceforge.com> (raw)

Bugs item #2497902, was opened at 2009-01-10 07:52
Message generated for change (Comment added) made by uklauer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=2497902&group_id=10706

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jean Beauve (bricolodu13)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wave files from SoX Rate Converter in 24bits can't be read

Initial Comment:
The files generated from the Rate converter in the 24 bit format (44.1kHz -> 88.2 kHz) are not recognised by Foobar also recognised by VLC.

Regards,
Jean

----------------------------------------------------------------------

>Comment By: Ulrich Klauer (uklauer)
Date: 2013-02-18 16:54

Message:
There are two changelog entries from 14.3.2 that may be related:
– Fix RIFF chunk length error when writing 24-bit files. (David Bryant)
– 24-bit WAV files were leaving channel maps unassigned. Change to use
common channel mappings based on channel count.  This allows to work more
seemlessly with other apps such as WavPack and Foobar2000. (David Bryant)

So it might be fixed.

----------------------------------------------------------------------

Comment By: bat (bat999)
Date: 2013-02-18 15:44

Message:
Hi
This bug report is from 2009.
Nobody has responded.

----------------------------------------------------------------------

Comment By: robs (robs)
Date: 2009-01-16 09:21

Message:
Hmmm... so far, not able to recreate this problem.

Perhaps you could try generating these 2 test files:

sox -b 24 -c 2 -r 96k -n -t wavpcm wavpcm.wav synth 1
sox -b 24 -c 2 -r 96k -n wav.wav synth 1

then testing with various players.

Here's what I find:

VLC 0.8.6a works with both

Audacity (libsndfile 1.0.17) works with both

foobar 0.9.6.1 works only with wavpcm.wav

Windows media player 10.00.00.4036 works only with wav.pcm

(pretty much as expected.)

----------------------------------------------------------------------

Comment By: Klaus Schulz (soundcheck)
Date: 2009-01-16 02:51

Message:

One more(perhaps a workaround for the time being):

If I  run: 

sox in.wav -t wavpcm out.wav vol 0db 

out.wav is readable even though -V says  vol has no effect!

----------------------------------------------------------------------

Comment By: Klaus Schulz (soundcheck)
Date: 2009-01-16 01:49

Message:

I forgot to mention:

I get the same result if I use -t wavpcm or -t wav as mentioned in FAQ

----------------------------------------------------------------------

Comment By: Klaus Schulz (soundcheck)
Date: 2009-01-16 01:42

Message:
Hi there

The same over here: 

Sox  Revision 14.2.0

Input is 24/2/96000 wav

Command: sox in.wav out.wav 

sox -V output:

sox sox: effects chain: input      96000Hz 2 channels 24 bits (multi)
sox sox: effects chain: output     96000Hz 2 channels 24 bits (multi)


In/Out Files:

124841432 2009-01-16 10:25
02-John_Gorka-The_Gypsy_Life-I_Saw_A_Stranger_With_Your_Hair.wav
124840424 2009-01-16 10:22 02test.wav


Is the format or header changed?? Even -t wav didn't work.

----------------------------------------------------------------------

Comment By: robs (robs)
Date: 2009-01-10 10:12

Message:
Please see FAQ #4: http://sox.sourceforge.net/Docs/FAQ

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=2497902&group_id=10706

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

             reply	other threads:[~2013-02-19  0:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  0:54 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-18 23:44 [ sox-Bugs-2497902 ] Wave files from SoX Rate Converter in 24bits can't be read SourceForge.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1U7bTr-0001vK-UV@sfs-ml-2.v29.ch3.sourceforge.com \
    --to=sox-devel@lists.sourceforge.net \
    --cc=noreply@sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).