KVR Audio

monolithx · Post by **monolithx** » Mon Sep 08, 2025 4:29 pm

In the end, I wll go back to Live. I was disapointed by Max integration but now that I have tested that VS Code Copilot is able to edit directly Max patches (!) and interface them with any language like python, I think it's the way to go for me.

It's incredible to see how efficient is the Max patch editing with Copilot! I was able to do things in one day that will have taken weeks to do during my spare time.

muzicxs · Post by **muzicxs** » Mon Sep 08, 2025 7:10 pm

What do you mean when you say that you interface Python with Max? Are you writing code in Python which will get executed by Max?

gulugulufish · Post by **gulugulufish** » Mon Sep 08, 2025 7:13 pm

Entire update consists of improvements to Bitwig's editors, piano roll tools, arranger, zoom behavior, automation, entire look and feel overhaul, clips

BW users: "I see no improvements"

_leras · Post by **_leras** » Mon Sep 08, 2025 8:07 pm

monolithx wrote: Mon Sep 08, 2025 9:10 am If I look at the release note, I see a lot of "new features", no improvements. That's exactly what it was said before "Their policy obviously prefers to gain new customers all the time, but at the price of disappointing and discouraging existing users non-stop".

Another example of the inconsistency between major updates that bring new features that will stay as is.

Bitwig has undergone large changes this past year or so:
Audio system update (multi interface)
UI improvements, now really coming through in v6
ARM support
CLAP support

It has also had a continuous stream of improvements to built in devices and the grid, with e.g. great new filters, a co convolution reverb, now having scale support in v6

And what do you even mean by new features, not improvements? Their release notes show fixes to many issues.

And underpinning everything is the smoothest workflow of any DAW for creating and mixing. To me, your comment doesn't really make much sense.

xbitz · Post by **xbitz** » Mon Sep 08, 2025 8:44 pm

All I asked from the Bitwig Jesus was not to have to think about where the add6, add9, add11 fall in different chords — and now I don’t have to. Amen.

I guess I’m a bit of an oddball — I use AI at work while coding so I can spend more time making music, not the other way around. I know that’s not exactly trendy these days.

monolithx · Post by **monolithx** » Mon Sep 08, 2025 10:55 pm

muzicxs wrote: Mon Sep 08, 2025 7:10 pm What do you mean when you say that you interface Python with Max? Are you writing code in Python which will get executed by Max?

Not really... I do the logic in Python and communicate with Max through OSC. But anyway, Copilot is really powerful at managing Max patches. It opens a whole new world! I'm just astonished how it's able to fix or customize very complex patches. I did the same with Bitiwg API, but Max is another beast...

stamp · Post by **stamp** » Tue Sep 09, 2025 12:30 am

xbitz wrote: Mon Sep 08, 2025 8:44 pm I guess I’m a bit of an oddball — I use AI at work while coding so I can spend more time making music, not the other way around. I know that’s not exactly trendy these days.

I usually don't justify the use of AI... but in your case it's for a good cause....

tapper mike · Post by **tapper mike** » Thu Sep 11, 2025 9:11 pm

I'm still not buying.

For years and years Abelton Live had tonnes of faults that they said they'd fix someday. I began to believe that the new wiz-bang features were there to cover up the mistakes pitfalls of using the daw. Then the sort of great rebellion happened and the fine programmers at AB left to form Bitwig with untold excuses as to why they didn't have something ready for market. When it finally arrived. It was crap but they said hold out it will get better. By the time I got a useable version I'd long given up because I'd rather have a useable traditional daw like Samplitude or Magix or Cakewalk or Mixcraft.

I find the workflow in Bitwig unbearable. And while I'll prolly never be using Cubase to it's full potential at least I can use it.

MacGyver · Post by **MacGyver** » Fri Sep 12, 2025 5:59 am

The new features are nice, yet most of it feels to me like standard functionality which should have been there already since v2. Then this immense update/renew pricing... Development is quite slow, too, and sadly they seem to only randomly listen to user feedback. Will wait some more years.

pdxindy · Post by **pdxindy** » Fri Sep 12, 2025 5:13 pm

_leras wrote: Mon Sep 08, 2025 8:07 pm Bitwig has undergone large changes this past year or so:
Audio system update (multi interface)
UI improvements, now really coming through in v6
ARM support
CLAP support

It has also had a continuous stream of improvements to built in devices and the grid, with e.g. great new filters, a co convolution reverb, now having scale support in v6

And what do you even mean by new features, not improvements? Their release notes show fixes to many issues.

And underpinning everything is the smoothest workflow of any DAW for creating and mixing. To me, your comment doesn't really make much sense.

It would be terrible if the comments of others affected the software.

Bitwig is my favorite DAW for workflow and ease of use. Getting from point A to point B there is minimal friction. I just get stuff done and it's fun!

xbitz · Post by **xbitz** » Fri Sep 12, 2025 7:39 pm

And special thanks go to Bitwig for keeping Ableton from getting completely lazy.

RunBeerRun · Post by **RunBeerRun** » Fri Sep 12, 2025 8:31 pm

I want it, but its not free. I don't want Ableton, they discontinued 32 bit as far as I've heard and there's no bit bridge.

Trancit · Post by **Trancit** » Sun Sep 14, 2025 9:45 am

RunBeerRun wrote: Fri Sep 12, 2025 8:31 pm I want it, but its not free. I don't want Ableton, they discontinued 32 bit as far as I've heard and there's no bit bridge.

I always ask myself what´s so rare and unreplaceable that there would be a need for supporting 32bit plugins still in 2025...
I think I haven´t touched a 32bit plugin since (don´t know) 2015??

jonljacobi · Post by **jonljacobi** » Sat Oct 04, 2025 4:49 pm

I see a lot of folks who seem to love Bitwig. I love the look (except for the different font-size menus -- I'm not sure why that bugs me), but I don't mesh with it very well. Most of the stuff I do (record, tweak audio onsets) is more awkward in Bitwig than in others. Could be five decades of other DAWs, but I just grind the gears when trying to work in Bitwig.

That said, I'm happy it's around as the company innovates (modularity, DAWproject, CLAP) and keeps others on their toes.

jonljacobi · Post by **jonljacobi** » Sat Oct 04, 2025 4:59 pm

Another thought. On the 32-bit thing. People these days seem to be overly addicted to updates and upgrades. FOMO and constant advertising no doubt. There are still perfectly viable older versions of software and hardware than can be used.

I was trying to sell my older M1 Max Studio, which is still hella' fast and upgradable OS-wise for quite a while. Only three years old and much less than half the price of a new Studio and all I got were nibbles. I said screw that and have it in another room as backup/second recording rig.

I also tried to donate a 27-inch 2015 iMac to a local cat rescue group and they refused it saying they were afraid it would become obsolete. All they do is browse the Web. Sheesh. Finally found a buyer for $300 after I told them they could always convert it to a display later using Aliexpress parts. I probably should've done that. 5K display for $450?

My Macbook Pro from 2013 still does a more than adequate job as well. That's all hardware, but I've still got older versions of many DAWs which work perfectly fine.

In the end, it's about what comes out the speakers, not necessarily how it got there.

Does Bitwig seem like a daw that very few people want? Kind of a rant I guess.