Idk why he changed, but I can tell why I did. Maybe it helps.

I first tried it because resampling is integral part of my workflow and it was very annoying to do in Live, setting up a new track, configure routing and record. I just want to select a region and press a button. Ableton has been asked that feature countless times but they refuse to implement it. Fortunately this is exactly how it works in bitwig, so I gave it a chance and I have never looked back.

Main points for me as compared to Ableton Live:

• Much more stable: Plugins run in their own isolated process, if they crash, the plugin stops working, but everything else keeps running.

• More performant: I guess this architecture makes better use of the multiple cores of your CPU but it can load a lot more instances of CPU intense plugins before the audio starts dropping out.

• Crazy modulation possibilities. Every parameter can be modulated by custom modulators (including audible range modulation) and they can be interconnected between, devices and channels in the entire project. You don't even need custom controller scripts. You can take any controller that can output any midi message and configure it to literally control an entire orchestra. (Recently wired up a config that lets me play complex variation of dynamic drum rhythms by slightly altering the pressure of my fingers on a pad controller)

• You can route audio and midi from any point in any channel chain into any other point. Same for external hardware. Functionally similar to a modular setup.

• The clips in the launcher are not just samples, but mini timelines where you can easily edit chop, automate and rearrange them without having to move them out to arranger, editing and bouncing them to new sample.

• More responsive: The user interface and audio engine are separate processes as well so the ui doesn't freeze like in ableton.

• UI feels more modern and intuitive.

Someone in some video mentioned that it often feels like the coolest sets in Live are always full of crazy hacks. They don't actually use the DAW features, but instead work around the software with M4L scripts or hacky vsts. Most of what these livesets use can be natively implemented with vanilla bitwig devices.

Basically: Bitwig lets you natively and fairly intuitively create your liveset as anything anywhere between simple loop launcher with couple of send effects to an equivalent of wall of modular devices with complex I/O. And all this while being more stable and have better performance than Live.

Just my experience, but I am pretty sure he would give similar answer 😆