robert bristow-johnson wrote:
you can have a periodic (or quasi-periodic) signal with absolutely no
energy at harmonic #1 (what i would call the fundamental), and as long as
it has energy in most other odd harmonics, the autocorrelation function
will work just as well. there will still be pe
On Nov 26, 2010, at 1:01 AM, Ross Bencina wrote:
Element Green wrote:
I would think autocorrelation or something like that would provide
the
location and size of the loop, so I don't see the need for a pitch
detection algorithm. Or am I overlooking something?
Peaks in the ACF might be goo
Element Green wrote:
I would think autocorrelation or something like that would provide the
location and size of the loop, so I don't see the need for a pitch
detection algorithm. Or am I overlooking something?
Peaks in the ACF might be good loop candidates but won't necessarily all be
multip
On Nov 25, 2010, at 11:40 PM, Element Green wrote:
On Wed, Nov 24, 2010 at 9:51 PM, Didier Dambrin
wrote:
IMHO "finding loop points" is the wrong problem to solve, it's
better to
"make something loop" instead, as (ideally) you're only gonna find
the least
bad loop points, nothing guarant
On Thu, Nov 25, 2010 at 4:43 AM, Ross Bencina
wrote:
> Element Green wrote:
>>
>> I'm the author of a SoundFont instrument editing application called
>> Swami (http://swami.sourceforge.net). A while back an interested
>> developer added a loop finding algorithm which I integrated into the
>> appl
On Thu, Nov 25, 2010 at 4:05 AM, Sebastian Stober wrote:
> Hi Joshua,
>
> you might be interested in this blog post:
> http://runningwithdata.tumblr.com/post/597154309/earworm-capsule
> about a graph-based approach.
>
> Best regards,
> Sebastian
>
Does indeed sound like an interesting project. F
On Thu, Nov 25, 2010 at 2:14 AM, Johannes Kroll wrote:
> On Thu, 25 Nov 2010 06:51:03 +0100
> "Didier Dambrin" wrote:
>
>> IMHO "finding loop points" is the wrong problem to solve, it's better to
>> "make something loop" instead, as (ideally) you're only gonna find the least
>> bad loop points, n
Hello Didier,
On Wed, Nov 24, 2010 at 9:51 PM, Didier Dambrin wrote:
> IMHO "finding loop points" is the wrong problem to solve, it's better to
> "make something loop" instead, as (ideally) you're only gonna find the least
> bad loop points, nothing guarantees that there's anything loopable.
> I
[Apologies for cross-postings]
[Please distribute]
8th Sound and Music Computing Conference
06-09 July 2011, Padova, Italy
Department of Information Engineering, University of Padova
Conservatorio Cesare Pollini, Padova
http://smc2011.smcnetwork.org/
The SMC Conference is the forum for internati
Element Green wrote:
I'm the author of a SoundFont instrument editing application called
Swami (http://swami.sourceforge.net). A while back an interested
developer added a loop finding algorithm which I integrated into the
application. This feature is supposed to generate a list of start/end
lo
Hi Joshua,
you might be interested in this blog post:
http://runningwithdata.tumblr.com/post/597154309/earworm-capsule
about a graph-based approach.
Best regards,
Sebastian
--
dupswapdrop -- the music-dsp mailing list and website:
subscription info, FAQ, source code archive, list archive, book r
On Thu, 25 Nov 2010 06:51:03 +0100
"Didier Dambrin" wrote:
> IMHO "finding loop points" is the wrong problem to solve, it's better to
> "make something loop" instead, as (ideally) you're only gonna find the least
> bad loop points, nothing guarantees that there's anything loopable.
> I would us
12 matches
Mail list logo
