You may find this one useful ua-cam.com/video/5rz2oXIQeys/v-deo.html Note: you can use the Pitch Bend wheel to change tempo as that has a good scale on it, so use the LFO to change the Pitch bend that will change the Tempo from the EMI.
Thanks for taking the time to demonstrate this. Maybe I'm missing something. How is this method any different from simply creating the instruments I need, and right-clicking to remote -overide the knobs/parameters I need directly? Just trying to figure out the benefit of using looback and EMI when it seems you have this functionality without it. What am I missing here?
I have done a number of video's where I use the Midi loopback and really this is a supplement to those videos. However you can take many different sources (LFO, ENV's, Audio, anything in CV) from within Reason and use that to control many many parameters on VST's and RE's that are not available for automation or via CV. Using this I have created a patch randomiser, you can do punch in and punch out, automatically do a Alt track, as I have been doing this since Reason 7 you can output ARP's from devices to Seq track (now it's quicker to do it via players if you have Reason 9 and above) and so so so much more... (Just the other day I answered a question where using loopback we could setup a Kong automatically, each pad to it's own output, panning the pads to the correct left ight, turning down sends and setting the outputs).
@@PoohBearsReasonChannel Wow- I was not prepared for that answer! I've been using Reason to produce professoinally for many years, and I actually thought my knowledge of the program was pretty sufficient until now. Going to check out some more of your videos; Thanks for taking the time to respond.
Hi poobear, can you advise me, I use a Roland TD9 drum kit and record midi from that, i also use (SD3) Superior drummer 3 as the drum device, but unfortunately my current Reason v 10.4 does not transmit CC4 data to vst's, i have a couple of work around, one is using SD3 in stand alone and using EMI and midi loopback, so thank you for this video, but with the new release of Reason 11.2 EMI is no more and is replaced with midi out device, Question: have you any idea if that works with midi loopback? i contacted support and asked if CC# data to vst is now working, the reply..."no additional functions regarding sending out MIDI CC# etc. We will continue to develop the standalone version of Reason " just to explain why i need this CC4 data, the Roland TD9 transmits this data for hi hat foot pedal, but without various tweaks to both TD9 midi output data and SD3 setting the hi hat stays open all the time! but Reason does record this CC# data it just doesn't send it to vst's, however it does send it to Reason RE drum kit.
First the easy question, the new Midi Out Device to me is nothing more than a upgraded EMI, I have loaded several of my old project (big one being my patch randomiser as I run over 400 EMI's in that project and all runs OK via loopbacks). I don't have SD3 however I would have thought you could have controlled the hi-hat pedal using CV, So from the frontend VST interface see if that parameter is available, if it is then I would load something like the CV8x4 and wire that to the VST, You can then record the knob movement. So you can not record the CC directly to Seq. however you can record the result of the CC e.g. the movement of the knob, then on playback that will drive the SD3...
Why are you using midi clock sync with your Nektar? it does not need it, unless you have T series for the repeats and that is a bit of an over kill, If you really need it, does your drum machine have midi thru? or get a midi splitter.
Thanks sorted it out didnt know you had to be in tranport on panarama to use knob on left to use ovarall tempo and took my system 8 of midi clock sync inwards as theirs a play button on keyboard and everyning synced up
Hi, thanks for the tutorial! I managed to install the loopback, select the external midi loopback to it, but then i add some reason device, when i right click (in v10.4) there i can't see anything like 'lock controller to this device'... when i look back in preferences it is correctly installed and also selected in the external midi loopback device... would you have any ideas? basically i would like to output some arp patches from my vengeance avenger so i can give it to an artist to remix so he would need recorded midi notes.. thanks!
I did reply to this yesterday, not sure what happened. Make sure you don't have the controller selected as the master keyboard as you can not lock those. (under preferences). Out of interest are you using the Avenger in another DAW?
Hi Poohbear, I have a vst called echo boy by soundtoys, and i need to automate some of it's controls, i right click echoboys controls but nothing seems to be automatable! is there a way using CV ? two controls i want to automate are wet dry mix and echo length e.g. from 1/8th note to 1/4 note
You don't right click a VST to automate you click the icons at the top, click either Automate or remote, then click the control, you can control a lot of VST's via CV from the VST interface, click the CV Programmer set the parameter you want to control and connect the correct cable at the back..
Hey PoohBear. It's Daniel Rhoads, we always met inside the FB Reason Users group! I need help. I purchased a piano tool for musicians software and I can't figure this out. I need your expert advice. At 4 minutes into your video you "right click" Thor and "Lock this device to keyboard". This is the step i can't figure out and it's not working. I've been trouble shooting this for hours! Please see the URL i provided below in this comment. This is the software i'm trying to get working. I am getting MIDI out data but I can't seem to get the MIDI OUT device to playback audio from Thor. At the bottom of the FAQ article it states specifically "Do not enable it as a MIDI In destination. Doing so will create a midi feedback loop and LoopMIDI will mute the port." And this is really (really) throwing a curveball for me. Please see FAQ titled "How do I use Chordie with my DAW and MIDI Controller on Windows?" in the URL below. Thanks for your time PoohBear! I much appreciate you ! Regards, Daniel www.chordieapp.com/
Also i'm using the Nektar p6 as well. So the only way i can get instruments is by using Reason devices and presets. Oh yes, and i'm also using the latest version of Reason 11.3.3d10. The MIDI OUT instrument changed from R10 like in your video. But i don't think that should matter. :)
PoohBear, after hours and hours of trouble shooting, I literally just put everything into a combinator and included the MIDI OUT Device within the combinator so that it plays both THOR and MIDI OUT Device at the same time. If you're reading this, don't worry about it. It's still not working how it should but i am satisfied with this result. haha. :) sorry for the troubles! If you feel like investigating this along with me that would still be awesome but no worries. :)
@@danielrhoads8676 Hi, really it should not be in the same combinator due to creating a feedback midi loop. So I think you want your setup to be, play a note -> Midi Out -> Chordie ->back to Reason to play a Thor ecord the results. So the first part is straight forward, just send the EMI\Midi Out device to the correct port, Next create a new port in loopmidi for Chordie to talk too, create a surface controller in Reason for that Port, lock that port to Thor and this is point where I believe you are having some issues...
@@PoohBearsReasonChannel amazing! Thanks PoohBear!! Soon as I get home from a day of work I'm going to trouble shoot some more and see if I can resolve this. I appreciate your reply! And I agree it shouldn't be in a combinator. (Although it was giving me a desired result exactly what I was looking to achieve) I still know that it's wrong and should be able to work without combinator. I'll check my preferences and make sure the surface controller is not selected as the main. This might be an area I have not explored yet. So thanks so much!
Many thanks for your contributions to the community, PoohBear 🙏🏼
Any time :)
Loving your Reason knowledge mate. Cheers. I want to get an lfo modulating the master tempo and this looks like the way to do it.
You may find this one useful ua-cam.com/video/5rz2oXIQeys/v-deo.html
Note: you can use the Pitch Bend wheel to change tempo as that has a good scale on it, so use the LFO to change the Pitch bend that will change the Tempo from the EMI.
Thanks for taking the time to demonstrate this. Maybe I'm missing something. How is this method any different from simply creating the instruments I need, and right-clicking to remote -overide the knobs/parameters I need directly? Just trying to figure out the benefit of using looback and EMI when it seems you have this functionality without it. What am I missing here?
I have done a number of video's where I use the Midi loopback and really this is a supplement to those videos.
However you can take many different sources (LFO, ENV's, Audio, anything in CV) from within Reason and use that to control many many parameters on VST's and RE's that are not available for automation or via CV. Using this I have created a patch randomiser, you can do punch in and punch out, automatically do a Alt track, as I have been doing this since Reason 7 you can output ARP's from devices to Seq track (now it's quicker to do it via players if you have Reason 9 and above) and so so so much more... (Just the other day I answered a question where using loopback we could setup a Kong automatically, each pad to it's own output, panning the pads to the correct left
ight, turning down sends and setting the outputs).
@@PoohBearsReasonChannel Wow- I was not prepared for that answer! I've been using Reason to produce professoinally for many years, and I actually thought my knowledge of the program was pretty sufficient until now. Going to check out some more of your videos; Thanks for taking the time to respond.
Great info thx
Hi poobear, can you advise me, I use a Roland TD9 drum kit and record midi from that, i also use (SD3) Superior drummer 3 as the drum device, but unfortunately my current Reason v 10.4 does not transmit CC4 data to vst's, i have a couple of work around, one is using SD3 in stand alone and using EMI and midi loopback, so thank you for this video,
but with the new release of Reason 11.2 EMI is no more and is replaced with midi out device,
Question: have you any idea if that works with midi loopback? i contacted support and asked if CC# data to vst is now working, the reply..."no additional functions regarding sending out MIDI CC# etc.
We will continue to develop the standalone version of Reason "
just to explain why i need this CC4 data, the Roland TD9 transmits this data for hi hat foot pedal, but without various tweaks to both TD9 midi output data and SD3 setting the hi hat stays open all the time! but Reason does record this CC# data it just doesn't send it to vst's, however it does send it to Reason RE drum kit.
First the easy question, the new Midi Out Device to me is nothing more than a upgraded EMI, I have loaded several of my old project (big one being my patch randomiser as I run over 400 EMI's in that project and all runs OK via loopbacks).
I don't have SD3 however I would have thought you could have controlled the hi-hat pedal using CV, So from the frontend VST interface see if that parameter is available, if it is then I would load something like the CV8x4 and wire that to the VST, You can then record the knob movement. So you can not record the CC directly to Seq. however you can record the result of the CC e.g. the movement of the knob, then on playback that will drive the SD3...
Do you know how to get tempo syncing with external device to drum machine in reason as i got midi clock sync with my panarama ?
Why are you using midi clock sync with your Nektar? it does not need it, unless you have T series for the repeats and that is a bit of an over kill, If you really need it, does your drum machine have midi thru? or get a midi splitter.
Thanks sorted it out didnt know you had to be in tranport on panarama to use knob on left to use ovarall tempo and took my system 8 of midi clock sync inwards as theirs a play button on keyboard and everyning synced up
@@jaymcaaa glad you are sorted, now have fun 🥳
Hi, thanks for the tutorial! I managed to install the loopback, select the external midi loopback to it, but then i add some reason device, when i right click (in v10.4) there i can't see anything like 'lock controller to this device'... when i look back in preferences it is correctly installed and also selected in the external midi loopback device... would you have any ideas? basically i would like to output some arp patches from my vengeance avenger so i can give it to an artist to remix so he would need recorded midi notes.. thanks!
I did reply to this yesterday, not sure what happened.
Make sure you don't have the controller selected as the master keyboard as you can not lock those. (under preferences).
Out of interest are you using the Avenger in another DAW?
@@PoohBearsReasonChannel in my reason you have to set the midi controller to master keyboard to
Hi Poohbear, I have a vst called echo boy by soundtoys, and i need to automate some of it's controls, i right click echoboys controls but nothing seems to be automatable! is there a way using CV ? two controls i want to automate are wet dry mix and echo length e.g. from 1/8th note to 1/4 note
You don't right click a VST to automate you click the icons at the top, click either Automate or remote, then click the control, you can control a lot of VST's via CV from the VST interface, click the CV Programmer set the parameter you want to control and connect the correct cable at the back..
Ah I see, yeah Great it creates a new lane for VST with the appropriate control lane, Thanks Poohbear
Hey PoohBear. It's Daniel Rhoads, we always met inside the FB Reason Users group! I need help.
I purchased a piano tool for musicians software and I can't figure this out. I need your expert advice.
At 4 minutes into your video you "right click" Thor and "Lock this device to keyboard". This is the step i can't figure out and it's not working.
I've been trouble shooting this for hours! Please see the URL i provided below in this comment. This is the software i'm trying to get working.
I am getting MIDI out data but I can't seem to get the MIDI OUT device to playback audio from Thor.
At the bottom of the FAQ article it states specifically
"Do not enable it as a MIDI In destination. Doing so will create a midi feedback loop and LoopMIDI will mute the port."
And this is really (really) throwing a curveball for me.
Please see FAQ titled "How do I use Chordie with my DAW and MIDI Controller on Windows?" in the URL below.
Thanks for your time PoohBear! I much appreciate you !
Regards,
Daniel
www.chordieapp.com/
Also i'm using the Nektar p6 as well. So the only way i can get instruments is by using Reason devices and presets.
Oh yes, and i'm also using the latest version of Reason 11.3.3d10. The MIDI OUT instrument changed from R10 like in your video. But i don't think that should matter. :)
PoohBear, after hours and hours of trouble shooting, I literally just put everything into a combinator and included the MIDI OUT Device within the combinator so that it plays both THOR and MIDI OUT Device at the same time. If you're reading this, don't worry about it. It's still not working how it should but i am satisfied with this result. haha. :) sorry for the troubles! If you feel like investigating this along with me that would still be awesome but no worries. :)
@@danielrhoads8676 Hi, really it should not be in the same combinator due to creating a feedback midi loop.
So I think you want your setup to be, play a note -> Midi Out -> Chordie ->back to Reason to play a Thor
ecord the results.
So the first part is straight forward, just send the EMI\Midi Out device to the correct port, Next create a new port in loopmidi for Chordie to talk too, create a surface controller in Reason for that Port, lock that port to Thor and this is point where I believe you are having some issues...
@@danielrhoads8676 Make sure you don't have the new surface controller selected as the master keyboard as you can not lock those. (under preferences)
@@PoohBearsReasonChannel amazing! Thanks PoohBear!! Soon as I get home from a day of work I'm going to trouble shoot some more and see if I can resolve this. I appreciate your reply! And I agree it shouldn't be in a combinator. (Although it was giving me a desired result exactly what I was looking to achieve) I still know that it's wrong and should be able to work without combinator. I'll check my preferences and make sure the surface controller is not selected as the main. This might be an area I have not explored yet. So thanks so much!