<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.audio.ecasound.general">
    <title>gmane.comp.audio.ecasound.general</title>
    <link>http://blog.gmane.org/gmane.comp.audio.ecasound.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4261"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4258"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4256"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4250"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4246"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4244"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4238"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4237"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4226"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4225"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4224"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4223"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4222"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4215"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4208"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4207"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4205"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4194"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4193"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4183"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4261">
    <title>ecasound 2.9.0rc1</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4261</link>
    <description>&lt;pre&gt;Hello,

somewhat faster than planned, I'm now facing a move (to a new apartment)
next month. That means I'm seriously running of development time for 2.9.0 
in May-June timeframe, so I'd really like to push 2.9.0 (or maybe 3.0.0, 
haven't decided yet) out as soon as possible. Once I need to tear down my 
home network, servers, home studio stuff, etc and pack for move, who knows 
when I'm back online. :P I do hate moving, but here's hoping the next 
place will last until retirement. ;)

So here's the first release candidate:
http://ecasound.seul.org/download/snapshots/ecasound-2.8.1+dev-20120522.tar.gz

This tarball will go out as 2.9.0, EXCEPT for two fixes:

- the etd/etm perf issue reported by S.Massy
- segfault with cop-add'ing a lot of etd (from S.Massy as well)

If all goes well, no other changes are needed. But do not stop reporting 
errors...I'll prioritize issues if/when they appear. But as of now, the 
two above things are the only two things severe enough not to make a 
release.

------------------&lt;/pre&gt;</description>
    <dc:creator>Kai Vehmanen</dc:creator>
    <dc:date>2012-05-22T18:59:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4258">
    <title>Bug report: etm consumes too much CPU</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4258</link>
    <description>&lt;pre&gt;Hello,

Within the context of investigating ways to perform latency compensation
in nama, I ran the following test. I created a chain setup with a
hundred chains with rtnull at either end and a delay op on each,
either etd or etm. With etd, I only get a slight overhead (about 3% on
my 2.26ghz dual-core processor), while etm goes right through the roof
and has tonnes of xruns. I figure that can't be right. Please find the
test ecs  files attached.

Cheers,
S.M.
&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-05-20T02:51:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4256">
    <title>torture-testing -z:nodb scenarios</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4256</link>
    <description>&lt;pre&gt;Hi,

I've seen many post here about enabling/disabling double buffering and 
I'm still confused about what can go wrong with -z:nodb set.

I've been writing an Front End to Ecasound for about 8 years (and 
therefore running on a regular basis as I test new features). It's a 
'Jack Only' program. So everything I say pertains to Ecasound/Jack.

I'm currently running ecasound v2.8.1 but have not had any unusual 
behavior the whole 8 years of testing my front end with prior versions 
of ecasound with -z:nodb set.

I need to say several things. First, I have the most well tuned system. 
I run Fedora + CCRMA and that addresses just about any issue necessary 
to allow for most well tuned system for audio work. I also run Jack and 
Ecasound in 'Realtime Mode'. Also... the 'Recording Hard Drive' is 
separate so that the only Input/Output is from Ecasound (all System 
Activity happens on the other Hard Drive).

So far, I've not seen anything unusual with normal use. What kinds of 
things could go wrong by using -z:nod&lt;/pre&gt;</description>
    <dc:creator>linux media 4</dc:creator>
    <dc:date>2012-05-19T23:00:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4250">
    <title>analyselv2</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4250</link>
    <description>&lt;pre&gt;Hello,

With LV2 support now present in ecasound, and hence in nama, I have
found out that the utilities describing the plugins aren't very friendly
to the human reader with their long URI and properties strings. So after
some frustrating time, I finally decided to bite the bullet and write
some ugly code to hopefully make the layout of lv2 plugins more
intelligible at a glance. The result is analyselv2, which I attach to
this message. Right now it will:
- Take a plugin URI (obtained using lv2-register in ecasound,
  find_effects from nama, or lv2ls from the shell) and output plugin
  information closely resembling that of analyseplugin.
- If the string is just alphanumeric, it will perform a search on the
  list of plugins installed and either display the info for the plugin
  if a single match occurs or return the URIs of matching plugins.

