|
|
I just notice that when the click does not output sound, its output is indeed not connected to the soundcard. When I try to connect it in qjackctl, it just refuses silently. This is with 2.0beta6.2, I don't know if this has changed since beta4. |
|
|
Still there in 2.0 beta7.1... Did not notice this before, and I used click not so long ago. When connecting it to anything, it appears that either no click sound is generated or nothing is output to the click out port. |
|
2006-11-09 19:30
|
screenshot1.jpg (74,086 bytes) |
|
|
Playing around with ardour's option editor and qjackctl connection window, I managed to optain the screenshot I attached. Have a close look at what connections are reported in the connection window and those in the options editor... Weird hu ? As far as what is heard is concerned, if the connections are made using the options editor, the click works fine. when doing it with the connections window, no sound is played and for click/out1, no manual connection can be made. |
|
|
I am suffering the same problem. Via debug code I could trace it to _clicking not being set in session.cc:Session::click So for me it looks like the gui is not correctly attached to a new session. However since I am new to Ardour as well as gtk I couldn't get deeper by now. |
|
|
Looks like it is fixed in 2.0.5. |
|
|
see notes. |
|
|
see above |
- Anonymous
