soundwayv wrote:what's up guys,
sparq helped a lot on the video he did about using the mpc as a sound module, and he helped me with a few issues i had using the mpc, but i thought i'd ask somebody else for advice this time around. my question is: when switching reason sounds in reason using the bus ports, i come up with the problem of getting both sounds read at the same time on my mpc. is there away to resolve this?
when using reason as a sound module, make sure you have a mixer created. the create your sound devices. for each device created off of the mixer, assign it to a channel at the top. then, create your mpc tracks, select midi, no program, and then your corresponding midi track 1a, 2a, 3a etc.... whichever one you choose for the mpc track ( example: you create a dr rex player, and you have a mpc track set to 1a, at the top of the hardware reason engine you would set dr to 1 a... then you create a maelstrom player and have a mpc track 2a, you would then set reasons hardware engine to 2a for the maelstrom, the you have a nn19 sample and a mpc track set to 3a, you would set reasons harware engine to 3a for the nn19 and so on, but you must have a mixer to use multiple instruments. ) Another note, is, say you have 5 reason instruments, and they are all configured at the top of reasons harware engine 1-5, and you have 5 mpc tracks of midi set 1a-5a, you have to make sure that the little midi sign next to the midi tracks in reasons sequencer ARE NOT lit up. At this point you will choose which reason instrument to play by switching between mpc tracks. This is important. If the midi signal is highlited next to any of the reason instruments in the reason sequencer it will cause issues. Another important note is you MUST have a mixer first for multiple reason modules. When you rewire to record it in another program like protools, this is where you would get rid of the mixer and plug your instruments directly into the reason hardware interface. I hope this helps you. Let me know if you need anything else.
Peace
