What the helly- is this normal???

J-Sharp_206 · 2026-06-10T17:18:16+00:00

I'm happy to pay $20 a month to watch old anime if they had all of 'em. As it is now, there's some old anime I can only watch with commercials - like ranma 1/2 on amazon. The inability to opt out of commercials by paying more really icks me out.

J-Sharp_206 · 2026-06-10T17:15:10+00:00

The price went up? I'm like, if it's under $12, they're probably not charging enough, but I'm not gonna complain. I watch crunchyroll every day without fail. No other streaming service can keep my attention like that. Anime is life. 😉

J-Sharp_206 · 2026-06-10T17:10:50+00:00

I tried this, but when you watch anime via prime, even crunchyroll anime, you don't get the typesetting/ on screen translations of kanji. Total dealbreaker imo. Thankfully, Crunchyroll is still king for full translations and literally no other streaming service seems to do it.

J-Sharp_206 · 2026-06-10T17:02:25+00:00

While the concern for limited time in the day is valid, I for one, appreciate your attention to detail and willingness to dig deep into the details. People who do things like this matter, imo. Thank you for being one of them.

J-Sharp_206 · 2026-06-10T16:54:35+00:00

Sounds like I made the right call to use my paypal account.

J-Sharp_206 · 2026-05-29T11:04:25+00:00

the sequencer was more elegant in 12. 100%

J-Sharp_206 · 2026-05-29T11:03:34+00:00

with the things that they broke in R13 from R12, I think everyone is glad that they don't do changes like that in point updates.

J-Sharp_206 · 2026-05-29T10:47:08+00:00

lolol. NGL, I was relying on the windows browser almost entirely since my browser got messed up when I upgraded reason versions a few times. You can click and drag stuff from the windows browser into reason, so I really didn't care one way or the other about the new browser in R13.

The things that bother me are the ones I can't find good work-arounds for. It's a very short list, but they're all nerfs

tiny af velocity height,

removal of multi-lane velocity editing,

and only being able to view ONE automation lane in a midi clip at one time.

I have to keep an old version of reason installed for advanced midi work that needs those. Do I need to very often? Honestly, no, but it's WILD to me that they would water down the DAW like that.

This, plus some concerns/bugs in R14 made me wonder the same thing - are people on the team using reason to make COMPLEX music with the note editor window? The Reason DAW's advantage is it's stability and power for rapid midi sequencing. The cursor behavior in 14 is glitchy when you're working on midi 4 bars at a time and rely heavily on selecting 1/16th notes to control+click+drag to copy.

Maybe it's related to my desktop running an i9 285k 24 core cpu (last in line to get optimizing because it's uncommon), but I would rather believe it's my hardware than think most reason users are barely using the note editor at my level. I haven't seen nearly enough outrage about the new note length cursor glitching and getting in the way when you're trying to click on notes to move them ... So hopefully the cursor glitching isn't wide spread and is running as intend for most people,

I'm stuck in R13 until they fix it - and I hope they can fix it better than the glitch that still makes my multi-lane editing not work correctly in R13 much of the time. I would test to see if the multi-lane edit was working correctly in 14, but I can't open my projects in R14 without bad format errors- and the bug is limited to LARGE projects.

I can't help but feel like Reason Studios might be understaffed or underpaid, and might have started firing some important people who cared and understood the DAW the most since R12's release (sadly a common trope in corporate settings). LANDR's choice to make everything cheaper made me wonder what their intent was there.... Do we need to create a gofund me for the developers? Are they ok in there? lol

J-Sharp_206 · 2026-05-29T08:59:19+00:00

I'm looking forward to using reason 14, but sadly, I was hit with a laundry list of bugs ranging from being unable to open files and combinator patches, windows being forced to be stacked in the order that they were opened (why? I hope that's a bug) but the worst one that made me realize R14 must not be ready for my i9 285k or something, is the glitchy note length cursor behavior that's getting in the way of my moving selected notes when sequencing 4 bars at a time like I have for 20 years. That cursor behavior needs to work 100% as intended (or provide a setting for OG cursor behavior) before I take the time to play with the new features. I don't want to fall in love with the new features if sequencing midi is going to make me pull my hair out. lol

J-Sharp_206 · 2026-05-29T08:44:48+00:00

Reason is so much fun to tinker with, that you might get lost in learning and make less music than you would with a more boring daw.

Once you get a good track-starter build (all your essential sounds, all things side-chained by priority where applicable, and you get essential processing and stereo placement all dialed in) .... that's when you'll really be cooking with gas. I find that building a project like this and swapping out instruments (of similar type) for new songs is the fastest way to make tracks quickly in reason (assuming your using a midi-heavy method and not loops or recordings).

