Have you also turned on the record arm/monitor icon for the respective audio tracks?

Change the monitoring setting from automatic to manual: http://docs.propellerheads.se/reasonsui ... .06.3.html

Marc64 wrote: ↑

12 Nov 2024

Every daw has it's strenght and weakness. The BIG! strong side of reason is that you can use another daw of choice and stil use reason as vst. It don't think any another daw has that ?

Ehem, FL wants to have word with you.

They can be found here: https://www.reasonstudios.com/news/giveaways

For Mimic or NN19 recording a filter sweep into a long sample and then playing with the sample offset (like we did in the old tracker days) can be a fun way to make music.

If you want to get as close as sampling a synth allows for the best would be each note individually. And depending on the characteristics of the synth (filters, modulation, etc.) even some variations of those (again for all notes).

In the option menu there is an option to select if automation is recorded in note clips:
https://docs.reasonstudios.com/reason13 ... nce#509284

If you need some more CV inputs to further route as CV in the combinator you can use the Hamu MatchMaker to keep things organised.

I just tried it out to see if I remembered it correctly. And one thing that has to be done a little different: Create a combinator Put a line mixer 6:2 in it Put some instruments in it Put a "Receive Notes" on top of each of the instruments you want to control and leave set it to "Any". Add a "Selec...

Put a "Receive Notes" on top of each of the instruments you want to control and set it to the respective channel (1-4). Then add a "Select Program" on top and map its select rotary to a rotary of the combinator to stretch its values from 1 (0%) to 4 (100%). Then wire the "in Enable" on each of the "...

That's easy to do using just those two free REs inside of a combinator:

https://www.reasonstudios.com/shop/rack ... t-program/
https://www.reasonstudios.com/shop/rack ... ive-notes/

Hmm, then I suppose that's a question for bitwig support, then.

I think it is related to how much bitwig is sandboxing the VST and if I remember correctly you can configure it for each VST individually.

Depending on the number of VST you already have from them going "all in" could also be a good option.

YAY, it totally worked to bring Objekt into my collection.

Thank you so much, Quarmat.

In this whole thread you still have not given the exact version number of your R11 installation if it is not 11.3.9 this might be the missing puzzle piece (as that version had some changes regarding Authorizer and handling RE licenses).

One step that might be missing: Set the loop markers to the section to where the notes shall be rendered.

Hi Quarmat,
thank you for the very generous offer.
I'd be interested to try it (as I didn't get one, as I registered the R12 upgrade during the grace period and thus got R13 on release).

I'll reorganise things a little (i.e. put sample/refill libraries on the storage server instead of a local spinning rust disc) and give it another go to see how that would work out. But I'll most likely wait until the next release version drops before trying again.

Oh, well. Yesterday I gave this version a try and imported most of my rather huge sample (~1.5 TiB in ~700k files) and Refill libraries (~138 GiB, including 26.5GiB R+ packs). Here are my results: After only a few hours of scanning it finished and resulted in a __ReasonIndex_v7 file of about 2.7 GiB...

Last SDK is 4.5.0 and RE under it, support work under any Reason version from 10.1 and newer. Problem not in SDK update and compabilty of RE with Reason version in range 10.1 - 13 OK, I stand corrected. Then I suppose a possible Hi-Res update of the RE instead might be the culprit here which possib...

Thanks for the information: then it looks like they lost the backwards compatibility. What good reason could there be to throw away the backwards compatibility just when the developer stopped supporting the RE? Why not leave it alone in that state? I really hope this is just a mistake. I raised a t...

bxbrkrz wrote: ↑

24 Oct 2024

That's a great classic which was quite ahead of its time imho.

Selig, I think you misread the OP. You're describing how to route CV to a VST in Reason stand-alone.

But I think OP is trying to get CV out of the RRP (which sadly still can't host VSTs) into their unnamed DAW to then route it to a VST there.