Thanks to both you guys in helping me! I was hoping for something new.

Tempo Maping in ACW has never worked for me, based on how I want it to work. I have been surprized that few if any others have pointed the weaknesses out. Which is why I only bring this up every other year or two.

Quote
Here is what has recently been reported regardign how the ACW works, "...It looks like you have to manually tempo map the entire song by inserting bar lines where all the downbeats are. When you have auto on it just merely mimics your last bar BPM which is interesting but not a real tempo map."


I want BIAB to to exchange tempos with other music application by creating a feature to import or export, a true tempo map which aligns a project's timeline (grid) to the natural fluctuations of an unclicked audio or MIDI recording. This lets us retain a human groove while allowing MIDI, loops, and effects to quantize perfectly (synchronized) to the track's tempo in the event that a fixed tempo is not preferred. Primarily load a chord sheet from a midi file which includes a true tempo map, and then create RTs in synch with that map!

Yes, this is generally done via importing a MIDI. The Standard MIDI File (SMF) can be formatted to share a tempo map across different music application as a .mid file. The MIDI data is typically placed on a dedicated, silent Track 1.
It utilizes two specific types of meta-events: Set Tempo (stored in microseconds per quarter note) and Time Signature.Exporting: You share this by exporting or importing a project’s tempo track using "Export/Import MIDI" or "Export/import Tempo Map" functions.

Why does BIAB not do this?

Retired to Make Music - No Plan B
My SoundCloud
View Current Projects