On Thu, 2008-10-23 at 02:16 -0400, Hector Centeno wrote:
> Hello,
> 
> I just worked on a project that involved recording several tracks of
> sound synthesized by Csound in realtime (tried both official 5.09 and
> CVS build) plus ambisonic ladspa panners, ambdec (ambisonic decoder)
> and jconv (convolution application). I started this project using
> Ubuntu Studio Linux and ended it with OpenSuse (both using their
> respective RT kernels and getting same problems with both). It became
> a very unstable combination since every time I stopped Csound,
> randomly Ardour would disconnect from jack or jack would crash, and
> then I was unable to make Ardour reconnect after restarting jack (it
> would complain about not being able to reconnect the ports). It was
> happening so regularly that I had ready on my desktop a couple of
> scripts to restart everything.
> 
> Is there anything I could do to avoid this? Is it Csounds fault? Is it
> my system? Jack is running like this: jackd -R -P60 -p1024 -t2000 -u
> -dfreebob -r48000 -p1024 -n3 -D (using a Edirol FA-101). Could this be
> a realtime priorities issue? I installed the rtirq script by Rui Nuno
> Capela tunned to prioritize the firewire ports and made sure Jack is
> running at a lower priority (firewire is at 70). Jack's version is
> 0.109.2 and Ardour's is 2.5.

Some of your instability probably comes from JACK 0.109.2 (not all of
it, but some). There will be a new release out very soon which will fix
the JACK-contributed portion. If you feel comfortable doing it, then you
can use JACK from svn already.

I repeat what I have said so often: there is almost never any reason for
users to use the -P flag to JACK. Unless you are working on a special
system, just leave JACK to pick priorities. 

--p

On Thu, 2008-10-23 at 03:00 -0400, Hector Centeno wrote:
> Thanks Paul,
> 
> I did the priority setting following someone else's advice on setting
> the rtirq script and jack. I'll try taking it out.
that won't fix your problems. its just general advice.

> 
> I tried jack from SVN a few weeks ago and had a few crashes too... but
> maybe it was caused by the fact that I installed it on top of the
> already installed official Jack from Ubuntu (I was a bit lazy to deal
> with the dependency mess). I'll give it a better try.

its fine to install it over the top, as long as you compile it
with ./configure --prefix=/usr

if you get crashes with it, i want to know. IRC is most convenient, but
email will do.

--p

Hector Centeno wrote:
> Thanks Paul,
> 
> I did the priority setting following someone else's advice on setting
> the rtirq script and jack. I'll try taking it out.
> 
> I tried jack from SVN a few weeks ago and had a few crashes too... but
> maybe it was caused by the fact that I installed it on top of the
> already installed official Jack from Ubuntu (I was a bit lazy to deal
> with the dependency mess). I'll give it a better try.

for a brief description of the problem (and a brutal approach to its
solution), see
http://subversion.ffado.org/wiki/AvoidingParallelInstallations

best,

jörn


-- 
Jörn Nettingsmeier

Verantwortlicher für Veranstaltungstechnik

Audio and event engineer
Ambisonic surround recordings

nettings@stackingdwarves.net
+49 177 7937487

Hello there,

Just out of interest, did this work? Or did you manage to fix it another 
way? I was just about to email the list about similar issues (Csound 
crashing Ardour/Jack) and I ran across this thread.

Thanks,

Joe

