Fake "Monitor on"

Forums

It took me years to learn that some kinds of problems caused by plugins can be fixed by switching audio tracks to Monitor on. Some plugins don't make problems when transport is stopped, others seem to need a constant input data stream, e.g. LSP plugins or PitchNet. The problems are not only related to the plugins, they can even affect Qtractor's shutdown and cause hanging.

But having tracks on monitor could have some side effects like unwanted audio while playing.

Would it be possible that "Monitor off" for audio tracks would be in fact the same as "Monitor on" with audio data come from a hidden input bus nothing else can connect to, so it's ensured only silence comes from it?

Permalink

I know this question isn't directed at me, but I’ll offer my perspective, perhaps it might help.

To me, it would make much more sense to set the input bus fader to 0 (or insert a mute plugin, like "Bollie Fader," onto it) and continue using the monitor button in that scenario.

Alternatively, for more precise control, you could create a dedicated "Mute" input bus with a mute plugin always active. When I’m not recording, the input is set to this "Mute" bus; when I am recording, I simply change the input.

In fact, when setting up templates for this workflow, it would be logical to have the "Mute" bus as the default input, only changing it via the track properties when you’re ready to record.

Why change Qtractor’s underlying logic? The current approach is sound and offers both control and efficiency in every situation.

That said... I’ve always wished it were possible to select "none" as an input or output bus. That would be useful in many scenarios, including this one.
It would avoid having to explicitly create a silence bus.

It took me a while to find out how to handle plugins that need this workaround.

I am afraid that new Qtractor users may run into the same problem and dump Qtractor because that problem doesn't seem to exist in other DAWs.

EDITED

Conclusion:
1_ Disabling monitoring on tracks should not affect the plugin rack.
2_ Mute, however, should do it, both on audio tracks and on MIDI tracks that include audio.

The solution is not a "fake monitor," but rather ensuring that the plugin rack remains unaffected by monitoring actions on audio tracks.

...

The mental process that led me to this conclusion:

I’ve verified that MIDI tracks are not affected by this.
If you load a noise generator onto a MIDI track, it continues to produce noise even when the track is neither selected nor active.

The same applies to audio and MIDI buses.

Audio tracks, however, behave differently.
It is as if, for audio tracks, the plugin chain is explicitly disconnected from the audio signal path.

I haven’t checked the code, but you might be right, it would be worth looking into how this works.
Actually, it’s not really about the input bus; rather, it concerns the actions Qtractor performs on an audio track when monitoring is disabled and the track is not selected.

Removing the current behavior under these conditions would allow plugins on audio tracks to continue generating/processing sound even when the track is not selected.

Perhaps the conditional logic "if X condition is met, execute Y function" should be shifted from "monitor" to "mute."
That way, Audio and MIDI tracks containing audio plugins would be muted correctly. (Currently, the mute does not affect them.)

These are just assumptions, though.
So, it’s quite possible I’m talking nonsense...

Permalink

hold your horses!

please have a serious look on the Evil Signal Flow Diagram

the "monitor" on tracks is about the respective signal type, either audio or MIDI; on a MIDI track it commutes on or off the input MIDI stream into the track plugin-chain; on audio tracks it lets the input audio stream go through the audio track's plugin-chain when set on, drops it off otherwise.

take note that this is only the case when not playing ie. transport is stopped or paused; when monitor is off, no input goes a tracks plugin chain whatsoever, unless it's armed for recording or current if Auto Monitor is on.

that means, that when "monitor" is off, and specially for audio tracks only, the track's plugin-chain is not being run, behaving as if all its plugins are (auto-)deactivated, but this is only while playback is not rolling and the track is neither R-armed or current in auto-monitor mode.

all this behavior is quite old (almost two decades old) and I get the shivers when even thinking about to change on any of that :)

we'll see!

Permalink

I don’t really see the point of editing a plugin when no is playing. I’m not saying there aren’t any legitimate reasons for doing so, just that they aren’t clear to me.

What concerns me is that @bluebell mentioned this could cause certain plugins to freeze the program.

Looking at the diagram, preventing audio from reaching the crossover point—before it even hits the plugin chain—shouldn’t necessarily disable the chain itself.

On the other hand, engaging the mute function should disable it, but currently, it doesn’t.

These are just some observations for you to keep in mind.

Personally, I don’t consider these to be major issues, and I completely understand why you might prefer not to touch that part of the code. I’ve taken a quick look at it, and it appears to be a very sensitive area that involves complex interdependencies between various critical components of the program.

