linuxaudio.org

On 01/12/11 19:45, Robin Gareus wrote:

quoted text
> On 01/12/2011 07:31 AM, Goran Mekić wrote:

>> On 01/12/11 04:17, Paul Davis wrote:

>>> 2011/1/11 Goran Mekić:

>>>>      I've tested ardour2 and ardour3. What happens is that I save the

>>>> session

>>>> with one track, and when I close ardour and open it again, the track is

>>>> connected to more inputs and outputs then it was when I've hit save.

>>>> I use

>>>> jackdbus + M-Audio Delta 1010LT. Is there any other info I should give?

>>> (1) wrong mailing list (ardour-users would be more appropriate)

>>      I suspected it's not ardour, but here it is, anyway.

>>> (2) please provide a LOT more details about the connections "before"

>>> and "after"

>> OK, here's what I have (more tracks to show it's not always the same,

>> but for the track with the same name, additional connections are always

>> the same)

> I think you may have made a few typos. e.g there's no "meka (wet)"

> ports in the "connections after" list. Is that correct?

> The suggestion made by allcoms to post the output of `lack_lsp -c` is

> more reliable.

>

> Anyway. Intuitively this _could_ be related to

>   - using brackets in the port-names

>   - having ardour's auto-connect ports option enabled.

> but a quick test shows that both of these work just fine here.

> I can't reproduce the problem you describe.

>

> Since you're experiencing the problem with both ardour2 and 3:

> Could it be that you have some JACK patchbay or session-manager running

> that actually does make the connections?

     I thought it has nothing to do with it, but once I've killed

ladishd and ladishconf it works like a charm. Thanx a lot!

_______________________________________________

Linux-audio-user mailing list

Linux-audio-user@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-user