You need the lv2info and lv2ls utilities installed in your $PATH. to
use, rename it to analyselv2 and make it executable. Please let me know
if you find this useful so &lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-05-18T23:28:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4246">
    <title>Double-buffering and audio</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4246</link>
    <description>&lt;pre&gt;Hello,

When double-buffering is enabled, if one issues stop and start, there is an
audible "gap" in the audio, i.e some samples are never played back. Is
that a bug or a feature? Which leads me to ask... When I issue getpos,
what does the number reflect? Is it more or less what I'm hearing, give
or take a jack period or an internal buffer, or is it where the read
pointer is at in the audio files? Does double-buffeering affect this?

Cheers,
S.M.
&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-05-12T23:27:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4244">
    <title>Bug report: etd's buffer isn't flushed on engine stop</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4244</link>
    <description>&lt;pre&gt;Hello,

When stopping the engine the delay buffer doesn't get flushed, resulting
in the audio in the same buffer being played back on restart, even when
the playhead has been moved. The buffer should be cleared and effect
reset so that it might behave as expected.

Cheers,
S.M.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ecasound-list mailing list
Ecasound-list&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list

&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-05-12T20:59:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4238">
    <title>Bug report: segfault, etd, time sensitive operations</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4238</link>
    <description>&lt;pre&gt;Hello,

Context:
In the process of adding latency compensation to nama, we are employing
the etd chain-op to create artificial latency so that all tracks in a
chain-setup will be synchronised. The end result is that, once relative
latencies are calculated, we add etd ops where needed with the following
parameters: -etd:x,0,1,100,100, where x substitutes for the required
amount of added latency.

It seems, however, that aadding many such ops in a short period of time
causes ecasound to segfault. Here is the backtrace:
#0  0x0000000000566822 in SAMPLE_ITERATOR_CHANNEL::begin (this=0x7fffd8f60358,
    channel=0) at samplebuffer_iterators.cpp:68
#1  0x0000000000519f0c in EFFECT_DELAY::process (this=0x7fffd8f60330)
    at audiofx_timebased.cpp:209
#2  0x00000000004bebde in CHAIN::process (this=0x7fffd8002e30)
    at eca-chain.cpp:825
#3  0x000000000056082c in ECA_ENGINE::process_chains (this=0x7fffd8012c80)
    at eca-engine.cpp:1699
#4  0x00000000005653c2 in ECA_ENGINE::engine_iteration (this=0x7fffd8012c80)
   &lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-05-10T19:45:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4237">
    <title>[PATCH] ecasound.el: fix regexp to match ewf files</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4237</link>
    <description>&lt;pre&gt;Hi,

attached is a trivial patch that fixes the regexp inside ecasound.el which
matches *.ewf files. The patch basically replaces "$" with "\\'" to match an
end of string instead of a newline as per the example at [0].

Also, when bytecompiling it, I get:


Though, not being an elisp expert, I can't tell what needs to be fixed.

Cheers

[0] http://www.gnu.org/software/emacs/manual/html_node/elisp/Auto-Major-Mode.html

&lt;/pre&gt;</description>
    <dc:creator>Alessandro Ghedini</dc:creator>
    <dc:date>2012-05-10T11:00:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4226">
    <title>A bug - recurring DBC_require warning</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4226</link>
    <description>&lt;pre&gt;Hello everyone!
   I recently get this quite a few times:
Warning: type DBC_REQUIRE soft-assert 'get_chain_operator() != 0' failed at -&amp;gt; 
eca-control-objects.cpp:2074 [void 
ECA_CONTROL::set_chain_operator_parameter(SAMPLE_SPECS::sample_t)]
   What can be responsible for this? I can't see a rule behind it. Sometimes it 
happens when I just change volume on a track in Nama, which should really just 
be a cop-select and change.
   Warmly yours
          Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

======      Find my music at      ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has&lt;/pre&gt;</description>
    <dc:creator>Julien Claassen</dc:creator>
    <dc:date>2012-05-07T10:06:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4225">
    <title>Double buffering</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4225</link>
    <description>&lt;pre&gt;Hi,

According to 'man ecasoundrc' the default value of the
'bmode-defaults-nonrt' setting is no double buffering.

Is there any situation that one would *not* want double
buffering?