Hector Centeno wrote:
> Thanks Paul,
> 
> I did the priority setting following someone else's advice on setting
> the rtirq script and jack. I'll try taking it out.
> 
> I tried jack from SVN a few weeks ago and had a few crashes too... but
> maybe it was caused by the fact that I installed it on top of the
> already installed official Jack from Ubuntu (I was a bit lazy to deal
> with the dependency mess). I'll give it a better try.
> 
> 
> Cheers!
> 
> 
> Hector
> 
> 
> 
> On Thu, Oct 23, 2008 at 2:30 AM, Paul Davis  wrote:
>> On Thu, 2008-10-23 at 02:16 -0400, Hector Centeno wrote:
>>> Hello,
>>>
>>> I just worked on a project that involved recording several tracks of
>>> sound synthesized by Csound in realtime (tried both official 5.09 and
>>> CVS build) plus ambisonic ladspa panners, ambdec (ambisonic decoder)
>>> and jconv (convolution application). I started this project using
>>> Ubuntu Studio Linux and ended it with OpenSuse (both using their
>>> respective RT kernels and getting same problems with both). It became
>>> a very unstable combination since every time I stopped Csound,
>>> randomly Ardour would disconnect from jack or jack would crash, and
>>> then I was unable to make Ardour reconnect after restarting jack (it
>>> would complain about not being able to reconnect the ports). It was
>>> happening so regularly that I had ready on my desktop a couple of
>>> scripts to restart everything.
>>>
>>> Is there anything I could do to avoid this? Is it Csounds fault? Is it
>>> my system? Jack is running like this: jackd -R -P60 -p1024 -t2000 -u
>>> -dfreebob -r48000 -p1024 -n3 -D (using a Edirol FA-101). Could this be
>>> a realtime priorities issue? I installed the rtirq script by Rui Nuno
>>> Capela tunned to prioritize the firewire ports and made sure Jack is
>>> running at a lower priority (firewire is at 70). Jack's version is
>>> 0.109.2 and Ardour's is 2.5.
>> Some of your instability probably comes from JACK 0.109.2 (not all of
>> it, but some). There will be a new release out very soon which will fix
>> the JACK-contributed portion. If you feel comfortable doing it, then you
>> can use JACK from svn already.
>>
>> I repeat what I have said so often: there is almost never any reason for
>> users to use the -P flag to JACK. Unless you are working on a special
>> system, just leave JACK to pick priorities.
>>
>> --p
>>
>>
>>
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

-- 
Joseph Sanger

Blueberry Eikaiwa
www.bbeikaiwa.com
joe@bbeikaiwa.com

Hi there Hector,

Many thanks! I'll check this out.

Just for anyone who's interested:

I spent last night on a sort of "there's got to be an easier way" 
project; I've been experimenting with the API and made two instances of 
csound, one of which contains the actual sound-making csound code and 
sends via chnset and can be stopped and started for recompiling etc., 
the other of which is always on and always connected to jack and gets 
audio from chnget. The API simply copies audio from one channel to the 
other every ksmps.

To my surprise it works and means I don't have to disconnect / reconnect 
to Jack, and in fact I can keep complex connections, but it would be 
much simpler if Jack worked without hanging; however it means I can wait 
for the next official Jack release without playing with CVS too much.

Thanks again,

Joe

