Uploaded March 2026 | Updated September 2026, 3 hours ago
Now that Bitwig 6 is finally out(soon), it feels like the right time to move away from Suno — without losing the fast arrangement prototyping workflow that made it useful in the first place.
As it turns out, there’s already a .dawproject generator project, and Claude(for sure) can easily port and use it directly. This basically means AI music generation itself becomes replaceable by an AI-assisted production workflow instead.
The open .dawproject format is a major advantage too, since it’s well documented and DAW-agnostic.
Since Bitwig 6 can now merge already created clips on a per-track basis(in one step as is on the video), the project can then be quickly expanded from the Clip Launcher in an FL Studio–like workflow, which is another huge + point
I’ve also posted the idea on Reddit: reddit.com/r/Bitwig/comments/1rhbixi/building_starting_templates_using_an_llmclaude can find the details there
Now that Bitwig 6 is finally out(soon), it feels like the right time to move away from Suno — without losing the fast arrangement prototyping workflow that made it useful in the first place.
As it turns out, there’s already a .dawproject generator project, and Claude(for sure) can easily port and use it directly. This basically means AI music generation itself becomes replaceable by an AI-assisted production workflow instead.
The open .dawproject format is a major advantage too, since it’s well documented and DAW-agnostic.
Since Bitwig 6 can now merge already created clips on a per-track basis(in one step as is on the video), the project can then be quickly expanded from the Clip Launcher in an FL Studio–like workflow, which is another huge + point
I’ve also posted the idea on Reddit: reddit.com/r/Bitwig/comments/1rhbixi/building_starting_templates_using_an_llmclaude can find the details there