Joel
&lt;/pre&gt;</description>
    <dc:creator>Joel Roth</dc:creator>
    <dc:date>2012-05-04T09:55:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4224">
    <title>jack_multi has mismatched sample rate</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4224</link>
    <description>&lt;pre&gt;Running JACK at frequency 44100 and connecting
a chain setup, I get this error:

Connecting chainsetup failed: "All audio objects must have
a common sampling rate; sampling rate of audio object
"jack_multi" differs from engine rate (48000 &amp;lt;-&amp;gt; 44100);
unable to continue."

This error persisted despite placing this setting 
in ecasoundrc:

default-audio-format f32_le,2,44100

This is with latest ecasound from github.

Regards,

Joel

&lt;/pre&gt;</description>
    <dc:creator>Joel Roth</dc:creator>
    <dc:date>2012-05-02T23:58:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4223">
    <title>Multitrack mode latency effects</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4223</link>
    <description>&lt;pre&gt;Hi,

I'm in the midst of working on latency compensation
for Nama, to equalize the latency in all parallel
paths in the signal processing network. 

My understanding is that in multitrack mode,
Ecasound slightly offsets the WAV inputs to keep the
signals in sync with device inputs.

My questions are:

* how is Ecasound multitrack mode compensation calculated?

* Are there any reasons to manually determine the offset?

* Is this distinct from the latency adjustment functions
  provided to jackd through the -I and -O arguments?

Thanks,

Joel
&lt;/pre&gt;</description>
    <dc:creator>Joel Roth</dc:creator>
    <dc:date>2012-05-02T21:21:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4222">
    <title>preset-register segfaults ecasound</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4222</link>
    <description>&lt;pre&gt;Hello,

Updating from commit 40c1c08f140f0eeee92ae79314688645664995fd to HEAD, I
nnow get a segfault when calling preset-register. The segfault seems to
be ladspa related, because it doesn't occur unless LADSPA_PATH is
defined. Also, a cursory backtrace in gdb shows:
#1  0x00007fffed8f206c in ?? () from /usr/lib/ladspa//ladspa_guitarix.so
#2  0x00007fffed86450a in ladspa_descriptor ()
   from /usr/lib/ladspa//ladspa_guitarix.so
#3  0x00000000004f3bd0 in eca_create_ladspa_plugins (fname=...)
    at eca-static-object-maps.cpp:625
#4  eca_import_ladspa_plugins (objmap=0x804540, reg_with_id=false)
    at eca-static-object-maps.cpp:590
...

Note that ladspa-register itself works just fine.

Cheers,
S.M.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the late&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-05-01T22:47:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4215">
    <title>-kog, -kf and LV2 testing needed</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4215</link>
    <description>&lt;pre&gt;Hi,

quite a bit of activity in the git master again, so time to upload
a snapshot tarball again.

Tarball
-------

The snapshot tarball is at (matching git HEAD 
323e08bfa80246a372be31512022591d1f38c696):
http://ecasound.seul.org/download/snapshots/ecasound-2.8.1+dev-20120429.tar.gz

Feedback needed on
------------------

I'd welcome feedback (read: "ack, nothing odd found" or "stop the press"):

   - -kog and -kf, these have been basicly rewritten (only sane
     way to close the bugs there were)

   - new configure checks for liblilv now that 0.14.2 is
     officially out
 -&amp;gt; LV2 support should be enabled by default if you
    have sufficiently new liblilv installed (newer
    than 0.5.0)

   - in general, more stress-testing for the LV2 support

Example test sequences
----------------------

