Plugins crashing

[x42]

Ardour build 8.4.126 fixed the staticky/crackling problem on my particular machine on the plugins that were giving me trouble when placed on aux sends (Waves Abbey Road chambers and dbx-160, UAD distressor, waterfall, Lexicon224, and Relab LX480 essentials).

This is great news! Thanks for testing on short notice.

I do have a Xeon CPU here (running Windows 10)

I don't believe those have support avx512f. At least two Xeon machines I have access to only support avx. Check Ardour's startup message output. Early on there should be

Code:

Ardour: [INFO]: AVX512F capable processor

[johne53]

Ah thanks Robin - that explains why I've not been not seeing the problem here...  the messages I see here say this:-

Code:

Mixbus32C: [INFO]: AVX capable processor
Mixbus32C: [INFO]: CPU brand:      Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
Mixbus32C: [INFO]: Using AVX optimized routines

[Monofin]

Cool stuff, @x42 :-) Thanks: I'll see what results I get on 8.4.122 and report back.
Just wondering: what's the kind of cycle time between Harrison updates vs. Ardour bugfixes?

[johne53]

Cool stuff, @x42 :-) Thanks: I'll see what results I get on 8.4.122 and report back.

Around 8 or 9 posts ago @mattjmail reported that it's still broken in 8.4.122 - i.e. updating binutils didn't fix it in Ardour. You'll need to be testing with 8.4.126 or later.

[MikeTPR]

Another affected here. Issue with the Pulsar Primavera.
w10, Intel® Core™ i7-7800X CPU @ 3.50GHz, 32c v9 last release.

Thanks to johne53 for helping me identify the problem.

So... 
I'm going to drop this here, not knowing if I'm doing right or wrong, but I think it's okay to keep this in mind. 

I have been able to test v10 and it seems that there is the same problem.
I leave the log here.


Mixbus10.0.rc1.14 (built using 10.0-rc1-14-g75c73aa837 and GCC version 8.3-posix 20190406)
Crash Log: C:\Users\ESTUDIOS TPR\AppData\Local\Mixbus10\CrashLog\Mixbus-10.0.rc1.14-crash-1713081621.txt
Mixbus: [INFO]: MMCSS Initialized
Mixbus: [INFO]: Your system is configured to limit Mixbus to 2048 open files
ARDOUR_CONFIG_PATH not set in environment
Mixbus: [INFO]: Loading system configuration file C:\Program Files\Mixbus10\share\ardour10\system_config
Mixbus: [INFO]: Loading user configuration file C:\Users\ESTUDIOS TPR\AppData\Local\Mixbus10\config
Mixbus: [INFO]: CPU vendor: GenuineIntel
Mixbus: [INFO]: AVX capable processor
Mixbus: [INFO]: AVX with FMA capable processor
Mixbus: [INFO]: AVX512F capable processor
Mixbus: [INFO]: CPU brand: Intel® Core™ i7-7800X CPU @ 3.50GHz
Mixbus: [INFO]: Using AVX512F optimized routines
Mixbus: [INFO]: Loading plugin meta data file C:\Program Files\Mixbus10\share\ardour10\plugin_metadata\plugin_tags
Mixbus: [INFO]: Loading plugin meta data file C:\Users\ESTUDIOS TPR\AppData\Local\Mixbus10\plugin_metadata\plugin_tags
Mixbus: [INFO]: Loading plugin statistics file C:\Users\ESTUDIOS TPR\AppData\Local\Mixbus10\plugin_metadata\plugin_statsMixbus: [INFO]: add_lrdf_data 'C:\Users\ESTUDIOS TPR\AppData\Local\Mixbus10\rdf;C:\Program Files\Mixbus10\share\ardour10\rdf'
Mixbus: [INFO]: read rdf_file 'file:///C:/Program%20Files/Mixbus10/share/ardour10/rdf/ardour-presets.n3'
Mixbus: [INFO]: Loading 459 MIDI patches from C:\Program Files\Mixbus10\share\ardour10\patchfiles
Mixbus: [INFO]: Loading default ui configuration file C:\Program Files\Mixbus10\share\ardour10\default_ui_config
Mixbus: [INFO]: Loading user ui configuration file C:\Users\ESTUDIOS TPR\AppData\Local\Mixbus10\ui_config
Mixbus: [INFO]: Loading color file C:\Program Files\Mixbus10\share\ardour10\themes\dark-mixbus.colors
Mixbus: [INFO]: Loading ui configuration file C:\Program Files\Mixbus10\share\ardour10\clearlooks.rc
start clocking
Mixbus: [INFO]: Loading bindings from C:\Program Files\Mixbus10\share\ardour10\ardour.keys
Loading ui configuration file C:\Program Files\Mixbus10\share\ardour10\clearlooks.rc

[johne53]

@MikeTPR - while in the Command Prompt window, try closing Mixbus and then type set ARDOUR_FPU_FLAGS=95 (followed by a carriage return). Now launch Mixbus again from your Command Line.

Hopefully you won't see the AVX512F message this time and if you don't see it, you shouldn't hear the glitching either.

[MikeTPR]

@MikeTPR - while in the Command Prompt window, try closing Mixbus and then type set ARDOUR_FPU_FLAGS=95 (followed by a carriage return). Now launch Mixbus again from your Command Line.

Hopefully you won't see the AVX512F message this time and if you don't see it, you shouldn't hear the glitching either.

This made it! Thank you so much!

I suppose there won't be any problems resulting from launching Mixbus with this command....
I hope it can be fixed in future updates (Since the idea is to implement v10 as soon as possible in the studio), I am not a tech expert but I suppose it is not easy.

Thanks again.

[sirpas]

Not sure about this getting worked out, but I started having issue with ACE/XT/AVA plugins in version 9.  I bought v10 thinking the plugins that were crashing were related to the DAW. I love the XT Tom Gate plugin for example.  I can't touch that one now.  If I load it, it will crash the session.  ACE Delay crashes my computer as well.  It's nice to have these around when you're looking to use as little DSP as possible on the internal DAW side.  

I get what other described which is the border of the plugin with a black box.  Seconds after opening, I'm staring at my desktop.  Any possible solutions?

My rig is:
Windows 11 -- latest update
AMD 5900X 12-core
32gb 
AMD Radeon 6700X

All drivers are up to date which I know can be an issue, but that's usually with games where intense GPU work is happening.  

I read through the pages of this thread, but didn't see a solution.

Thanks for the help and guidance if any.

[johne53]

Would you mind checking your settings in Preferences->Plugins->GUI

   

Back in version 8, a new feature got added which allowed plugin GUI's to get destroyed while the plugin wasn't visible (to save memory). But it introduced a problem with some VST plugins which sounds very like the one you've reported. At the time it seemed it was only affecting certain VST2 plugins but maybe it's become extended somehow and is now affecting all plugins.

If you look at your settings, the default setting is to only hide the window so if that's the one showing for you, this must be some new problem.