Capturing MIDI and Weird Quantization Experience

Author
doncolga
Max Output Level: -60 dBFS
  • Total Posts : 1519
  • Joined: 2006/01/03 17:15:48
  • Location: Statesboro, GA USA
  • Status: offline
2015/09/11 10:19:09 (permalink)

Capturing MIDI and Weird Quantization Experience

Hi all,
I'm noticing when I record MIDI, it's not capturing it the same way I play.  The initial playback is rushed noticeably more than how I played it.  It's much more evident when I'm doing 16th notes and it seems to be worse when I have a count in on the metronome.  This in turn is messing up quanitization, which has always been tricky for me in Sonar.  I'll play in my part, then quanitize and it rarely places things where they should be.  I'm not noticing this on other platforms or DAWS that I use so I'm wondering if there any settings in Sonar that I could adjust?  This has happened on my RME Multiface II MIDI on PCIe and a Behringer XR18 MIDI over USB 2 and with two different controllers.  Strength 100, swing 50, window 100, offset 0, so it should just line it right up.  I don't thing I'm actually playing that much out of time.
 
Thanks!
 
Donny

HP Z220 Workstation I7 3770, 8 GB RAM, Windows 10, Sonar Platinum, RME Multiface II via PCIe, JBL 4326 w/sub, AvanTone MixCubes
#1

3 Replies Related Threads

    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Capturing MIDI and Weird Quantization Experience 2015/09/12 12:20:13 (permalink)
    First make sure you don't have a non-zero Timing Offset entered under Synchronization in Preferences > Audio Sync and Caching.
     
    Are you recording while performing with a soft synth, a direct-monitored hardware synth or input-monitored hardware synth? And what's your audio buffer size and round-trip latency? If using WDM driver mode, try ASIO, or vice versa.
     
    If you have a keyboard synth, you can check your timing by recording simultaneous audio and MIDI from the synth with Local Control enabled, and checking alignment of the MIDI to the audio transients. If MIDI is still being laid down down consistently early, you may need to use a Timing Offset to correct that, but it shouldn't be necessary and can cause other problems if it's more than a few milliseconds (which wouldn't affect quantizing).
     
    This "early MIDI" issue seems to affect some specific systems/interfaces, but it would be unusual that you've encountered it with two different MIDI/Audio interfaces using two different bus types.

    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
    #2
    doncolga
    Max Output Level: -60 dBFS
    • Total Posts : 1519
    • Joined: 2006/01/03 17:15:48
    • Location: Statesboro, GA USA
    • Status: offline
    Re: Capturing MIDI and Weird Quantization Experience 2015/09/12 23:53:29 (permalink)
    Thanks for the reply. Will check here in a minute. It's definitely frustrating because so much of what I put down won't quantize without a hassle. I always thought it was just me and and didn't think about it much until I was on another rig and didn't have the issue at all.
    post edited by doncolga - 2015/09/13 00:03:08

    HP Z220 Workstation I7 3770, 8 GB RAM, Windows 10, Sonar Platinum, RME Multiface II via PCIe, JBL 4326 w/sub, AvanTone MixCubes
    #3
    doncolga
    Max Output Level: -60 dBFS
    • Total Posts : 1519
    • Joined: 2006/01/03 17:15:48
    • Location: Statesboro, GA USA
    • Status: offline
    Re: Capturing MIDI and Weird Quantization Experience 2015/09/13 09:44:36 (permalink)
    Everything looks ok and midi and audio do indeed line up off my synth. I am noticing However that quantization is much better when auto quantize is on. Don't know why that's the case, but sure seems better that way.

    HP Z220 Workstation I7 3770, 8 GB RAM, Windows 10, Sonar Platinum, RME Multiface II via PCIe, JBL 4326 w/sub, AvanTone MixCubes
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1