fasadlens.blogg.se

1. #CUBASE 5 REASON REWIRE HOW TO#
2. #CUBASE 5 REASON REWIRE MANUALS#
3. #CUBASE 5 REASON REWIRE INSTALL#
4. #CUBASE 5 REASON REWIRE CODE#

The Sibelius and Cubase manuals seem to contradict each other. Also, when I subsequently open Sibelius I get an error "Audio Engine: Bad Settings" and it opens in Rewire mode - the Clean Up button fixes this. Close Sibelius and try again." If I then quit Sibelius, I still get the error from Cubase and have to do a Force Quit. However, when I try to quit Cubase, I get an error "Can not quit because Sibelius is still open. works fine, though I had to use the Repair Button the first time. I'm guessing with the Akai LPK25 that I tested it is a very simple item and just using the generic midi keyboard framework is how it just drops into place.I can open open Cubase 5 then Sibelius 6 in Rewire mode without problems, and playback, etc. So I'm wondering, does Cubase need some kind of extra file like Reason does with the a file to fully understand the blocks behaviour. No problem at all in Cubase, playback was perfect from pad 1 to 16. in standalone reason and in rewired mode in cubase. I did a test again with the Akai LPK25 - and straight away, it worked perfectly in both scenarios i.e. If I use Reason in standalone mode with the Block - everything is perfect so something must be going on in Cubase? The midi goes into cubase as it should but then playback is scrambled with loads of the notes not getting played back. I did a simple recording test - pressing the buttons I have mapped to rows 3 + 4 on the block which map to pads 1 through to 16 on a Kong. But on playback it doesn't play the notes you pressed, but only a few of them. You play the notes in and it sounds and looks fine. Yes, exactly the same behaviour even with 'Master Keyboard' unchecked.

#CUBASE 5 REASON REWIRE CODE#

I am happy to experiment with any code modifications if someone has any ideas ? I would sacrifice all other features (transport row at the top, mute row etc) just for 16 pads that would behave the same as a basic midi keyboard. What I am aiming for initially is to strip out any of the extra functionality of Kong's / Block relationship so that all it does is say trigger the 16 pads in a Kong. Or maybe I need to do further editing of the a file? Now that I've added Rewire to the mix I think I need to maybe edit the block.remotemap file also? Yes, if you just use Reason (and Kongs) standalone just editing that file so that you can trigger the 16 pads in a Kong etc - perfect, it worked a treat. assigning the Midi keyboard values to rows 2,3,4 for example.

#CUBASE 5 REASON REWIRE HOW TO#

Peter showed me how to edit this in a previous post and it works a treat i.e. Now I'm sure with some help I can figure this out. I can use the Block to go up and down the key scales, it records midi parts into its cubase channel, then on playback it triggers the midi pattern in Cubase which in turn triggers the Midi instrument in Reason which routes the Audio back via rewire and out of the Audio channel in Cubase.

If I rewire a more simpler instrument such as a Maelstrom or an ID8 - no problem, everything works as it should. The main problem I have identified is with Kong.

#CUBASE 5 REASON REWIRE INSTALL#

I wiped the MBPro and put a clean install on and no problems. I have done some further research and narrowed things down.įirstly, Rewire 64-Bit works perfectly between Reason 6.5.1 and Cubase 6.5.3 on Mountain Lion.