11593 posts since 21 Mar, 2008, from Hannover, Germany
Before i forget:
There is a bug related to PPG Wave 3.V in Bitwig Studio that i already reported back in March 2014:viewtopic.php?f=259&t=407354
This also happens for the old 32-bit plugin and also in the latest Bitwig version v1.0.10.
It was a huge problem to get any reply concerning this or to get any user confirm this bug. I guess i even asked in a thread in the instruments forum (amybe this one?)
The problem was reported to Waldorf and i did that again recently. It ssems to be difficult to get the responsible persons at Bitwig involved with this. I had sent an E-Mail t their support address but never got a reply. The only reply was fro mone of the Bitwig bet testers and that one was not really helpful.
A similar problem did not seem to happen in other hosts where i have tested PPG Wave 3.V.
This doesn't happen with patches that use internal wavetables, just with patches that use samples like many in my own commercial bank and several of my factory presets (sub-folder in the factory banks folder: "IW - Ingo Weidner"). For those who missed it samples are called "transients" in the PPG Wave 3.V.
What happens is that patches using samples will stay quet in Bitwig or when used in Bitwig for the very first time they will play for a new notes and then will stay quiet forever.
Personally i am not really a big a fan of Bitwig Studio yet and only kept the demo version installed to check the bug i mentioned.
HW: Blofeld, Pulse 2, UltraNova, Bass Station 2
SW: PPG 3.V, Largo, Nave, Icarus, Avenger, Serum, Legend, Saurus 2, Diva, Repro-5, VC 6, Komplete 10, many more
i5-3350P / Win 10 x64 / Live 9 / Cubase Pro 9.5 / Bitwig 2 / Studio One 3