MUTOOLS

docbot · Post by **docbot** » Tue Dec 03, 2019 11:41 am

Not sure if this is a Bitwig issue, but it just won't see the MUX VST if I move the whole folder into my VST folder.

Shows up in Renoise though.

mutools · Post by **mutools** » Tue Dec 03, 2019 11:56 am

When i was working on MUX 8 i also tested it in Bitwig, and it works fine. However i noticed that Bitwig sometimes removes MUX from its plugin list. I intensively researched that but could not find anything wrong in MUX and could only conclude that it's a Bitwig quirk. You can bypass the issue by disabling auto scan in Bitwig (uncheck "Should Update Automatically") and manually rescan the VST folder. ("Update Index" or "Reindex")

Hanz Meyzer · Post by **Hanz Meyzer** » Tue Dec 03, 2019 12:03 pm

Bitwig logs issues into ~/Library/Logs/Bitwig or so. There is an engine and I think also a scanner log.

mutools · Post by **mutools** » Tue Dec 03, 2019 12:41 pm

I tried to find such BW scan log on Windows, but couldn't find it. Does anyone know where to find the BW vst scan log on windows? I wonder whether BW's scan log would reveal any reason why BW first recognizes MUX and then removes it again.

Hanz Meyzer · Post by **Hanz Meyzer** » Tue Dec 03, 2019 12:49 pm

Oh wait, it actually is here on macos:
~/Library/Logs/Bitwig/BitwigStudio.log
~/Library/Logs/Bitwig/engine.log

You can also look at these logs using the system's console.app. I guess there might be a similar directory for general logging under windows?

mutools · Post by **mutools** » Tue Dec 03, 2019 8:43 pm

I had a look at those bw logs but don't see anything that could clarify the issue. But thing is that it only happens sometimes that bw doesn't list mux (anymore), it's very unpredictable. I did notice that when you uncheck "Should update automatically" (right-click in bw on the Mux Vst folder) then the issue doesn't happen, so it seems something with bw indexing system. Again, i researched it seriously and did not find any issue in Mux and could only conclude it's an issue in bw. If the issue persists i'd recommend posting it on a bw support forum. I'm interested to know the reason.

docbot · Post by **docbot** » Wed Dec 04, 2019 3:23 pm

here is the error Bitwig shows

"com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process
stdout:
PluginHost: Reading VST 2.4 plugin metadata for /Library/Audio/Plug-Ins/VST/MUX Modular/MUX Modular Synth.vst

stderr:

2019-12-02 23:14:02.213 BitwigPluginHost[42459:3458908] AppFilePath=/Volumes/Macintosh HD/Library/Audio/Plug-Ins/VST/MUX Modular/MUX Modular Synth.vst
2019-12-02 23:14:02.213 BitwigPluginHost[42459:3458908] AppFilePath exists
2019-12-02 23:14:02.215 BitwigPluginHost[42459:3458908] Gonna get desktop path
2019-12-02 23:14:02.215 BitwigPluginHost[42459:3458908] Gonna init prefs & settings
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] Gonna define graph folder
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] Gonna read settings
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] MacOs-BufferedWindows=1
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] MacOs-SeparateClipToRectCallsDuringBlitting=1
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] MacOs-AppPollMethod=TmOb
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] Gonna init sub-systems
2019-12-02 23:14:02.295 BitwigPluginHost[42459:3458908] Log file path = /Volumes/Macintosh HD/Library/Audio/Plug-Ins/VST/MUX Modular/User/LogFiles/Log-20191202-231402.txt"

mutools · Post by **mutools** » Wed Dec 04, 2019 6:44 pm

docbot wrote: ↑Wed Dec 04, 2019 3:23 pm here is the error Bitwig shows
"com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process
stdout:
PluginHost: Reading VST 2.4 plugin metadata for /Library/Audio/Plug-Ins/VST/MUX Modular/MUX Modular Synth.vst

That's BW data, i don't know what it means, please ask Bitwig what this means and why this error occurs. I'm curious for their answer.

