Imagine ...a "new" Reason

Simple(r) GUI, no screen wasting extra pixel padding around the essentials,
with every section at a distance of 1 click (top bar)


"pancake" style main menu when at the minimum width of the rack
(which I'll keep in these mock-up examples)


With modular sections, layout customization and all (browser included) detachable as separate windows
(to keep it simple, these mock-ups will show them all still attached)


So the Browser could still show up on the left


or on the Right, according to how it's configured
...or simply detached as a new separate window


The top bar could also include the toggle buttons for Virtual Keys and ReGroove
which both could still be detached on separate windows
or attached/stacked horizontally in any order vertically


Same with the Sequencer, could show up at the top of the Rack or still at the bottom


We could quickly toggle the Navigators with 1 click, as/if needed


same for the Transport (on all windows: Rack, Sequencer and Mixer)
...with a bigger Tap Tempo button, btw!


Any vertical oriented section could be dragged/moved/swapped horizontally


and any horizontal section could be dragged/moved vertically to any position


The Tools window could show attached on the opposite side of the Browser or detached as usual.
or, like we've seen on recent R13 screenshots, in the Clip editor section

This style of section/window hide/show/detach/attach modularity isn't new
Developers are quite used to this on modern IDEs
A simple example: Visual Studio Code

Even being able to get multiple views of the same Rack/Sequencer/Mixer

Speaking of modularity and imagining a "new" Reason...
a Modules "combinator" Rack Device would be very welcome too

Not necessarily Euro-rack "cables-at-the-front" style of modules.
Could still be Reason-style "cables-at-the-back", but different size form-factors would allow simpler rack devices to become smaller, simpler modules:
Think Kong-style modules (but probably taller).

Some Rack Extensions already "fake" it with that modular look

not quite but the look helps to imagine 
how smaller vertical modules would snap together horizontally
like horizontal rack devices snap to vertically

and in-Rack MIDI routing ?
like we've always had auto-magically-connected Audio cables that we can then reroute
that could happen with MIDI cables too, allowing "Players" to be just regular Rack Devices

Then a new class of Rack Devices could happen:
Full MIDI (not just Note msgs) processors, mergers, splitter, routers, generators, etc
...and this would finally open the way to VST that generate MIDI

Comments

Post a Comment

Popular posts from this blog

Generic MIDI Channel aware Remote Codec+Map

Image
If you have a controller capable of sending MIDI messages on multiple MIDI Channels, like an M-Audio Axiom 's 4 Keyboard zones (so 4 MIDI Channels from the same keyboard) plus the Pads on Channel 10 or an Arturia BeatStep PRO that can send 2 sequences on their own MIDI Channel (1 and 2) and its Drum sequencer on MIDI Channel 10 plus the controller on, say, MIDI Channel 16, etc,  then you certainly felt the need for a MIDI Channel-aware type of Remote Codec like this one. Taking the BSP example, here's how to get its 4 sources of MIDI into Reason with this Remote Codec+Map. Add a Control Surface per MIDI source  with these 3 easy steps: 1)  Add a Control Surface from the " <Other> " Manufacturer and choose the correct " Generic Controller on MIDI Channel __ /< " Model with the MIDI Channel you'll need 2) Give it a proper name, so you know what's the real controller being used with this generic map (that you
Read more

Arturia SparkLE Remote Codec+Map

Image
Hey all :) I've been asked last week to share my Arturia SparkLE Codec so here it is :) (unofficial) Arturia SparkLE Remote Codec (and partial Map) V1.0.2 ReDrum: Added Drum Channel selection support through the Dial encoder Edit Flam with Select+Loop Button Flam Amount  with  Select+Tempo Encoder Shuffle On/Off through Loop Button Actually, this has been sitting on my Remote projects folder for 2 years now (and far from being alone in there, eh), waiting for me to complete the rest of the Remote Map, because my initial need for it was really just to control Kong, Dr.OctoRex and ReDrum, that's why those are really the ones that got some partial love on the included map. Early this year, due to the improvements added to the ReDrum remoteables s ince Reason 8.2 , I ended up making some editing to support the new ReDrum remoteables :) I'm hoping that anyone wanting to extend it or complete it has enough examples already in the partial map I'm
Read more

Random access to a CV values list

Just added this little CV tool in the free download section (on the right): "K's Basics - Random access to a CV values list" It's basically a way to access through CV indexing, a list of 3x32 "cells" of CV values (well, one of the list is within the Note range of CV values, but this example is enough to demo the concept). So, if you're ever in need of generating a specific sequence of CV values controlled by another CV source, this is one way to do it :) It's like having random or sequential access (in whatever direction you want) to a specific custom list of CV or note values, by using a CV controlled "cursor" (just connect the CV "cursor" source to the Rotary 1 CV input and tweak the Combinator modulation programmer Min/Max values to your needs). This device was enough for something I was testing, but I'm sure it can be optimized with some thought and more time. It won't work well in a real-time fast switching situation,
Read more