|
Title: Ableton Issues Post by: djvicar on June 02, 2007, 02:25:24 PM Yes i do like it but..
1) why is it that it sometimes warps the same track differently? Is it a processor thing? Is it better to import tracks one at a time? 2) Is there a fail safe way of finding the first beat on a track? I spend ages lining up the beats with metronome, but then some tracks still dont match! So enough saying ableton is cheating or not really djing or too easy! Title: Re: Ableton Issues Post by: Dave Richards on June 02, 2007, 02:49:41 PM the first beat should be solved by zooming in closer and listening. The other... learn to warp it manually if ableton screws up. It's good, but it still isn't perfect.
Title: Re: Ableton Issues Post by: DJ Ellipse on June 03, 2007, 09:49:17 PM that warp thing is actually something i have no idea how to use... tried to mess with it with a sample the other day and i could NOT figure out how to get it to line up well...
Title: Re: Ableton Issues Post by: Responsible T on June 04, 2007, 11:42:40 PM solution: don't warp the track. seriously! you know what bpm it is, you can push/pull the tempo by enabling the little button on the right hand side, "d" track delay, and dragging the values ( negative values in milliseconds > 0 > positive values in milliseconds), this is for plug-in delay compensation, but you can also nudge tracks with it for beatmatching believe it or not. Unfortunately you can't map that midi yet, but you can use it like a non-pitch tempo adjust.
worst case scenario - warp the track and take your mouse and push/pull the 1:1 warp marker by dragging it left and right to compensate, a bit like steering a gigantic ship in a storm, but works in a pinch :) there is a tiny little triangle that appears when you do this in the warp view, you can map that to midi with a little cunning. just my two cents which prob aren't worth that :-[ Title: Re: Ableton Issues Post by: deeflash on June 05, 2007, 01:59:39 AM http://vinkalmann.com/index.php?option=com_content&task=view&id=26&Itemid=2
;D Title: Re: Ableton Issues Post by: djvicar on June 05, 2007, 02:04:40 AM solution: don't warp the track. seriously! you know what bpm it is, you can push/pull the tempo by enabling the little button on the right hand side, "d" track delay, and dragging the values ( negative values in milliseconds > 0 > positive values in milliseconds), this is for plug-in delay compensation, but you can also nudge tracks with it for beatmatching believe it or not. Unfortunately you can't map that midi yet, but you can use it like a non-pitch tempo adjust. worst case scenario - warp the track and take your mouse and push/pull the 1:1 warp marker by dragging it left and right to compensate, a bit like steering a gigantic ship in a storm, but works in a pinch :) there is a tiny little triangle that appears when you do this in the warp view, you can map that to midi with a little cunning. just my two cents which prob aren't worth that :-[ I been doing this but thought it was a bit unorthadox. What i mean is i spend time lining up my tracks then whn im in a mix i move the marker which means i then have to move the marker of the next incomming track and so on. Which kind of defeats the point of prepering tracks before hand. Id prefer to know that once ive used mixed a track that it will be ready for future use rather than having to keep shifting the marker! Title: Re: Ableton Issues Post by: Responsible T on June 05, 2007, 02:41:14 AM if i worked at ableton i would implement a timecode-striping metadata markup language that would reside in the header file of the mp3 (when they get around to mp3 encoding at 740 kbps). The warp markers would translate to clock signals that lock to virtual word-clock or midi clock/timecode residing in the host via a universal standard for dj mixing applications like torq, traktor, or cue. it wouldn't be that difficult, an algorithm that could effictively stripe mp3's with sync information based on the asd file associated with the mp3 could be developed by a third party, and adopted if it worked well. any synthmaker users out there that would care to collaborate? :)
film has had embedded sync information on it since it's inception, locking video to audio, why not audio to audio? |