How's Reason 10.3 beta going?

[xbitz]

still the sequencer its weakest point (although yepp it's not beta related), luckily Notion works with it using Bidule as ReWire master host in it

it has quite good hybrid view (not super complicated so quite good PR replacement in Reason at song starting phase, good to have a secondary monitor ofc.) >>

Notion allows you to view both notation and performance information within the same staff . This special mode is called Sequencer Overlay and can be accessed via View > Show > Sequencer Overlay (or by pressing Tab) . When you enable Sequencer Overlay, you will see bars appearing on top of the noteheads in your score . Those bars represent the note’s duration and position and even velocity or dynamic . By clicking and dragging on the end points of the bars you can adjust the note’s start and end times as well as when the note starts in the measure .

[reggie1979]

One thing I hope the rewrite does is make it so that it doesn't crackle when accessing the web. It's not a critical thing but it's really annoying.

I would think that is more related to hardware and drivers rather than how any particular piece of software accesses the audio hardware of a machine.

It isn't. I don't have that problem with other hosts.

If it's Reason, don't you think that every Reason user would have this issue? Reason is exactly the same for every Reason user - the variable for every user is their audio infrastructure and the drivers that Reason uses to access that hardware.

Am I blind or did the person directly below CONFIRM the issue?

Honestly, I don't understand forums.

[Deep Purple]

Am I blind or did the person directly below CONFIRM the issue?

But that's still not the totality of Reason users.

All I'm saying is that when you have issues with some users, the likely culprit is the variable, not the fixed value.

Drivers and hardware can be extremely variable, and device drivers are usually closed source code that software developers do not have access to - Reason may be making quite reasonable (sic) demands of the driver that are triggering bugs in the driver not caught during testing as the driver manufacturer did not foresee a particular use for the driver.

[chimp_spanner]

I wouldn’t get too hung up on it; ultimately I don’t think any DAW is designed to allow you to browse the web while rendering unbroken audio at 64 samples. Stands to reason that you’ll have a smoother experience with a higher buffer size as your cpu has more time to do everything it has to do. It’s a nice little bonus if you can have a browser open now but it’s not like, a feature. And it’s definitely not a fix as I’d say it was never an issue.

Most important thing is that VSTs are performing on a level with Cubase for me now, which is great as I much prefer working in Reason. Static automation values keep me sane

[THE INTRANCER]

Studio One 3 and above has had the option to isolate the audio from the rest of the operating system to avoid audio screwing up whilst doing other things like watching videos on youtube for example. If Reason doesn't have that option, then that's a problem.

[chimp_spanner]

Huhm. Well, that is useful obviously! Not heard about that kind of thing in other DAWs. Maybe it’ll become more common. Let’s just say it wasn’t something I was waiting for in 10.3, personally. But there ya go!

[Yorrrrrr]

Sigh..I just wish Reason was Retina compatible. I'd love to purchase a license, but it looks like crap in my MBP.

[ShawnG]

Im guessing this would only happen when using your audio interface as the windows sound device at the same time? My Interface only sees DAW use. I use the mobo sound chip for games/web/streaming/spotify/whatever.

[Deep Purple]

Sigh..I just wish Reason was Retina compatible. I'd love to purchase a license, but it looks like crap in my MBP.

I hadn't even noticed that - I use it on mine and it does fine, even without retina support.

[reggie1979]

Am I blind or did the person directly below CONFIRM the issue?

But that's still not the totality of Reason users.

All I'm saying is that when you have issues with some users, the likely culprit is the variable, not the fixed value.

Drivers and hardware can be extremely variable, and device drivers are usually closed source code that software developers do not have access to - Reason may be making quite reasonable (sic) demands of the driver that are triggering bugs in the driver not caught during testing as the driver manufacturer did not foresee a particular use for the driver.

Who cares. I'm saying on at least two computers it's an issue and other hosts it's not. Since when is an issue not an issue just because not EVERYONE has it

Anyways, sorry I brought it up. The pretzel logic on forums is beyond my pay-grade.

"Don't fix issues because not every-single person has them? BRILLIANT!"

[Deep Purple]

Who cares. I'm saying on at least two computers it's an issue and other hosts it's not. Since when is an issue not an issue just because not EVERYONE has it

Anyways, sorry I brought it up. The pretzel logic on forums is beyond my pay-grade.

"Don't fix issues because not every-single person has them? BRILLIANT!"

I don't recall either saying or implying any of these things, nor did I question that there is an issue on at least two computers for just one host.

[Danilo Villanova]

Who the hell cares about watching YouTube while making music? Focus on what you're doing so you can do it well! Or use your goddam phone. Western people truly have become weaklings who need to be pampered like babies in every single way. You want the software to give you a BJ too? Did you need to highjack half the thread with that nonsense?

[starflakeprj]

Who the hell cares about watching YouTube while making music? Focus on what you're doing so you can do it well! Or use your goddam phone. Western people truly have become weaklings who need to be pampered like babies in every single way. You want the software to give you a BJ too? Did you need to highjack half the thread with that nonsense?

I do, I often watch tutorials while I'm in my DAW.

In my case my audio problems is not because of my DAW, as it doesn't matter which DAW I use (Reason, Studio One, Bitwig or even Reaper). When watching YouTube videos at the same time when using my DAW, the sound suddenly stops and the video either stops or continue playing without sound.

Anyway, without changing the topic to how much I dislike my audio interface, or the vendor that can't seem to help, there are people who would like to be able to use other features of the OS while producing music.

[chimp_spanner]

That’s weird - I’ve only ever had that problem when using the built in sound chip, where my DAW has exclusive access to the audio driver. Shouldn’t happen with an ASIO interface. Which do you have?

[Hanz Meyzer]

What patch was used, a monophonic one? What was the samplerate and buffer size? Why should Bitwig perform such better when the main cpu work is done within the plugin and the mixing should barely take cpu at all? Does Reason use an individual sandboxing, and what about Ableton?