MIDI Timing/Delay Issue when using external gear/software

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
Mark EG
Posts: 14
Joined: Fri Mar 04, 2005 11:18 am

MIDI Timing/Delay Issue when using external gear/software

Post by Mark EG » Wed Aug 23, 2006 9:18 pm

Well I've spent all day trying to get a external software step sequencer recording it's MIDI notes into ableton so I could then use and edit those notes to control a hardware synth but all I was getting was some crazy timing delay happpening. I went through so many forums and nobody really had the answer I was looking for, and I finially stumbled across it. So I thought I'd post my answer up here just in case anyone ever has the same problem :)

Basically I'm using a standalone step sequencer, outputing the notes via a loopback cable and then selecting that cable in ableton on a MIDI channel. Then listening back as I tweak the external synth within is hooked up via Midisport, finding something rockin, then recording the mdi notes and tweaking via the ableton editor. Nothing was tight whilst auditioning everything through Ableton - even though the output of the step seq was spot on cause I routed that directly to the external and it was tight as a babies nut sack.

OK, so there I was tweakin the MIDI sync delay time in Prefs and it's doing nothing. 10 hours later and I've realised the problem - each INPUT and OUTPUT Midi device has it's OWN SYNC SETTTING. Now, I don't know about most of you, but unless you've been through the manual with a fine tooth comb, it's very, very easy to think that the MIDI Sync is a global setting. It's NOT.

So basically pulled the delay back on my loopback cable and got it bang on.

I think this may also help some of the other people who say the MIDI timing for external gear is awful, even though they might not be doing what I'm doing with the step sequencer. Sure it is, but as sooon as you realise that each MIDISPORT A,B,C,D (or whatever yours are called) has it's own setting, you set this by click in the device in the input and output, then you can change it's value and the problem is sorted.

Don't you just hate it when you've spend hours trying to find a solution, using other things that MIGHT do the job (and they never do) and returning later just to realise it's something as simple as that.

Heheheh.

Hope this helps someone :)

Affiliation
Posts: 259
Joined: Tue Jul 18, 2006 6:20 am
Location: Montreal
Contact:

Post by Affiliation » Wed Aug 23, 2006 9:51 pm

nice to see someone figure that one out on their own once in awhile. Bravo.

Pasha
Posts: 3337
Joined: Tue Dec 27, 2005 12:45 pm
Location: Lost Island
Contact:

Post by Pasha » Thu Aug 24, 2006 6:38 am

Thanks. I'll keep this in mind.
Mac Studio M1
Live 12 Suite,Zebra ,Valhalla Plugins, MIDI Guitar (2+3),Guitar, Bass, VG99, GP10, JV1010 and some controllers
______________________________________
Music : http://alonetone.com/pasha

taximouse
Posts: 371
Joined: Sat Mar 19, 2005 4:05 am
Location: the woods, north
Contact:

Post by taximouse » Mon Sep 11, 2006 12:35 am

HA! THANK YE! Was having the same problem....you just fixed it.
MacBook Pro 2.93 Ghz, early 2009, 4GB RAM
OS 10.5.8
Live 8.1.4
Motu Ultralite + FCB1010 + SooperLooper + cello


twitter: zoecello
http://www.zoekeating.com

Locked