Hello Radias gurus
After many happy weeks trying to learn the vast intricacies of my new Radias, I was struck with a brainwave; Why not use Reason 4.0 on the ibook G4 as my drum machine? This would save a timbre and a step sequencer. Surely it would be relatively strightforward to sync Reasons tempo to the Radias internal clock by conencting both with the USB and using the Radias internal clock as master? Apparently not & I suspect I’m missing something obvious. I’ve read & reread the manual for both the radias & reason but am at a loss.
I set up Radias is set up as follows:
P-04 Midi
MidiCh: 01
LocalCtrl: On
Routing: USB
Clock: Internal
Reason:
Preferences
Advanced Audio
No midi input on bus A, B, C or D
Midi Clock Sync is set to: Radias KBD/KNOB
ALSO; Options; Sync; Midi Sync is checked.
When I try to activate the play function on the Reason Transport Panel, I get the following message “…..midi sync enabled, Reason not incontrol of Transport controls or playback/start stop”
So I figured that the Radias needs to trigger the playback – the question is how? Playing a note doesn’t do it so I tried setting up a simple step sequencer on timbre 1 of the radias but it doesn’t seem to affect reasons tempo. If I use the preview function on the indivaidual instruments within reason, I get playback but they are not in sync with radias tempo and are unaffected by tempo changes made on the radias. Any ideas anybody?
Much appreciated
Tempo Sync Reason 4.0 as slave to Radias Internal Clock
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
not sure about reason, as this is really a reason problem, but i think you need to turn off 'midi sync'.
sounds like 'midi sync' sets the playback control. for example if you had something which did transmit start/stop messages such as a triton's sequencer mode.
you've already set the clock source to the korg, so this should be enough.
its complaining that it can't start because you've told it to start when instructed to over midi.
sounds like 'midi sync' sets the playback control. for example if you had something which did transmit start/stop messages such as a triton's sequencer mode.
you've already set the clock source to the korg, so this should be enough.
its complaining that it can't start because you've told it to start when instructed to over midi.
- meatballfulton
- Senior Member
- Posts: 351
- Joined: Wed Jun 20, 2007 11:28 am
I don't have Reason 4.0, I'm still at 2.5 and in that version the transport still works when MIDI sync is selected.
According to a post I read at the Propellerhead forums in 3.0 they added a "feature" that disables the transport when MIDI synch is selected. That would work if the MIDI clock master sent start/stop messages, but the Radias does not.
Looks like you are out of luck.
According to a post I read at the Propellerhead forums in 3.0 they added a "feature" that disables the transport when MIDI synch is selected. That would work if the MIDI clock master sent start/stop messages, but the Radias does not.
Looks like you are out of luck.
I sing the body electric
Thanks for the reply Meatball, you've cleared that mystery up for me.
As a work around, do you think that using Cubase might be the answer? I've never the software but apparently I can plug Reason into it via Rewire and then somehow route the Radias to it also, controlling master tempo of both Radias & Reason via Cubase. Do you think this would work?
Cheers
As a work around, do you think that using Cubase might be the answer? I've never the software but apparently I can plug Reason into it via Rewire and then somehow route the Radias to it also, controlling master tempo of both Radias & Reason via Cubase. Do you think this would work?
Cheers