Late for the Blockparty. Maybe you guys have already thought/talked about this, but I use blocks only to test song structures. I feel that it's what it is made for. Works for most genres. Of course you have to have some imagination of the songs dynamics- and sounds evolving to be able to use this : ...

I got into Bitwig really fast! It's really good and has many features I had already quit hoping for in Reason. Really good modulating capabilities and loads of pleasant surprises. Crappiest thing for me is the lack of a good groove pool/mixer. You only have your clip-level global groove, and midiedi...

I wonder how difficult would it be to allow multiple outputs from same parallel outputs, so we could get rid of the hassle of multiple spiders etc...

Cool stuff dudes!

This one was a "what ever suits the arpeggio"- meter, if I remember correctly.

A device capable of the same simple idea, but 8 rows and 32 steps?

Another vote for the comfy DT770pro and maybe the Sonarworks plugin later.

Great work! I'm very thankful.

YOLO-dive.

One more problem with them also: Convert block clip to song clip and mute it. OK, now you can hear the original block clip under the muted song clip... So if you want to leave a pause on that tambourine on the first bar, you have to f.ex write an empty clip on top of the block clip, or maybe you wan...

Blocks would be great IF you could instantly create a block of something you did, right in the sequencer (No need for Block-MODE) and also move/copy it around and drop it in somewhere. Dropping it in somewhere should move the previous stuff a block-length forward of course. This way you could REALLY...

Splice Bridge

I'm just happy for the small things, like names on all rotary-automationlanes under the combi.
I honestly feel this sequencer just got a lot better

Enjoy! (or not) Reason-made anyway!

OverneathTheSkyBridg wrote: ↑

16 Jun 2021

Yes! It would be great to have all of those effect devices in the sequencer being "children" of their parent instrument / track, rather than being their own tracks that I you have to keep track of when moving stuff around.

Out of interest what do you find messy about the sequencer. Every single automated device in the actual instruments chain gets it's own separate track. So when mixing a 20-track piece, you can easily end up with a constantly visible 100+ track hellhole in all rainbows colors. The sequencer should A...

adfielding wrote: ↑

15 Jun 2021

Less stuff, more refinement.

This.

The messy sequencer keeps me in Live, even if I like Reasons editing workflow more, f.ex.

Sequencer: All chained devices (not just the main device) automation behind one button on the track. One color dedicated to mark these automationlanes. : )

I think this update is just silly, but maybe there are some who appreciate a subscription for the whole daw/sounds-package. Applying constraints (limiting tools etc.) before starting to work, is one of the first advice for creativity in EVERY friggin' book about it. Now, browsing the "new" sounds we...

selig wrote: ↑

30 Dec 2020

http://docs.propellerheads.se/reasoness ... .01.7.html

Aaaaah damn of course! Thank you Selig, once again

Did you try ticking the second of the options shown in red here? I don't have an option for external keybd there. I guess it has something to do with mine being a Deltaco-keyboard and not Apple. All the 3rd party apps, same thing. Forcing Reason to use normal F doesn't solve the problem with half o...

This really pisses me off lol. Could someone with a MBP and Apples own magic keybd confirm if F7 works (show sequencer) without Fn-button? Maybe this is a third party keybd specific problem and I have to buy it.

Well, Reason Studios confirmed "trigger notes while editing" isn't there at all, when editing with keybd. I asked them to consider adding this addon to the existing feature, because it absolutely is a standard in midi editors (logic/LIVE/etc.), and helps composing work a lot. I don't really have any...

Do you have trigger notes while editing ticked in the general preferences tab? Yes, but that only affects notes triggered with mouse. It would be really convinient to hear the sound of notes when arranging voicings/searching the right drumsound etc. just with keyboard :) Not possible in Reason...?

Is there a way to get the midi to have sound when moving it around with cmd+arrows? Or is it really only happening when grabbing/moving with mouse.
I'm getting faster with editing on keybd, so would be really useful

Thanks.

estuary wrote: ↑

18 Jul 2020

Hi

You can change F1 to F12 behavior on keyboard settings (mac preferences)
You will be able to use F1/F12 as standard keys, but then if you want to use as your MBP shortcut you need to press "fn"

There seems to be settings only for the MBP-keyboard, not the bluetooth one....