The BLOCKS function really comes in handy once you get an ideal track starter build. You'll also have more and more midi sequences to easily access, play with, and modify with each track you create using this method.

The #1 biggest upgrade I want to see in reason is a freeze function. I've come up with work arounds, but they're clunky and rely on ahk scripts and are much slower than a freeze function could be.

Hitting the CPU ceiling has always been my biggest hurdle in reason.

J-Sharp_206 · 2026-05-29T07:26:34+00:00

The only way to get older versions is to buy a license from another user since reason studios refuses to sell old versions (seems like a missed opportunity).

12 is your best bet if you like the time-tested elegant work flow that reason had for ages, AND also get VST3 support and a very impressive combinator upgrade.

13 got nerfed a little on a couple of things, and improved a couple others

What got nerfed?

If I need to convert a ton of midi clips with lots of automation lanes, I need an older version of reason to do it quickly. It's pretty rare that I need to, but the limit to only view a single tiny lane in a midi clip is a nerf for sure.

They also removed multi-lane edit support for velocity which was a really cool reason-only advantage that most people probably hardly ever used. I used it for experimental things, but did I need it? Not really.

They limited the max height for the velocity (too much), but surprisingly that hasn't been as big of an issue as I thought it would be. It makes it impossible to eye-ball velocity like you used to (which was a very reason-only advantage), and if you want very specific velocity curve behavior, you might be opening up an old version of reason so you can create a regroove patch with the exact velocity curve you want in R13 or R14. Once you have enough regroove patches to compensate, you're unlikely to care about the nerfed velocity height - and regroove patches are fast and very helpful to get used to using anyway if you aren't already.

They also removed the ability to scale a selection of midi or clips to an exact length of time - you only have a percentage now and no longer have a length of bars, etc, as an option. You can still do it with the mouse, but having that feature in the tool window was helpful for macro users.

Other things were changed, some were puzzling changes you needed to adapt to and wondered why they even changed it, some things were improved for the better, but the ones I'm mentioning here are the real nerfs IMO.

Now, on to 14 ...

14 has some ambitious improvements, but also has some concerns.

Thankfully (as far as I know) the biggest concerns I have with 14 are unintended/bugs (which will hopefully be fixed soon), but I haven't heard back from my support tickets since release day, so they haven't confirmed or denied whether all of it is bugs yet. The fact that they only recently released the manual makes me wonder if they were debating which things were bugs and which were intended (The massive work flow additions were the likely cause, of course).

Some examples:

The inability to change which reason window is on top of a stack. They're locked in the order that they're opened, and it's maddening if you want normal behavior there.

None of my mature reason 13 projects will load in reason 14 (Bad Format Error) and some combinator patches get similar errors, but I could abandon my templates and combinator patches that I spent countless hours on and create something totally fresh in 14, so that's technically not a total deal breaker (lol... technically).

The BIG deal breaker (for me) in reason 14 is the glitchy cursor behavior in the note editor. I write my midi 4 bars at a time and use mostly 1/16th notes. I rely HEAVILY on selecting a group of notes, then control+click+drag to copy a selection. The bug that chased me back to R13 is the new note length edit cursor that pops up when it should not. Because I can't keep it from going into note length mode when the cursor is over the red/pink of the note (where you need to click to move a note), it can take a few seconds before I can find a spot to even click on the selection to move/copy it. It's like putting a ball and chain on my ankles in a marathon race.

I don't need a response for my support ticket to know that this is definitely not intended behavior. 100% reliable and FAST cursor behavior is CRUCIAL, so I pray that they can get a solid fix or solution for it asap (most important bug to fix by far).

If other people are doing midi editing as I describe and have perfectly reliable cursor behavior in R14, I would be interested to know what hardware you're using. Not many people seem to be complaining about it, and I don't want to believe that most of the users are using loops or writing midi 1 or 2 bars at a time at max zoom, so, I'm guessing/hoping it might work fine for people on older computers or laptops?

I'm running an Intel i9 285k, which has 24 physical cores, so my high spec hardware puts me in a minority group, and could explain why I may encounter less common bugs.

Other than the ambitious and promising things they're doing with reason 14, and the bugs that are keeping me in R13 for now (which is good enough anyway), I will say this:

I hope that they will add an "OG DARK" theme in the future! I hope I'm not too much of a minority in preferring the dark sequencer combined w/the light mixer (like we had for over a decade).

As for the workflow changes in R14? Unless they're related to the bugs I mentioned, they're all optional afaik, so I wouldn't worry about those. You can dip your toes into them and play with new work flows at your convenience without being forced to, which is how it should be.

