Re: [MoAccess] e: Inquiry: Motif XF6 and Sonar
- From: D!J!X! <megamansuperior@xxxxxxxxxxx>
- To: <MoAccess@xxxxxxxxxxxxx>
- Date: Thu, 12 Apr 2012 14:21:35 -0400
Where I can, I'll answer within your message to make it easier...
Quote: "It's better to say screw it and buy a $200 Behringer BCF2000 with
motorized faders than try to get the Motif to play nice as a surface."
Is this a keyboard type of controller, or is it more like a mixer type thing
with only sliders and such? Where may I find more info for curiosity's
sake?
This is a mixer type of unit, no keyboard. It has nobs and motorized sliders
that you can use to controll sonar/soft synths via it.
If you want something that is both controll surface and keyboard, there are
other options like the oxygen, axiums, etc. These don't have motorized
faders and are more limitted when it comes to controlling.
Google Behringer bcf2000 for more info.
Quote: "Recording MIDI in Sonar is fine."
Does this mean I can hit "record" in Sonar, play what I want recorded and
have that data go from the Motif into Sonar? If so, can I then route that
data to a softsynth and have that generate sounds instead of the Motif?
Would this mean that Sonar is receiving the data and acting as the Motif's
internal sequencer normally would? If so, this means that the recording and
playing back of the midi would all be happening through Sonar, unless I
assign a track's output to the firebox midi port and make the Motif's tone
generator play that way, right?
To do this, the best way is to set local off, switch to song mode or pattern
mode, then yes use sonar to record the midi data. If you want to use a patch
from the motif, create a midi track, set the output to the port that the
motif is connected to, then use the track properties to select a bank/voice
(requires that the motif's instrument definition be properly imported and
assigned to the correct port), then you should hear the motif patch playing;
this also means you'll need to have the motif connected to the interface and
some kind of realtime monitoring (usually called 0-latency monitoring) going
on. Once you record the track with the patch, then you create an audio data
and use it to record the motif's output. This might get more complex as you
ad more than 1 track/patch, depending on how you'd like to approach it; that
is to say, if you want to have all the motif output on one single audio
track, then it's simple, if you'd like to have each instrument on its own
audio track for mixing purposes and post processing etc, then you'll have to
record a track 1 by 1, being sure to use a combination of either solo tracks
or mutes and unmutes for the midi tracks.
Quote: "If you feel adventurous, connect the Motif's SPDIF output to the
SPDIF input on the FireBox. That will save your line-level inputs on the
Firebox."
This quote makes me nervous. Why would this be adventurous? Are there
settings in the Motif I need to be aware of? Isn't it just a "plug cables
in and play" kind of thing? Speaking of cables, what sort of cables would I
need for this kind of connection? Once I had those cables, wouldn't it just
be a matter of making the correct connections between the Motif and the
firebox? That doesn't sound too scary if that's the case.
Not sure what the motif requires done, but in most cases, working with SPDIF
requires samplreRate changes and clock source (for audio), in order for it
to work. You just need 1 single RCA-type cable with an RCA tip on both ends;
this is digital signals, so one cable is enough. you'll have to look around
on your interface's controll panel to see how to use the SPDIF jack and
successfully get input into the card.
"That article actually made me curious, do I need to set the Motif to follow
Sonar's midi clock? Will it still work properly even though Sonar has more
ticks per quarter note? I'm not entirely sure how that bit works... LOL"
You'll have to match both resolutions (I think the motif uses 480, sonar
uses 960), try and get the clocks to work together, and that's as far as I
made it; it was a mess on my eS, so I scrapped the whole idea; what I did
was make audio versions of arps and use those as loops if I wanted them.
Quote: "Trying to direct-dump is no good. As good as Yamaha is at some
things, one area where they're hopeless is their clock. The Motif clock is
loose, and it gets worse as the sequence is more complex."
So then, this means that if I sequence on the Motif with its loose clock,
the issue will still be reflected even if I set the Motif to follow Sonar's
clock during the transfer process? Speaking of "the transfer process," I'm
curious if the above article I quoted was referring to transferring via FW
or some other means. When you say "dump directly into Sonar," does that
mean press play on the Motif and the data will go out via its midi ports and
go right into Sonar? Or are you referring to one of those complicated sysex
command thingies of yours?
Transfer is probably refering to midi, though there are probably some sysX
messages along with those arps, but I think the clock issue would still
apply, because in order to use the motif's internal sequencer to record and
play the arps you'll have to use the internal clock, and sync sonar to it (I
might be wrong, but I believe that's how it's done). If the clock problem is
in the hardware, then no matter who is slave or master it'll still be
present.
HTH, D!J!X!
--
You received this message because you're subscribed to the MoAccess e-mail list.
To unsubscribe, change your list options, or view archives for the MoAccess
list, please use the FreeLists page.
//www.freelists.org/list/moaccess
Other related posts:
