Discussion related to the LADI session handler

Nedko Arnaudov | 2 Jan 2011 04:44

ladish-0.3-rc20110102

I've created the ladish-0.3-rc20101231 release candidate tarball.
Download from from here:

http://ladish.org/download/
http://ladish.org/download/ladish-0.3-rc20110102.tar.bz2
http://ladish.org/download/ladish-0.3-rc20110102.tar.bz2.sig

There are two changes since ladish-0.3-rc20101231:
 * Improved the fix for #62 so that L1 apps with a2j ports
   are properly handled.
 * Implement a workaround for a jack2/jackdbus bug that happens from
   time to time. http://trac.jackaudio.org/ticket/209

The jack2/jackdbus but, when hits, causes a project unload, studio
stop, app stop or app remove to never finish. It happened to me from
time to time, with yoshimi or ardour client box not leaving the gladish
canvas.

There are no pending tickets for 0.3 so with more luck this tarball
will be identical to the 0.3 release that will follow in few days.

--

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

I've created the ladish-0.3-rc20101231 release candidate tarball.
Download from from here:

http://ladish.org/download/
http://ladish.org/download/ladish-0.3-rc20110102.tar.bz2

(Continue reading)

headers

Nedko Arnaudov | 2 Jan 2011 14:41

Re: ladish-0.3-rc20110102

Nedko Arnaudov <nedko@...> writes:

> I've created the ladish-0.3-rc20101231 release candidate tarball.

It is ladish-0.3-rc20110102, of couse. :]

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

Nedko Arnaudov <nedko@...> writes:

> I've created the ladish-0.3-rc20101231 release candidate tarball.

It is ladish-0.3-rc20110102, of couse. :]

--

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

headers

Wayne | 3 Jan 2011 19:50

Re: buggy Project file?

Il giorno sab, 18/12/2010 alle 20.41 +0200, Nedko Arnaudov ha scritto:

Wayne <wayne-6v2rLk5JRENAfugRpC6u6w@public.gmane.org> writes: > ahoy Nedko, > > i have attached a LADISH Project file to this email that was loading > well enough (there are issues with auto-starting some apps > simultaneously, still investigating, but the Project at least would load > and connect in the Room). this morning, the project fails to load, and > looking at the ladishd.log file (also attached), i cannot find the > reason. there is only one error listed in the end of the file, > indicating that the project did not load. i have tried different > Studios, new Studios, etc, all no luck. other simple Projects are > loading, just this one. > > when you have time, perhaps you could take a look at the log file > and let me know if you see something amiss? as far as i can tell, the > only thing i changed in the Project yesterday was stopping certain apps > from auto-launching (due to above mentioned separate problem). The problem is indicated by this line: Fri Dec 17 13:07:29 2010: app port "record in" with uuid 41dcdaed-7959-4721-b6f1-ae5081339693 not found in the jack graph This should really be logged as an error. I changed this in git. I've seen this bug before but it is still not clear when it happens. IIRC Frank Kober reported this some time ago, but I had the impression that the problem was caused by studio->project conversion he did. As it appears now, this is a nasty bug lurking in the ladishd code. We need a reliable steps for creating such corrupted projects. Maybe some action that is done before saving the project triggers this bug? It seems to be highly probable to be related to a2j handling, because IIRC the other report I had also had a problematic midi port. In this case the problematic port is: <port name="record in" uuid="41dcdaed-7959-4721-b6f1-ae5081339693" type="midi" direction="input" /> It is a rosegarden port.

ahoy Nedko e company,

    thanks for the reply and apologies for the holidays+travel delayed response.

    thanks to your help, the project is now loading again. the things that i had changed:

+ i edited the LADISH project file to remove all the MIDI ports in Ardour2 and RG one by one, as the project was continually failing on each MIDI port.
+ i also removed a connection that involved a removed MIDI port.
+ i updated to the latest GIT this morning 91b87783d7a68c49c01252465dfdf6cc3a63d1a7

with these changes, i was able to bring up the Project, and reconnect the MIDI connections. subsequent reloads and edits have been fine, in fact more reliable than previous versions of LADISH.

    is it possible that i saved this Project with 1 version of gladish, then updated, then tried to open it with a newer version, hence the problem with the MIDI ports?

    either way, the problem seems to have been corrected in the latest+greatest.

Please fill a ticket for this issue.

should i still file a ticket as it seems to be already resolved?

thanks, w

-- http://wayne.in-giro.org

<div>
Il giorno sab, 18/12/2010 alle 20.41 +0200, Nedko Arnaudov ha scritto:
<blockquote type="CITE">

Wayne &lt;<a href="mailto:wayne@...">wayne@...</a>&gt; writes:

&gt; ahoy Nedko,
&gt;
&gt;     i have attached a LADISH Project file to this email that was loading
&gt; well enough (there are issues with auto-starting some apps
&gt; simultaneously, still investigating, but the Project at least would load
&gt; and connect in the Room).  this morning, the project fails to load, and
&gt; looking at the ladishd.log file (also attached), i cannot find the
&gt; reason.  there is only one error listed in the end of the file,
&gt; indicating that the project did not load.  i have tried different
&gt; Studios, new Studios, etc, all no luck.  other simple Projects are
&gt; loading, just this one.
&gt;
&gt;     when you have time, perhaps you could take a look at the log file
&gt; and let me know if you see something amiss?  as far as i can tell, the
&gt; only thing i changed in the Project yesterday was stopping certain apps
&gt; from auto-launching (due to above mentioned separate problem).

The problem is indicated by this line:

Fri Dec 17 13:07:29 2010: app port "record in" with uuid 41dcdaed-7959-4721-b6f1-ae5081339693 not found in the jack graph

This should really be logged as an error. I changed this in git.

I've seen this bug before but it is still not clear when it
happens. IIRC Frank Kober reported this some time ago, but I had the
impression that the problem was caused by studio-&gt;project conversion he
did. As it appears now, this is a nasty bug lurking in the ladishd
code. We need a reliable steps for creating such corrupted
projects. Maybe some action that is done before saving the project
triggers this bug? It seems to be highly probable to be related to a2j
handling, because IIRC the other report I had also had a problematic
midi port. In this case the problematic port is:

&lt;port name="record in" uuid="41dcdaed-7959-4721-b6f1-ae5081339693" type="midi" direction="input" /&gt;

It is a rosegarden port.

</blockquote>
<br>
ahoy Nedko e company,<br><br>
&nbsp;&nbsp;&nbsp; thanks for the reply and apologies for the holidays+travel delayed response.<br><br>
&nbsp;&nbsp;&nbsp; thanks to your help, the project is now loading again.&nbsp; the things that i had changed:<br><br>
+ i edited the LADISH project file to remove all the MIDI ports in Ardour2 and RG one by one, as the project was continually failing on each MIDI port.<br>
+ i also removed a connection that involved a removed MIDI port.<br>
+ i updated to the latest GIT this morning 91b87783d7a68c49c01252465dfdf6cc3a63d1a7<br><br>
with these changes, i was able to bring up the Project, and reconnect the MIDI connections.&nbsp; subsequent reloads and edits have been fine, in fact more reliable than previous versions of LADISH.<br><br>
&nbsp;&nbsp;&nbsp; is it possible that i saved this Project with 1 version of gladish, then updated, then tried to open it with a newer version, hence the problem with the MIDI ports?<br><br>
&nbsp;&nbsp;&nbsp; either way, the problem seems to have been corrected in the latest+greatest.<br><br><blockquote type="CITE">

Please fill a ticket for this issue.

</blockquote>
&nbsp;&nbsp;&nbsp; should i still file a ticket as it seems to be already resolved?<br><br>
thanks, w<br><br><blockquote type="CITE">

</blockquote>
<br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>

--

-- 
<a href="http://wayne.in-giro.org">http://wayne.in-giro.org</a>

</td>
</tr></table>
</div>

headers

Wayne | 3 Jan 2011 19:53

Re: small bug on loading project with stopped studio...

Il giorno sab, 18/12/2010 alle 19.58 +0200, Nedko Arnaudov ha scritto:

Wayne <wayne-6v2rLk5JRENAfugRpC6u6w@public.gmane.org> writes: > seems like there is a small bug which causes the following error in > the ladishd log file when trying to load a Project in a stopped Studio: > > Tue Dec 14 15:05:42 2010: Load project request > Tue Dec 14 15:05:42 2010: ------- > Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called > for graph '/org/ladish/Room1' > Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1 > Tue Dec 14 15:05:42 2010: version 926 > Tue Dec 14 15:05:42 2010: persist: yes > Tue Dec 14 15:05:42 2010: clients: > Tue Dec 14 15:05:42 2010: connections: > Tue Dec 14 15:05:42 2010: ------- > Tue Dec 14 15:05:42 2010: Loading project > '/home/in0giro/casa/musica/progetti/in-giro/canzoni/a dim light/a dim > light 2010.001' into room 'room 01' > Tue Dec 14 15:05:42 2010: Project 'a dim light 2010.001' with uuid > 0bea1f65-99ea-4496-a87f-30e2885c984b > Tue Dec 14 15:05:42 2010: room port "audio_capture_1" with uuid > f3b66bdf-eabd-4c73-969e-852a8f18db60 > Tue Dec 14 15:05:42 2010: ERROR: callback_elstart: Cannot find > room link port. > Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called > for graph '/org/ladish/Room1' > Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1 > Tue Dec 14 15:05:42 2010: version 926 > Tue Dec 14 15:05:42 2010: persist: yes > Tue Dec 14 15:05:42 2010: clients: > Tue Dec 14 15:05:42 2010: connections: > Tue Dec 14 15:05:42 2010: ERROR: run: Project load failed. > Tue Dec 14 15:05:42 2010: load project command destructor > > i imagine we could eventually just have a dialog box that says the > studio must be started first, or even better, prevent Projects from > being loaded when a Studio is not started (similar to how one cannot > save a Studio until the Studio is started). > > let me know if i should file a ticket. I created one: http://ladish.org/ticket/128 I think the best will be to disable project load when studio is not started. In long term, maybe it should be possible to load project when studio is stopped. What others think about this?

in the long term it could be useful to edit a Project even when JACK is not running/Studio not started. however, i imagine that this would involve emulating the JACK graph somehow and it seems complicated. for now, my vote is for just disabling Project actions when a Studio is not started.

thanks, w

-- http://wayne.in-giro.org

<div>
Il giorno sab, 18/12/2010 alle 19.58 +0200, Nedko Arnaudov ha scritto:
<blockquote type="CITE">

Wayne &lt;<a href="mailto:wayne@...">wayne@...</a>&gt; writes:

&gt;     seems like there is a small bug which causes the following error in
&gt; the ladishd log file when trying to load a Project in a stopped Studio:
&gt;
&gt; Tue Dec 14 15:05:42 2010: Load project request
&gt; Tue Dec 14 15:05:42 2010: -------
&gt; Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called
&gt; for graph '/org/ladish/Room1'
&gt; Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1
&gt; Tue Dec 14 15:05:42 2010:   version 926
&gt; Tue Dec 14 15:05:42 2010:   persist: yes
&gt; Tue Dec 14 15:05:42 2010:   clients:
&gt; Tue Dec 14 15:05:42 2010:   connections:
&gt; Tue Dec 14 15:05:42 2010: -------
&gt; Tue Dec 14 15:05:42 2010: Loading project
&gt; '/home/in0giro/casa/musica/progetti/in-giro/canzoni/a dim light/a dim
&gt; light 2010.001' into room 'room 01'
&gt; Tue Dec 14 15:05:42 2010: Project 'a dim light 2010.001' with uuid
&gt; 0bea1f65-99ea-4496-a87f-30e2885c984b
&gt; Tue Dec 14 15:05:42 2010: room port "audio_capture_1" with uuid
&gt; f3b66bdf-eabd-4c73-969e-852a8f18db60
&gt; Tue Dec 14 15:05:42 2010: ERROR: callback_elstart: Cannot find
&gt; room link port.
&gt; Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called
&gt; for graph '/org/ladish/Room1'
&gt; Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1
&gt; Tue Dec 14 15:05:42 2010:   version 926
&gt; Tue Dec 14 15:05:42 2010:   persist: yes
&gt; Tue Dec 14 15:05:42 2010:   clients:
&gt; Tue Dec 14 15:05:42 2010:   connections:
&gt; Tue Dec 14 15:05:42 2010: ERROR: run: Project load failed.
&gt; Tue Dec 14 15:05:42 2010: load project command destructor
&gt;
&gt; i imagine we could eventually just have a dialog box that says the
&gt; studio must be started first, or even better, prevent Projects from
&gt; being loaded when a Studio is not started (similar to how one cannot
&gt; save a Studio until the Studio is started).
&gt;
&gt;     let me know if i should file a ticket.

