Quantize a midi in a different tempo of the project tempo

Author
communion
Max Output Level: -90 dBFS
  • Total Posts : 3
  • Joined: 2009/08/26 10:11:37
  • Status: offline
2009/08/26 11:07:16 (permalink)

Quantize a midi in a different tempo of the project tempo

Hi first post here.
I've got a problem quantizing a midi project. there are 3 piano tracks, but they are not matching the tempo.
the player recorded them without hearing the click tempo, the project was set to 100. and the song is slower, around 70-80.
so, all of the notes are not correctly placing in the piano roll. are there any ways to correct them so that i can quantize them to match all tracks? thanks!
#1

11 Replies Related Threads

    AudioDef
    Max Output Level: -89 dBFS
    • Total Posts : 96
    • Joined: 2005/06/12 10:43:12
    • Location: Maryland
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 11:42:08 (permalink)
    I started a thread with a similar topic: http://forum.cakewalk.com/tm.aspx?m=1795772

    Hope something in there helps!

    Join Audiodef's ReverbNation street team
    Get free Audiodef CDs
    http://www.audiodef.com
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 12:23:57 (permalink)
    the player recorded them without hearing the click tempo, the project was set to 100. and the song is slower, around 70-80.


    The player recorded without any click, or he recorded with a 100BPM click?

    If he played to a click in the 100BPM project, you should be able to just import the MIDI into the project with the varying tempo, and it will will follow the new tempo map. If he didn't play to a click, the first thing I would do is use Audiosnap to align the piano parts with the grid in that project, and then bring it in to the varying tempo project.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #3
    communion
    Max Output Level: -90 dBFS
    • Total Posts : 3
    • Joined: 2009/08/26 10:11:37
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 13:22:28 (permalink)
    brundlefly



    The player recorded without any click, or he recorded with a 100BPM click?

    If he played to a click in the 100BPM project, you should be able to just import the MIDI into the project with the varying tempo, and it will will follow the new tempo map. If he didn't play to a click, the first thing I would do is use Audiosnap to align the piano parts with the grid in that project, and then bring it in to the varying tempo project.

    he recorded without click in a 100bpm project.
    i tried some methods, they are not working 


    #4
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 14:06:08 (permalink)

    he recorded without click in a 100bpm project.


    I thought that might be the case, so I took the "precaution" of writing up some steps for you to get what you want with Audiosnap.   This assumes that the piece you're importing to is already roughly aligned to the Time Ruler (though not necessarily quantized). If not, you'll have to follow this procedure for both projects before combining them. I'm also assuming you know your way around SONAR with respect to basic operations, opening different views, using Snap to Grid, etc. If not, you might have some trouble following all of this. Hang on to your hat; it's not as bad as it looks:

    Edit:  It would probably be a good idea to try this on a copy of the piano project. 

    - In the 100BPM project, slide the piano clip so that the first note is on the correct starting measure and beat to line up with the new project.

    - Enable PRV mode in the Track view, and Shift-A to open the Audiosnap palette.

    - If the clip does not start at 1:01:000, this step is critical: Click on that first note in the PRV, and hit F7 to set the Now time at the beginning of that event. Then click the Set Measure Beat At Now button in the Audiosnap Palette to "pin" down that starting point. 

    - Play the piece through without the metronome running, and count measures and beats to the last downbeat.

    - Click on the downbeat note, Set the Now time there with F7, and Set Measure/Beat at the value you counted out.

    - Enable the metronome for playback, and listen though the piece.

    - If necessary, set additional events to beats within the part if anything is way off. If it's close, leave it for now; you can do a percentage quantize later on if necessary. You just need the part to be aligned closely enough that quantize won't move things in the wrong direction.

    - Now, here comes the key step. Using Set Measure/Beat At Now has entered a bunch of tempo changes in the tempo map, effectively aligning the Time Ruler with the MIDI part. You want to keep the part aligned with the Time Ruler, but eliminate all the tempo changes it took to get that alignment. Here's how you do that:

    - Right-click the clip, and choose properties. Set the timebase to Absolute, and lock both position and data. Now open the Tempo View, and delete all the tempo entries except the first (which you can't remove, anyway). You can change that initial tempo to match the initial tempo of the new project now if you like, but it's not necessary.

    - That's it; the hard part's over. Unlock the clip, and change its timebase back to M:B:T.

    - If you want, now is the time to quantize the part.

    - Now the clip is ready to Copy-Paste, Drag-and-Drop or Export-Import into the other project. All you have to do is get the starting event lined up, and the rest of the clip will follow the tempo map in the new project.


    Note 1: The only downside of the above procedure is that the beats that you lock to the Time Ruler with Set Measure Beat at Now will effectively be quantized to 100%. So if you want to preserve as much of the "feel" in the timing of the part as possible, it is best to lock as few beats as you can get away with, and use percentage Quantize to tighten things up later if necessary.


    Note 2: The same procedure would apply to aligning freely played audio with the time ruler. But instead of locking the clip to Absolute time (which audio already is), you would enable Autostretch on the clip before deleting all the tempo changes and changing the initial tempo, then bounce the clip down with an offline stretching algorithm.









    post edited by brundlefly - 2009/08/26 14:11:07

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #5
    communion
    Max Output Level: -90 dBFS
    • Total Posts : 3
    • Joined: 2009/08/26 10:11:37
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 15:46:01 (permalink)
    brundlefly



    wow, thanks so much brundlefly!!!
    it's just working great, i didn't know audiosnap is that useful.
    you are sonar pro!
    #6
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 16:38:01 (permalink)
    wow, thanks so much brundlefly!!!


    You're welcome.

    Let me know if you get stuck. Weird, unintuitive things can happen if you overlook one detail, and I might well have left something out that's needed for your particular situation. If it comes to it, you can send me the MIDI file, and I'll see what I can do with it. You're helping me keep my Audiosnap chops sharp. 

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #7
    ericyeoman
    Max Output Level: -71 dBFS
    • Total Posts : 976
    • Joined: 2003/11/07 07:54:18
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 16:53:18 (permalink)
    EDIT: Hang on, ignore the below, think I'm getting somewhere....
     
    I am really not getting this at all...
     
     
    SECOND EDIT:
    Got it!
     
    Thanks brundle, great instructions.
    post edited by ericyeoman - 2009/08/26 17:14:41

    CuBase, Ableton, Steinberg UR-22 MKII, i7-4790K 4.00 Ghz, 32Gb Corsair Vengeance Pro RAM, Windows 10. 
    #8
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 17:35:14 (permalink)

    Do you know of any videos showing this?

    No I don't. I suppose I could make one... I'll see what I can do, but it probably won't be too soon. The way you're doing it is exactly how I worked it out, though, so you should get there, eventually.


    post edited by brundlefly - 2009/08/26 17:37:26

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #9
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 17:53:37 (permalink)
    Got it!   Thanks brundle, great instructions.


    Groovy! I was going to add the following to my previous post, but the new froum doesn't like text pasted in from other apps. 

    I don't want to muddy the waters, but this might help you get the big picture:

    One of the reasons that Audiosnap can seem so unintuitive is that Sonar treats the M:B:T ruler as the absolute measure of "time" relative to screen position. So when you change tempo, it is the audio clip length that changes in the display, even though mathematically, it is the ruler length that is changing to fit the audio (i.e. the measures/beats are going by faster or slower relative to absolute clock time).

    MIDI on the other hand is referenced to the M:B:T grid, so it won't move relative to the grid unless its timebase is changed to Absolute and its position and data are locked as described earlier. Then it will behave like audio.

    Having the M:B:T grid be the fixed reference is somewhat counter-intuitive for anyone who is used to the X axis representing a fixed time scale in other applications. Time is the mutable measure in SONAR's display. It might be more intuitive if the M:B:T ruler compressed with an increase in tempo, and the audio clip length only changed if Autostretch were enabled.

    Incidentally, this behavior does not change when you change the time ruler format to an absolute measure like SMPTE or Milliseconds. If you do that, and change the tempo, the time ruler will change scale. 


    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #10
    ericyeoman
    Max Output Level: -71 dBFS
    • Total Posts : 976
    • Joined: 2003/11/07 07:54:18
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 18:28:23 (permalink)
    Thankyou!
     
    That really has cleared up a lot of confusion on my part.
     
    I'd read the help files, watched videos, but none went into
    the depth you have here. And I could never get it to work :-(
     
    I've been trying to figure out how to do this since SP3 (using Fit to improvisation), so am
    honestly really chuffed.
     
    Again, thanks!
     
    Eric.
     
    PS to paste things in from other apps, I copy to notepad, then paste into the message,
    wait for ages with crossed fingers, and sometimes it works. Sometimes it takes a couple of goes though.
     
     

    CuBase, Ableton, Steinberg UR-22 MKII, i7-4790K 4.00 Ghz, 32Gb Corsair Vengeance Pro RAM, Windows 10. 
    #11
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quantize a midi in a different tempo of the project tempo 2009/08/26 19:23:16 (permalink)
    I've been trying to figure out how to do this since SP3 (using Fit to improvisation), so am honestly really chuffed.   Again, thanks!


    You're welome. Glad you found it helpful. Audiosnap is a great set of tools for working with MIDI as well as Audio. I play pretty well to a click after all these years, but for solo piano stuff, especially, I think I get a better, more natural sounding result if I play without it. But then I still like to be able to lock it to the grid with tempo changes for editing and syncing up other parts or printing notation if I need to later on. So I spent some time working out a consistent process for doing this, and there you have it! It's also really useful for importing and transcribing music that has a really variable tempo.



    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #12
    Jump to:
    © 2025 APG vNext Commercial Version 5.1