#165

How does it differ from the wavetable mode in the Sampler? I haven’t used Live beyond vague tinkering with the LE version that came with some controller I bought.

1 Like
#166

Wavetable in Bitwig’s sampler doesn’t oversample afaik, so it gets aliasing artifacts. But the sampler module oversamples 4x in grid. I‘d be curious to hear what feature people would like from a dedicated wavetable device beyond workflow improvement over poly grid.

As far as my own feature wishlist, midi grid is probably still on top…

3 Likes
#167

well - I renewed my yearly license for the third year running (despite not meaning to). The reason I did this year was a) decent summer sale offer and b) am vaguely wondering about setting up a non Mac based music machine (jury still out on that one).

I’ve been using it a bit so I feel better about the license (& also been using my Seaboard a bit more too which precludes Ableton)

There is a lot of love about Bitwig. It feels like you need to properly embrace their way of doing things - and it’s a real “studio is the instrument” kind of tool. Feeling like I should immerse myself in it a bit and see where I get to

4 Likes
#168

Alas, my clocking misadventures with Bitwig continue. While the clocking strategy I’ve adopted here works—initially—after a period of time, something like 15 minutes, it totally freaks out, races, and fluctuates wildly. The only way I’ve found to reset it is to restart Bitwig, and then it will work for another short period of time. This one is going to be tedious to document, but I guess I’ll try.

1 Like
#169

I was traveling and left my DIN sync cable at home that I usually use with PNW. I didn’t have cv interface, but I did have midi-to-cv through Entropy Engine.

Perhaps there was an easier method (I couldn’t find a midi metronome like Logic has), but I built a clock using the grid (LFO with Transport and NAND out to Replacer and Note Receiver) to send midi at whatever division Pam’s best followed through Engine channel with midi-to-cv. The clock held up for the few hours I used it.

So grid to midi to cv at least seems to be stable.

1 Like
#170

Does one have to pay every year? Is that to get new upgrades? Will old versions still work if you stop paying?

#171

The license gets you the upgrades. I believe it keeps running at whatever version.

1 Like
#172

I really like Bitwig. I’ve been running it on a 2018 15" MacBook Pro for a few years and decided I like it enough to continue use on a dedicated PC build. We’ll see how that goes soon enough. Will be nice to push it and not have to worry about burning the table my MacBook sits on.

There are some nice options for 10th gen Intel motherboards with integrated Thunderbolt 3 support.

…And RGB to match that new EQ+ look…

2 Likes
#173

I’m looking at Bitwig more and thinking it might be worth investing a few days in a trial to see if it works for me. Just to clarify though, can the modulators be used on any VST, or just bitwig devices? Anyone had any compatibility issues there? Also I don’t have anything like an expert sleepers but have been thinking about it for a long time and if I switched over to bitwig would probably pick one up since it seems they really have integration in mind. So can those modulators then also be used then for generating CV signals to go out?

#174

I haven’t done a lot of internal modulation, but I have used the modulators from BitWig to be sent out of the Expert Sleepers. It’s very good at that. Honestly, I have done the same with those modulators out of my Poly2 (to sometimes free up ES-8 ports for bringing audio signals in to my rack). Either way, I find BitWig to be very good at creating signals like that.

2 Likes
#175

Yes to both. There could be some VSTs that don’t allow host modulation but I’ve yet to run into any. I’ve tried it with Aalto, Kaivo, Omnisphere, Goodhertz, Soundtoys, and more.

Similar to @kasselvania I’ve used it with ES-8 and I had a Poly (one) which worked as well. I would try it out and test it with your most used VSTs and hardware to make sure but I’ve yet to run into any major issues.

3 Likes
#176

Modulators and controllers can be assigned to any VST parameter that the plugin exposes for automation. (I’ve seen a few plugins in the past that put things on the GUI but not in the host, or which have really arcane naming schemes for their parameters… though Bitwig tries to highlight the last edited parameter in the GUI and bring it to the top of the list.

Here’s an example of doing that to Aalto:

image
image792×296 55.3 KB

To send out CV from Bitwig I usually route it in the Grid:

image

8 Likes
#177

Yeah I’ve had the same trouble from time to time that @Starthief describes but I definitely feel like Bitwig does its best to make it easy. If the plugin developer(s) has made things painful, then there’s not much more that can be asked of the host developer(s) imo.

#178

Yesterday was a strange day. Amongst other oddities, I installed the lated Bitwig point release, and on a whim, re-attempted clocking PNW with a HW Clock signal via my ES-3 and an attenuator. I did this because I’ve been having annoying problems with the Grid-based workaround (above). Well, for the first time, PNW didn’t complain about the HW Clock being unstable! It just worked. I found nothing in the release notes to suggest any clocking improvements other than an Ableton link reference.

More testing required.

1 Like
#179

Is anyone else feeling frustrated by the issue with muting external hardware tracks? (E.g. if you solo a track, any other tracks which send midi to external hardware are not muted.) As I understand it this is not an issue if you route the audio from the external hardware back into the track sending midi. For me this isn’t a practical solution as I have multiple external devices and only one set of inputs on my audio interface. Seems like a strange oversight on the part of the developers to implement it this way.

I am also having some syncing / latency compensation issues with external equipment. So far I have just worked round them and it hasn’t been a big deal - they are consistent in their inconsistency, and therefore fixable. I will put some time aside to work out what’s going on.

That and some other minor quirks aside, I am really impressed with Bitwig overall and it has quickly become my main DAW. I also increasingly like the fact that with the Grid, Bitwig is effectively a hybrid DAW / sound design tool and I look forward to exploring that side of it further. The Grid certainly seems like a more inspiring patching environment than something like Reaktor.

1 Like
#180

@slowsounds In addition to that, you can also create a remote control presets page which can also be used to discover which parameters can be modulated from the GUI; simply click on an empty slot (with the blue icon) and toggle controls in the VST’s own GUI. They will still correspond with those parameters already listed, obviously, but this would allow one to keep relevant parameters handy as well as organized and, more importantly, be able to rename them to something more memorable or coherent.

bw051711-Bub6HxcTVvbKVxgX.0v7gcXBy4YBKv8o

Also, additionally, routing all of one’s CV can be handled with a singular Grid device by using sidechains as inputs.

7 Likes
#181

God I feel a bit embarrassed that I didn’t realise how easily you can work with feedback inside Bitwig until the latest newsletter.

I’m used to a visual patching paradigm, so the use of the Delay and Reverb feedback fx and tank fx was something I had overlooked. Already having a lot of fun injecting surprises into the feedback chain this way.

#182

you can work with feedback only when its allowed. For example, in order to send an fx chain onto itself I have to use loopback on my audio interface, because bitwig blocks feedback sends. Which is okay)

1 Like
#183

Yeah for sure, but most of the time I do want to include a delay in that loop, so it’s fine by me.

#184

You can cheat at feedback in Bitwig…

Add a DC Offset device, and attach an Audio Rate modulator to it, linked to its fader. Assign the output of a later device in the chain to the modulator.

There is probably some inherent delay but I haven’t tested it – probably less than the round trip latency of a hardware loopback.

4 Likes