On Thu, 20 May 2010, Orcan Ogetbil wrote:
Thanks for spotting this. I'll backported a fix to our Fedora package.
Please download and test:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2198449
I uninstalled ardour, verified that it also deleted the /etc/ardour2/
directory, manually deleted my ~/.ardour2/ directory, and installed your
new i686 package.
I haven't been able to test it. For some strange reason, jackd is
segfaulting every time I try to start it:
(from dmesg:)
jackd[2722]: segfault at 47169c97 ip 47169c97 sp b14b2210 error 4 in
libgcc_s-4.4.3-20100127.so.1[47d47000+1d000]
(from qjackctl message window:)
JACK server starting in realtime mode with priority 60
libffado 2.0.0 built Jan 21 2010 16:27:49
10:11:52.265 Could not connect to JACK server as client. - Overall
operation failed. - Server communication error. Please check the messages
window for more info.
firewire ERR: Could not prepare streaming device!
Cannot attach audio driver
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
Cannot connect to the server
JackServer::Open() failed with -1
If I start ardour, and use its audio setup dialog to select the alsa
backend, I can open my 'test' session. The existing tracks in that
session still retain their disabled mutes, but when I add a new track to
the session, it is created with all four mute points enabled.
A step forward, and a step backwards...
--
Rick Green
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
"As for our common defense, we reject as false the choice between our
safety and our ideals."
-President Barack Obama 20 Jan 2009
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
