MIDI Take Lanes

Author
Post
Essentials Only Full Version
brconflict
Max Output Level: -56.5 dBFS
  • Total Posts : 1891
  • Joined: 2012/10/05 21:28:30
  • Status: offline
2017/01/03 14:10:20 (permalink)

MIDI Take Lanes

So, we all pretty much get how Take Lanes work, but what about for MIDI tracks? You can program a MIDI track with notes on the Piano Roll, or using the Step Sequencer. Then play that track over to an audio track to capture the audio.
What we don't have is a way to easily go back an edit the Step Sequencer after the fact, (and the Step Sequencer apparently doesn't save the Swing/Timing settings when you save/recall a loop; an issue I reported in 2015, I believe--still isn't resolved).

Is it possible to (easily) create a MIDI Take Lane with the Step Sequencer, create a new MIDI Take Lane, make changes to the Step Sequencer and play it onto the new Take Lane? In other words, I'd like to have different loops recorded to different/separate Take Lanes on the MIDI track, so I can bounce the takes to separate audio tracks. This way, I don't have to create new MIDI tracks for each part of a Step-Sequence.

Is there an easy way? I can do this with a few tricks as-is, but it doesn't appear Sonar was designed to.

Brian
 
Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
#1

4 Replies Related Threads
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: MIDI Take Lanes 2017/01/03 14:44:47 (permalink)
    I don't use the SS... like at all and much prefer the PRV for MIDI stuff so I don't know how helpful this will be but I do often do much of the Take Lane tracking and editing/comping techniques I do with audio tracks/lanes.
     
    Since I'm not fully digesting/visualizing what exactly you are trying to do (because I don't use the SS... but will give myself a crash course at some point just to "know") I think my recommendation is to program/edit your SS clips then convert them to regular MIDI clips to take full advantage of what take lanes have to offer to MIDI editing. This might require a bit of manual futzery at first to get your lanes setup (not a big deal) but you're a smart lad so I'm sure you could come up with a nice workflow. Sounds like the limitation(s) lie within SS clips... which is really one of the reasons I kind of avoid SS programming (but not the biggest).
     
    Sorry if that is not helpful. I'll keep an eye on the thread to see if you have any followups I can maybe test/help with.
     
    Cheers and HNY, br.
     
    :-)
     
    Edit/PS: If I remember my studies on the SS you can also convert any MIDI clip into (or back into) an SS clip at any time if you want to return to the SS style MIDI editing environment. For whatever that's worth.
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: MIDI Take Lanes 2017/01/03 14:55:29 (permalink)
    Each time you click the Step Sequencer button in a synth's UI, a new SS clip will be started in the MIDI/Instrument track associated with the synth. If you leave lanes closed, you'll automatically get a new lane for each SS instance, but once you show lanes, new SS clips will get stacked on top of the first one in T1; this is a bug, but you can manually add a new lane, and drag the new clip to it.

    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
    brconflict
    Max Output Level: -56.5 dBFS
    • Total Posts : 1891
    • Joined: 2012/10/05 21:28:30
    • Status: offline
    Re: MIDI Take Lanes 2017/01/05 16:14:30 (permalink)
    Thanks! That helps. That's what I'm doing as a workaround. There's some bugs still left untouched in Take Lanes for some time. I'm assuming, to some degree, that these are being checked in the Editor re-work underway. 

    Brian
     
    Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
    #4
    JayCee99
    Max Output Level: -83 dBFS
    • Total Posts : 353
    • Joined: 2011/10/01 12:22:42
    • Location: Katy, TX
    • Status: offline
    Re: MIDI Take Lanes 2017/01/05 16:34:46 (permalink)
    I would suggest completely avoiding take lanes when dealing with MIDI until they make improvements to them.  In my humble opinion, working with MIDI and take lanes makes me want to put my head through my monitor. . . the workflow is buggy as hell.  Throw the step sequencer into the mix, which has plenty of bugs as well, and it's a recipe for disaster.
     
    Instead, create a folder for your MIDI tracks and have them all point to the same synth.  Then you can make the first track and step sequencer clip, and then duplicate the track with events.  Once you bounce to audio, you can just archive or mute the MIDI tracks.

    Sonar Platinum
    Audio Interface: Focusrite 18i8 ASIO Interface 
    Keys: Korg Kronos 88, Alesis VI25
    Windows 8.1 x64 Laptop, 8GB RAM, i7 CPU
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1