Some samples to test (using alsa as outpu here, replace with JACK or a 
file, ..). All of these use the same params for swh-plugins 'analogueOsc', 
which is available both as a LADSPA and a LV2 plugin (so you can &lt;/pre&gt;</description>
    <dc:creator>Kai Vehmanen</dc:creator>
    <dc:date>2012-04-28T22:05:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4208">
    <title>Question about channel operations</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4208</link>
    <description>&lt;pre&gt;Hello,

For operations such as -chcopy, -chmove, etc. Does it replace aaaudio in
the target channel, or is it mixed in? IOW, if I want to convert a
stereo file to mono, Should I use -chmove:2,1 or -chmix:1?

Cheers,
S.M.
&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-04-21T23:18:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4207">
    <title>Fortunate discrepency in man page about -etd</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4207</link>
    <description>&lt;pre&gt;Hello,

Well, I was fumbling around in audiofx_timebased.cpp, thinking about the
best way to implement a delay-only signal when I found this on line 268:
*l.current() = (*l.current() * (1.0 - mix)) + (temp2_left * mix);
...which means that I need look no further, but write this e-mail. For
-etd, the man page reads:
"'mix-%' determines how much effected (wet) signal is mixed  to  the
original." But in fact should read something like this: "'mix-%'
expresses the mix balance between the original and delayed signal, with
0 meaning no delayed signal, 100 meaning no original signal, and 50 (the
default) achieving an equal balance."

A few further remarks:
- Even though some boundaries are set for the mix parameter in
  EFFECT_DELAY::parameter_description, they don't seem to be enforced,
  and, if a value above 100 is given, some startling results may
  occur.
- Setting a delay time of 0 causes ecasound to segfault.

Cheers,
S.M.

&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-04-21T00:57:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4205">
    <title>control oscillator samplerates?</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4205</link>
    <description>&lt;pre&gt;Hi all,

I was wondering at what rate the -kos oscillators are sampled and their
values applied to effects? Is this once per block? I ask as I found that
using an oscillator to modulate, for example, the length of delay on a
delay effect leads to some nasty scratchy-sounding artefacts, perhaps to do
with the control oscillator being sampled at a lower rate than the audio.

I would be interested in any way to erase or attenuate this problem, if
anyone knows of one.

Thanks!
J
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev_______________________________________________
Ecasound-list mailing list
Ecasound-list&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list
&lt;/pre&gt;</description>
    <dc:creator>James Mckernon</dc:creator>
    <dc:date>2012-04-18T23:37:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4194">
    <title>Ecasound aborts at the end when using ladspa</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4194</link>
    <description>&lt;pre&gt;Hello,

I'm curious, has anybody else seen this? This has been going on for me
for a very long time but I never reported it because its harmless and
might not be ecasound's fault at all. Basically, when using ladspa, on
exit, ecasound is aborted and the OS claims a double free error. Is this
ecasound, or perhaps an errant plugin causing this?

Cheers,
S.M.
&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-04-15T19:35:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4193">
    <title>Wishlist: Clip warning operator</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4193</link>
    <description>&lt;pre&gt;Hello,

Before anything else, thanks Kai for cop-bypass and for ecasound in
general. The text-based audio world is much richer for your
long-standing work!

One nice feature of sox is its clip monitoring ability: as it processes
data, it will issue a warning when a sample is clipped and a total count
of such occurences at the end. Now, ecasignalview does something like
this, but it would be useful to have an  chain op to do something
similar. In terms of nama, it would be great to have something like this
sitting in the master bus along with a limiter to prevent nasty
surprises and yet be alerted at once when going over the line, so to
speak. (A typo whilst modifying a compressor's parameters can yield
interesting and startling results!)

In general, I'd like to plant the seed for the idea of more signal
analysis and monitoring ops in ecasound. Over on the nama list, I
mentioned how I use the output from -ev to get a rough idea of how much
compression to apply on a signal, for instance. I've no idea how much&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-04-15T19:18:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4183">
    <title>Loops and latency</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4183</link>
    <description>&lt;pre&gt;Hello,

The mention of latency in the circular loop thread reminded me of a
question I've wanted to ask on this list for a while now: do loops add
latency to a chain, and, if so, is it compensated for?

Cheers,
S.M.
&lt;/pre&gt;</description>
    <dc:creator>S. Massy</dc:creator>
    <dc:date>2012-04-14T23:25:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.audio.ecasound.general/4178">
    <title>Build fails at pyecasound</title>
    <link>http://comments.gmane.org/gmane.comp.audio.ecasound.general/4178</link>
    <description>&lt;pre&gt;Hi,

I just pulled the latest Git version, and had trouble
building.  Would appreciate any suggestions.

Regards,

Joel

&lt;/pre&gt;</description>
    <dc:creator>Joel Roth</dc:creator>
    <dc:date>2012-04-14T22:19:51</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.audio.ecasound.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.audio.ecasound.general</link>
  </textinput>
</rdf:RDF>