I created one: <a href="http://ladish.org/ticket/128">http://ladish.org/ticket/128</a>

I think the best will be to disable project load when studio is not
started. In long term, maybe it should be possible to load project when
studio is stopped. What others think about this?

</blockquote>
<br>
&nbsp;&nbsp;&nbsp; in the long term it could be useful to edit a Project even when JACK is not running/Studio not started.&nbsp; however, i imagine that this would involve emulating the JACK graph somehow and it seems complicated.&nbsp; for now, my vote is for just disabling Project actions when a Studio is not started.<br><br>
thanks, w<br><br><blockquote type="CITE">

</blockquote>
<br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>

--

-- 
<a href="http://wayne.in-giro.org">http://wayne.in-giro.org</a>

</td>
</tr></table>
</div>

headers

Wayne | 3 Jan 2011 20:18

Re: non-started Rooms?

Il giorno sab, 18/12/2010 alle 20.17 +0200, Nedko Arnaudov ha scritto:

Wayne <wayne-6v2rLk5JRENAfugRpC6u6w@public.gmane.org> writes: > ahoy all, > > possible bug here: > > after creating a simple Project in a Room with Ardour+Rosegarden > +Hydrogen, and saving the project, sometimes when opening and starting a > studio with the Room in which this Project was created, the Room, though > listed on the left panel upon Studio load, is not created on Studio > start, and thus the Project load will fail. often, but not always, > stopping the Studio, unloading it, restarting Gladish, reloading the > Studio, and starting the Studio will bring the Room back to life. i > have included the ladishd.log file below: > > Tue Dec 14 15:11:25 2010: app 'a2jmidid' (1) > Tue Dec 14 15:11:28 2010: Start studio request > Tue Dec 14 15:11:28 2010: ------- > Tue Dec 14 15:11:28 2010: Starting JACK server. > Tue Dec 14 15:11:28 2010: graph /org/ladish/Studio > Tue Dec 14 15:11:28 2010: version 177 > Tue Dec 14 15:11:28 2010: persist: yes > Tue Dec 14 15:11:28 2010: clients: > Tue Dec 14 15:11:28 2010: invisible client 'room 01', id=3, > ptr=0xd028a0% > Tue Dec 14 15:11:28 2010: uuid=0ccbf13b-6403-4937-a8a1-49382575782e > Tue Dec 14 15:11:28 2010: no interlink > Tue Dec 14 15:11:28 2010: dict: > Tue Dec 14 15:11:28 2010: key 'http://ladish.org/ns/canvas/x' > with value '1731.000000' > Tue Dec 14 15:11:28 2010: key 'http://ladish.org/ns/canvas/y' > with value '989.000000' > Tue Dec 14 15:11:28 2010: ports: > Tue Dec 14 15:11:28 2010: invisible port 'audio_capture_1', > uuid=f3b66bdf-eabd-4c73-969e-852a8f18db60, id=17, type=0x0, flags=0x1, > ptr=0xd029a0 > Tue Dec 14 15:11:28 2010: invisible port 'audio_capture_2', > uuid=2d82eed7-bd61-4e76-8210-1aac23e1d769, id=18, type=0x0, flags=0x1, > ptr=0xd02c20 > Tue Dec 14 15:11:28 2010: invisible port 'audio_capture_3', > uuid=c65026bd-f6c8-4311-a00c-58d35a07f465, id=19, type=0x0, flags=0x1, > ptr=0xd02c90 > Tue Dec 14 15:11:28 2010: invisible port 'audio_capture_4', > uuid=5d5fe203-f90f-4b90-84b8-4531ff87cd2a, id=20, type=0x0, flags=0x1, > ptr=0xd01670 > Tue Dec 14 15:11:28 2010: invisible port 'midi_capture_1', > uuid=b8c4c2c6-d44b-4f98-a691-872571025587, id=21, type=0x1, flags=0x1, > ptr=0xd01800 > Tue Dec 14 15:11:28 2010: invisible port 'midi_capture_2', > uuid=802b3e39-b717-4c8f-9190-99b04b6e7d16, id=22, type=0x1, flags=0x1, > ptr=0xd01990 > Tue Dec 14 15:11:28 2010: invisible port 'audio_playback_1', > uuid=db670a8a-c5b4-4965-a756-332fbe8dcded, id=23, type=0x0, flags=0x2, > ptr=0xd01b20 > Tue Dec 14 15:11:28 2010: invisible port 'audio_playback_2', > uuid=9499c01f-8150-440c-a7ca-65d451e59508, id=24, type=0x0, flags=0x2, > ptr=0xd01da0 > Tue Dec 14 15:11:28 2010: invisible port 'audio_playback_3', > uuid=d7022565-617f-4a12-9e21-6d480768f5b5, id=25, type=0x0, flags=0x2, > ptr=0xcfb480 > Tue Dec 14 15:11:28 2010: invisible port 'audio_playback_4', > uuid=efd3dd32-bde3-4a5c-b377-22c110d44a70, id=26, type=0x0, flags=0x2, > ptr=0xcfb610 > Tue Dec 14 15:11:28 2010: invisible port 'midi_playback_1', > uuid=cb439a96-74e6-4c60-8105-4fc35d33b9d5, id=27, type=0x1, flags=0x2, > ptr=0xcfb7a0 > Tue Dec 14 15:11:28 2010: invisible port 'midi_playback_2', > uuid=21f2812b-80e7-4fb7-b403-3ae5585854c0, id=28, type=0x1, flags=0x2, > ptr=0xcfb930 > Tue Dec 14 15:11:28 2010: invisible client 'firewire_pcm', id=4, > ptr=0xcfbae0% > Tue Dec 14 15:11:28 2010: uuid=3be3324c-036a-49cc-97ec-9f4ea1d85f32 > Tue Dec 14 15:11:28 2010: no interlink > Tue Dec 14 15:11:28 2010: dict: > Tue Dec 14 15:11:28 2010: key 'http://ladish.org/ns/canvas/x' > with value '1479.000000' > Tue Dec 14 15:11:28 2010: key 'http://ladish.org/ns/canvas/y' > with value '971.000000' > Tue Dec 14 15:11:28 2010: ports: > Tue Dec 14 15:11:28 2010: invisible port 'dev0_MicIn1 left_in', > uuid=1bd061ac-b9ab-41e7-95a5-4119edf25040, id=29, type=0x0, flags=0x12, > ptr=0xcfed10 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_MicIn1 right_in', > uuid=64b0fa5e-a336-4f84-b2ac-dd033d6266fc, id=30, type=0x0, flags=0x12, > ptr=0xcfd7e0 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_LineIn 3+4 > left_in', uuid=f051b755-2725-447d-911f-024102af2705, id=31, type=0x0, > flags=0x12, ptr=0xcfd850 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_LineIn 3+4 > right_in', uuid=1d6c9cd2-2e61-4761-85ac-a1d00a26d72a, id=32, type=0x0, > flags=0x12, ptr=0xd09d60 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_SpdifIn left_in', > uuid=a19bd802-0c3e-43ad-99d3-77c952d06188, id=33, type=0x0, flags=0x12, > ptr=0xcff050 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_SpdifIn > right_in', uuid=865d4107-eee8-4e8a-aa21-290d8f0c46ba, id=34, type=0x0, > flags=0x12, ptr=0xd02490 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_MidiPort_1_in', > uuid=aa2136d5-2243-4ae5-84e3-8b32c5f0be37, id=35, type=0x1, flags=0x12, > ptr=0xd02590 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_LineOut 1+2 > left_out', uuid=dc8a9654-6b04-490c-9829-ae13952314f4, id=36, type=0x0, > flags=0x11, ptr=0xd09830 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_LineOut 1+2 > right_out', uuid=bad1bc16-e43f-4526-a9ad-1022d3af4ee6, id=37, type=0x0, > flags=0x11, ptr=0xd098f0 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_LineOut 3+4 > left_out', uuid=ff5dc10e-c0d2-4120-82d7-da4a34b4c65a, id=38, type=0x0, > flags=0x11, ptr=0xd00020 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_LineOut 3+4 > right_out', uuid=e5158afc-4160-4547-8b9b-b09c50179442, id=39, type=0x0, > flags=0x11, ptr=0xd00110 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_SpdifOut > left_out', uuid=51bb9f36-b508-4822-a2b0-ebef2bb747f6, id=40, type=0x0, > flags=0x11, ptr=0xcf6460 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_SpdifOut > right_out', uuid=e77c3b5e-59aa-4b9b-95ac-7fcf2a0f5210, id=41, type=0x0, > flags=0x11, ptr=0xcf6560 > Tue Dec 14 15:11:28 2010: invisible port 'dev0_MidiPort_1_out', > uuid=b2dea22b-d8ad-44ea-ba3d-3d6131b33b65, id=42, type=0x1, flags=0x11, > ptr=0xcf6660 > Tue Dec 14 15:11:28 2010: invisible client 'Midi Through', id=5, > ptr=0xcfc650% > Tue Dec 14 15:11:28 2010: uuid=2f2c8e8e-7c0e-4af9-bfc7-e92aab62bb5e > Tue Dec 14 15:11:28 2010: no interlink > Tue Dec 14 15:11:28 2010: dict: > Tue Dec 14 15:11:28 2010: key 'http://ladish.org/ns/canvas/x' > with value '1198.000000' > Tue Dec 14 15:11:28 2010: key 'http://ladish.org/ns/canvas/y' > with value '949.000000' > Tue Dec 14 15:11:28 2010: ports: > Tue Dec 14 15:11:28 2010: invisible port 'Midi Through Port-0', > uuid=08371936-df46-4e17-8504-903e4db742d4, id=43, type=0x1, flags=0x12, > ptr=0xcfdab0 > Tue Dec 14 15:11:28 2010: invisible port 'Midi Through Port-0', > uuid=97272319-c8ed-427c-9259-d76c7b055aa0, id=44, type=0x1, flags=0x11, > ptr=0xcfdb70 > Tue Dec 14 15:11:28 2010: connections: > Tue Dec 14 15:11:28 2010: invisible connection > 'firewire_pcm':'dev0_MicIn1 left_in' - 'room 01':'audio_capture_1' > Tue Dec 14 15:11:28 2010: invisible connection > 'firewire_pcm':'dev0_MicIn1 right_in' - 'room 01':'audio_capture_2' > Tue Dec 14 15:11:28 2010: invisible connection > 'firewire_pcm':'dev0_MidiPort_1_in' - 'room 01':'midi_capture_1' > Tue Dec 14 15:11:28 2010: invisible connection 'room > 01':'audio_playback_1' - 'firewire_pcm':'dev0_LineOut 1+2 left_out' > Tue Dec 14 15:11:28 2010: invisible connection 'room > 01':'audio_playback_2' - 'firewire_pcm':'dev0_LineOut 1+2 right_out' > Tue Dec 14 15:11:28 2010: invisible connection 'room > 01':'midi_playback_1' - 'firewire_pcm':'dev0_MidiPort_1_out' > Tue Dec 14 15:11:30 2010: JACK server start detected. > Tue Dec 14 15:11:30 2010: Wait for JACK server start complete. > Tue Dec 14 15:11:30 2010: jack conf successfully retrieved > Tue Dec 14 15:11:30 2010: setting connection handlers for graph > '/org/ladish/Studio' > Tue Dec 14 15:11:30 2010: setting connection handlers for graph > '/org/ladish/Room1' > Tue Dec 14 15:11:30 2010: refresh_internal() called > Tue Dec 14 15:11:30 2010: clear > Tue Dec 14 15:11:30 2010: client_appeared(1, firewire_pcm) > Tue Dec 14 15:11:30 2010: client pid is 0 > Tue Dec 14 15:11:30 2010: Lookup by app uuid failed, attempting lookup > by name 'firewire_pcm' > Tue Dec 14 15:11:30 2010: found existing client > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: ladish_graph_show_client() called. > Tue Dec 14 15:11:30 2010: port_appeared(1, 1, dev0_MicIn1 left_in (out, > audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xcfed10 > Tue Dec 14 15:11:30 2010: port 0xcfed10 jack id set to 1 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 2, dev0_MicIn1 right_in (out, > audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xcfd7e0 > Tue Dec 14 15:11:30 2010: port 0xcfd7e0 jack id set to 2 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 3, dev0_LineIn 3+4 left_in > (out, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xcfd850 > Tue Dec 14 15:11:30 2010: port 0xcfd850 jack id set to 3 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 4, dev0_LineIn 3+4 right_in > (out, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xd09d60 > Tue Dec 14 15:11:30 2010: port 0xd09d60 jack id set to 4 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 5, dev0_SpdifIn left_in (out, > audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xcff050 > Tue Dec 14 15:11:30 2010: port 0xcff050 jack id set to 5 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 6, dev0_SpdifIn right_in > (out, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xd02490 > Tue Dec 14 15:11:30 2010: port 0xd02490 jack id set to 6 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 7, dev0_MidiPort_1_in (out, > midi)) > Tue Dec 14 15:11:30 2010: found existing port 0xd02590 > Tue Dec 14 15:11:30 2010: port 0xd02590 jack id set to 7 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 8, dev0_LineOut 1+2 left_out > (in, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xd09830 > Tue Dec 14 15:11:30 2010: port 0xd09830 jack id set to 8 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 9, dev0_LineOut 1+2 right_out > (in, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xd098f0 > Tue Dec 14 15:11:30 2010: port 0xd098f0 jack id set to 9 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 10, dev0_LineOut 3+4 left_out > (in, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xd00020 > Tue Dec 14 15:11:30 2010: port 0xd00020 jack id set to 10 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 11, dev0_LineOut 3+4 > right_out (in, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xd00110 > Tue Dec 14 15:11:30 2010: port 0xd00110 jack id set to 11 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 12, dev0_SpdifOut left_out > (in, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xcf6460 > Tue Dec 14 15:11:30 2010: port 0xcf6460 jack id set to 12 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 13, dev0_SpdifOut right_out > (in, audio)) > Tue Dec 14 15:11:30 2010: found existing port 0xcf6560 > Tue Dec 14 15:11:30 2010: port 0xcf6560 jack id set to 13 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: port_appeared(1, 14, dev0_MidiPort_1_out (in, > midi)) > Tue Dec 14 15:11:30 2010: found existing port 0xcf6660 > Tue Dec 14 15:11:30 2010: port 0xcf6660 jack id set to 14 > Tue Dec 14 15:11:30 2010: client jack id set to 1 > Tue Dec 14 15:11:30 2010: autorun('a2jmidid', shell, 'a2j -e') called > Tue Dec 14 15:11:30 2010: Forked to run program studio:a2jmidid pid = > 10578 > Tue Dec 14 15:11:30 2010: setting connection handlers for graph > '/org/ladish/Room1' > Tue Dec 14 15:11:30 2010: studio:a2jmidid: hardware ports export > Tue Dec 14 15:11:30 2010: studio:a2jmidid: --- enable export of hardware > ports > Tue Dec 14 15:11:30 2010: studio:a2jmidid: --- start > Tue Dec 14 15:11:30 2010: a2j bridge start detected. > Tue Dec 14 15:11:30 2010: client_appeared(2, a2j) > Tue Dec 14 15:11:30 2010: client pid is 9927 > Tue Dec 14 15:11:30 2010: found existing client > Tue Dec 14 15:11:30 2010: client jack id set to 2 > Tue Dec 14 15:11:30 2010: ladish_graph_show_client() called. > Tue Dec 14 15:11:30 2010: port_appeared(2, 15, Midi Through [14] > (capture): Midi Through Port-0 (out, midi)) > Tue Dec 14 15:11:30 2010: a2j port appeared > Tue Dec 14 15:11:30 2010: a2j: 'Midi Through':'Midi Through Port-0' (14) > Tue Dec 14 15:11:30 2010: ERROR: port_appeared: UNKNOWN ALSA > client pid > Tue Dec 14 15:11:30 2010: found existing port 0xcfdab0 > Tue Dec 14 15:11:30 2010: port 0xcfdab0 jack id set to 15 > Tue Dec 14 15:11:30 2010: client jack id set to 2 > Tue Dec 14 15:11:30 2010: port_appeared(2, 16, Midi Through [14] > (playback): Midi Through Port-0 (in, midi)) > Tue Dec 14 15:11:30 2010: a2j port appeared > Tue Dec 14 15:11:30 2010: a2j: 'Midi Through':'Midi Through Port-0' (14) > Tue Dec 14 15:11:30 2010: ERROR: port_appeared: UNKNOWN ALSA > client pid > Tue Dec 14 15:11:30 2010: found existing port 0xcfdb70 > Tue Dec 14 15:11:30 2010: port 0xcfdb70 jack id set to 16 > Tue Dec 14 15:11:30 2010: client jack id set to 2 > Tue Dec 14 15:11:39 2010: Load project request > Tue Dec 14 15:11:39 2010: ------- > Tue Dec 14 15:11:39 2010: ladish_graph_remove_hidden_objects() called > for graph '/org/ladish/Room1' > Tue Dec 14 15:11:39 2010: graph /org/ladish/Room1 > Tue Dec 14 15:11:39 2010: version 926 > Tue Dec 14 15:11:39 2010: persist: yes > Tue Dec 14 15:11:39 2010: clients: > Tue Dec 14 15:11:39 2010: connections: > Tue Dec 14 15:11:39 2010: ------- > Tue Dec 14 15:11:39 2010: Loading project > '/home/in0giro/casa/musica/progetti/in-giro/canzoni/a dim light/a dim > light 2010.001' into room 'room 01' > Tue Dec 14 15:11:39 2010: Project 'a dim light 2010.001' with uuid > 0bea1f65-99ea-4496-a87f-30e2885c984b > Tue Dec 14 15:11:39 2010: room port "audio_capture_1" with uuid > f3b66bdf-eabd-4c73-969e-852a8f18db60 > Tue Dec 14 15:11:39 2010: ERROR: callback_elstart: Cannot find > room link port. > Tue Dec 14 15:11:39 2010: ladish_graph_remove_hidden_objects() called > for graph '/org/ladish/Room1' > Tue Dec 14 15:11:39 2010: graph /org/ladish/Room1 > Tue Dec 14 15:11:39 2010: version 926 > Tue Dec 14 15:11:39 2010: persist: yes > Tue Dec 14 15:11:39 2010: clients: > Tue Dec 14 15:11:39 2010: connections: > Tue Dec 14 15:11:39 2010: ERROR: run: Project load failed. > Tue Dec 14 15:11:39 2010: load project command destructor > Tue Dec 14 15:13:40 2010: app 'a2jmidid' (1) > Tue Dec 14 15:13:40 2010: client 'firewire_pcm' (4) > Tue Dec 14 15:13:40 2010: client 'Midi Through' (5) > Tue Dec 14 15:13:53 2010: http://ladish.org/ns/canvas/x <- 1526.000000 > Tue Dec 14 15:13:53 2010: http://ladish.org/ns/canvas/y <- 1111.875000 > Tue Dec 14 15:13:53 2010: http://ladish.org/ns/canvas/x <- 1543.500000 > Tue Dec 14 15:13:53 2010: http://ladish.org/ns/canvas/y <- 1067.125000 > Tue Dec 14 15:13:55 2010: http://ladish.org/ns/canvas/x <- 1759.200000 > Tue Dec 14 15:13:55 2010: http://ladish.org/ns/canvas/y <- 1149.275000 > > > it looks like there are problems with "MIDI through port" getting > reloaded, thus causing the Room not to be created. thus, the Project > load fails. note that there is 1 Studio L0 app: a2j -e. > > let me know if this should be ticketed. Yes, please create a ticket.

http://ladish.org/ticket/161

And please, check whether it is really Midi Through that is causing this problem. It can disabled somehow, IIRC it was some kernel module or a parameter of a kernel module.

the MIDI Through ports only show up when a2j -e is started as a Studio level app. regardless, you are correct: even without MIDI Through and a2j -e being run, this problem still occurs. the latest+greatest version of LADISH gives some more error messages in the log, which i attached to the ticket. here is the relavant part i believe:

owner graph input port e59b4013-519f-46c7-9b67-0421b099a138 is linked to room output port 7eecf3d1-b2c9-4e49-ae3a-51672d95c362
Mon Jan 3 14:01:53 2011: [31mERROR: [0mjmcore_proxy_create_link: jmcore::create() failed.
Mon Jan 3 14:01:53 2011: [31mERROR: [0mcreate_port_link: jmcore_proxy_create_link() failed.
Mon Jan 3 14:01:53 2011: [31mERROR: [0mladish_room_start: Creation of room port links failed.
Mon Jan 3 14:01:53 2011: client_appeared(2, jmcore-13)
Mon Jan 3 14:01:53 2011: [31mERROR: [0mgraph_proxy_get_client_pid: GetClientPID() failed.
Mon Jan 3 14:01:53 2011: client 2 pid is unknown
Mon Jan 3 14:01:53 2011: Lookup by app uuid failed, attempting lookup by name 'jmcore-13'

peace, w

-- http://wayne.in-giro.org

<div>
Il giorno sab, 18/12/2010 alle 20.17 +0200, Nedko Arnaudov ha scritto:
<blockquote type="CITE">

Wayne &lt;<a href="mailto:wayne@...">wayne@...</a>&gt; writes:

&gt; ahoy all,
&gt;
&gt;     possible bug here:
&gt;
&gt;     after creating a simple Project in a Room with Ardour+Rosegarden
&gt; +Hydrogen, and saving the project, sometimes when opening and starting a
&gt; studio with the Room in which this Project was created, the Room, though
&gt; listed on the left panel upon Studio load, is not created on Studio
&gt; start, and thus the Project load will fail.  often, but not always,
&gt; stopping the Studio, unloading it, restarting Gladish, reloading the
&gt; Studio, and starting the Studio will bring the Room back to life.  i
&gt; have included the ladishd.log file below:
&gt;
&gt; Tue Dec 14 15:11:25 2010: app 'a2jmidid' (1)
&gt; Tue Dec 14 15:11:28 2010: Start studio request
&gt; Tue Dec 14 15:11:28 2010: -------
&gt; Tue Dec 14 15:11:28 2010: Starting JACK server.
&gt; Tue Dec 14 15:11:28 2010: graph /org/ladish/Studio
&gt; Tue Dec 14 15:11:28 2010:   version 177
&gt; Tue Dec 14 15:11:28 2010:   persist: yes
&gt; Tue Dec 14 15:11:28 2010:   clients:
&gt; Tue Dec 14 15:11:28 2010:     invisible client 'room 01', id=3,
&gt; ptr=0xd028a0%
&gt; Tue Dec 14 15:11:28 2010:     uuid=0ccbf13b-6403-4937-a8a1-49382575782e
&gt; Tue Dec 14 15:11:28 2010:     no interlink
&gt; Tue Dec 14 15:11:28 2010:       dict:
&gt; Tue Dec 14 15:11:28 2010:         key '<a href="http://ladish.org/ns/canvas/x'">http://ladish.org/ns/canvas/x'</a>
&gt; with value '1731.000000'
&gt; Tue Dec 14 15:11:28 2010:         key '<a href="http://ladish.org/ns/canvas/y'">http://ladish.org/ns/canvas/y'</a>
&gt; with value '989.000000'
&gt; Tue Dec 14 15:11:28 2010:       ports:
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_capture_1',
&gt; uuid=f3b66bdf-eabd-4c73-969e-852a8f18db60, id=17, type=0x0, flags=0x1,
&gt; ptr=0xd029a0
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_capture_2',
&gt; uuid=2d82eed7-bd61-4e76-8210-1aac23e1d769, id=18, type=0x0, flags=0x1,
&gt; ptr=0xd02c20
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_capture_3',
&gt; uuid=c65026bd-f6c8-4311-a00c-58d35a07f465, id=19, type=0x0, flags=0x1,
&gt; ptr=0xd02c90
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_capture_4',
&gt; uuid=5d5fe203-f90f-4b90-84b8-4531ff87cd2a, id=20, type=0x0, flags=0x1,
&gt; ptr=0xd01670
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'midi_capture_1',
&gt; uuid=b8c4c2c6-d44b-4f98-a691-872571025587, id=21, type=0x1, flags=0x1,
&gt; ptr=0xd01800
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'midi_capture_2',
&gt; uuid=802b3e39-b717-4c8f-9190-99b04b6e7d16, id=22, type=0x1, flags=0x1,
&gt; ptr=0xd01990
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_playback_1',
&gt; uuid=db670a8a-c5b4-4965-a756-332fbe8dcded, id=23, type=0x0, flags=0x2,
&gt; ptr=0xd01b20
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_playback_2',
&gt; uuid=9499c01f-8150-440c-a7ca-65d451e59508, id=24, type=0x0, flags=0x2,
&gt; ptr=0xd01da0
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_playback_3',
&gt; uuid=d7022565-617f-4a12-9e21-6d480768f5b5, id=25, type=0x0, flags=0x2,
&gt; ptr=0xcfb480
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'audio_playback_4',
&gt; uuid=efd3dd32-bde3-4a5c-b377-22c110d44a70, id=26, type=0x0, flags=0x2,
&gt; ptr=0xcfb610
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'midi_playback_1',
&gt; uuid=cb439a96-74e6-4c60-8105-4fc35d33b9d5, id=27, type=0x1, flags=0x2,
&gt; ptr=0xcfb7a0
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'midi_playback_2',
&gt; uuid=21f2812b-80e7-4fb7-b403-3ae5585854c0, id=28, type=0x1, flags=0x2,
&gt; ptr=0xcfb930
&gt; Tue Dec 14 15:11:28 2010:     invisible client 'firewire_pcm', id=4,
&gt; ptr=0xcfbae0%
&gt; Tue Dec 14 15:11:28 2010:     uuid=3be3324c-036a-49cc-97ec-9f4ea1d85f32
&gt; Tue Dec 14 15:11:28 2010:     no interlink
&gt; Tue Dec 14 15:11:28 2010:       dict:
&gt; Tue Dec 14 15:11:28 2010:         key '<a href="http://ladish.org/ns/canvas/x'">http://ladish.org/ns/canvas/x'</a>
&gt; with value '1479.000000'
&gt; Tue Dec 14 15:11:28 2010:         key '<a href="http://ladish.org/ns/canvas/y'">http://ladish.org/ns/canvas/y'</a>
&gt; with value '971.000000'
&gt; Tue Dec 14 15:11:28 2010:       ports:
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_MicIn1 left_in',
&gt; uuid=1bd061ac-b9ab-41e7-95a5-4119edf25040, id=29, type=0x0, flags=0x12,
&gt; ptr=0xcfed10
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_MicIn1 right_in',
&gt; uuid=64b0fa5e-a336-4f84-b2ac-dd033d6266fc, id=30, type=0x0, flags=0x12,
&gt; ptr=0xcfd7e0
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_LineIn 3+4
&gt; left_in', uuid=f051b755-2725-447d-911f-024102af2705, id=31, type=0x0,
&gt; flags=0x12, ptr=0xcfd850
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_LineIn 3+4
&gt; right_in', uuid=1d6c9cd2-2e61-4761-85ac-a1d00a26d72a, id=32, type=0x0,
&gt; flags=0x12, ptr=0xd09d60
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_SpdifIn left_in',
&gt; uuid=a19bd802-0c3e-43ad-99d3-77c952d06188, id=33, type=0x0, flags=0x12,
&gt; ptr=0xcff050
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_SpdifIn
&gt; right_in', uuid=865d4107-eee8-4e8a-aa21-290d8f0c46ba, id=34, type=0x0,
&gt; flags=0x12, ptr=0xd02490
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_MidiPort_1_in',
&gt; uuid=aa2136d5-2243-4ae5-84e3-8b32c5f0be37, id=35, type=0x1, flags=0x12,
&gt; ptr=0xd02590
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_LineOut 1+2
&gt; left_out', uuid=dc8a9654-6b04-490c-9829-ae13952314f4, id=36, type=0x0,
&gt; flags=0x11, ptr=0xd09830
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_LineOut 1+2
&gt; right_out', uuid=bad1bc16-e43f-4526-a9ad-1022d3af4ee6, id=37, type=0x0,
&gt; flags=0x11, ptr=0xd098f0
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_LineOut 3+4
&gt; left_out', uuid=ff5dc10e-c0d2-4120-82d7-da4a34b4c65a, id=38, type=0x0,
&gt; flags=0x11, ptr=0xd00020
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_LineOut 3+4
&gt; right_out', uuid=e5158afc-4160-4547-8b9b-b09c50179442, id=39, type=0x0,
&gt; flags=0x11, ptr=0xd00110
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_SpdifOut
&gt; left_out', uuid=51bb9f36-b508-4822-a2b0-ebef2bb747f6, id=40, type=0x0,
&gt; flags=0x11, ptr=0xcf6460
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_SpdifOut
&gt; right_out', uuid=e77c3b5e-59aa-4b9b-95ac-7fcf2a0f5210, id=41, type=0x0,
&gt; flags=0x11, ptr=0xcf6560
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'dev0_MidiPort_1_out',
&gt; uuid=b2dea22b-d8ad-44ea-ba3d-3d6131b33b65, id=42, type=0x1, flags=0x11,
&gt; ptr=0xcf6660
&gt; Tue Dec 14 15:11:28 2010:     invisible client 'Midi Through', id=5,
&gt; ptr=0xcfc650%
&gt; Tue Dec 14 15:11:28 2010:     uuid=2f2c8e8e-7c0e-4af9-bfc7-e92aab62bb5e
&gt; Tue Dec 14 15:11:28 2010:     no interlink
&gt; Tue Dec 14 15:11:28 2010:       dict:
&gt; Tue Dec 14 15:11:28 2010:         key '<a href="http://ladish.org/ns/canvas/x'">http://ladish.org/ns/canvas/x'</a>
&gt; with value '1198.000000'
&gt; Tue Dec 14 15:11:28 2010:         key '<a href="http://ladish.org/ns/canvas/y'">http://ladish.org/ns/canvas/y'</a>
&gt; with value '949.000000'
&gt; Tue Dec 14 15:11:28 2010:       ports:
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'Midi Through Port-0',
&gt; uuid=08371936-df46-4e17-8504-903e4db742d4, id=43, type=0x1, flags=0x12,
&gt; ptr=0xcfdab0
&gt; Tue Dec 14 15:11:28 2010:         invisible port 'Midi Through Port-0',
&gt; uuid=97272319-c8ed-427c-9259-d76c7b055aa0, id=44, type=0x1, flags=0x11,
&gt; ptr=0xcfdb70
&gt; Tue Dec 14 15:11:28 2010:   connections:
&gt; Tue Dec 14 15:11:28 2010:     invisible connection
&gt; 'firewire_pcm':'dev0_MicIn1 left_in' - 'room 01':'audio_capture_1'
&gt; Tue Dec 14 15:11:28 2010:     invisible connection
&gt; 'firewire_pcm':'dev0_MicIn1 right_in' - 'room 01':'audio_capture_2'
&gt; Tue Dec 14 15:11:28 2010:     invisible connection
&gt; 'firewire_pcm':'dev0_MidiPort_1_in' - 'room 01':'midi_capture_1'
&gt; Tue Dec 14 15:11:28 2010:     invisible connection 'room
&gt; 01':'audio_playback_1' - 'firewire_pcm':'dev0_LineOut 1+2 left_out'
&gt; Tue Dec 14 15:11:28 2010:     invisible connection 'room
&gt; 01':'audio_playback_2' - 'firewire_pcm':'dev0_LineOut 1+2 right_out'
&gt; Tue Dec 14 15:11:28 2010:     invisible connection 'room
&gt; 01':'midi_playback_1' - 'firewire_pcm':'dev0_MidiPort_1_out'
&gt; Tue Dec 14 15:11:30 2010: JACK server start detected.
&gt; Tue Dec 14 15:11:30 2010: Wait for JACK server start complete.
&gt; Tue Dec 14 15:11:30 2010: jack conf successfully retrieved
&gt; Tue Dec 14 15:11:30 2010: setting connection handlers for graph
&gt; '/org/ladish/Studio'
&gt; Tue Dec 14 15:11:30 2010: setting connection handlers for graph
&gt; '/org/ladish/Room1'
&gt; Tue Dec 14 15:11:30 2010: refresh_internal() called
&gt; Tue Dec 14 15:11:30 2010: clear
&gt; Tue Dec 14 15:11:30 2010: client_appeared(1, firewire_pcm)
&gt; Tue Dec 14 15:11:30 2010: client pid is 0
&gt; Tue Dec 14 15:11:30 2010: Lookup by app uuid failed, attempting lookup
&gt; by name 'firewire_pcm'
&gt; Tue Dec 14 15:11:30 2010: found existing client
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: ladish_graph_show_client() called.
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 1, dev0_MicIn1 left_in (out,
&gt; audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcfed10
&gt; Tue Dec 14 15:11:30 2010: port 0xcfed10 jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 2, dev0_MicIn1 right_in (out,
&gt; audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcfd7e0
&gt; Tue Dec 14 15:11:30 2010: port 0xcfd7e0 jack id set to 2
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 3, dev0_LineIn 3+4 left_in
&gt; (out, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcfd850
&gt; Tue Dec 14 15:11:30 2010: port 0xcfd850 jack id set to 3
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 4, dev0_LineIn 3+4 right_in
&gt; (out, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd09d60
&gt; Tue Dec 14 15:11:30 2010: port 0xd09d60 jack id set to 4
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 5, dev0_SpdifIn left_in (out,
&gt; audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcff050
&gt; Tue Dec 14 15:11:30 2010: port 0xcff050 jack id set to 5
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 6, dev0_SpdifIn right_in
&gt; (out, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd02490
&gt; Tue Dec 14 15:11:30 2010: port 0xd02490 jack id set to 6
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 7, dev0_MidiPort_1_in (out,
&gt; midi))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd02590
&gt; Tue Dec 14 15:11:30 2010: port 0xd02590 jack id set to 7
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 8, dev0_LineOut 1+2 left_out
&gt; (in, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd09830
&gt; Tue Dec 14 15:11:30 2010: port 0xd09830 jack id set to 8
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 9, dev0_LineOut 1+2 right_out
&gt; (in, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd098f0
&gt; Tue Dec 14 15:11:30 2010: port 0xd098f0 jack id set to 9
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 10, dev0_LineOut 3+4 left_out
&gt; (in, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd00020
&gt; Tue Dec 14 15:11:30 2010: port 0xd00020 jack id set to 10
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 11, dev0_LineOut 3+4
&gt; right_out (in, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xd00110
&gt; Tue Dec 14 15:11:30 2010: port 0xd00110 jack id set to 11
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 12, dev0_SpdifOut left_out
&gt; (in, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcf6460
&gt; Tue Dec 14 15:11:30 2010: port 0xcf6460 jack id set to 12
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 13, dev0_SpdifOut right_out
&gt; (in, audio))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcf6560
&gt; Tue Dec 14 15:11:30 2010: port 0xcf6560 jack id set to 13
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: port_appeared(1, 14, dev0_MidiPort_1_out (in,
&gt; midi))
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcf6660
&gt; Tue Dec 14 15:11:30 2010: port 0xcf6660 jack id set to 14
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 1
&gt; Tue Dec 14 15:11:30 2010: autorun('a2jmidid', shell, 'a2j -e') called
&gt; Tue Dec 14 15:11:30 2010: Forked to run program studio:a2jmidid pid =
&gt; 10578
&gt; Tue Dec 14 15:11:30 2010: setting connection handlers for graph
&gt; '/org/ladish/Room1'
&gt; Tue Dec 14 15:11:30 2010: studio:a2jmidid: hardware ports export
&gt; Tue Dec 14 15:11:30 2010: studio:a2jmidid: --- enable export of hardware
&gt; ports
&gt; Tue Dec 14 15:11:30 2010: studio:a2jmidid: --- start
&gt; Tue Dec 14 15:11:30 2010: a2j bridge start detected.
&gt; Tue Dec 14 15:11:30 2010: client_appeared(2, a2j)
&gt; Tue Dec 14 15:11:30 2010: client pid is 9927
&gt; Tue Dec 14 15:11:30 2010: found existing client
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 2
&gt; Tue Dec 14 15:11:30 2010: ladish_graph_show_client() called.
&gt; Tue Dec 14 15:11:30 2010: port_appeared(2, 15, Midi Through [14]
&gt; (capture): Midi Through Port-0 (out, midi))
&gt; Tue Dec 14 15:11:30 2010: a2j port appeared
&gt; Tue Dec 14 15:11:30 2010: a2j: 'Midi Through':'Midi Through Port-0' (14)
&gt; Tue Dec 14 15:11:30 2010: ERROR: port_appeared: UNKNOWN ALSA
&gt; client pid
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcfdab0
&gt; Tue Dec 14 15:11:30 2010: port 0xcfdab0 jack id set to 15
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 2
&gt; Tue Dec 14 15:11:30 2010: port_appeared(2, 16, Midi Through [14]
&gt; (playback): Midi Through Port-0 (in, midi))
&gt; Tue Dec 14 15:11:30 2010: a2j port appeared
&gt; Tue Dec 14 15:11:30 2010: a2j: 'Midi Through':'Midi Through Port-0' (14)
&gt; Tue Dec 14 15:11:30 2010: ERROR: port_appeared: UNKNOWN ALSA
&gt; client pid
&gt; Tue Dec 14 15:11:30 2010: found existing port 0xcfdb70
&gt; Tue Dec 14 15:11:30 2010: port 0xcfdb70 jack id set to 16
&gt; Tue Dec 14 15:11:30 2010: client jack id set to 2
&gt; Tue Dec 14 15:11:39 2010: Load project request
&gt; Tue Dec 14 15:11:39 2010: -------
&gt; Tue Dec 14 15:11:39 2010: ladish_graph_remove_hidden_objects() called
&gt; for graph '/org/ladish/Room1'
&gt; Tue Dec 14 15:11:39 2010: graph /org/ladish/Room1
&gt; Tue Dec 14 15:11:39 2010:   version 926
&gt; Tue Dec 14 15:11:39 2010:   persist: yes
&gt; Tue Dec 14 15:11:39 2010:   clients:
&gt; Tue Dec 14 15:11:39 2010:   connections:
&gt; Tue Dec 14 15:11:39 2010: -------
&gt; Tue Dec 14 15:11:39 2010: Loading project
&gt; '/home/in0giro/casa/musica/progetti/in-giro/canzoni/a dim light/a dim
&gt; light 2010.001' into room 'room 01'
&gt; Tue Dec 14 15:11:39 2010: Project 'a dim light 2010.001' with uuid
&gt; 0bea1f65-99ea-4496-a87f-30e2885c984b
&gt; Tue Dec 14 15:11:39 2010: room port "audio_capture_1" with uuid
&gt; f3b66bdf-eabd-4c73-969e-852a8f18db60
&gt; Tue Dec 14 15:11:39 2010: ERROR: callback_elstart: Cannot find
&gt; room link port.
&gt; Tue Dec 14 15:11:39 2010: ladish_graph_remove_hidden_objects() called
&gt; for graph '/org/ladish/Room1'
&gt; Tue Dec 14 15:11:39 2010: graph /org/ladish/Room1
&gt; Tue Dec 14 15:11:39 2010:   version 926
&gt; Tue Dec 14 15:11:39 2010:   persist: yes
&gt; Tue Dec 14 15:11:39 2010:   clients:
&gt; Tue Dec 14 15:11:39 2010:   connections:
&gt; Tue Dec 14 15:11:39 2010: ERROR: run: Project load failed.
&gt; Tue Dec 14 15:11:39 2010: load project command destructor
&gt; Tue Dec 14 15:13:40 2010: app 'a2jmidid' (1)
&gt; Tue Dec 14 15:13:40 2010: client 'firewire_pcm' (4)
&gt; Tue Dec 14 15:13:40 2010: client 'Midi Through' (5)
&gt; Tue Dec 14 15:13:53 2010: <a href="http://ladish.org/ns/canvas/x">http://ladish.org/ns/canvas/x</a> &lt;- 1526.000000
&gt; Tue Dec 14 15:13:53 2010: <a href="http://ladish.org/ns/canvas/y">http://ladish.org/ns/canvas/y</a> &lt;- 1111.875000
&gt; Tue Dec 14 15:13:53 2010: <a href="http://ladish.org/ns/canvas/x">http://ladish.org/ns/canvas/x</a> &lt;- 1543.500000
&gt; Tue Dec 14 15:13:53 2010: <a href="http://ladish.org/ns/canvas/y">http://ladish.org/ns/canvas/y</a> &lt;- 1067.125000
&gt; Tue Dec 14 15:13:55 2010: <a href="http://ladish.org/ns/canvas/x">http://ladish.org/ns/canvas/x</a> &lt;- 1759.200000
&gt; Tue Dec 14 15:13:55 2010: <a href="http://ladish.org/ns/canvas/y">http://ladish.org/ns/canvas/y</a> &lt;- 1149.275000
&gt;
&gt;
&gt; it looks like there are problems with "MIDI through port" getting
&gt; reloaded, thus causing the Room not to be created.  thus, the Project
&gt; load fails.  note that there is 1 Studio L0 app: a2j -e.
&gt;
&gt;     let me know if this should be ticketed.

Yes, please create a ticket. 

</blockquote>
<br>
&nbsp;&nbsp;&nbsp; http://ladish.org/ticket/161<br><br><blockquote type="CITE">

And please, check whether it is really Midi
Through that is causing this problem. It can disabled somehow, IIRC it
was some kernel module or a parameter of a kernel module.

</blockquote>
&nbsp;&nbsp;&nbsp; the MIDI Through ports only show up when a2j -e is started as a Studio level app.&nbsp; regardless, you are correct: even without MIDI Through and a2j -e being run, this problem still occurs.&nbsp; the latest+greatest version of LADISH gives some more error messages in the log, which i attached to the ticket.&nbsp; here is the relavant part i believe:<br><br>
owner graph input port e59b4013-519f-46c7-9b67-0421b099a138 is linked to room output port 7eecf3d1-b2c9-4e49-ae3a-51672d95c362<br>
Mon Jan&nbsp; 3 14:01:53 2011: [31mERROR: [0mjmcore_proxy_create_link: jmcore::create() failed.<br>
Mon Jan&nbsp; 3 14:01:53 2011: [31mERROR: [0mcreate_port_link: jmcore_proxy_create_link() failed.<br>
Mon Jan&nbsp; 3 14:01:53 2011: [31mERROR: [0mladish_room_start: Creation of room port links failed.<br>
Mon Jan&nbsp; 3 14:01:53 2011: client_appeared(2, jmcore-13)<br>
Mon Jan&nbsp; 3 14:01:53 2011: [31mERROR: [0mgraph_proxy_get_client_pid: GetClientPID() failed.<br>
Mon Jan&nbsp; 3 14:01:53 2011: client 2 pid is unknown<br>
Mon Jan&nbsp; 3 14:01:53 2011: Lookup by app uuid failed, attempting lookup by name 'jmcore-13'<br><br>
peace, w<br><br><blockquote type="CITE">

</blockquote>
<br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>

--

-- 
<a href="http://wayne.in-giro.org">http://wayne.in-giro.org</a>

</td>
</tr></table>
</div>

headers

Wayne | 3 Jan 2011 20:27

Re: auto connection problems

Il giorno mer, 08/12/2010 alle 00.58 +0200, Nedko Arnaudov ha scritto:

Wayne <wayne-6v2rLk5JRENAfugRpC6u6w@public.gmane.org> writes: > Il giorno lun, 06/12/2010 alle 22.54 +0200, Nedko Arnaudov ha scritto: > >> Wayne <wayne-6v2rLk5JRENAfugRpC6u6w@public.gmane.org> writes: >> >> >> >> What jack version do you use? >> >> > >> >> > media-sound/jack-audio-connection-kit-1.9.6 from Gentoo pro-audio >> >> > overlay >> >> >> >> Not directly related but it is a good idea to use the one from >> >> ladi-overlay. It has the no-self-connect option that is very useful if >> >> you use ladish rooms/projects. >> > >> > >> > good timing: i was just starting to write another ticket/email about >> > a potential issue that has been popping up on some large Ardour >> > +Rosegardn projects that i have been trying to move to LADISH. >> > unfortunately, this issue has really been difficult to track down. but >> > now when you mention a "self-connect" option in JACK, maybe i am just >> > not configured correctly. >> > >> > the problem i am having is that either LADISH or JACK or Ardour, or >> > even Rosegarden, is automatically connecting various ports, even after i >> > disconnect them in Ardour and save the Studio and the Ardour session. >> > both Ardour and Rosegarden are just at the top level Studio for now, not >> > even in a Room or Project. mainly, something is re-attaching the outs >> > of tracks/buses in Ardour to Ardour:Master-In, which i usually remove >> > and route to a bus. i first thought it was because the Studio was saved >> > with the tracks connected to Master-In (as is the default in Ardour for >> > a track). however, i started a new Studio and found the same problem. >> > it was so bad that i had to use QJackCtl to get the project back to >> > normal. i could not tell when, but every once in a while, or after >> > restarting either Ardour or Rosegarden, the tracks would have added to >> > their outs a connection to Master-In again. so far, back with QJackCtl, >> > the issue has stopped. >> >> Ardour autoconnects to jack ports for sure. At least ardour2. > > i was aware of this, but i thought since i was deleting the > connections within Ardour (2.8.11), then Ardour would not be the culprit > reconnecting in the background. that left only JACK and LADISH. Before jack port is removed it is disconnected, either by the app that created the port or by jack server. There is no way to know whether user manually initiated port disconnect or not. This is not the case with ladish though. All connect and disconnect requests that come from the frontends like gladish are assumed to be manually initiated by user. Additionally ladish watches from connects that happen at JACK level and are not initiated by ladish. This is a part that is probably not very well tested though, because of the no-self-connect option being widely used. If ladish notices that JACK connection was created between ports in different vgraphs (vgraphs are room graphs and the studio graph), it will simply ignore it (and print error in the log). >> Rosegarden >> autoconnects at ALSA level. at least. I've not found a way to disable >> this rosegarden "feature" yet. > > yes, Rosegarden does this even when in a Room i believe. > >> A JACK option will not help with ALSA >> autoconnections. Maybe something can be implemented in alsapid.so, a >> share library that is used when apps are started through ladish. > > or ask the Rosegarden folks to make it an option? Maybe there is one already, we just dont know it :) If you find out, please share this info with the list. >> > however, if you are saying that there exists an auto/self connect >> > feature in JACK, maybe this is causing the problem? >> >> I think that it is a good idea to enable this option when you use >> ladish. for pure jackdbus/jackd setups it is less important. > > OK, i am a bit confused: JACK does have an auto connect option, but > i cannot find where to enable/disable it, unless you are saying that > only the LADISH repo version has the JACK auto connection disabled? The jack engine option is called "self-connect-mode". It has five possible states: 1. "Don't restrict self connect requests" 2. "Fail self connect requests to external ports only" 3. "Ignore self connect requests to external ports only" 4. "Fail all self connect requests" 5. "Ignore all self connect requests" The default value is "Don't restrict self connect requests". This option is enabled in the jack no-self-connect branch: http://repo.or.cz/w/jack2.git/shortlog/refs/heads/no-self-connect The no-self-connect branch is merged into the ladi branch: http://repo.or.cz/w/jack2.git/shortlog/refs/heads/ladi Merged means that ladi branch has the no-self-connect functionality. Currently the ladi branch also has a fix for autorenamed clients that will be part of the next jack release. To summarize, if you want no-self-connect for use with ladish, use the jack2 "ladi" git branch. The jack version that sits in the ladish repo in the jack2 subdir is same as the jack2 "ladi" branch. > i searched for some docs on this in JACK and did not find anything yet. > can i ask you what exactly does this JACK auto connection do (it might > be something that i am used to by now, as i have been using normal JACK > for a few years, so i apologize if i am missing something simple)? and > why would it be a good idea to have this option enabled when LADISH is > already doing auto connection? seems like this may be a common problem > for LADISH users: since almost all JACK apps have a way to manage > connections, then i would guess that the less we have auto connecting > the better. *Some* apps autoconnect. This is more common for apps that are designed to be all-in-one solutions. They often try to act as JACK session handlers themself. Like ardour does. Smaller apps tend to not connect automatically. It is a good idea to have this option enabled because you dont want apps to connect to system ports when they are in rooms.

with the latest+greatest LADISH as of this morning, and the LADISH overlay version of JACK, i now see a "self-connect-mode" option in the JACK config dialog for "engine". it is set to "Don't restrict self connect requests". to be clear for future generations: with LADISH, this should be set to ??? i am guessing "Ignore self connect requests to external ports only" or "Ignore all self connect requests" to prevent apps like Ardour from connecting to hardware ports? this way, only LADISH can make connections? sorry for the continued confusion.

thanks, w

>> > also, the new Rosegarden 10.10 seems to have L1 >> > support as well (according to their release notes), but not in overlays >> > yet (i posted a request for a version bump). >> > >> > in the meantime, some more LADISH questions came up if you have the >> > time: >> > >> > + does LADISH handle/save/record connections between apps that are not >> > in Rooms or Projects, but just in the Studio? i assume yes, for Studio >> > level apps. >> >> yes it does. when it notices that connection is being made it remembers >> it. to remove the connections you have to disconnect through gladish. >> >> since some time ladish also saves connections of ports that are >> invisible. > > are these invisible connections those in Gladish's Raw Jack view? Unfortunately the invisible connections are invisible in frontends. It is definitively a good idea to have an option to see them sometimes. Implementing this however is not trivial and because of this I've postponed it as a non-critical feature. >> the intent is to have apps that you run only occasionaly. so >> they are saved in stopped state. when you load&start the studio you can >> manually start the "registered" app. ladish will reconnect its ports >> when they appear. >> >> For apps that are not started through ladish this autoconnection >> functionality should be probably more tweakable. For example, "whether >> to remember connections of ports of apps started outside of ladish" and >> "whether to save connections of ports of apps started outside of >> ladish". They are not implemented mainly because I almost never start >> apps outside of ladish and this it was never been my priority. > > this may have been the problem: i was starting Ardour 2 and > Rosegarden outside of LADISH (because i am still learning/having > problems with Rooms and Projects), and i assumed that ladishd would not > be remembering those connections since i was managing them via Ardour, > not Gladish/etc. thus, when i edited the connections via Ardour, > ladishd may have been remembering the old state and reconnecting them. > so i guess i cast my vote for this tweak-able option for > saving/remembering connection state of apps started outside LADISH. managing connections from within ardour is not a good idea with current state of ladish codebase. > another issue that came up: could we have a way to indicate visually > in Gladish/LadiTray or even via a message to ladishd, that studio state > has been edited and not saved? often, i would look back at Gladish to > see if it's state (i.e. Studio, Room, Project) had changed, and if it > had been saved, as i am unsure when ladishd is "noticing" and > remembering the new connections, that i would be deleting in Ardour > (that ladishd would be reconnecting)? kind of like the * next to the > Studio/Room/Project name when it is edited but not saved? i can submit > a more detailed ticket once i get a better handle on how that would work > for Studio, Rooms, and Projects, and what i am actually asking for ;) This is a feature that will probably come with supoprt for L2 apps (LASH and jack-session), i.e. in ladish-0.5. > finally, one other thing ;) the main reason i was using the Ardour > connection manager was because it became very unwieldy/cluttered in > Gladish's Patchage-like window to see/manager the JACK connections. i > had quite a few projects with at least 30 tracks in Ardour, if not 50. > add in Rosegarden's 10 tracks, QSynth, etc, and it becomes very > difficult to manage the connections in Gladish. i believe an > alternative text-based (ala QJackCtl or Ardour) connection manager would > be necessary for any large projects in Gladish, especially when now i > realize that for a LADISH project, all connections must be managed via > Gladish (or other LADISH tool). even zooming out and arranging does not > really help, as an Ardour box with 30 tracks gives us at least 60 ports > (assuming 1 in, 1 out), usually more. thus, the Ardour box is bigger > than the viewport, with massive amounts of connections running > everywhere. zooming out makes the other boxes too small, almost > illegible on a laptop/netbook. i will submit a ticket for this if you > think it is something that cannot be handled by other apps? I'm aware of this problem. In short-term you will be able to manage connections through ladish_control. In long-term ladish will be able to run plugins that will allow to script complex graph manipulation tasks. The short term plan should be complete for ladish-0.4. Or with more luck, even for ladish-0.3. I create a ticket for it: http://ladish.org/ticket/125

-- http://wayne.in-giro.org

<div>
Il giorno mer, 08/12/2010 alle 00.58 +0200, Nedko Arnaudov ha scritto:
<blockquote type="CITE">

Wayne &lt;<a href="mailto:wayne@...">wayne@...</a>&gt; writes:

&gt; Il giorno lun, 06/12/2010 alle 22.54 +0200, Nedko Arnaudov ha scritto:
&gt;
&gt;&gt; Wayne &lt;<a href="mailto:wayne@...">wayne@...</a>&gt; writes:
&gt;&gt; 
&gt;&gt; &gt;&gt; &gt;&gt; What jack version do you use?
&gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;     media-sound/jack-audio-connection-kit-1.9.6 from Gentoo pro-audio
&gt;&gt; &gt;&gt; &gt; overlay
&gt;&gt; &gt;&gt; 
&gt;&gt; &gt;&gt; Not directly related but it is a good idea to use the one from
&gt;&gt; &gt;&gt; ladi-overlay. It has the no-self-connect option that is very useful if
&gt;&gt; &gt;&gt; you use ladish rooms/projects.
&gt;&gt; &gt;
&gt;&gt; &gt;
&gt;&gt; &gt;     good timing: i was just starting to write another ticket/email about
&gt;&gt; &gt; a potential issue that has been popping up on some large Ardour
&gt;&gt; &gt; +Rosegardn projects that i have been trying to move to LADISH.
&gt;&gt; &gt; unfortunately, this issue has really been difficult to track down.  but
&gt;&gt; &gt; now when you mention a "self-connect" option in JACK, maybe i am just
&gt;&gt; &gt; not configured correctly.
&gt;&gt; &gt;
&gt;&gt; &gt;     the problem i am having is that either LADISH or JACK or Ardour, or
&gt;&gt; &gt; even Rosegarden, is automatically connecting various ports, even after i
&gt;&gt; &gt; disconnect them in Ardour and save the Studio and the Ardour session.
&gt;&gt; &gt; both Ardour and Rosegarden are just at the top level Studio for now, not
&gt;&gt; &gt; even in a Room or Project.  mainly, something is re-attaching the outs
&gt;&gt; &gt; of tracks/buses in Ardour to Ardour:Master-In, which i usually remove
&gt;&gt; &gt; and route to a bus.  i first thought it was because the Studio was saved
&gt;&gt; &gt; with the tracks connected to Master-In (as is the default in Ardour for
&gt;&gt; &gt; a track).  however, i started a new Studio and found the same problem.
&gt;&gt; &gt; it was so bad that i had to use QJackCtl to get the project back to
&gt;&gt; &gt; normal.  i could not tell when, but every once in a while, or after
&gt;&gt; &gt; restarting either Ardour or Rosegarden, the tracks would have added to
&gt;&gt; &gt; their outs a connection to Master-In again.  so far, back with QJackCtl,
&gt;&gt; &gt; the issue has stopped.
&gt;&gt; 
&gt;&gt; Ardour autoconnects to jack ports for sure. At least ardour2. 
&gt;
&gt;     i was aware of this, but i thought since i was deleting the
&gt; connections within Ardour (2.8.11), then Ardour would not be the culprit
&gt; reconnecting in the background.  that left only JACK and LADISH.

Before jack port is removed it is disconnected, either by the app that
created the port or by jack server. There is no way to know whether user
manually initiated port disconnect or not. This is not the case with
ladish though. All connect and disconnect requests that come from the
frontends like gladish are assumed to be manually initiated by
user.

Additionally ladish watches from connects that happen at JACK level
and are not initiated by ladish. This is a part that is probably not
very well tested though, because of the no-self-connect option being
widely used. If ladish notices that JACK connection was created between
ports in different vgraphs (vgraphs are room graphs and the studio
graph), it will simply ignore it (and print error in the log).

&gt;&gt; Rosegarden
&gt;&gt; autoconnects at ALSA level. at least. I've not found a way to disable
&gt;&gt; this rosegarden "feature" yet. 
&gt;
&gt;     yes, Rosegarden does this even when in a Room i believe.
&gt;
&gt;&gt; A JACK option will not help with ALSA
&gt;&gt; autoconnections. Maybe something can be implemented in alsapid.so, a
&gt;&gt; share library  that is used when apps are started through ladish.
&gt;
&gt;     or ask the Rosegarden folks to make it an option?

Maybe there is one already, we just dont know it :) If you find out,
please share this info with the list.

&gt;&gt; &gt;     however, if you are saying that there exists an auto/self connect
&gt;&gt; &gt; feature in JACK, maybe this is causing the problem?
&gt;&gt; 
&gt;&gt; I think that it is a good idea to enable this option when you use
&gt;&gt; ladish. for pure jackdbus/jackd setups it is less important.
&gt;
&gt;     OK, i am a bit confused: JACK does have an auto connect option, but
&gt; i cannot find where to enable/disable it, unless you are saying that
&gt; only the LADISH repo version has the JACK auto connection disabled?

The jack engine option is called "self-connect-mode". It has five
possible states:
 1. "Don't restrict self connect requests"
 2. "Fail self connect requests to external ports only"
 3. "Ignore self connect requests to external ports only"
 4. "Fail all self connect requests"
 5. "Ignore all self connect requests"

The default value is "Don't restrict self connect requests".
This option is enabled in the jack no-self-connect branch:

<a href="http://repo.or.cz/w/jack2.git/shortlog/refs/heads/no-self-connect">http://repo.or.cz/w/jack2.git/shortlog/refs/heads/no-self-connect</a>

The no-self-connect branch is merged into the ladi branch:

<a href="http://repo.or.cz/w/jack2.git/shortlog/refs/heads/ladi">http://repo.or.cz/w/jack2.git/shortlog/refs/heads/ladi</a>

Merged means that ladi branch has the no-self-connect
functionality. Currently the ladi branch also has a fix for autorenamed
clients that will be part of the next jack release.

To summarize, if you want no-self-connect for use with ladish, use the
jack2 "ladi" git branch.

The jack version that sits in the ladish repo in the jack2 subdir is
same as the jack2 "ladi" branch.
&gt; i searched for some docs on this in JACK and did not find anything yet.
&gt; can i ask you what exactly does this JACK auto connection do (it might
&gt; be something that i am used to by now, as i have been using normal JACK
&gt; for a few years, so i apologize if i am missing something simple)?  and
&gt; why would it be a good idea to have this option enabled when LADISH is
&gt; already doing auto connection?  seems like this may be a common problem
&gt; for LADISH users: since almost all JACK apps have a way to manage
&gt; connections, then i would guess that the less we have auto connecting
&gt; the better.

*Some* apps autoconnect. This is more common for apps that are designed
to be all-in-one solutions. They often try to act as JACK session
handlers themself. Like ardour does. Smaller apps tend to not connect
automatically.

It is a good idea to have this option enabled because you dont want apps
to connect to system ports when they are in rooms.

</blockquote>
<br>
&nbsp;&nbsp;&nbsp; with the latest+greatest LADISH as of this morning, and the LADISH overlay version of JACK, i now see a "self-connect-mode" option in the JACK config dialog for "engine".&nbsp; it is set to "Don't restrict self connect requests".&nbsp; to be clear for future generations: with LADISH, this should be set to ???&nbsp; i am guessing "Ignore self connect requests to external ports only" or "Ignore all self connect requests" to prevent apps like Ardour from connecting to hardware ports?&nbsp; this way, only LADISH can make connections?&nbsp; sorry for the continued confusion.<br><br>
thanks, w<br><br><blockquote type="CITE">

&gt;&gt; &gt;  also, the new Rosegarden 10.10 seems to have L1
&gt;&gt; &gt; support as well (according to their release notes), but not in overlays
&gt;&gt; &gt; yet (i posted a request for a version bump).
&gt;&gt; &gt;
&gt;&gt; &gt;     in the meantime, some more LADISH questions came up if you have the
&gt;&gt; &gt; time:
&gt;&gt; &gt;
&gt;&gt; &gt; + does LADISH handle/save/record connections between apps that are not
&gt;&gt; &gt; in Rooms or Projects, but just in the Studio?  i assume yes, for Studio
&gt;&gt; &gt; level apps.
&gt;&gt; 
&gt;&gt; yes it does. when it notices that connection is being made it remembers
&gt;&gt; it. to remove the connections you have to disconnect through gladish.
&gt;&gt; 
&gt;&gt; since some time ladish also saves connections of ports that are
&gt;&gt; invisible. 
&gt;
&gt;     are these invisible connections those in Gladish's Raw Jack view?

Unfortunately the invisible connections are invisible in frontends. It
is definitively a good idea to have an option to see them
sometimes. Implementing this however is not trivial and because of this
I've postponed it as a non-critical feature.

&gt;&gt; the intent is to have apps that you run only occasionaly. so
&gt;&gt; they are saved in stopped state. when you load&amp;start the studio you can
&gt;&gt; manually start the "registered" app. ladish will reconnect its ports
&gt;&gt; when they appear.
&gt;&gt; 
&gt;&gt; For apps that are not started through ladish this autoconnection
&gt;&gt; functionality should be probably more tweakable. For example, "whether
&gt;&gt; to remember connections of ports of apps started outside of ladish" and
&gt;&gt; "whether to save connections of ports of apps started outside of
&gt;&gt; ladish". They are not implemented mainly because I almost never start
&gt;&gt; apps outside of ladish and this it was never been my priority.
&gt;
&gt;     this may have been the problem: i was starting Ardour 2 and
&gt; Rosegarden outside of LADISH (because i am still learning/having
&gt; problems with Rooms and Projects), and i assumed that ladishd would not
&gt; be remembering those connections since i was managing them via Ardour,
&gt; not Gladish/etc.  thus, when i edited the connections via Ardour,
&gt; ladishd may have been remembering the old state and reconnecting them.
&gt; so i guess i cast my vote for this tweak-able option for
&gt; saving/remembering connection state of apps started outside LADISH.

managing connections from within ardour is not a good idea with current
state of ladish codebase.

&gt;     another issue that came up: could we have a way to indicate visually
&gt; in Gladish/LadiTray or even via a message to ladishd, that studio state
&gt; has been edited and not saved?  often, i would look back at Gladish to
&gt; see if it's state (i.e. Studio, Room, Project) had changed, and if it
&gt; had been saved, as i am unsure when ladishd is "noticing" and
&gt; remembering the new connections, that i would be deleting in Ardour
&gt; (that ladishd would be reconnecting)?  kind of like the * next to the
&gt; Studio/Room/Project name when it is edited but not saved?  i can submit
&gt; a more detailed ticket once i get a better handle on how that would work
&gt; for Studio, Rooms, and Projects, and what i am actually asking for ;)

This is a feature that will probably come with supoprt for L2 apps (LASH
and jack-session), i.e. in ladish-0.5.

&gt;     finally, one other thing ;)  the main reason i was using the Ardour
&gt; connection manager was because it became very unwieldy/cluttered in
&gt; Gladish's Patchage-like window to see/manager the JACK connections.  i
&gt; had quite a few projects with at least 30 tracks in Ardour, if not 50.
&gt; add in Rosegarden's 10 tracks, QSynth, etc, and it becomes very
&gt; difficult to manage the connections in Gladish.  i believe an
&gt; alternative text-based (ala QJackCtl or Ardour) connection manager would
&gt; be necessary for any large projects in Gladish, especially when now i
&gt; realize that for a LADISH project, all connections must be managed via
&gt; Gladish (or other LADISH tool).  even zooming out and arranging does not
&gt; really help, as an Ardour box with 30 tracks gives us at least 60 ports
&gt; (assuming 1 in, 1 out), usually more.  thus, the Ardour box is bigger
&gt; than the viewport, with massive amounts of connections running
&gt; everywhere.  zooming out makes the other boxes too small, almost
&gt; illegible on a laptop/netbook.  i will submit a ticket for this if you
&gt; think it is something that cannot be handled by other apps?

I'm aware of this problem. In short-term you will be able to manage
connections through ladish_control. In long-term ladish will be able to
run plugins that will allow to script complex graph manipulation tasks.

The short term plan should be complete for ladish-0.4. Or with more luck,
even for ladish-0.3. I create a ticket for it:

<a href="http://ladish.org/ticket/125">http://ladish.org/ticket/125</a>

</blockquote>
<br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>

--

-- 
<a href="http://wayne.in-giro.org">http://wayne.in-giro.org</a>

</td>
</tr></table>
</div>

headers

Wayne | 3 Jan 2011 20:45

Re: RFC: Acceleration of workflow?

Il giorno sab, 18/12/2010 alle 21.16 +0000, Frank Kober ha scritto:

Hi all,
I'd just like to collect some input on the following:

I think ticket 128 raised by Wayne is an important point that could actually be solved in a beneficial way.
I thought about this before, because working with rooms I missed the fast startup of everything by choosing a studio from laditray. Since projects exist, I need to take two actions instead of one to get started (start studio AND project).

In the discussion on IRC, I had suggested to attribute a default room and a default studio.
The default studio could be one chosen by the user from the existing studio list.
For the default room there are several possibilities:
1) attribute a default room chosen by user to the project in case the room type doesn't match

should there be a default Room per Project or per Studio?

2) always default to the first room in the studio if the room type doesn't match

So what do you all think? How should Ladish best handle projects started without previously starting a studio?

    perhaps having a default Studio selected, a user can open a Project, and the default Studio is loaded, started, and then the Project loaded into a compatible Room (if it exists), or the default Room of the Studio (designated per Studio as you mentioned above). one could even get fancier and create a compatible Room for the Project if it did not exist in the Studio, though i assume that the user would still have to wire up the Room at the Studio level.

    as long as the default Studio/Project/Room loading is configurable, seems like a great idea. personally, i like loading Projects and having everything start from there. usually, i have 1 of 2 Studios that i am currently working with (depending on available hardware) and 1 Room in each Studio. changing the default Studio (e.g. via LadiTray) would be neat, then just double-clicking Project files in the file manager to start working (obviously we would need a more unique file extension or something).

    is there a ticket for this Frank?

peace, w

Happy Ladiing

Frank

_______________________________________________
Discuss mailing list
Discuss-oU9gvf+ajcSbNyr/yzA+mQ@public.gmane.org
http://lists.ladish.org/listinfo/discuss

--
http://wayne.in-giro.org

<div>
Il giorno sab, 18/12/2010 alle 21.16 +0000, Frank Kober ha scritto:<br><blockquote type="CITE">
    Hi all,<br>I'd just like to collect some input on the following:<br><br>I think ticket 128 raised by Wayne is an important point that could actually be solved in a beneficial way. <br>I thought about this before, because working with rooms I missed the fast startup of everything by choosing a studio from laditray. Since projects exist, I need to take two actions instead of one to get started (start studio AND project).<br><br>In the discussion on IRC, I had suggested to attribute a default room and a default studio.<br>The default studio could be one chosen by the user from the existing studio list.<br>For the default room there are several possibilities:<br>1) attribute a default room chosen by user to the project in case the room type doesn't match<br>
</blockquote>
&nbsp;&nbsp;&nbsp; should there be a default Room per Project or per Studio?<br><blockquote type="CITE">
    2) always default to the first room in the studio if the room type doesn't match<br><br><br>So what do you all think? How should Ladish best handle projects started without previously starting a studio?<br>
</blockquote>
&nbsp;&nbsp;&nbsp; perhaps having a default Studio selected, a user can open a Project, and the default Studio is loaded, started, and then the Project loaded into a compatible Room (if it exists), or the default Room of the Studio (designated per Studio as you mentioned above).&nbsp; one could even get fancier and create a compatible Room for the Project if it did not exist in the Studio, though i assume that the user would still have to wire up the Room at the Studio level.<br><br>
&nbsp;&nbsp;&nbsp; as long as the default Studio/Project/Room loading is configurable, seems like a great idea.&nbsp; personally, i like loading Projects and having everything start from there.&nbsp; usually, i have 1 of 2 Studios that i am currently working with (depending on available hardware) and 1 Room in each Studio.&nbsp; changing the default Studio (e.g. via LadiTray) would be neat, then just double-clicking Project files in the file manager to start working (obviously we would need a more unique file extension or something).<br><br>
&nbsp;&nbsp;&nbsp; is there a ticket for this Frank?<br><br>
peace, w<br><br><blockquote type="CITE">
    <br>Happy Ladiing<br><br>Frank<br><br><br><br>      <br>_______________________________________________<br>Discuss mailing list<br><a href="mailto:Discuss@...">Discuss@...</a><br><a href="http://lists.ladish.org/listinfo/discuss">http://lists.ladish.org/listinfo/discuss</a><br>
</blockquote>
<br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>
-- <br><a href="http://wayne.in-giro.org">http://wayne.in-giro.org</a>
</td>
</tr></table>
</div>

headers

Wayne | 3 Jan 2011 21:25

Re: problems with Ardour connections

Il giorno sab, 18/12/2010 alle 20.29 +0200, Nedko Arnaudov ha scritto:

Wayne <wayne-6v2rLk5JRENAfugRpC6u6w@public.gmane.org> writes: > small issue here with Ardour (perhaps with others apps, though i > mainly route all other apps through Ardour, and then Ardour to the > world): when loading a Project with Ardour already wired up to have > Master out bus, as well as a click track bus, connected to the virtual > Room ports for output, Ardour consistently starts with the following > message: > > [ERROR]: AudioEngine: cannot connect ardour:master/out 1 > (ardour:master/out 1) to jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f > (jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f) > [ERROR]: AudioEngine: cannot connect ardour:master/out 2 > (ardour:master/out 2) to jmcore-20:9e74a265-cc9e-4b6a-8e4c-c7577f3930fc > (jmcore-20:9e74a265-cc9e-4b6a-8e4c-c7577f3930fc) > [ERROR]: AudioEngine: cannot connect ardour:click 01 -- bus/out 1 > (ardour:click 01 -- bus/out 1) to > jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f > (jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f) > > they are not the only output connections Ardour has to the virtual > hardware for output, as the "auditioner" bus is also connected to the > Room virtual outputs. however, the auditioner bus to connect no problem > every time. > > i was able to get the Ardour error message to go away by saving the > Ardour session with no connections for the Master bus and click bus. > however, even if i wire the connections in Gladish and save, upon > reloading Ardour, the Master bus and click bus are not connected. then, > upon re-making the connections in Gladish and saving Ardour, subsequent > loads of the Project (and thus Ardour) bring back the error message from > Ardour, although with different jmcore-XXX values. I get these too. They are annoying but dont cause any real harm here. The reason for these is that jmcore (JACK multicore) JACK clients have somewhat random names. I'm still thinking how to best handle this issue. Not handling it at all is also a possibility because AFAIK with ardour3 one can disable all autoconnections to external ports. jmcore clients are created when rooms are started. so if you save the ardour project, unload the ladish project and then load it without stopping and restarting the studio, then these connections should get away. All of the above assumes that no-self-connect is configured to ignore requests. If it is configured to fail the requests, then ardour reports these failures. > also, connections made in Gladish from the Room's virtual hardware > inputs to inputs of tracks in Ardour are not remembered across Project > loads. however, in this case, there is no error message from Ardour. > the connections are simply gone. > > basically, the current state of this project is that Ardour will > start, with error messages only about not being able to connect the > Master out and click buses, in a Project+Room, but the Master out, > click, and 2 inputs, all connected to the Room's virtual hardware (input > and output), are not re-connected by Gladish. > > thanks,w > > PS. i am using the LADI overlay JACK 2.9999 with "no self-connect" > option, and the latest ladi/ladi-tools from git this is quite disturbing... Please fill a ticket for this. I have a real (as in not a test one) ladish project with ardour2 in it and the connections get restored.

with latest+greatest, things seem to be working. also, i have enabled the "no self-connect" option in JACK. thus, only LADISH can make the connections. this seems to have prevented Ardour from removing the connections, which is what i believe was happening. in fact, as Ardour loaded, i could see the connections made by LADISH in Gladish, but then removed when Ardour is setting up signal flow on startup.

will monitor this and submit ticket if i can recreate it with newer LADISH release.

thanks, w

-- http://wayne.in-giro.org

<div>
Il giorno sab, 18/12/2010 alle 20.29 +0200, Nedko Arnaudov ha scritto:
<blockquote type="CITE">

Wayne &lt;<a href="mailto:wayne@...">wayne@...</a>&gt; writes:

&gt;     small issue here with Ardour (perhaps with others apps, though i
&gt; mainly route all other apps through Ardour, and then Ardour to the
&gt; world): when loading a Project with Ardour already wired up to have
&gt; Master out bus, as well as a click track bus, connected to the virtual
&gt; Room ports for output, Ardour consistently starts with the following
&gt; message:
&gt;
&gt; [ERROR]: AudioEngine: cannot connect ardour:master/out 1
&gt; (ardour:master/out 1) to jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f
&gt; (jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f)
&gt; [ERROR]: AudioEngine: cannot connect ardour:master/out 2
&gt; (ardour:master/out 2) to jmcore-20:9e74a265-cc9e-4b6a-8e4c-c7577f3930fc
&gt; (jmcore-20:9e74a265-cc9e-4b6a-8e4c-c7577f3930fc)
&gt; [ERROR]: AudioEngine: cannot connect ardour:click 01 -- bus/out 1
&gt; (ardour:click 01 -- bus/out 1) to
&gt; jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f
&gt; (jmcore-19:07199a74-f48a-4f0d-a685-d201f0a79b2f)
&gt;
&gt; they are not the only output connections Ardour has to the virtual
&gt; hardware for output, as the "auditioner" bus is also connected to the
&gt; Room virtual outputs.  however, the auditioner bus to connect no problem
&gt; every time.
&gt;
&gt;     i was able to get the Ardour error message to go away by saving the
&gt; Ardour session with no connections for the Master bus and click bus.
&gt; however, even if i wire the connections in Gladish and save, upon
&gt; reloading Ardour, the Master bus and click bus are not connected.  then,
&gt; upon re-making the connections in Gladish and saving Ardour, subsequent
&gt; loads of the Project (and thus Ardour) bring back the error message from
&gt; Ardour, although with different jmcore-XXX values.

I get these too. They are annoying but dont cause any real harm
here. The reason for these is that jmcore (JACK multicore) JACK clients
have somewhat random names. I'm still thinking how to best handle this
issue. Not handling it at all is also a possibility because AFAIK with
ardour3 one can disable all autoconnections to external ports.

jmcore clients are created when rooms are started. so if you save the
ardour project, unload the ladish project and then load it without
stopping and restarting the studio, then these connections should get
away.

All of the above assumes that no-self-connect is configured to ignore
requests. If it is configured to fail the requests, then ardour reports
these failures.

&gt;     also, connections made in Gladish from the Room's virtual hardware
&gt; inputs to inputs of tracks in Ardour are not remembered across Project
&gt; loads.  however, in this case, there is no error message from Ardour.
&gt; the connections are simply gone.
&gt;
&gt;     basically, the current state of this project is that Ardour will
&gt; start, with error messages only about not being able to connect the
&gt; Master out and click buses, in a Project+Room, but the Master out,
&gt; click, and 2 inputs, all connected to the Room's virtual hardware (input
&gt; and output), are not re-connected by Gladish.
&gt;
&gt; thanks,w
&gt;
&gt; PS. i am using the LADI overlay JACK 2.9999 with "no self-connect"
&gt; option, and the latest ladi/ladi-tools from git

this is quite disturbing... Please fill a ticket for this.
I have a real (as in not a test one) ladish project with ardour2 in it
and the connections get restored.

</blockquote>
<br>
&nbsp;&nbsp;&nbsp; with latest+greatest, things seem to be working.&nbsp; also, i have enabled the "no self-connect" option in JACK.&nbsp; thus, only LADISH can make the connections.&nbsp; this seems to have prevented Ardour from removing the connections, which is what i believe was happening.&nbsp; in fact, as Ardour loaded, i could see the connections made by LADISH in Gladish, but then removed when Ardour is setting up signal flow on startup.<br><br>
&nbsp;&nbsp;&nbsp; will monitor this and submit ticket if i can recreate it with newer LADISH release.<br><br>
thanks, w<br><br><blockquote type="CITE">

</blockquote>
<br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>

--

-- 
<a href="http://wayne.in-giro.org">http://wayne.in-giro.org</a>

</td>
</tr></table>
</div>

headers

Nedko Arnaudov | 9 Jan 2011 16:13

Re: buggy Project file?

Hi Wayne,

>     thanks to your help, the project is now loading again.  the things
> that i had changed:
>
> + i edited the LADISH project file to remove all the MIDI ports in
> Ardour2 and RG one by one, as the project was continually failing on
> each MIDI port.
> + i also removed a connection that involved a removed MIDI port.
> + i updated to the latest GIT this morning
> 91b87783d7a68c49c01252465dfdf6cc3a63d1a7
>
> with these changes, i was able to bring up the Project, and reconnect
> the MIDI connections.  subsequent reloads and edits have been fine, in
> fact more reliable than previous versions of LADISH.
>
>     is it possible that i saved this Project with 1 version of gladish,
> then updated, then tried to open it with a newer version, hence the
> problem with the MIDI ports?

I've fixed some bugs that were "corrupting" the studio/project xml on
save and thus making it non-loadable.

>     either way, the problem seems to have been corrected in the latest
> +greatest.

>> Please fill a ticket for this issue.
>
>     should i still file a ticket as it seems to be already resolved?

I think it is already solved.

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

Hi Wayne,

>     thanks to your help, the project is now loading again.  the things
> that i had changed:
>
> + i edited the LADISH project file to remove all the MIDI ports in
> Ardour2 and RG one by one, as the project was continually failing on
> each MIDI port.
> + i also removed a connection that involved a removed MIDI port.
> + i updated to the latest GIT this morning
> 91b87783d7a68c49c01252465dfdf6cc3a63d1a7
>
> with these changes, i was able to bring up the Project, and reconnect
> the MIDI connections.  subsequent reloads and edits have been fine, in
> fact more reliable than previous versions of LADISH.
>
>     is it possible that i saved this Project with 1 version of gladish,
> then updated, then tried to open it with a newer version, hence the
> problem with the MIDI ports?

I've fixed some bugs that were "corrupting" the studio/project xml on
save and thus making it non-loadable.

>     either way, the problem seems to have been corrected in the latest
> +greatest.

>> Please fill a ticket for this issue.
>
>     should i still file a ticket as it seems to be already resolved?

I think it is already solved.

--

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

headers

Nedko Arnaudov | 9 Jan 2011 16:17

Re: small bug on loading project with stopped studio...

Wayne <wayne@...> writes:

> Il giorno sab, 18/12/2010 alle 19.58 +0200, Nedko Arnaudov ha scritto:
>
>> Wayne <wayne@...> writes:
>> 
>> >     seems like there is a small bug which causes the following error in
>> > the ladishd log file when trying to load a Project in a stopped Studio:
>> >
>> > Tue Dec 14 15:05:42 2010: Load project request
>> > Tue Dec 14 15:05:42 2010: -------
>> > Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called
>> > for graph '/org/ladish/Room1'
>> > Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1
>> > Tue Dec 14 15:05:42 2010:   version 926
>> > Tue Dec 14 15:05:42 2010:   persist: yes
>> > Tue Dec 14 15:05:42 2010:   clients:
>> > Tue Dec 14 15:05:42 2010:   connections:
>> > Tue Dec 14 15:05:42 2010: -------
>> > Tue Dec 14 15:05:42 2010: Loading project
>> > '/home/in0giro/casa/musica/progetti/in-giro/canzoni/a dim light/a dim
>> > light 2010.001' into room 'room 01'
>> > Tue Dec 14 15:05:42 2010: Project 'a dim light 2010.001' with uuid
>> > 0bea1f65-99ea-4496-a87f-30e2885c984b
>> > Tue Dec 14 15:05:42 2010: room port "audio_capture_1" with uuid
>> > f3b66bdf-eabd-4c73-969e-852a8f18db60
>> > Tue Dec 14 15:05:42 2010: ERROR: callback_elstart: Cannot find
>> > room link port.
>> > Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called
>> > for graph '/org/ladish/Room1'
>> > Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1
>> > Tue Dec 14 15:05:42 2010:   version 926
>> > Tue Dec 14 15:05:42 2010:   persist: yes
>> > Tue Dec 14 15:05:42 2010:   clients:
>> > Tue Dec 14 15:05:42 2010:   connections:
>> > Tue Dec 14 15:05:42 2010: ERROR: run: Project load failed.
>> > Tue Dec 14 15:05:42 2010: load project command destructor
>> >
>> > i imagine we could eventually just have a dialog box that says the
>> > studio must be started first, or even better, prevent Projects from
>> > being loaded when a Studio is not started (similar to how one cannot
>> > save a Studio until the Studio is started).
>> >
>> >     let me know if i should file a ticket.
>> 
>> I created one: http://ladish.org/ticket/128
>> 
>> I think the best will be to disable project load when studio is not
>> started. In long term, maybe it should be possible to load project when
>> studio is stopped. What others think about this?
>
>
>     in the long term it could be useful to edit a Project even when JACK
> is not running/Studio not started.  however, i imagine that this would
> involve emulating the JACK graph somehow and it seems complicated.  for
> now, my vote is for just disabling Project actions when a Studio is not
> started.

Ticket 128 is marked as fixed. Editing in stopped state is indeed
somewhat complicated.

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

Wayne <wayne@...> writes:

> Il giorno sab, 18/12/2010 alle 19.58 +0200, Nedko Arnaudov ha scritto:
>
>> Wayne <wayne@...> writes:
>> 
>> >     seems like there is a small bug which causes the following error in
>> > the ladishd log file when trying to load a Project in a stopped Studio:
>> >
>> > Tue Dec 14 15:05:42 2010: Load project request
>> > Tue Dec 14 15:05:42 2010: -------
>> > Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called
>> > for graph '/org/ladish/Room1'
>> > Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1
>> > Tue Dec 14 15:05:42 2010:   version 926
>> > Tue Dec 14 15:05:42 2010:   persist: yes
>> > Tue Dec 14 15:05:42 2010:   clients:
>> > Tue Dec 14 15:05:42 2010:   connections:
>> > Tue Dec 14 15:05:42 2010: -------
>> > Tue Dec 14 15:05:42 2010: Loading project
>> > '/home/in0giro/casa/musica/progetti/in-giro/canzoni/a dim light/a dim
>> > light 2010.001' into room 'room 01'
>> > Tue Dec 14 15:05:42 2010: Project 'a dim light 2010.001' with uuid
>> > 0bea1f65-99ea-4496-a87f-30e2885c984b
>> > Tue Dec 14 15:05:42 2010: room port "audio_capture_1" with uuid
>> > f3b66bdf-eabd-4c73-969e-852a8f18db60
>> > Tue Dec 14 15:05:42 2010: ERROR: callback_elstart: Cannot find
>> > room link port.
>> > Tue Dec 14 15:05:42 2010: ladish_graph_remove_hidden_objects() called
>> > for graph '/org/ladish/Room1'
>> > Tue Dec 14 15:05:42 2010: graph /org/ladish/Room1
>> > Tue Dec 14 15:05:42 2010:   version 926
>> > Tue Dec 14 15:05:42 2010:   persist: yes
>> > Tue Dec 14 15:05:42 2010:   clients:
>> > Tue Dec 14 15:05:42 2010:   connections:
>> > Tue Dec 14 15:05:42 2010: ERROR: run: Project load failed.
>> > Tue Dec 14 15:05:42 2010: load project command destructor
>> >
>> > i imagine we could eventually just have a dialog box that says the
>> > studio must be started first, or even better, prevent Projects from
>> > being loaded when a Studio is not started (similar to how one cannot
>> > save a Studio until the Studio is started).
>> >
>> >     let me know if i should file a ticket.
>> 
>> I created one: http://ladish.org/ticket/128
>> 
>> I think the best will be to disable project load when studio is not
>> started. In long term, maybe it should be possible to load project when
>> studio is stopped. What others think about this?
>
>
>     in the long term it could be useful to edit a Project even when JACK
> is not running/Studio not started.  however, i imagine that this would
> involve emulating the JACK graph somehow and it seems complicated.  for
> now, my vote is for just disabling Project actions when a Studio is not
> started.

Ticket 128 is marked as fixed. Editing in stopped state is indeed
somewhat complicated.

--

-- 
Nedko Arnaudov <GnuPG KeyID: 7862B9E45D1B58ED>

5	October 2012
1	September 2012
11	August 2012
1	May 2012
6	April 2012
3	March 2012
12	January 2012
6	November 2011
2	October 2011
10	September 2011
7	August 2011
4	July 2011
18	June 2011
75	May 2011
7	April 2011
12	March 2011
12	February 2011
22	January 2011
56	December 2010
32	November 2010
3	September 2010
19	July 2010
5	June 2010
9	May 2010
14	April 2010
32	February 2010
8	January 2010

Mon	Tue	Wed	Thu	Fri	Sat	Sun

					1	2
3	4	5	6	7	8	9
10	11	12	13	14	15	16
17	18	19	20	21	22	23
24	25	26	27	28	29	30
31