Anyone have experience using Procmon for Windows?

[talby]

Nothing selected defaults to Software, to my experience.

[irpacynot]

Looks like right now the GUI rendering mode is set to software renderer.

[Peter Widdicombe]

... did you change it, and did it make a difference; or still glitching video ?

[irpacynot]

... did you change it, and did it make a difference; or still glitching video ?

Changed it to OpenGL last night before going to bed. So far, so good. But, I don't know, man. I think it's outside of Waveform now. I think anytime either Firefox or Microsoft is about to update, they're automatically sending the data to my PC in the background, 'cause sure enough, almost every time I experience these major hiccup issues, I get some type of Windows update, or Firefox wants to update when I restart it shortly after closing out of Waveform.

I've made sure that I shut off automatic updates for both, but I think Firefox has covertly taken that option out, as I haven't been able to find it now in the settings.

Ah well...that's the sum of a Corpacracy.

Thanks for the help, all the same. I'll see, though, if OpenGL can help mitigate the background goings on.

[talby]

That's easy to test. If working on a Waveform session, just disconnect from the net and observe.

If disconnected from teh net, you could for that time also disbale any anti virus app. I think Win10/Win11 bring its own one, but I don't know about it and cannot guide you where to pause it.

[irpacynot]

Let me ask you this, is Waves MaxAudio Service necessary? I'm not familiar with it, but when looking in my start-up apps, it's listed as "high impact." Not sure what it does or if it's perhaps something I should disable when using Waveform.

[talby]

Here are all settings, which I found by now, which to me appear worth to give them a try.
Note that I looked them up in W14 PRO and not all of them might be available in lower editions or versions.

SETTINGS - GENERAL - SAVING - Enable autosave --> enable/disable
SETTINGS - MIDI Devices - MIDI OPTIONS - Scan for new MIDI devices --> min/max
SETTINGS - PLUGINS - PLUGIN VIEW OPTIONS - Automatically check for newly added plugins --> enable/disable
SETTINGS - PLUGINS - PLUGIN MANAGEMENT - Plugin Sandboxing --> enable/disable
SETTINGS - ADVANCED - EXPERIMENTAL - Enable shared playback memory --> enable/disable
SETTINGS - ADVANCED - PERFORMANCE - CPU cores to use --> min/max
SETTINGS - ADVANCED - PERFORMANCE - GUI rendering mode --> choice1/choice2

[irpacynot]

Here are all settings, which I found by now, which to me appear worth to give them a try.
Note that I looked them up in W14 PRO and not all of them might be available in lower editions or versions.

SETTINGS - GENERAL - SAVING - Enable autosave --> enable/disable
SETTINGS - MIDI Devices - MIDI OPTIONS - Scan for new MIDI devices --> min/max
SETTINGS - PLUGINS - PLUGIN VIEW OPTIONS - Automatically check for newly added plugins --> enable/disable
SETTINGS - PLUGINS - PLUGIN MANAGEMENT - Plugin Sandboxing --> enable/disable
SETTINGS - ADVANCED - EXPERIMENTAL - Enable shared playback memory --> enable/disable
SETTINGS - ADVANCED - PERFORMANCE - CPU cores to use --> min/max
SETTINGS - ADVANCED - PERFORMANCE - GUI rendering mode --> choice1/choice2

Okay, so let me ask you about some of the options:

Sandboxing: Is that simply ensuring the plugin is not affected by other plugins on other tracks?
Shared playback memory: Not sure at all what that indicates.
GUI rendering mode: Any explanation given by Tracktion as to what the different choices do?

Thanks

[talby]

First of all, for testing, just test it to get your problem located or solved. You should anyway have backups of your important data.

If the sandbox is active, then all plugins which are not an internal part of WF, so, all plugins not listed under Waveform, will run in that one sandbox. If one plugin crashes, WF is supposed to continue to work, you restart the sandbox, all plugins are reloaded into the new sandbox, and the show can continue without a restart of WF. Without sandboxing WF might become pushed to crash by a crashing plugin. But without sandboxing communcation paths between WF and the plugins is easier. So, the sandbox can save your session, or no sandbox can avoid bugs being still undiscovered in the sandboxing code and causing issues.

Shared Playback memory. I have no reliable idea. As it's experimental, it is obviously something what the devs programmed as an improvement, but they still want to observe that it is running stable for everybody in the wild stable. If they won't see it pop up in crash reports, then it will move from "experimental" = "user activate this and know that you are testing it", to under the hood having become the new way of doing things for everybody and not making any opt-in (= test warning) anymore.

Rendering mode: there are various techniques how a computer could draw graphics. All your apps, an office app, some internet browser, they all use the one they like for letting the computer draw all of their stuff onto the screen. Some of these techniques became outdated over the years, and replaced by other techniques. They are still heavily in use on many systems, though. WF obviously gives you the choice to try two of them according to your own experience on your particular computer (each computer might behave slightly different, depending on the chips and software in use).
So,this is exactly made for your use case. There is an issue with the app running smoothly? Try it with the other graphical rendering technique and maybe this solves your issue!

[irpacynot]

First of all, for testing, just test it to get your problem located or solved. You should anyway have backups of your important data.

If the sandbox is active, then all plugins which are not an internal part of WF, so, all plugins not listed under Waveform, will run in that one sandbox. If one plugin crashes, WF is supposed to continue to work, you restart the sandbox, all plugins are reloaded into the new sandbox, and the show can continue without a restart of WF. Without sandboxing WF might become pushed to crash by a crashing plugin. But without sandboxing communcation paths between WF and the plugins is easier. So, the sandbox can save your session, or no sandbox can avoid bugs being still undiscovered in the sandboxing code and causing issues.

Shared Playback memory. I have no reliable idea. As it's experimental, it is obviously something what the devs programmed as an improvement, but they still want to observe that it is running stable for everybody in the wild stable. If they won't see it pop up in crash reports, then it will move from "experimental" = "user activate this and know that you are testing it", to under the hood having become the new way of doing things for everybody and not making any opt-in (= test warning) anymore.

Rendering mode: there are various techniques how a computer could draw graphics. All your apps, an office app, some internet browser, they all use the one they like for letting the computer draw all of their stuff onto the screen. Some of these techniques became outdated over the years, and replaced by other techniques. They are still heavily in use on many systems, though. WF obviously gives you the choice to try two of them according to your own experience on your particular computer (each computer might behave slightly different, depending on the chips and software in use).
So,this is exactly made for your use case. There is an issue with the app running smoothly? Try it with the other graphical rendering technique and maybe this solves your issue!

Many thanks!

Will tinker with all those things.

To try and offer perhaps more clues to consider, I've been using Tracktion 12 (I updated to 12.5, but didn't care for the interface changes and reverted back to the last version of 12 before 12.5 came out) for, well, probably about three or so years now. Didn't experience these issues until the past couple of months.

Now, I did update to a new PC and Windows 11, but that was 13 months ago. Again, the issue seems to be only a couple of months old, and I never tinkered with any of those parameters you mentioned.

That being said, I did install some new drivers shortly before these issues started. I had to start using a Behringer audio interface because my old Roland VS started to break down. But the drivers, I assumed, were simply affecting the audio end of things. Also, I stopped using it and changed the audio driver in Waveform back to its default (I was able to find an IDE drive in my Roland that was still functioning okay, and restarted using that to record my tracks).