11:10 no need to convert to Poly grid. Click on the arrow that is under instrument's name and you will have access to modulators, where you can load any number of modulators, including different kinds of envelopes, LFOs, custom drawable curves (aka MSEGs) and so on. There is even the Wavetable LFO modulator. Yes, a wavetable itself can be a modulation source. The modulation system is the strongest part of Bitwig. It works the same way for all its builtin instruments and CLAP plugins.
Awesome feedback, CuriousPassenger. Like I said, I'm not much of a deep Bitwig user! I was aware of the wavetable LFO modulator, but haven't played with it yet. Obviously, I have *a lot* of wavetables that could be used as modulation sources in Bitwig. 😀
Hi Keith! Very late to the party here, (I believe) I was the one who first asked you on the Vital forums if it would be possible to convert the wavetables so that SurgeXT could read them. Thank you SO much for this! I was messing with a python script that kept the tables as .wav but converted the bit depth etc, it was a total mess. This is much more simple and elegant. Always appreciated! I can't wait to dive into all of the new goodies you have shared! Keep on rockin'.
Hey @auedpo, thanks for watching and for having made that suggestion! This is linked in the description, but if you want a simpler script than the tools the Surge XT team supplies, you can find a link to a version of my Python script that converts Serum-style wavetables to the .wt format at the end of this post: www.wavetables.lol/p/how-to-import-wavetables-to-bitwig-for-use-in-bitwig-s-polymer-synth (Obviously, you don't need to run this on KRC Mathwaves wavetables, as I provide them as .wt versions now.) One thing I have learned recently is that it seems like the real issue with Surge XT and the KRC Mathwaves wavetables is that, unlike modwave and Serum (which will handle wavetables where the wave data is either 32-bit PCM/integer or 32-bit floating point), Surge seems to expect *only* 32-bit floating point. All of the Mathwaves wavetables in .wav format are 32-bit PCM (integer), not float. I did this for compatibility reasons with older audio software and software synths that might not understand floating point. (That is, it looks to me like Surge does properly understand a 2048 sample-per-frame .wav format wavetable if it's saved as 32-bit floating-point, at least in some cases.) However, this is not true with Bitwig and -- if you try to import a 2048 sample-per-frame .wav wavetable, regardless of whether its int or floating-point -- Bitwig doesn't understand the frame size properly. It assumes 256 samples-per-frame and so will misread the wavetable. While the wavetable will make a sound, it is not the *correct* sound. Even though this is easily observable, there are certain folks out there on the interweb who insist that this isn't the case. They are sorely mistaken... anyway... in Bitwig, one does need wavetables that are in .wt format which explicitly specifies both the frame length (number of samples per frame) and the number of frames. This ensures that the wavetable is understood correctly.
Hey @potsandjacks, thanks for watching! Yep, I was being a bit derpy there. I appreciate helpful comments like this from you and others who pointed this out. (In my videos about Sumu - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-U4zVIqyCQKM.html - and CrunchCoat - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-s-V-VqBujAs.html - I put simple Bitwig modulations like this to work on plugin parameters that are otherwise not natively modulatable. This is such a great Bitwig feature.)
The fact that Bitwig is using the same file format for wavetables as SurgeXT is not surprising if you know that the developer of the original Surge Synth is now at Bitwig.
My child knew right away not to right-click the icon. It took me reading the whole "How to Import Wavetables..." article, sitting through the "talkie talkie talkie" portion to discover that right-clicking NOT on the icon but OUTSIDE of the icon is in fact where the pop up dialogue is generated. But my kid knew right away. I brought her in to show her what it is like to track down information on the web that is not in manuals and that is scattered across various other sites such as YT or .LOL sites. LOL indeed! Thanks for this tutorial. (She explained her reasoning, why she would never have clicked on the icon in the first place. Isn't there a Rolling Stones song about this?)
