11.1.3 Meter Bug

[Norad155]

Metering no longer displays on a track when there is no output assigned, but there are active sends.

Can anyone else confirm... or am I missing an obvious setting?... works in 11.1.2 and 10.3.7 (and every version I've ever used)

Steps to recreate:

1. Create a track.
2. Select "no output"
3. Add a send at unity.
4. Slap some audio on it.
5. observe the absence of metering on the channel.

System:
HD Native 10.1.3

[connor@@vid]

I've just checked 11.1.2 and 11.0 and they behave the same as 11.1.3 when following your steps to recreate: no signal on the track meter.

[Norad155]

Really?... that's interesting... I'll have to downgrade and double check (not that I don't trust you, it's just a part of my template so I thought I would have noticed)

Definitely shows in 10.

Is this expected behavior in 11? (I don't agree with it FWIW if it is expected behavior... pre-fader metering should show regardless of where it's going.)

[8dB.co.uk]

From memory, hasn't this always been the case?

[Norad155]

No... before 11 it showed in the meters. (I just triple checked as I was mistaken in the OP regarding earlier versions of 11)

Maybe I'm in the minority, but I know several people that use this workflow to automate bussing.

For now I just assigned the track output to a dummy bus to get meters... but... still... it makes me sad...

Best,
-Major

[8dB.co.uk]

Ah yes. It would be better if Avid implemented automated routing, but they never will.

[Nathan W.]

Have the same issue. The EDIT window track meter doesn't display if there's "no output." This is NOT to be confused with the SEND metering which works great. Don't believe this is limited to 11.1.3 but have seen it in all other versions of 11.

Is this a new "feature" or a bug? Couldn't find info.

ProTools 11.1.3 HD
iMac Late 2013
OSX Mavericks 10.9.2

[connor@@vid]

I will investigate further to determine if this is just an unfixed bug or a design decision.

[Norad155]

Thanks Connor!

[C]

This was designed behavior when the question was asked shortly after release. workaround is to have a dummy bus to output your track to instead.

Weird -Yes.
Bug - Arguable.
Change - Unlikely.

C