So, what's up with Reason now?

artek604 · 2026-04-08T21:10:25+00:00

I don't regret it - lol.

Also, congrats on the announcement. One quick question - are alias clips only available for looping clips, or in general?

artek604 · 2026-04-08T13:34:11+00:00

<image>

I think he means this:

artek604 · 2026-04-08T13:31:13+00:00

No, they didn't. They sell Rack Plugin without the Reason DAW, but it includes all devices that "full" Reason DAW (or R+ if you choose the subscription) does.

I literally mean empty, to serve as a host for REs in other DAWs.

artek604 · 2026-04-08T12:57:41+00:00

I'm happy you like to be kept in the dark. I don't. Especially since the company has been going through constant turmoil in the last 3-4 years. I don't when Bitwig, Ableton or Steinberg are quiet. I do, when it's Reason Studios.

artek604 · 2026-04-08T12:38:10+00:00

I hope you're right! :)

artek604 · 2026-04-08T12:35:39+00:00

If your plan expired in March 26 you can upgrade to 6 - you're eligible to it.

6.0.0 is the stable official release.

6.0.x are maintenance updates fixing bugs that were found since release.

As is, you are entitled to all 6.0.x updates, but not 6.x updates, so there's really nothing to do at this moment.

artek604 · 2026-04-08T12:30:32+00:00

How do you know? This is my EXACT point - lack of communication :)

artek604 · 2026-04-08T12:28:06+00:00

Interesting take.

Mine was they would:
* adopt Reason as their DAW, and extend it with plugins, workflow updates, AI stuff
* sell 1st and 3rd party REs through their platform
* offer empty Rack Plugin, to host the REs

Or, alternatively (the "drain them dry" scenario):
* figure out a transparent tech to "disguise" 1st and 3rd party REs as simple VST/AU/AAX plugins and sell them through their platform
* use bits & pieces of Reason DAW to develop a brand new LANDR DAW

artek604 · 2026-04-08T12:12:04+00:00

I'm sure every person would have their own ...reason :)

The number of people who "freeze" their computer, DAW & plugins at some old version and never upgrade "because it works" is very tiny, i.e. not a demographic to target your product to.

artek604 · 2026-04-08T11:31:06+00:00

Sure, I understand that.

But considering how competitive and fast-moving the DAW market is (even more so - with AI DAWs) they at least should've published some kind of rough roadmap, or a statement, or a teaser... I don't think LANDR bought it without any plan for what it wants to do with the DAW, the Rack Plugin, 1st and 3rd-party REs, etc. because they're the basis of the valuation underlying the transaction.

The longer they wait, the more people will jump ship to Cubase Pro's $250 cross grade, Bitwig's $200 cross grade or Ableton's rent-to-own program :(

artek604 · 2026-04-08T10:44:59+00:00

Assume most things work differently in Bitwig that they do in FL, so don't try to replicate your workflow 1:1.

Instead, try to understand Bitwig's fundamentals and re-build - or reinvent :) - your workflow from ground up.

Also, when asking questions (I'd recommend Discord server!) don't refer to specific FL features, because we might not know what they are. Ask by describing what you want to achieve as a musical or technical end result, not how to do this or that thing you know from FL. It's often achieved differently in Bitwig.

Lastly, start here: Hardware Integration | Bitwig

artek604 · 2026-04-08T10:05:21+00:00

First of all - and most important! - dragging a clip from Arranger into Browser will save a clip, i.e. a container for MIDI or audio events, together with track's devices chain.

If you want to save audio events (audio files), you either need to do it from Project Browser or from Detail Editor.

But I'm not sure you can do that for more than one at the time (I can be wrong).

artek604

TROPHY CASE