Bitwig

Cyoon · Post by **Cyoon** » Sun Apr 19, 2020 10:51 am

shouldn't this indicator show some I/O stream?

antic604 · Post by **antic604** » Sun Apr 19, 2020 11:02 am

irre wrote: Sun Apr 19, 2020 10:51 am shouldn't this indicator show some I/O stream?

Is there any I/O stream at your project right now? I.e. reading or writing to disc?

Cyoon · Post by **Cyoon** » Sun Apr 19, 2020 2:10 pm

no, not in that moment. Will check with samples etc.

antic604 · Post by **antic604** » Sun Apr 19, 2020 2:15 pm

irre wrote: Sun Apr 19, 2020 2:10 pm no, not in that moment. Will check with samples etc.

Yes, it only shows something when Bitwig is reading or writing to disc. So if you have a sample playing for 30s, it might just blink for 0.5s when it loads it into memory. I guess it's just to see if your computer can keep up with project's demands.

Hez · Post by **Hez** » Fri Apr 24, 2020 9:54 am

w00t_b00ts wrote: Sat Apr 18, 2020 6:52 pm Hello,

I'm still having issues with LFO Tool failing to load (could not load plugin).
To recreate the issue:
1. Open a new Bitwig 3.1 session
2. Drag LFO Tool (vst2 64bit) to track
3. Save & exit
4. Open project in Bitwig 3.2 Beta (1 or 2)

Thanks

I'm having the same problem with LFOTool (VST2), and Speakerphone (also VST2), same error message for both:

"Plugin host died: Could not read async reply: End of stream: Broken pipe"

Have submitted a ticket.

SLiC · Post by **SLiC** » Fri Apr 24, 2020 12:02 pm

I wonder how much longer VST2 has (official development support from Steinberg ended a couple of years ago). I am not saying it should end, I just wonder who will be the first DAW to say 'VST3 only' like the first 64 bit only DAW! I have had my Bitwig browser set to only show VST3 for some time and I haven't missed anything yet, but there are obviusly a few people still needing plugs that haven't been updated to VST3.

Hanz Meyzer · Post by **Hanz Meyzer** » Fri Apr 24, 2020 12:06 pm

There are a ton of good plugins which are only available as VST2. And since VST2 already is implemented, it would not make a lot of sense to remove it. e.g. see Native Instruments, they still are not supporting VST3.

SLiC · Post by **SLiC** » Fri Apr 24, 2020 12:18 pm

I absolutely agree, but I still wonder if its coming...it used to be that plugin issues with Bitwig were with VST3 plug ins, now it seems to be with the VST2 plug ins! The Beta 2 fix was related to a VST2 issue (disable variable buffer size processing for vst2) so it looks like the focus was on VST3!

coolblinger · Post by **coolblinger** » Fri Apr 24, 2020 1:59 pm

The problem with the VST2 format right now is that you just can't legally make new VST2 plugins anymore if you haven't requested a license from Steinberg before the end of 2018. This forces new plugin developers to target the VST3 format (since there's no commercial support for any open plugin formats such as LV2) which is incredibly complex compared to the VST2 format, is still lacking features compared to VST2.4 and is limited C++ only. So if a new company decided to make a DAW, they won't be able to support VST2 plugins at all.

SLiC · Post by **SLiC** » Fri Apr 24, 2020 2:10 pm

Its a bit like when Bitwig first came out and one of its 'features 'was that it could run 32 bit and 64 bit plugs witout a bridge....not something you ever realy hear about now...

antic604 · Post by **antic604** » Fri Apr 24, 2020 2:21 pm

SLiC wrote: Fri Apr 24, 2020 12:02 pmI have had my Bitwig browser set to only show VST3 for some time and I haven't missed anything yet...

Because this particular setting shows VST3 if you have both installed, but will show VST2 still if that's the only version there is

Hez · Post by **Hez** » Fri Apr 24, 2020 2:35 pm

For anyone wondering, the VST2 issue will apparently be fixed in the next beta release.

Bitwig

KVR Audio

3.2 (Beta 2) is OUT!!!