Ditto. I've had issues with two libraries so far (I have not gone through all of my libraries, but have run into issues with these two): Impact Soundworks Shreddage 3 Fretless (but, interestingly, no issue with Impact Soundworks Shreddage 3 Archtop, my other Shreddage 3 library) and Embertone Walker 1955 Concert D (but not any other Embertone instrument I've tried.) Interestingly, if one reloads Kontakt 7 and rechooses the library, it continues to load from where it left off. Picking the third party company "brand," seems to help lower the number of load attempts required somewhat. (With Fretless, for example, it took me about 5-7 reloads to load the full sample set when "brand" sort was not enabled; enabling the "brand" sort tab lowers the required attempts to two or three.) Once a project is saved with the instrument, however, it loads fine when the project is reopened.Is anyone having trouble with Kontakt 7 and Bitwig 5.2 Beta? Some of my Kontakt libraries crash Bitwig when loading (no trouble with version 5.1).
The logs show: -
[2024-5-29 20:52:11.755 error] Unexpected result in location Vst3PluginInstance::getPluginSize: kNotInitialized
[2024-5-29 20:52:11.755 error] Could not get initial size of plugin before opening window
[2024-5-29 20:52:22.949 error] Could not read repsonses: End of stream: Broken pipe
[2024-5-29 20:52:22.949 error] Could not process audio on client audio thread 0 using remote audio thread 0: End of stream: Broken pipe
[2024-5-29 20:52:22.949 info] Killing pluginhost process
[2024-5-29 20:52:22.950 info] Waiting for plugin host process to exit
[2024-5-29 20:52:23.018 info] Plugin host process exited with code: -1073740791
They load ok in Komplete Kontrol.
No issues at all with BWS 5.1.9 and Kontakt 7.
At the suggestion of a techie, I did contact NI with the issue. As I had expected, NI is not interested in looking at the issue at least until BWS 5.2 is out of beta. I can't say as I blame them.
Statistics: Posted by dlandis — Fri May 31, 2024 10:34 pm