[Scan Units]
Info: ===Scan Units ====================================
Info: This component has 4 unit(s).
ERROR: Unit 000: Invalid ID!
[XXXXXXX Failed]
Wrong Thread with pluginval
Running traction pluginval at default sensitivity (../../third_party/pluginval.app/Contents/MacOS/pluginval cmake-build-debug/Conduit.vst3) gives us, once the automation starts
Starting tests in: pluginval / Automatable Parameters...
Host called the method clap_plugin_params.value_to_text() on wrong thread! It must be called on main thread!
PLUGIN: HOST MISBEHAVING: Host called the method clap_plugin_params.value_to_text() on wrong thread! It must be called on main thread!
libc++abi: terminating
That comes from the fact that conduit is a strict terminate clap helper. But we should fix it somehow, since the traction validation is useful
Using this as an issue for various validator problems.
Two validators in question
This report is building conduit at 44dec6fa15108 which has clap-wrapper at dd5e512bc
steinberg validator: Unit Info problems
Conduit params have modules (groups). So the conduit validation shows for the poly synth (correctly)
but then shortly thereafter
Wrong Thread with pluginval
Running traction pluginval at default sensitivity (
../../third_party/pluginval.app/Contents/MacOS/pluginval cmake-build-debug/Conduit.vst3
) gives us, once the automation startsThat comes from the fact that conduit is a strict terminate clap helper. But we should fix it somehow, since the traction validation is useful