Hector Centeno wrote:
> Hello Joe,
> 
> The discussion about this issue continued in the Ardour list and
> that's why the solution to this problem didn't make it to this list.
> You can read the whole thread here:
> 
> http://tinyurl.com/5ntyr8
> 
> Basically it seems that installing Jack from CVS solves the problem,
> I've done some testing and seems to help.
> 
> Cheers,
> 
> Hector
> 
> 
> On Sat, Nov 1, 2008 at 10:59 PM, Joseph Sanger  wrote:
>> Hello there,
>>
>> Just out of interest, did this work? Or did you manage to fix it another
>> way? I was just about to email the list about similar issues (Csound
>> crashing Ardour/Jack) and I ran across this thread.
>>
>> Thanks,
>>
>> Joe
>>
>> Hector Centeno wrote:
>>> Thanks Paul,
>>>
>>> I did the priority setting following someone else's advice on setting
>>> the rtirq script and jack. I'll try taking it out.
>>>
>>> I tried jack from SVN a few weeks ago and had a few crashes too... but
>>> maybe it was caused by the fact that I installed it on top of the
>>> already installed official Jack from Ubuntu (I was a bit lazy to deal
>>> with the dependency mess). I'll give it a better try.
>>>
>>>
>>> Cheers!
>>>
>>>
>>> Hector
>>>
>>>
>>>
>>> On Thu, Oct 23, 2008 at 2:30 AM, Paul Davis 
>>> wrote:
>>>> On Thu, 2008-10-23 at 02:16 -0400, Hector Centeno wrote:
>>>>> Hello,
>>>>>
>>>>> I just worked on a project that involved recording several tracks of
>>>>> sound synthesized by Csound in realtime (tried both official 5.09 and
>>>>> CVS build) plus ambisonic ladspa panners, ambdec (ambisonic decoder)
>>>>> and jconv (convolution application). I started this project using
>>>>> Ubuntu Studio Linux and ended it with OpenSuse (both using their
>>>>> respective RT kernels and getting same problems with both). It became
>>>>> a very unstable combination since every time I stopped Csound,
>>>>> randomly Ardour would disconnect from jack or jack would crash, and
>>>>> then I was unable to make Ardour reconnect after restarting jack (it
>>>>> would complain about not being able to reconnect the ports). It was
>>>>> happening so regularly that I had ready on my desktop a couple of
>>>>> scripts to restart everything.
>>>>>
>>>>> Is there anything I could do to avoid this? Is it Csounds fault? Is it
>>>>> my system? Jack is running like this: jackd -R -P60 -p1024 -t2000 -u
>>>>> -dfreebob -r48000 -p1024 -n3 -D (using a Edirol FA-101). Could this be
>>>>> a realtime priorities issue? I installed the rtirq script by Rui Nuno
>>>>> Capela tunned to prioritize the firewire ports and made sure Jack is
>>>>> running at a lower priority (firewire is at 70). Jack's version is
>>>>> 0.109.2 and Ardour's is 2.5.
>>>> Some of your instability probably comes from JACK 0.109.2 (not all of
>>>> it, but some). There will be a new release out very soon which will fix
>>>> the JACK-contributed portion. If you feel comfortable doing it, then you
>>>> can use JACK from svn already.
>>>>
>>>> I repeat what I have said so often: there is almost never any reason for
>>>> users to use the -P flag to JACK. Unless you are working on a special
>>>> system, just leave JACK to pick priorities.
>>>>
>>>> --p
>>>>
>>>>
>>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>> --
>> Joseph Sanger
>>
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>> joe@bbeikaiwa.com
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

-- 
Joseph Sanger

Blueberry Eikaiwa
www.bbeikaiwa.com
joe@bbeikaiwa.com

Thank you Hector, that's a really good article. It throws a lot of light 
onto a seemingly obscure feature.

Joe

