<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#333399">
<br>
<br>
sara lidgey wrote:
<blockquote id="mid_659272_44217_qm_web35715_mail_mud_yahoo_com"
cite="mid:659272.44217.qm@web35715.mail.mud.yahoo.com" type="cite">I
deactivated the channels that I'm not using (at the moment) by
right-clicking on the channel and un-checking "active". This did
nothing to help.<br>
Then I muted all the regions in these channels and that seems to have
solved the problem for now.<br>
<br>
I am using ardour2-2.1-1.fc7.ccrma but this session was started in an
older version of ardour. Could that be an issue? As noted in an
earlier post, I have another session on the same machine that has 63
channels at 96kHz that plays with few errors (I get that error once in
a while). This second session was has always existed in Ardour2.<br>
--S<br>
<br>
<b><i>Martin Lynch <a class="moz-txt-link-rfc2396E" href="mailto:martin.lynch@shaw.ca"><martin.lynch@shaw.ca></a></i></b> wrote:
<blockquote id="StationeryCiteGenerated_1" class="replbq"
style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">
<pre wrap="">Am Donnerstag, 25. Oktober 2007 schrieb sara lidgey:
</pre>
<blockquote id="StationeryCiteGenerated_2" type="cite"
style="font-style: italic; color: rgb(51, 51, 153);">
<pre wrap=""><span class="moz-txt-citetags">> </span>OK. I'm down to 17 active tracks and the error still happens constantly.
<span class="moz-txt-citetags">> </span>Is there something we're missing? Are the tracks really deactivated?... I
<span class="moz-txt-citetags">> </span>think something is wrong with this session. I have another 3 minute, 96kHz
<span class="moz-txt-citetags">> </span>session with 63 active tracks that plays through without errors.
</pre>
</blockquote>
<pre wrap=""><!----> I have the feeling that ardour (at least in 0.99.X that I am using) still streams the tracks unless the regions are muted (even though the channel is already muted and inactive). Maybe that is happening here too. Try muting the regions that are not played... Arnold <div
class="moz-txt-sig"> I had the exact same problem with Ardour 0.99, and I was only using 4 tracks on a RAID 0 array comprised of 2 Seagate SATA 320GB drives at 7200 RPM with Ardour running on a 3
drive! Drove me absolutely nuts, as the error message couldn't possibly have been true. The problem went away once I upgraded to Ardour 2.0... </div></pre>
begin:vcard<br>
fn:Martin Lynch<br>
n:Lynch;Martin<br>
version:2.1<br>
end:vcard<br>
<br>
_______________________________________________<br>
Ardour-Users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:ardour-users@lists.ardour.org">ardour-users@lists.ardour.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org">http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org</a><br>
</blockquote>
<br>
<p> </p>
<hr size="1">Be smarter than spam. See how smart SpamGuard is at
giving junk email the boot with the <a moz-do-not-send="true"
href="http://us.rd.yahoo.com/evt=40705/*http://mrd.mail.yahoo.com/try_beta?.intl=ca"><b>All-new
Yahoo! Mail </b></a> </blockquote>
Well, in my case, the tracks I'd recorded in Ardour 0.99 that had been
having that same error work error free in 2.0 - in fact, I've never
gotten that error since upgrading and used to get it all the time. As
an aside, my neighbours are much relieved since my strings of profanity
have reduced 78% since upgrading...<br>
<br>
One thing I should note tho: at the same time I upgraded from Ubuntu
Feisty to Gutsy Real-time, so maybe that had something to do with it -
the errors certainly weren't a function of my hardware.<br>
<br>
Could it be that you have many multiple takes on each track? Maybe
cleaning up some of the takes you know you won't be using will help -
just a thought...<br>
</body>
</html>