sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jeff Learman <jjlearman@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: (no subject)
Date: Tue, 12 May 2020 16:45:23 -0400	[thread overview]
Message-ID: <CAGyjer4HUKxwLOJ5+c6cQDip=uvyZfkM6qV4bpMwnqgkpYkqsg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1595 bytes --]

Thanks, that would be perfect!  Also, a flag to print skipped tags, if
there isn't one already.

Please forgive the late reply.  I'd just signed up and you replied so
fast the exploder didn't know me yet!

Jeff


Måns Rullgård writes:
>
> Jeff Learman <jjlearman@...>  writes:
>
>> I noticed that when converting stereo sample files to mono, the 'smpl'
>> chunks (which encode loop information used by sample players), SoX omits
>> the 'smpl' chunk in the output file.
>>
>> For example,
>>
>> sox input.wav -c 1 output.wav
>>
>> sums a stereo input.wav to a mono output.wav. However, the 'smpl' chunk in
>> input.wav is discarded.
>>
>> I have a workaround; I wrote code to extract the smpl chunk and append it
>> to the output. But it would be nice if 'smpl' chunks were supported by
>> default, at least for the easy cases. (I realize it could be difficult or
>> impossible for many cases.)
>>
>> What's the best way to file a bug report?
>
> The smpl chunk isn't part of the official WAV format, so SoX ignores it.
> It's the only reasonable thing to do with unknown chunks. Copying the macross
> to the output is risky since we can't know that the processing didn't
> invalidate them. For example, a chunk referencing specific samples is (likely)
> still relevant after downmixing stereo to mono, whereas resampling to a higher
> or lower rate will obviously make it useless.
>
> The best we can reasonably do
> is add a flag to specify extra chunks topreserve if found in the input. Would
> that be helpful in your case?
>
> -- Måns Rullgård

[-- Attachment #1.2: Type: text/html, Size: 1938 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

             reply	other threads:[~2020-05-12 20:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 20:45 Jeff Learman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-11  4:40 (no subject) urg
2014-12-27 12:12 paul fellows
2014-12-28  5:43 ` Eric Wong
2014-05-20 14:41 James Spencer
2013-06-18 18:54 Paul Arnold
2012-10-29 17:42 Eli Sanders
2009-01-09  9:13 maanu
2009-01-06 20:22 JJENGR
2007-11-20 18:49 Daniel Payne
     [not found] <kevinc@doink.com>
2007-07-25 17:02 ` [LAU] " Kevin Cosgrove
2007-07-25 17:31   ` David Graff
2007-07-25 17:34     ` Vijay Gaur
2007-07-25 17:36   ` Rafal Maszkowski
2007-07-25 17:37   ` David Graff

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-users

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

  git send-email \
    --in-reply-to='CAGyjer4HUKxwLOJ5+c6cQDip=uvyZfkM6qV4bpMwnqgkpYkqsg@mail.gmail.com' \
    --to=sox-users@lists.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).