Why you left Reason?

[Hink]

the appropriate action was taken

[jens]

[*]devices get their own lanes whenever automated and that can't be hidden only minimised),

A bug, I think - minimize the track, switch from Block to Song or from Song to Block and back (depending on where you added the Automation) and
the minimized track will have its normal (minimized) height as without automation and after that you can expand and re-minimize it all you like.

[antic604]

[*]devices get their own lanes whenever automated and that can't be hidden only minimised),

A bug, I think - minimize the track, switch from Block to Song or from Song to Block and back (depending on where you added the Automation) and
the minimized track will have its normal (minimized) height as without automation and after that you can expand and re-minimize it all you like.

I probably worded it poorly. What I meant is that in other DAWs (all of them, I think) if I have a synth and say a delay following it, if I automate the delay the automation lane 'belongs' to the track the instrument is on. And I can hide that lane completely, so that only the instrument track is visible.

By contrast in Reason not only the delay gets its own separate sequencer track (which is in no way connected to the instrument its attached to), but also automation lane cannot be hidden completely, but only folded to a thin line.

I mean it fits very well into the virtual hardware rack paradigm and is fun for small projects, but can get really confusing quickly. That's why lack of folders is my main complaint with Reason - it would make session organisation so much easier.

[antic604]

of course I dont want to or I would just do it, but the op started the attack (which could be interpreted several ways but said post was reported)...I see no reason to keep it open if he's going to act that way when people express their opinion

Yeah, sorry. That was uncalled for. But I'm tired of the ignorant "Reason sound" posts. Won't happen again

[Hink]

TY

[vurt]

bye.

[Hink]

jens please do not respond to him, he is upset by the board warning he received and he wants a ban...he wont get it but I will delete any post from this point on in this thread he makes even if it's 100% on topic

[jens]

I won't respond to that.

But let me use this opportunity to thank you for your mostly great & fair and balanced moderation and in case I inadvertendly somehow came across as being somehow critical towards your handling of this situation here then I am really sorry for it. Peace everyone!

[EnochLight]

I'm still on R11 (Suite) and don't plan to leave - I just haven't found another DAW that is as inspiring as Reason is (for me). I also own Studio One 4.5, and I've tried Ableton's Live as well as Bitwig.

That said, I have found myself using Reason less and less these days, simply because I bought an Akai MPC Live and some other hardware (see the sig) and find that working away from a computer has started to inspire me in many different ways. It's just nice not sitting in front of a computer screen to create. Having the Internet just a minimized window away is too distracting.

[Hink]

thanx jens

[jens]

[*]devices get their own lanes whenever automated and that can't be hidden only minimised),

A bug, I think - minimize the track, switch from Block to Song or from Song to Block and back (depending on where you added the Automation) and
the minimized track will have its normal (minimized) height as without automation and after that you can expand and re-minimize it all you like.

I probably worded it poorly. What I meant is that in other DAWs (all of them, I think) if I have a synth and say a delay following it, if I automate the delay the automation lane 'belongs' to the track the instrument is on. And I can hide that lane completely, so that only the instrument track is visible.

By contrast in Reason not only the delay gets its own separate sequencer track (which is in no way connected to the instrument its attached to), but also automation lane cannot be hidden completely, but only folded to a thin line.

I mean it fits very well into the virtual hardware rack paradigm and is fun for small projects, but can get really confusing quickly. That's why lack of folders is my main complaint with Reason - it would make session organisation so much easier.

Oh, I see - yes, I understand how that can be a serious PITA. For me it's quite nice as I don't typically use so much automation and I do not typically use a lot of tracks. With my resolution 32 minimized tracks fit on the mazimized mixer view at once and with the transport area hidden even 35, which for me is plenty. And it all looks stunningly clean, orderly and beautyful.

What I however don't like is the weirdly narrow height of the Clips in minimized view. Why make them even smaller instead of using all the available space? That doesn't seem to make sense to me, Looks weird (even buggy to me) and makes arranging minimized clips more cumbersome than neccessary.

[Psuper]

WYL: Core DAW Disapointing.
TCBTR:. Rack Released.
TLA: No Midi out of Rack.

Edit - this was not a reply, this was its own thread, and a pretty damn funny one. Mods there's a whole shitload of useless threads floating about here recently if you couldn't tell far more 'off topic' and worthless than mine -- may wanna clean your whole house instead of chase the one mouse you like chasing.

[Forgotten]

Had to go to work

[oonabe]

Yeah, the automation lanes are kind of weirdly designed on the sequencer track, I have never understood it either, why it's not possible to complete hide them.

Worse than that is that I've been having issues when I wanted to bounce tracks in place that had some automation. The bounced file would just complete ignore the automation and make bouncing completely useless, which actually is often needed to save CPU consuming. And it's not the only case I've had audio rendering issues.

Another thing I don't like in Reason is that reordering tracks in the sequencer won't reorder devices accordingly in the reason rack, so if you reorder tracks to get a better overview of your work you need to select them all and then tell Reason to order the devices accordingly. If you happen to have sorted devices in several parallel racks to have a better overview this can become easily very chaotic.

Also the three views are great if you have two or more monitors or a big one at least, but I am working on my laptop so I need to be constantly switching between there different views (sequencer, rack and mixer) and also the libraries tab on the left. It is not very hard to switch between them by clicking F5, F6 and F7 but it can get quite annoying having to do this when you're working on your songs, specially because it's easy to click the wrong key and then you get split views. That switching kind of gets in the middle of your workflow and makes it less smooth than it should.

I know these are minor issues but they're part of the daily work with this DAW and seeing that Reason Studios put more attention into mobile apps or creating a VST plugin rack no one asked for makes me sometimes want to definitely leave it.

[antic604]

Worse than that is that I've been having issues when I wanted to bounce tracks in place that had some automation. The bounced file would just complete ignore the automation and make bouncing completely useless, which actually is often needed to save CPU consuming. And it's not the only case I've had audio rendering issues.

What exactly were you automating? Was it be any chance an insert FX (in an Insert slot of the channel, not under the instrument)? I believe bounce-in-place renders the output of the channel, i.e. the audio is tapped before it goes into the SSL strip and Insert FX is part of that. You need to use File / Bounce Mixer Channel or copy over the Insert FX and their automation to the audio track.

BTW, it's interesting how Bitwig's GUI bothers you so much, while Reason which is on the total opposite end of the spectrum is fine