On Sun, 24 May 2020, Paul Gofman wrote: [...]
$ rpm -qf /usr/libexec/gstreamer-1.0/gst-plugin-scanner
gstreamer1-1.16.2-2.fc32.x86_64
This is the binary that maps element names like videoconvert to the name of the library to load, here /usr/lib64/gstreamer-1.0/libgstvideoconvert.so. Since it's a 64-bit binary (maybe a file would have been stronger proof), it cannot build the 32-bit registry.
$ rpm -qf /usr/bin/gst-inspect-1.0 gstreamer1-1.16.2-2.fc32.x86_64
$ gst-inspect-1.0 videoconvert | grep Filename Filename /usr/lib64/gstreamer-1.0/libgstvideoconvert.so
This is the library that provides the videoconvert plugin and since it's a 64-bit library that means 32-bit processes cannot use it, winegstreamer included... unless it has some cross-process communication mechanism so that all GStreamer code in fact runs in a 64-bit process (that seems highly unlikely).
It looks like Blaz Blue Calamity Trigger has a 64-bit version. Could it be that's the one you're actually running?
If not, does its behavior change if you rename winegstreamer.dll so it's not used?