Hector Centeno wrote:
> Joe,
> 
> You might also want to check Qjackctl's Patchbay. I didn't understand
> the usefulness of this feature until I read this article:
> http://www.rncbc.org/drupal/node/76 It keeps your connections
> persistent even if the applications close and reopen and you can save
> them as presets.
> 
> Cheers,
> 
> Hector
> 
> 
> On Sun, Nov 2, 2008 at 7:46 PM, Joseph Sanger  wrote:
>> Hi there Hector,
>>
>> Many thanks! I'll check this out.
>>
>> Just for anyone who's interested:
>>
>> I spent last night on a sort of "there's got to be an easier way" project;
>> I've been experimenting with the API and made two instances of csound, one
>> of which contains the actual sound-making csound code and sends via chnset
>> and can be stopped and started for recompiling etc., the other of which is
>> always on and always connected to jack and gets audio from chnget. The API
>> simply copies audio from one channel to the other every ksmps.
>>
>> To my surprise it works and means I don't have to disconnect / reconnect to
>> Jack, and in fact I can keep complex connections, but it would be much
>> simpler if Jack worked without hanging; however it means I can wait for the
>> next official Jack release without playing with CVS too much.
>>
>> Thanks again,
>>
>> Joe
>>
>> Hector Centeno wrote:
>>> Hello Joe,
>>>
>>> The discussion about this issue continued in the Ardour list and
>>> that's why the solution to this problem didn't make it to this list.
>>> You can read the whole thread here:
>>>
>>> http://tinyurl.com/5ntyr8
>>>
>>> Basically it seems that installing Jack from CVS solves the problem,
>>> I've done some testing and seems to help.
>>>
>>> Cheers,
>>>
>>> Hector
>>>
>>>
>>> On Sat, Nov 1, 2008 at 10:59 PM, Joseph Sanger  wrote:
>>>> Hello there,
>>>>
>>>> Just out of interest, did this work? Or did you manage to fix it another
>>>> way? I was just about to email the list about similar issues (Csound
>>>> crashing Ardour/Jack) and I ran across this thread.
>>>>
>>>> Thanks,
>>>>
>>>> Joe
>>>>
>>>> Hector Centeno wrote:
>>>>> Thanks Paul,
>>>>>
>>>>> I did the priority setting following someone else's advice on setting
>>>>> the rtirq script and jack. I'll try taking it out.
>>>>>
>>>>> I tried jack from SVN a few weeks ago and had a few crashes too... but
>>>>> maybe it was caused by the fact that I installed it on top of the
>>>>> already installed official Jack from Ubuntu (I was a bit lazy to deal
>>>>> with the dependency mess). I'll give it a better try.
>>>>>
>>>>>
>>>>> Cheers!
>>>>>
>>>>>
>>>>> Hector
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Oct 23, 2008 at 2:30 AM, Paul Davis 
>>>>> wrote:
>>>>>> On Thu, 2008-10-23 at 02:16 -0400, Hector Centeno wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I just worked on a project that involved recording several tracks of
>>>>>>> sound synthesized by Csound in realtime (tried both official 5.09 and
>>>>>>> CVS build) plus ambisonic ladspa panners, ambdec (ambisonic decoder)
>>>>>>> and jconv (convolution application). I started this project using
>>>>>>> Ubuntu Studio Linux and ended it with OpenSuse (both using their
>>>>>>> respective RT kernels and getting same problems with both). It became
>>>>>>> a very unstable combination since every time I stopped Csound,
>>>>>>> randomly Ardour would disconnect from jack or jack would crash, and
>>>>>>> then I was unable to make Ardour reconnect after restarting jack (it
>>>>>>> would complain about not being able to reconnect the ports). It was
>>>>>>> happening so regularly that I had ready on my desktop a couple of
>>>>>>> scripts to restart everything.
>>>>>>>
>>>>>>> Is there anything I could do to avoid this? Is it Csounds fault? Is it
>>>>>>> my system? Jack is running like this: jackd -R -P60 -p1024 -t2000 -u
>>>>>>> -dfreebob -r48000 -p1024 -n3 -D (using a Edirol FA-101). Could this be
>>>>>>> a realtime priorities issue? I installed the rtirq script by Rui Nuno
>>>>>>> Capela tunned to prioritize the firewire ports and made sure Jack is
>>>>>>> running at a lower priority (firewire is at 70). Jack's version is
>>>>>>> 0.109.2 and Ardour's is 2.5.
>>>>>> Some of your instability probably comes from JACK 0.109.2 (not all of
>>>>>> it, but some). There will be a new release out very soon which will fix
>>>>>> the JACK-contributed portion. If you feel comfortable doing it, then
>>>>>> you
>>>>>> can use JACK from svn already.
>>>>>>
>>>>>> I repeat what I have said so often: there is almost never any reason
>>>>>> for
>>>>>> users to use the -P flag to JACK. Unless you are working on a special
>>>>>> system, just leave JACK to pick priorities.
>>>>>>
>>>>>> --p
>>>>>>
>>>>>>
>>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>> --
>>>> Joseph Sanger
>>>>
>>>> Blueberry Eikaiwa
>>>> www.bbeikaiwa.com
>>>> joe@bbeikaiwa.com
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>> --
>> Joseph Sanger
>>
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>> joe@bbeikaiwa.com
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

-- 
Joseph Sanger

Blueberry Eikaiwa
www.bbeikaiwa.com
joe@bbeikaiwa.com