27 Jan
2010
27 Jan
'10
7:21 a.m.
I installed Ardour 2.8.4. (6077) on a new Arch
system today and it's showing some strange things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
* When following Jack transport:
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
Anyone seeing similar things ? I just want to
find out if this only affects the Arch binary,
or all systems.
Ciao,
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
27 Jan
27 Jan
7:36 a.m.
On Wed, Jan 27, 2010 at 6:17 AM, <fons(a)kokkinizita.net> wrote:
I installed Ardour 2.8.4. (6077) on a new Arch
2.8.5 came out last week ....
system today and it's showing some strange
things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
this is caused by a bug that was believed fixed in 2.8.4, but *might*
be hanging around because of the contents of your ~/.ardour2/ardour.rc
file. please post its contents.
* When following Jack transport:
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
i don't believe i've seen this one before. i'll check it in the next hour or
so.
7:55 a.m.
Excerpts from Paul Davis's message of Wed Jan 27 12:36:11 +0100 2010:
On Wed, Jan 27, 2010 at 6:17 AM,
<fons(a)kokkinizita.net> wrote:
I removed ardour.rc, the mute behavior didn't change. (2.8.6)
Transport rolls now and I can confirm that the counters are stuck
Regards,
Philipp
I installed Ardour 2.8.4. (6077) on a new Arch
2.8.5 came out last week ....
system today and it's showing some strange
things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
this is caused by a bug that was believed fixed in 2.8.4, but *might*
be hanging around because of the contents of your ~/.ardour2/ardour.rc
file. please post its contents.
* When following Jack transport:
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
i don't believe i've seen this one before. i'll check it in the next hour or
so.
10:23 a.m.
On Wed, Jan 27, 2010 at 06:36:11AM -0500, Paul Davis wrote:
I fixed the ardour.rc as suggested in previous
messages. But this was not the file from a previous
install, but the one created by the new Ardour.
Seems to be confirmed. Not a showstopper for me as the
remote control is used only in a system where the user
doesn't see Ardour at all... Could this be done by OSC
as well ?
Ciao,
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
2.8.5 came out last week ....
I noticed... Arch is usually quite fast in updating
packages (it's a 'rolling release' system), so I'll
have it soon.
* On newly
created sessions, the mute buttons
affect the meters but not the signal.
this is caused by a bug that was believed fixed in 2.8.4, but *might*
be hanging around because of the contents of your ~/.ardour2/ardour.rc
file. please post its contents. * When
following Jack transport:
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
i don't believe i've seen this one before. i'll check it in the next hour or
so.
11:21 a.m.
On Wed, Jan 27, 2010 at 9:19 AM, <fons(a)kokkinizita.net> wrote:
Seems to be confirmed. Not a showstopper for me as
the
remote control is used only in a system where the user
doesn't see Ardour at all... Could this be done by OSC
as well ?
yes. see libs/ardour/osc.cc for the messages. quite a few people have
done this with OSC.
4:55 p.m.
On Wed, Jan 27, 2010 at 10:21:46AM -0500, Paul Davis wrote:
On Wed, Jan 27, 2010 at 9:19 AM,
<fons(a)kokkinizita.net> wrote:
I've been testing this, and things work apart from
some oddities:
- 'locate-and-roll' is ignored completely if the
transport is already rolling.
- the alternative, 'locate' followed by 'play' always
does the locate part but ignores the 'play' if the
transport was already rolling while receiving the
'locate'. In that case Ardour locates and stops.
- 'locate', wait 0.1 seconds, 'play' always works.
This is similar to what I see when using Jack transport
instead: Ardour just ignores a 'play' command in some
cases (e.g. immediately following a locate) or stops
when receiving a locate while playing, instead of
remembering it has to play after having located.
No big deal for interactive use - the user will just
click play again. But for real remote control it's a
pain.
There are other things along the same line: any OSC
'*_toggle' command is useless unless you know the current
state of the thing being toggled. That's possible only
by looking at the GUI, and in that case you don't need
remote control.
A reliable remote control protocol either has to provide
feedback, or be usable blindly wich means it must never
throw away a command just because it can't be obeyed
without delay.
Ciao,
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
Seems to be confirmed. Not a showstopper for me
as the
remote control is used only in a system where the user
doesn't see Ardour at all... Could this be done by OSC
as well ?
yes. see libs/ardour/osc.cc for the messages. quite a few people have
done this with OSC. 
7:18 p.m.
On Wed, Jan 27, 2010 at 3:51 PM, <fons(a)kokkinizita.net> wrote:
There are other things along the same line: any OSC
'*_toggle' command is useless unless you know the current
state of the thing being toggled. That's possible only
by looking at the GUI, and in that case you don't need
remote control.
point taken for the current state of things. i'll be sure to address that.
however, this isn't actually true in general. Ardour (thanks to liblo)
supports the "standard" OSC query format
(/path/to/thing/#current_value)
err, well. the code is there to do this. its disabled right now.
--p
7:48 a.m.
Excerpts from fons's message of Wed Jan 27 12:17:11 +0100 2010:
I installed Ardour 2.8.4. (6077) on a new Arch
system today and it's showing some strange things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
* When following Jack transport:
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
Anyone seeing similar things ? I just want to
find out if this only affects the Arch binary,
or all systems.
Ciao,
I don't think that it's arch specific.
2.8.6 is available now btw., at least from AUR.
Muting behaves the same there, and it seems to be an issue with ardour's
default behavior. Right-click on the mute button and click Main Outs.
Now it should behave the way you and I would expect it to.
Regarding transport.. Ardour2.8.6 doesn't follow qjackctl (svn) at all,
but this is also with tschack, any of the three could be responsible and
I don't have the time to check atm.
Regards,
Philipp
7:54 a.m.
Hi Fons,
I'm on Arch, too (x86_64). I'm using the same version of Ardour. Jackd --
version is 0.118.2.
On Wednesday 27 January 2010 12:17:11 fons(a)kokkinizita.net wrote:
I installed Ardour 2.8.4. (6077) on a new Arch
system today and it's showing some strange things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
I cannot reproduce this one. Mute works as it should.
* When following Jack transport:
I normally don't use jack-transport, so I'm not really shure, but it
doesn't
seem to work at all over here. I created a new session, imported some Audio
and played it once in the session. When I now click on play, in qjackctl,
'Stopped' switches to 'Rolling', but there is no reaction in Ardour. Same
with
the jack_transport command-line control. Am I missing something? I mean, do I
need to make Ardour sensible for jack-transport in any way?
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
Anyone seeing similar things ? I just want to
find out if this only affects the Arch binary,
or all systems.
Ciao,
I hope that helps,
Sincerely, Bjoern
8:05 a.m.
fons(a)kokkinizita.net wrote:
I installed Ardour 2.8.4. (6077) on a new Arch
system today and it's showing some strange things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
hallo,
i am running sidux with repo jackd v0.118.0 and selfbuild of ardour 2.8.5.
muting works here as expected.
* When following Jack transport:
- Play for a few seconds
- Use the 'rewind to zero' on e.g. qjackctl
- Ardour goes to zero, and restarts playing,
but the position counters remain at the
place wher the 'rewind' was done, until
either
- position goes beyond this place
- or you stop.
this behaves pretty the same here. no matter if jack or ardour is the
transport master.
cheers,
doc
Anyone seeing similar things ? I just want to
find out if this only affects the Arch binary,
or all systems.
Ciao,
8:22 a.m.
On Wed, 2010-01-27 at 12:17 +0100, fons(a)kokkinizita.net wrote:
I installed Ardour 2.8.4. (6077) on a new Arch
system today and it's showing some strange things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
Hi fons, I can confirm this behaviour, and as mentioned by Paul Davis it
has to do with your ardour.rc. I changed the following values from 0 to
1:-
<Option name="mute-affects-pre-fader" value="1"/>
<Option name="mute-affects-post-fader" value="1"/>
<Option name="mute-affects-control-outs" value="1"/>
<Option name="mute-affects-main-outs" value="1"/>
Not sure where ardour.rc gets sourced for us using Arch though. I think
Paul (las) was the one who helped me trace it down at #ardour as well.
8:29 a.m.
Excerpts from Ng Oon-Ee's message of Wed Jan 27 13:21:59 +0100 2010:
On Wed, 2010-01-27 at 12:17 +0100,
fons(a)kokkinizita.net wrote:
There is /etc/ardour2/ardour_system.rc
<Option name="mute-affects-pre-fader" value="yes"/>
<Option name="mute-affects-post-fader" value="yes"/>
<Option name="mute-affects-control-outs" value="yes"/>
<Option name="mute-affects-main-outs" value="yes"/>
Whereas an automatically created ~./ardour2/ardour.rc says:
<Option name="mute-affects-pre-fader" value="0"/>
<Option name="mute-affects-post-fader" value="0"/>
<Option name="mute-affects-control-outs" value="0"/>
<Option name="mute-affects-main-outs" value="0"/>
Note that I deleted the whole ~./ardour2 folder.
No idea why ardour2.8.6 gets this wrong..
Regards,
Philipp
I installed Ardour 2.8.4. (6077) on a new Arch
system today and it's showing some strange things.
* On newly created sessions, the mute buttons
affect the meters but not the signal.
Hi fons, I can confirm this behaviour, and as mentioned by Paul Davis it
has to do with your ardour.rc. I changed the following values from 0 to
1:-
<Option name="mute-affects-pre-fader" value="1"/>
<Option name="mute-affects-post-fader" value="1"/>
<Option name="mute-affects-control-outs" value="1"/>
<Option name="mute-affects-main-outs" value="1"/>
Not sure where ardour.rc gets sourced for us using Arch though. I think
Paul (las) was the one who helped me trace it down at #ardour as well.
9:43 a.m.
On Wed, Jan 27, 2010 at 08:21:59PM +0800, Ng Oon-Ee wrote:
Hi fons, I can confirm this behaviour, and as
mentioned by Paul Davis it
has to do with your ardour.rc. I changed the following values from 0 to
1:-
<Option name="mute-affects-pre-fader" value="1"/>
<Option name="mute-affects-post-fader" value="1"/>
<Option name="mute-affects-control-outs" value="1"/>
<Option name="mute-affects-main-outs" value="1"/>
They are all at zero here. AFAIK, this file was created
by the new Ardour. This is a completely new system, and
I have not restored the complete contents of $HOME from
backup yet, just some essential things.
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
5417
days inactive
5417
days old
linux-audio-user@lists.linuxaudio.org
13 comments
7 participants
participants (7)
-
Bjoern Lindig -
Dragan Noveski -
fons＠kokkinizita.net -
hollunder -
Ng Oon-Ee -
Paul Davis -
Ray Rashif