2019-12-02 23:14:02.213 BitwigPluginHost[42459:3458908] AppFilePath=/Volumes/Macintosh HD/Library/Audio/Plug-Ins/VST/MUX Modular/MUX Modular Synth.vst
2019-12-02 23:14:02.213 BitwigPluginHost[42459:3458908] AppFilePath exists
2019-12-02 23:14:02.215 BitwigPluginHost[42459:3458908] Gonna get desktop path
2019-12-02 23:14:02.215 BitwigPluginHost[42459:3458908] Gonna init prefs & settings
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] Gonna define graph folder
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] Gonna read settings
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] MacOs-BufferedWindows=1
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] MacOs-SeparateClipToRectCallsDuringBlitting=1
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] MacOs-AppPollMethod=TmOb
2019-12-02 23:14:02.217 BitwigPluginHost[42459:3458908] Gonna init sub-systems
2019-12-02 23:14:02.295 BitwigPluginHost[42459:3458908] Log file path = /Volumes/Macintosh HD/Library/Audio/Plug-Ins/VST/MUX Modular/User/LogFiles/Log-20191202-231402.txt"

This is standard MUX log data, and it all looks normal, no errors in this. You don't have to include this data in your report to BW as this is MUX data.Only include the first part (that talks about a metadata read error) in your report to BW.

Pls keep me posted of their answer.

docbot · Post by **docbot** » Sun Dec 15, 2019 10:05 pm

still visible in the new beta, so might have been fixed

mutools · Post by **mutools** » Sun Dec 15, 2019 10:27 pm

In the new bitwig beta you mean?
Does the latest bitwig beta change-log confirm the fix?

charlesnavi · Post by **charlesnavi** » Sat Apr 18, 2020 3:26 pm

I'm running the latest versions of Bitwig (v3.1.3 and v3.2 beta 2), neither list MUX in its plugin list. I get this error in both versions:

Code: Select all

C:\Program Files\Common Files\VST2\MUX\MUX (Vst Synth).dll

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process
exit code:-1073741819
stdout:
PluginHost: Reading VST 2.4 plugin metadata for C:\Program Files\Common Files\VST2\MUX\MUX (Vst Synth).dll


-------------------------------------------------------------------

C:\Program Files\Common Files\VST2\MUX\MUX.dll

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process
exit code:-1073741819
stdout:
PluginHost: Reading VST 2.4 plugin metadata for C:\Program Files\Common Files\VST2\MUX\MUX.dll


-------------------------------------------------------------------

I'm on Windows 10. And I haven't had any problems with other VSTs on Bitwig.

mutools · Post by **mutools** » Sat Apr 18, 2020 5:48 pm

When a DAW calls the init function of MUX, MUX starts logging info to a text file. It's stored in your MUX/User/LogFiles folder. The name (Log-yyyymmdd-hhmmss.txt) and timestamp will correspond to the moment you plug in the first MUX instance. Please email me the MUX log file that matches plugin in MUX in BS.

charlesnavi · Post by **charlesnavi** » Sun Apr 19, 2020 4:26 pm

Hello Jo, sorry for the delay. The MUX/User/LogFiles folder is empty. I've tried to rescan the plugins many times, and the log file is still not getting created.

pljones · Post by **pljones** » Sun Apr 19, 2020 4:41 pm

Sounds like the DLL file is corrupt. Have you tried reinstalling?

mutools · Post by **mutools** » Sun Apr 19, 2020 5:03 pm

A corrupt file is possible but rather exceptional nowadays. To me it rather sounds like Bitwig decides to not scan the MUX.dll (hence no log file) for some reason, which is odd cause MUX is recognized by all major hosts. In the Bitwig log i see "CouldNotReadMetadataException" which seems to be an Eclipse issue and thus something on Bitwig's side. So best to ask the Bitwig support team. I'm curious for their answer, pls keep me posted.

MUTOOLS

KVR Audio

Bitwig doesn't see MUX