I came to skim through the discussion, but this was all I found:
This is some sort of grim, biblical prophecy, nuclear-winter-level meltdown if the venerable EnochLight
have announced having thrown in the towel. I say that with no disrespect or sarcasm; these two are practically institutions in this community. I just never thought I'd witness them reaching their limit with this app. Like, ever.
So many regulars have left this board it's like a graveyard of its former self. Scorched earth compared to just a couple years ago. I digress.
catblack wrote:My frustrations are not due to all of this controller programming, but rather how hidden away the remotables are from your midi controller. Even in the demo videos that Reason puts out, it's always a mouse moving one control at a time. I keep referring to this as an existential disconnect because the Remotables exist! It's a wonderful spec, an amazing technology! It's right there but you can't see it from the front end of the program!
Ah, yes. This old facepalm. I'll chime in one more time about this, maybe their ears will prick up..
The single most revolutionary change that Reason could make is to replace the Remote Override Edit Mode with a new skin on the current implementation. Something like this.
As a User, I Can:
- Set any and all pertinent Remote mappings from the Edit Mode view of the Rack.
- Draw links between device controls, allowing for visual feedback of affected min/max knob turn, etc. (as seen in Massive and others.)
- Visually program desired behavior entirely within the app interface, with "save in song" by default and option to export as customizable files.
Anyway, look. I'm already done. I've made that plain. Again, couldn't help myself. This time because of the whole nuclear winter vibe I'm getting from the die-off of regulars. But it's not all schadenfreude.
Actions speak louder than words, and even better if it's on video. So, I need somebody's help with getting OBS + Reason + Soundflower working (I want Reason Audio-Out and Built-In MacBook Audio-In combined inside of OBS). Then I can finally make a video I've been wanting to make for a loooong time. The mythical and potentially hilarious DataBridge Demo.
I mean, I think it'll be pretty funny. But I have a warped sense of humor.
adfielding wrote:Interestingly, I think the idea of workarounds actually explains my personal concern with the current direction of Reason to a certain degree. Despite being not-so-great for workflow, I've generally accepted that workarounds have been necessary to use Reason the way I've wanted to in the past - though certain features (mainly audio recording & VST support) have gone a massive way in stomping out the most egregious workarounds, it feels like new ones keep popping up.
However, the biggest for me is the idea of hosting Reason inside another DAW to compensate for the current limitations of the standalone environment. It's great that the option is there (and I think I'd be a fool to suggest otherwise), but it does feel like a very tidy way to side-step any issues people have with using Reason standalone. "Now you can use Reason in your favourite DAW" is a great selling point if your favourite DAW is anything other than Reason. If, like me, Reason IS your favourite DAW - well, sticking it in a completely different environment is quite the workaround! Still, it's absolutely in keeping with my own trend in accepting workarounds as a cost of using Reason the way I want to - so there's that, I guess.
This was exactly my breaking point. I worked on my Remote project for roughly 5 years, all told. But in the end, it was a massive, rabbit-hole-esque added layer of abstraction that was ultimately nothing but a giant workaround
The whole purpose was to shore up the user experience to what it could and should be. So once I had built my project and gotten used to it, it soured me on ever going back to "vanilla" Reason again. Even so, the experience was like handling a Faberge Egg with mile-long tweezers and a telescope. Remote just doesn't have the facilities to make what I had designed "user friendly" or "smoothly integrated". Namely, a GUI for mapping control flow networks between devices and native app support for "save in song" of those same control flow networks.
It was then that I realized my work had been a waste, despite having pushed the technology of Remote as far as I could take it. It felt like I, as one person, had more vision and drive than the entire team behind the app itself. The day would never come when my efforts would be realized as an official feature that I could no longer live without. So, I cut my losses and left.
But the thing is, no one has ever seen my creation (or more importantly heard
my creation) in action. I think that RS should at least be aware of the implications of adding such a feature officially; especially MattiasHG
. I'm agnostic to the outcome, I just owe everybody that's left a proper rundown after so much talk.
Somebody help me get my audio setup.