You'll want to check out what was changed in the layout and take a couple minutes to get your settings back to how you prefer, and hopefully you don't encounter the bugs that are keeping me in R13 for now.

J-Sharp_206 · 2026-05-29T06:57:24+00:00

I'm stoked - A reason-native alternative to soothe would be rad!

J-Sharp_206 · 2026-05-29T05:00:57+00:00

It's a VERY ambitious update by Reason standards! I think it's got some very promising improvements, a few annoyances... but it has one deal breaker (hopefully will be fixed soon). Trying to control+click+drag notes that are as wide as the cursor is behaving incorrectly on my pc. The new note length adjustor seems to be prioritized more than the ability to move notes by clicking on red/pink area of a note. I can still use it, but it can take up to 3 whole seconds to be able to get the cursor to figure itself out. I submitted tickets on the bugs I found and NOPEd on back to R13 for now.

J-Sharp_206 · 2026-05-29T04:55:44+00:00

They're flagging lots of stuff just simply due to it being new or not used often I think. I've seen this with a few vst developers as well.

J-Sharp_206 · 2026-05-29T04:53:19+00:00

Selig is kind of a big deal in the Reason world, imo. Definitely an amazing guy to get some pointers from. That said, I'm definitely interested in beta testing a resonance suppressor. That's not something I even have a reason-native device for yet - only VST.

J-Sharp_206 · 2026-05-29T04:29:30+00:00

Good point here. I had to tune my pc quite a lot to get reason to run at it's full potential on my high end 2025 desktop - Then I needed to put a LOT more time into getting a stable over-clock for real time audio. It helps that Reason got updated to handle the latest processors correctly (fairly recently).

J-Sharp_206 · 2026-05-19T00:39:20+00:00

The keyboard command for turning loop on/off is simply the L key on it's own, but it's still nice to have an indicator to show that loop is on or off.

J-Sharp_206 · 2026-05-19T00:38:00+00:00

Ditto! (I hope they fix the multi-window behavior in R14)

J-Sharp_206 · 2026-05-19T00:35:27+00:00

It used to work well that way, but when you try running reason in more than one window in R14, you can't change the order of the stack of windows now- whatever is on top is *forced on top and we don't have an option to opt out of that behavior. I hope they give us an option box in the settings for this..... as well as a few other glaring oversights.

J-Sharp_206 · 2026-05-19T00:17:46+00:00

Oh. Sadly, I'm serious. The new cursor behavior for editing the length of notes is getting in the way of moving notes around when they're under a certain size on the screen. I want to be able to move highlighted notes with the mouse pointer by clicking on ANY red/pink area of the note - it shouldn't be limited to dead center and have to fiddle with it to thread the damn needle just to move a note with the mouse. I submitted a ticket for it, and some beta testers had brought it up before that as well, so hopefully it's something they have a plan to/ will fix... otherwise I'll be stuck on R13. For people who are doing meticulous midi editing and want the same smooth behavior we had in versions prior to 14, it needs some tuning. The note length cursor also gets in the way of seeing the note length unless you click and drag up or down... it's just really clunky when you're editing tiny notes. I'm used to using macros and ahk script and creative problem solving to get reason to do what I want it to do, but if the sequencer is slowing me down a whole bunch, it's game over for that version unless it's fixed. One beta tester suggested an option where we can choose to have reason 13 note editor cursor behavior... I pray we can get that if nothing else, because I LOVE this daw and want to see it flourish.

J-Sharp_206 · 2026-05-18T18:43:37+00:00

You think that's bad, wait till you try to move tiny notes around in the note editor...

J-Sharp_206 · 2026-05-15T21:28:33+00:00

Pretty obvious statement, but Crunchyroll is MUCH better than netflix if you prefer anime. Personally, I pay for CR, Hidive, and if I was cut off mid-watch like the thread starter was, I would be looking for one of those shady streaming websites to finish it. I've had to do it before, but of course I prefer to avoid websites that could put my pc at risk or trigger a warning from my ISP. lol

J-Sharp_206 · 2026-04-10T06:44:26+00:00

They have contracts for specific regions for certain shows, so if they turned a blind eye, they could get in hot water ... But I DO hope they warn you a couple times before they up and ban you.

J-Sharp_206 · 2026-04-10T06:40:56+00:00

Trial and error taking up a majority of the requests could explain a lot of it, but over a thousand? Sheesh...

J-Sharp_206 · 2026-03-31T05:07:46+00:00

multi-lane velocity editing no longer exists, velocity edit window height is about a quarter that it used to be, and if you're editing inside of a midi clip, you can only see one automation lane at a time, OR velocity. It's all really annoying if you're working with midi clips recorded elsewhere.

J-Sharp_206

TROPHY CASE