1.) Not "freeze the program", only "freeze the program when Qtractor is closed"
2.) Some events at transport stop (especially the event, that the transport is stopped) are not reliably fed to the plugin chain.

Both issues smell like a race condition and might or might not occur, depending on CPU power, kernel, userland, phase of moon and whatever.

But both would be cured if the plugin chain would get a permanent input stream.

If the price to be paid is too high, then it was a pipe dream.

Permalink

PitchNet needs to be notified that transport is stopped. Then it analyzes the recorded audio. This and auto-scrolling work reliably when the track's Monitor is on. Not reliably when Monitor is off.

Since this is a "sometimes it works"-bug I suspect a race condition.

Some plugins (LSP) seem to affect Qtractor's shutdown as well and this is also fixed with Monitor on. My idea was like fix them all by providing a fake input source for the audio tracks' plugin chain when Monitor is off and transport is stopped.

Contras:

  • Might be complicated.
  • Might lead to another race condition. If the switch is too slow and swallows transport stop then the plugins will behave as before. No cigar.

However, the workaround "Monitor on" works reliably, but new Qtractor users won't know about it.

Permalink

Related to this:

Should a MIDI or Audio track be automatically selected when a plug-in is added, or when its GUI or properties window is opened?
Or simply when the plugin rack is clicked... just like any other part of a track.

That would avoid the confusion of loading a synthesizer and not finding any sound until the track is selected, and while it wouldn't completely solve this, it would mitigate the possibility of it occurring.

I believe this is an expected behavior; I’m not aware of any technical or practical obstacles that would prevent it from working this way.

Permalink

the whole reason to have these tracks (auto-)monitor controls are, yes, you guess it obviously right, to let you monitor your live input through audio (eg. guitar) or MIDI (eg. keyboard controller) inputs, and to have it rendered through track's audio fx or MIDI instruments plugins resp.

AND all that while NOT engaged in playback (or recording)!

the keywords there are just: monitoring live input !

as I understand the trouble comes when you're working with a plugin that expects live input all the time and it's inserted on an audio track which is not monitored, not record-armed nor current highlighted (and auto-monitor is on) and all of that only when not engaged in playback rolling...

sorry to tell, in any of those (transitional) cases, those plugins won't meet their expectations ever and that's not going to get fixed any day so soon...

but there are some controls that let you mitigate the damage:

  • Track > Auto Monitor - this gets monitor on automagically on the current highlighted track;
  • Track > Auto Deactivate - when on, this might even get it worse in this regard for those troubled plugins ;)

hth.
cheers

Permalink

My last question wasn’t directly related to the topic we were discussing.

I simply don’t understand why clicking on the plugin rack doesn’t select the track.

Since "Auto Monitor" is the default setting, it would make sense for the track to be selected automatically when a synth is loaded, allowing the synth to work right away. Currently, after loading a synth, you have to explicitly click on the track to select it.

Why doesn’t clicking on the plugin rack select the track, isn’t it part of the track?

It’s more of a doubt than anything else.

Permalink

it never did and... it's complicated :)

in the code, plugin-lists are in fact owned by tracks (or buses), but they have no link-back to their respective owners, so having it to select a track when one of its plugins is raised is a full search and lookup operation, something a little bit costly, even more so on every click, with a rather dubious benefit :)

hyu.
byee

Permalink

took the plunge and it might be simpler than thought earlier--and better yet without shivering:)

check out qtractor >= v1.6.4.28git.5f044c

cheers

Permalink

It now works in a more coherent way; even "Auto-deactivate" makes more sense.

For me, the only thing still missing is what I mentioned earlier:
Moving the "deactivate plugins" behavior to the Mute function, for both audio and MIDI tracks.
Mute should disable the plugin chain, so that it functions as a true track mute.

But that’s just my take, perhaps I’m overstating it! :)

Add new comment

The content of this field is kept private and will not be shown publicly.

Markdown

  • Parses markdown and converts it to HTML.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id> <img src alt height width> <strike> <pre> <p> <br>
  • Lines and paragraphs break automatically.

Filtered HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <b> <i> <pre> <img src alt height width> <strike>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
File attachments
Unlimited number of files can be uploaded to this field.
2 MB limit.
Allowed types: jpg jpeg gif png txt doc docx xls xlsx pdf ppt pps odt ods odp zip gz bz2 xz patch diff wav ogg flac ogv mp4 qtz.