View Issue Details

IDProjectCategoryView StatusLast Update
0007073ardourbugspublic2017-02-12 07:44
ReporterOliver Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Platformi686OSXubuntuOS Version16.04 LTS
Product Version5.4 
Summary0007073: 'Auto input' not working as expected
DescriptionPreviously, arming a track for recording when transport was stopped allowed to see the input signal to that track on the track meter. In Ardour 5.4, I need to manually select 'In' to accomplish that. The behaviour is the same if 'Auto input' is selected or not.

If neither 'Disk' nor 'In' is selected manually, I was expecting that 'Auto input' will select 'In' when arming the track. However, only when playing back is 'Disk' automatically selected (indicated by the yellow outline of the button).

As a side note, the tool tips 'Monitor playback' and 'Monitor input' were slightly confusing to me, as these buttons are not related to the 'Monitor section', but literally switch the input to the track.
TagsNo tags attached.

Activities

x42

2016-10-13 17:13

administrator   ~0018804

Check Preferences > Audio > Monitoring

  * tape machine mode is disabled
  * record monitoring: Ardour

see also https://github.com/Ardour/ardour/raw/master/doc/monitor_modes.pdf

Oliver

2016-10-13 20:51

reporter   ~0018810

Thanks a lot for the quick response, it works now as desired.

The pdf sheet: wow, that is almost quantum physics!

Oliver

2016-10-15 10:23

reporter   ~0018817

On closer inspection of the pdf, I find that no matter what either Monitoring Mode, Tape Machine Mode, Master Rec Enable, Transport, or Auto Input is set to: if Track Rec Enable is selected, I should see the input signal on the track meter.

That is not what I find. Only with the particular settings given above by x42 can I see the input signal on the meter. I actually use the headphone of my hardware for monitoring, but I like to be sure the signal arrives at the track before recording (and not watching the meter, then).

Could this please be checked?

Oliver

2016-10-15 17:15

reporter   ~0018820

Further, I created now a new session (all observations before where in one session). With the same 'Monitor Modes' setting, the track meter works as expected in that new session (except maybe that the 'In' button is still not outlined, but I see the input signal on the meter). Can something be mixed up in that affected session? It went through a number of crashes.

Just to make it clear, if I manually select 'In', then I see the signal on the track meter (and also on the Master Track).

x42

2016-10-15 18:28

administrator   ~0018821

That's the quantum mechanics part :)

The "monitor mode" list is the default for new sessions. You can set custom meter-positions later.

The default is that when record-arming a track, the meter-point automatically changes to "In" and when disabling rec-arm, it reverts to the previous position (default: "Post").

I just tested various preferences & session-props (not all 64, but some). In some case it needs a play/stop cycle for them to apply, but other than that it works as documented.

Do you have a step by step recipe how to get to some _invalid_ settings?

What are the settings (prefs > tape machine mode, record-monitoring and session-props > monitoring > auto-input) in case where "In" is not implicitly active?


> It went through a number of crashes.

That's worrying. Could you get a backtrace? https://ardour.org/debugging_ardour

Oliver

2016-10-15 18:56

reporter   ~0018822

The settings are as follows:
   Record monitoring - Audio hardware
   Tape machine mode - disabled
   Auto-Input - Enabled

The monitoring position in the channel strip is indicated as 'Post'.

It really seems to be session specific, as even here it works as expected on a new session. On the crashes: I was working on a recording, so I did not bother to debug any further, sorry, just restarted. The only obvious thing I remember is that once the 'Master Bus' was not at the top any more after a crash, but I just moved it back.

I just mentioned the crashes in case this could have had an influence on the monitoring issue.

The effect of not seeing the input signal when armed on the track meters is the same for all four tracks in that session, by the way.

I am working on this session quite some time, so I have not so much hope for a step-by-step recipe - but I will try. We are dealing with Schrödinger's cat, maybe...

Oliver

2016-10-15 19:05

reporter   ~0018823

Another piece of information: Now I added a new track to the affected session, and monitoring works as expected.

When I arms this new track, the metering point indication on the track strip changes from 'Post' to 'In', contrary to the other, old tracks.

I cycled through the metering points once, but for no selection does it work for the old track.

paul

2016-10-15 20:39

administrator   ~0018824

There is no "monitoring position" indicated in the channel strip - you are looking at the *metering* position. This is 100% independent of monitoring.

In addition, if "Monitoring" is set to Audio Hardware, then ardour will NEVER never provide record monitoring.

Oliver

2016-10-16 08:27

reporter  

Oliver

2016-10-16 08:30

reporter   ~0018825

To illustrate the problem further I attached a screen shot of the mixer view, with all tracks record enabled. Only the rightmost track shows 'In' for the metering point (and 'Post' if I disengage record enable). Shouldn't all tracks behave the same?

paul

2016-10-18 15:15

administrator   ~0018841

Agreed, that behaviour seems very odd. Can you attach the session file (.ardour) ?

Oliver

2016-10-18 20:49

reporter  

MeterTest.ardour (25,987 bytes)

Oliver

2016-10-18 20:50

reporter   ~0018844

Attached an .ardour file from a simplified session: only two tracks, one shows the problem, the other behaves as expected.

Oliver

2017-02-12 07:44

reporter   ~0019365

In latest Ardour 5.6.0 "Possible Musics" the meter point works as expected for the session attached to this bug report.

Issue History

Date Modified Username Field Change
2016-10-13 16:57 Oliver New Issue
2016-10-13 17:13 x42 Note Added: 0018804
2016-10-13 20:51 Oliver Note Added: 0018810
2016-10-13 20:52 Oliver Status new => closed
2016-10-13 20:52 Oliver Resolution open => no change required
2016-10-15 10:23 Oliver Note Added: 0018817
2016-10-15 10:23 Oliver Status closed => feedback
2016-10-15 10:23 Oliver Resolution no change required => reopened
2016-10-15 17:15 Oliver Note Added: 0018820
2016-10-15 17:15 Oliver Status feedback => new
2016-10-15 18:28 x42 Note Added: 0018821
2016-10-15 18:56 Oliver Note Added: 0018822
2016-10-15 19:05 Oliver Note Added: 0018823
2016-10-15 20:39 paul Note Added: 0018824
2016-10-16 08:27 Oliver File Added: Screenshot_2016-10-16_10-24-36.png
2016-10-16 08:30 Oliver Note Added: 0018825
2016-10-18 15:15 paul Note Added: 0018841
2016-10-18 20:49 Oliver File Added: MeterTest.ardour
2016-10-18 20:50 Oliver Note Added: 0018844
2017-02-12 07:44 Oliver Note Added: 0019365
2017-02-12 07:44 Oliver Status new => closed
2017-02-12 07:44 Oliver Resolution reopened => fixed