26 Feb
2010
26 Feb
'10
6:25 a.m.
Sometimes ardour, while otherwise working perfectly, goes completely
mute. Reconnecting to jack or restarting doesn't help. What should I
check or change?
(I'm using version 2.8.4 on Fedora 10 with no PulseAudio.)
Andras
26 Feb
26 Feb
11:12 a.m.
This happened to me once, but it had nothing to do with Ardour. My
VPN/Citrix login app took over sound somehow. :/
On 2/26/10 4:25 AM, Andras Simon wrote:
Sometimes ardour, while otherwise working perfectly,
goes completely
mute. Reconnecting to jack or restarting doesn't help. What should I
check or change?
(I'm using version 2.8.4 on Fedora 10 with no PulseAudio.)
Andras
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
11:59 a.m.
On 2/26/10, Brian Bergstrom <boilingbergstrom(a)gmail.com> wrote:
This happened to me once, but it had nothing to do
with Ardour. My
VPN/Citrix login app took over sound somehow. :/
That's one of the few things I'm reasonably sure about is not causing
the problem here :-)
And, by the way, I do have sound via jack: hydrogen, qsynth, rakarrack
all work fine.
Andras
12:27 p.m.
On 2/26/10, Andras Simon <szajmi(a)gmail.com> wrote:
Sometimes ardour, while otherwise working perfectly,
goes completely
mute. Reconnecting to jack or restarting doesn't help. What should I
check or change?
(I'm using version 2.8.4 on Fedora 10 with no PulseAudio.)
It turns out that this is project-specific: I opened a few other
projects and sound works fine with them. But still no sound with the
one where I experienced the problem.
Andras
5:42 p.m.
On Fri, Feb 26, 2010 at 11:27 AM, Andras Simon <szajmi(a)gmail.com> wrote:
On 2/26/10, Andras Simon <szajmi(a)gmail.com>
wrote:
try running without plugins.
ardour2 -d
--p
Sometimes ardour, while otherwise working
perfectly, goes completely
mute. Reconnecting to jack or restarting doesn't help. What should I
check or change?
(I'm using version 2.8.4 on Fedora 10 with no PulseAudio.)
It turns out that this is project-specific: I opened a few other
projects and sound works fine with them. But still no sound with the
one where I experienced the problem.
6:08 p.m.
On 2/26/10, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
try running without plugins.
I'm an ardour newbie... I'm not sure I could run it with plugins even
if I wanted to...
ardour2 -d
This is what is says:
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf
Ardour/GTK 2.8.4
(built using 6077 and GCC version 4.3.2 20081105 (Red Hat 4.3.2-7))
Copyright (C) 1999-2008 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker
Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/simon/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/simon/.ardour2/ardour.rc
ardour: [INFO]: Using SSE optimized routines
Warning: Unable to create "trees" RDF storage.
Performance can be improved by upgrading librdf.
ardour: [INFO]: looking for control protocols in
/home/simon/.ardour2/surfaces/:/usr/lib64/ardour2/surfaces/
ardour: [INFO]: Control protocol Tranzport not usable
ardour: [INFO]: Control surface protocol discovered: "Generic MIDI"
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: "Wiimote"
ardour: [INFO]: Control surface protocol discovered: "Mackie"
system template path = /usr/share/ardour2/templates
loading bindings from /etc/ardour2/mnemonic-us.bindings
Session writable based on /opt/home/simon/music/ardour-sessions/222/
Thanks for looking into this!
Andras
6:18 p.m.
On Fri, Feb 26, 2010 at 5:27 PM, Andras Simon <szajmi(a)gmail.com> wrote:
It turns out that this is project-specific: I opened a
few other
projects and sound works fine with them. But still no sound with the
one where I experienced the problem.
Is everything OK with the wiring? Maybe you accidentally disconnected
some channels and now it plays but sound is not coming to main output
(this happened to me once)
Igor
6:24 p.m.
On 2/26/10, Igor Brkic <igor(a)hyperglitch.com> wrote:
On Fri, Feb 26, 2010 at 5:27 PM, Andras Simon
<szajmi(a)gmail.com> wrote:
Do you mean wiring in jack, or in ardour itself? Jack-wise everything
_seems_ to be OK, and ardour opened with other projects working fine
confirms this.
Within ardour, I'm not sure what to check...
Andras
It turns out that this is project-specific: I
opened a few other
projects and sound works fine with them. But still no sound with the
one where I experienced the problem.
Is everything OK with the wiring? Maybe you accidentally disconnected
some channels and now it plays but sound is not coming to main output
(this happened to me once)
6:55 p.m.
On Fri, Feb 26, 2010 at 11:24 PM, Andras Simon <szajmi(a)gmail.com> wrote:
Do you mean wiring in jack, or in ardour itself?
Jack-wise everything
_seems_ to be OK, and ardour opened with other projects working fine
confirms this.
Within ardour, I'm not sure what to check...
Try to create new session in ardour and add the same number of tracks
as in your problematic session. Then compare the wiring in Jack from
that session and problematic session.
After each track you add to ardour session, some wirings are
automatically created (system captures are connected to new tracks and
tracks are connected with master ins). I remember that once I tried
messing up something with that wiring and after that didn't hear the
sound anymore. Can't remember now what exactly I did.
Just to mention, I'm also a pretty much newbie with ardour and at the
time I had that problem I was even newbier :)
Igor
28 Feb
28 Feb
7:33 a.m.
On 02/26/2010 11:24 PM, Andras Simon wrote:
On 2/26/10, Igor Brkic<igor(a)hyperglitch.com>
wrote:
sometimes, ardour is unable to recreate some jack connections when it
loads a session, for reasons i haven't been able to pinpoint yet.
check the small "ardour log" window for error messages.
i suspect some zombie jack ports somewhere, but i don't know enough
about jack internals to be sure. all i know is that restarting jack and
restarting ardour always fixes the issue for me.
and ever since i've taken to scripting my session set-up, no new
bite-marks have shown up on my keyboard. ;-D
On Fri, Feb 26, 2010 at 5:27 PM, Andras
Simon<szajmi(a)gmail.com> wrote:
Do you mean wiring in jack, or in ardour itself? Jack-wise everything
_seems_ to be OK, and ardour opened with other projects working fine
confirms this.
Within ardour, I'm not sure what to check... It turns out that this is project-specific: I
opened a few other
projects and sound works fine with them. But still no sound with the
one where I experienced the problem.
Is everything OK with the wiring? Maybe you accidentally disconnected
some channels and now it plays but sound is not coming to main output
(this happened to me once)
2 Mar
2 Mar
12:52 p.m.
On 2/28/10, Jörn Nettingsmeier <nettings(a)folkwang-hochschule.de> wrote:
sometimes, ardour is unable to recreate some jack
connections when it
loads a session, for reasons i haven't been able to pinpoint yet.
check the small "ardour log" window for error messages.
I don't know how to bring up that window, but now I had a spontaneous
disconnect from jackd, and after restarting jackd and reconnecting
ardour, I see
[ERROR]: could not reconnect system:capture_1 and ardour:Audio 3/in 1 (err = -1)
[ERROR]: could not reconnect system:capture_2 and ardour:Audio 3/in 2 (err = -1)
[ERROR]: could not reconnect ardour:Audio 3/out 1 and ardour:master/in
1 (err = -1)
[ERROR]: could not reconnect ardour:Audio 3/out 2 and ardour:master/in
2 (err = -1)
And ardour is muted again...
i suspect some zombie jack ports somewhere, but i don't know enough
about jack internals to be sure. all i know is that restarting jack and
restarting ardour always fixes the issue for me.
Not for me, it seems.
and ever since i've taken to scripting my session
set-up, no new
bite-marks have shown up on my keyboard. ;-D
I'm definitely interested. Time for a friendly session with google :-)
Andras
5382
days inactive
5386
days old
linux-audio-user@lists.linuxaudio.org
10 comments
5 participants
participants (5)
-
Andras Simon -
Brian Bergstrom -
Igor Brkic -
Jörn Nettingsmeier -
Paul Davis