From: Pander <pander@users.sourceforge.net>
To: sox-devel@lists.sourceforge.net
Subject: Re: spectrogram values
Date: Tue, 26 Jan 2016 13:24:39 +0100 [thread overview]
Message-ID: <56A76587.5030704@users.sourceforge.net> (raw)
In-Reply-To: <20160122235422.GA10636@toggle.be>
Let me know when you start working on it. It is very tricky and I am
willing to be a critical tester if you want.
On 01/23/2016 12:54 AM, Thor Andreassen wrote:
> On Thu, Jan 21, 2016 at 04:33:19PM +0100, Pander wrote:
>
> [...]
>
>>> Note that if your output from sox is short, the spectrogram dimensions
>>> will be different from 800x513 and Gnuplot will barf.
>
>> Please note that there are some tricky side effects if you do it
>> incorrectly. See my post
>> https://sourceforge.net/p/sox/mailman/message/34724933/ on when to omit
>> and when not to omit the last sample of spectrogram data. Only when that
>> sample is completely filled, it may be included. That is the best
>> approach. All others result in deformed or suboptimal energy spectra.
>
> Interesting. I will have a closer look when I have more time.
>
> Here is a link to the original mail you sent on the subject:
>
> https://sourceforge.net/p/sox/mailman/message/33625255/
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
next prev parent reply other threads:[~2016-01-26 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 14:31 spectrogram values Markus Glugla
2016-01-20 2:37 ` Thor Andreassen
2016-01-21 15:33 ` Pander
2016-01-22 23:54 ` Thor Andreassen
2016-01-26 12:24 ` Pander [this message]
2016-01-22 17:38 ` Thor Andreassen
2016-01-28 12:51 ` Markus Glugla
2016-01-28 13:00 ` Pander
2016-01-28 14:47 ` Markus Glugla
2016-01-28 16:17 ` Pander
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=56A76587.5030704@users.sourceforge.net \
--to=sox-devel@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).