MIDI dragged from drones timing is off

7 posts / 0 new
Last post
Ruchir's picture
Ruchir
Offline
Last seen 2 weeks 13 hours ago

MIDI dragged from drones timing is off

Hi. Using 64bit drones in ableton live. When dragging the midi from the drone green button to the tracks in live, the notes are slightly out of sync (compressed) with the beats and measures, and therefore drifts over time. Also, the tempo template doesn't translate across.

Yet, when dragging the container from synfire into live directly, timing, sync and tempo changes all works (albeit everything starting one bar late). 

andre's picture
andre
Offline
Last seen 2 days 16 hours ago

This could be due to a tempo change MIDI messages. Tempo changes don't work well with DAW synch, unless you drag the entire span of the song as a whole. I'd recommend prototyping with constant tempo and only applying tempo changes once your song is ready for production in the DAW.

Ruchir's picture
Ruchir
Offline
Last seen 2 weeks 13 hours ago

Thanks Andre

we had a look at this during the Skype meetup. 

The tempo changes translate perfectly when dragging the top container from synfire, holding the space key, then dropping into live. It just doesn't work when dragging from the drone. So what you say makes sense as the individual drones do not cover the whole song.

The reason I'd prefer to drag from the drone, is that it's then easier to assign the newly imported midi tracks to the channels of that drone. Dragging from synfire brings too many tracks in at once and all mixed up, rather than sorted by the plugin they are targeting. Can the latter have a function for sorting by plugin/instrument when being dragged?

andre's picture
andre
Offline
Last seen 2 days 16 hours ago

How does it work when you drag a single instrument from the root container only?

Ruchir's picture
Ruchir
Offline
Last seen 2 weeks 13 hours ago

Dragging single instrument from root container works fine.

Also dragging another (whole) container works fine.

As long as it's from Synfire...

andre's picture
andre
Offline
Last seen 2 days 16 hours ago

I don't remember right now if the tempo map is included with the drag from the Drone, but that's probably the culprit. The issue is, tempo events run on a 'global' MIDI track, so if tempo changes are supposed to be included, at least 2 tracks need to be contained in the dragged file. Every DAW responds differently to a dropped file. Some ignore tempo changes altogether, others would create a new track for them. That's why I recomend sparing tempo changes out until a song is ready to live entirely in the DAW for final production.

blacksun's picture
blacksun
Offline
Last seen 1 day 48 min ago

Ableton Live does prompt to say the material dragged from the drone or synfire contains a temp map and ask if it should be used, however it doesnt seem to be correct if the midi comes from the drone.

Log in or register to post comments

Scholarly Lite is a free theme, contributed to the Drupal Community by More than Themes.