Looper's Delight Archive Top (Search)
Date Index
Thread Index
Author Index
Looper's Delight Home
Mailing List Info
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: Laptop looping... sync sank sunk...

One problem may be the FCB1010 MIDI merge.  It's notoriously flakey and it's recommended to not use it at all.  Using a seperate MIDI merge box may solve your problem.

Todd


On 5/17/06, mark sottilaro <zerocrossing2001@yahoo.com> wrote:
Hi kids!  Welcome to the trials of laptop looping
show!  Most of this was also posted on the
sooperlooper list, so if you read it there you can
stop now.  I'm reposting it here because the problem
I'm having seems dual platform with two of the most
popular software loopers.

OK, I tried this set up last night.

Rather than try and tax my desktop G4, I ran
Sooperlooper on the G4 1.25er I'm barrowing.  1 gig of
ram and a pretty clean hard drive. M-Audio 410
firewire interface and a MOTU Fastlane MIDI USB
converter. MIDI Passed through a FCB1010 to merge it
with PC info.

Couldn't get a loop to sync to the clock at all.  What
do you think is the problem?  I had this exact same
problem with trying to get Mobius to run on my
girlfriend's Thinkpad.

Now I had good luck running it from within Digital
Performer but I didn't try to control it via MIDI.
Perhaps I'll try it this weekend.  Ultimately this is
how I'd like to use it, but I'm at a loss at figuring
out why it won't respond to my clock correctly.  I've
had no issues getting it to sync with a Repeater, an
EDP and some basic sync with the Looperlative.  Could
it be that those devices are more tolerant of bad
clock?  I could try another merge box for the MIDI
too.  Has anyone else tried a similar setup and had
this problem?

Mark

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com