Timing Issues with Step Sequencer

Author
meh
Max Output Level: -82 dBFS
  • Total Posts : 431
  • Joined: 2005/06/11 13:01:57
  • Location: Tempe, Az
  • Status: offline
2012/11/19 14:32:23 (permalink)

Timing Issues with Step Sequencer

X2 has been running great here since installing a couple of months ago but...
 
This morning I noticed on a new project that the step sequence is not keeping accurate time.
 
Can't think of anything I've changer....
 
Any Thoughts
tia
meh

SONAR Version 2017.09
HP Z-420 Workstation
Intel Xeon W3680 @3.50ghz 
32g memory
2tb disk space 
Win2008 Server R2 Standard 64-bit
TASCAM US-1641 interface
#1

5 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:Timing Issues with Step Sequencer 2012/11/19 15:11:53 (permalink)
    What synth is it driving, and what is the exact nature of the timing errors? It's unusual to get randomness, but a fixed offset (early/late) could have to do with Plug-ins that add latency and need PDC. What if you convert the SS clip to a regular MIDI clip?

    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
    meh
    Max Output Level: -82 dBFS
    • Total Posts : 431
    • Joined: 2005/06/11 13:01:57
    • Location: Tempe, Az
    • Status: offline
    Re:Timing Issues with Step Sequencer 2012/11/19 16:17:46 (permalink)
    Standard stuff....SD3....just a straight 1 measure bass 1&3 and Snare 2&4.
    it's the second time around on the snare it that jumps ahead and now for as long as you want to loop it it fights itself.
     
    meh

    SONAR Version 2017.09
    HP Z-420 Workstation
    Intel Xeon W3680 @3.50ghz 
    32g memory
    2tb disk space 
    Win2008 Server R2 Standard 64-bit
    TASCAM US-1641 interface
    #3
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Timing Issues with Step Sequencer 2012/11/19 16:48:51 (permalink)
    If there are any MIDI FX in the project, anywhere, try removing them (disabling is not enough). There is a bug with MIDI FX that causes some or all of the next measure after the loop region to be played back on all passes after the first. Depending on what's in that measure it can screw up the timing.

    EDIT: This bug is a pet peeve of mine because I need MIDI FX in a lot of projects while tracking to block CC123 from my old Roland RD-300s. Fortunately, I just got an RD-700NX, and it doesn't send CC123. Will be retiring the RD-300s as soon as possible!



    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
    #4
    tlw
    Max Output Level: -49.5 dBFS
    • Total Posts : 2567
    • Joined: 2008/10/11 22:06:32
    • Location: West Midlands, UK
    • Status: offline
    Re:Timing Issues with Step Sequencer 2012/11/19 17:59:55 (permalink)
    What's your MIDI buffer set to in preferences? If it's less than 500, try 500. 

    While this may not fix your particular problem, it fixes an awful lot of step sequencer timing/missing notes oddities so is worth a try if applicable.

    Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board,
    ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre.
    Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
    #5
    meh
    Max Output Level: -82 dBFS
    • Total Posts : 431
    • Joined: 2005/06/11 13:01:57
    • Location: Tempe, Az
    • Status: offline
    Re:Timing Issues with Step Sequencer 2012/11/20 09:12:11 (permalink)
    This was an upgradded X1 box so in a fit of desperation I started up X1 and it worked fine.  After doing so I opened up X2 and now it is fine????????????????????????
     
    thanks to all
    meh

    SONAR Version 2017.09
    HP Z-420 Workstation
    Intel Xeon W3680 @3.50ghz 
    32g memory
    2tb disk space 
    Win2008 Server R2 Standard 64-bit
    TASCAM US-1641 interface
    #6
    Jump to:
    © 2025 APG vNext Commercial Version 5.1