Midi Monitoring Idea

Author
jimkleban
Max Output Level: -64 dBFS
  • Total Posts : 1319
  • Joined: 2008/11/09 09:42:45
  • Status: offline
2011/07/31 20:52:36 (permalink)

Midi Monitoring Idea

So, I can't stand the fact that if I try and play a MIDI controller, triggering a VSTi in a project that is already mixed, that the LATENCY is unbearable without turning off all the plugins in every bin and which point the MIX is unbearable.

So, I have an idea that I would like to run by you folks (and perhaps someone has already tried this). 

What if I got a MIDI patchbay and took the MIDI output from my controller and send one MIDI send to the DAW to record the MIDI with the PORT muted so it wouldn't trigger anything on the recording, project DAW but just recorded the MIDI data in the track?

At this point, I wouldn't be able to hear what I was playing which for me wouldn't work at all. However, I think take another MIDI out from the MIDI patchbay and send it to another computer which had the same VSTi's on it and I used this other computer to trigger the MIDI input to an instrument which would have very LOW latency.

In order to hear both PC's audio, I then could send a stereo out from each PC to a mixer desk and hear both the mixed song and my performance in real time.

The more I thought about this the more I realized I wouldn't need a very powerful PC to be the VSTi monitoring machine since all it would be doing is triggering one VST (stand alone) and sending its audio out to the mixer.

So, I have a AXIOM 61 (old one) controller keyboard and was wondering if there exists a MIDI patchbay that can handle MIDI over one USB in and two USB outs?

Thanks, and please let me know you thoughts,
Jim

PS - been thinking about this for quite awhile now but haven't yet tried it hoping that somebody on the forum has already solved this problem.





The Lamb Laid Down on MIDI
www.lldom.com
 
Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
Apollo Duo (via TB)
UAD Quad
UAD Duo
WIN 8.1 x64 with 32 GB Ram
4 SSD for programs and sample libraries
Splat (latest version)
#1

27 Replies Related Threads

    lorneyb2
    Max Output Level: -58.5 dBFS
    • Total Posts : 1667
    • Joined: 2007/04/26 04:02:10
    • Location: Saskatchewan, Canada
    • Status: offline
    Re:Midi Monitoring Idea 2011/07/31 22:55:10 (permalink)
    Just to make sure you are aware of being able to right click in the FX bin and select "Bybass all bins of this Type" which will turn off/on all of your plugins at once.(you have to do the same for the Bus section as well).
     You won't be able to hear the mix but your latency issue could be resolved and be much less convoluted than trying to co-ordinate two comps. 

    Another option would be to use the "Bounce to Tracks" option under the Tracks menu in TV and select Entire Mix for the bounce down.  Then you can use the "Bypass bins" option to free up resources and still get to hear the entire mix.  If additional resources are needed you could archive all the other tracks so you ultimately end up with only 1 audio track plus the track you are working on recording.  The bounce down may take a while if you still have a lot of synths open but will likely be worthwhile for the results in reduced resources used and latency reduction.

    Sonar Platinum 64bit, Win 8.1 Pro 64bit,  Quad Core 3.2GHz,  16G ram, Edirol FA 101, Nvidia
    EW (Platinum Orchestra, Hollywood Strings, Pianos, Gypsy, Fab 4, Ministry of Rock,Choirs, etc)
                     
    #2
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/07/31 23:04:42 (permalink)
    Thanks Lorney...

    I am aware of both options. Turning off the plugins makes my mixes fall apart as well as the groove.

    It is really inconvenient for me to BOUNCE all the tracks.. mixing is such an interactive thing.

    Jim


    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #3
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 11:24:40 (permalink)
    PDC Override for input monitored tracks will solve the audio latency problem, but SONAR has a bug that recorded MIDI is not compensated for PDC and will lay down late in the timeline. Your workaround won't solve that problem either.

    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
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 11:30:25 (permalink)
    Brundlefly....

    My issue is being able to play a midi part in time and "in the mix" and hear what I am playing.  Even if SONAR lays it down late, I can simply slide it to compensate later.

    I literally can't record MIDI parts while songs are mixed and hearing what I am playing in real time since the MIDI is triggering a VSTi in the project.

    And thanks for the heads up, I will look for the MIDI track offset you mentioned and compensate.

    Jim


    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #5
    daveny5
    Max Output Level: 0 dBFS
    • Total Posts : 16934
    • Joined: 2003/11/06 09:54:36
    • Location: North Carolina
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 14:09:47 (permalink)
    What soundcard do you have? What's your computer's specs? I record MIDI tracks all the time and don't have any problem with latency and my Delta 44 is probably 10 years old or more. I do use an external mixer. (Mackie). 

    Dave
    Computer: Intel i7, ASROCK H170M, 16GB/5TB+, Windows 10 Pro 64-bit, Sonar Platinum, TASCAM US-16x08, Cakewalk UM-3G MIDI I/F
    Instruments: SL-880 Keyboard controller, Korg 05R/W, Korg N1R, KORG Wavestation EX
    Axes: Fender Stratocaster, Line6 Variax 300, Ovation Acoustic, Takamine Nylon Acoustic, Behringer GX212 amp, Shure SM-58 mic, Rode NT1 condenser mic.
    Outboard: Mackie 1402-VLZ mixer, TC Helicon VoiceLive 2, Digitech Vocalist WS EX, PODXTLive, various stompboxes and stuff. 
    Controllers: Korg nanoKONTROL, Wacom Bamboo Touchpad
    #6
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 14:39:34 (permalink)
    daveny5What soundcard do you have? What's your computer's specs? I record MIDI tracks all the time and don't have any problem with latency and my Delta 44 is probably 10 years old or more. I do use an external mixer. (Mackie). 



    I'm pretty sure he's talking about PDC latency. As mentioned, PDC Override will take care of the input monitoring latency, but he will have to manually fix the MIDI position after the fact.


    If you don't track with PDC plugs, and/or are direct-monitoring through an eternal mixer, you might never have encountered either of these issues.

    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
    JoseC.
    Max Output Level: -81 dBFS
    • Total Posts : 471
    • Joined: 2003/11/10 14:46:11
    • Location: León, Spain
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 15:28:12 (permalink)
    I use a MOTU MIdi Express XT that would make it very easy to arrange that setup with it. You would not really need to have two USB, as long as the second PC has MIDI connections it would behave as a hardware synth. The MOTU is configurable as a patchbay, so you can program any routings you would need, and it takes care of distributing MIDI clock (it also generates SMPTE and MTC sync if you need that).  
    #8
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 15:39:50 (permalink)
    I've done a similar kind of thing using Savihost using WDM to trigger the VSTi for the Audio (so as not to clash with the ASIO driver in Sonar) then routing the midi out through that via a virtual midi cable into Sonar.  There's a small (but acceptable) latency for the audio coming from the Savihosted synth but the miid latency into Sonar is virtually nil.

    Not only that it wont cost a penny to set it up to try.

    See this thread for the downloads you'll need to do it.

    http://forum.cakewalk.com/tm.aspx?m=2350382

    That kind of setup is good to go on 64 bit now too and it is midi routing bliss.  Hey you can even run VST3's already.


    post edited by Jonbouy - 2011/08/01 15:42:15

    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #9
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 15:52:57 (permalink)
    I've done a similar kind of thing using Savihost using WDM to trigger the VSTi for the Audio (so as not to clash with the ASIO driver in Sonar) then routing the midi out through that via a virtual midi cable into Sonar.  There's a small (but acceptable) latency for the audio coming from the Savihosted synth but the miid latency into Sonar is virtually nil.



    That's still not going to address the late MIDI recording issue, because the root of the problem with PDC is that you're syncing your playing to a delayed audio signal, and the MIDI recording position is not compensated for that.

    And all the hoop-jumping is not necessary just to eliminate the audio monitoring latency. PDC Override will take care of that.



    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
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 16:03:34 (permalink)
    brundlefly



    I've done a similar kind of thing using Savihost using WDM to trigger the VSTi for the Audio (so as not to clash with the ASIO driver in Sonar) then routing the midi out through that via a virtual midi cable into Sonar.  There's a small (but acceptable) latency for the audio coming from the Savihosted synth but the miid latency into Sonar is virtually nil.



    That's still not going to address the late MIDI recording issue, because the root of the problem with PDC is that you're syncing your playing to a delayed audio signal, and the MIDI recording position is not compensated for that.

    And all the hoop-jumping is not necessary just to eliminate the audio monitoring latency. PDC Override will take care of that.


    Yes I understand all that but he's looking for a way of working. If PDC override takes care of it then great, if not it's really not that much of a hoop jump to dog-leg the midi-routing so you can monitor what you are doing.

    Not only that it isn't just a possible workaround here it provides a whole plethora of creative possibilites.  Tom (B-Rock) knew this.  I miss him...
    post edited by Jonbouy - 2011/08/01 16:40:45

    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #11
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 17:00:21 (permalink)
    Not only that it isn't just a possible workaround here it provides a whole plethora of creative possibilites. 



    Don't get me wrong, I'm all for creative workarounds when they're needed. I just didn't want the OP to lose sight of the forest for the tress, given there's a one-click solution right in the application.

    And if you throw in setting up the independent hosting machine/app, it's a little more involved than just to "dog-leg the midi-routing".



    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
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 17:45:59 (permalink)
    OK... I tried it using my Axion 61... I used the USB port to go to my MAC AIR... I have Kontakt installed on the Macbook Air and its audio output going to my desk.

    I think used the MIDI OUT port from Axiom to go to my USB Midisport (running x64 WIN 7) on my DAW.  I was thinking that the Axiom wouldn't output thru both the USB and MIDI out port at the same time and that this wouldn't work because I could not find a USB ONLY midi patch bay to do it the way i thought I would have to.

    But alas, it WORKS like a CHARM... my DAW plays back the project in all of its mixed glory. I can add a part and here the performance in real time and here is the kicker.  The MIDI is almost SPOT ON to the timing of the project in Sonar.

    So, it a nutshell, it WORKS PERFECTLY and I finally can play some MIDI parts in real time.  YAHOOOOOO

    Jim


    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #13
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 18:18:11 (permalink)
     The MIDI is almost SPOT ON to the timing of the project in Sonar.



    Did you actually test in a project that has added latency due to plug-ins needing PDC? I don't see how any setup could overcome the bug I described.





    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
    #14
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 18:26:41 (permalink)

    And if you throw in setting up the independent hosting machine/app, it's a little more involved than just to "dog-leg the midi-routing".


    Seriously all that is a non-issue now, one double click the VMC setup is on your system you can create midi ports on the fly after that without even rebooting.  So yes it is just a dog-leg. Especially with a native standalone you don't even need Savihost.  I'd suggest getting current with Tobias Erichson's midi stuff he has a cool midi over lan (or any network for that matter) driver too.

    Glad you got it working anyway Jim did you over-ride PDC too?


    post edited by Jonbouy - 2011/08/01 18:38:53

    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #15
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 20:37:38 (permalink)
    Well,

    Didn't need to override anything... it just WORKS (almost perfectly).  It is a pleasure hearing my MIDI triggered instruments in real time along with the pre-mixed tracks.. I think I even felt a groove going (been a long time for that in MIDI).

    Jim


    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #16
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 21:14:39 (permalink)
    jkleban


    Well,

    Didn't need to override anything... it just WORKS (almost perfectly).  It is a pleasure hearing my MIDI triggered instruments in real time along with the pre-mixed tracks.. I think I even felt a groove going (been a long time for that in MIDI).

    Jim


    Cool,

    Like I say I had a similar scenario with a project once and  re-routing the midi as a seperate synth for monitoring did the trick for me too, albeit on the same machine.  I've only had the one project where that has happened to the point where I needed to take such action though.

    I normally have PDC override checked as it makes the needed nudge to get the midi to line up (if needed) easier to quantify more accurately.



    post edited by Jonbouy - 2011/08/01 21:18:23

    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #17
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 21:28:50 (permalink)
    Jonbouy,

    My problem is every project for me is like this.  I only use Virtual Instruments triggered by MIDI, I have tons of plug-ins and my projects are pretty much huge.  Add to the problem, UAD2 latency and you can see what a mess this is.

    Just being able to monitor my MIDI performance in real time, playing the correct instrument is a godsend.  Been years since I was able to do this.

    But it is worth it, my MIDI projects DO NOT sound like MIDI at all (which was my goal).

    Jim


    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #18
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/01 21:31:59 (permalink)
    jkleban


    Jonbouy,

    My problem is every project for me is like this.  I only use Virtual Instruments triggered by MIDI, I have tons of plug-ins and my projects are pretty much huge.  Add to the problem, UAD2 latency and you can see what a mess this is.

    Just being able to monitor my MIDI performance in real time, playing the correct instrument is a godsend.  Been years since I was able to do this.

    But it is worth it, my MIDI projects DO NOT sound like MIDI at all (which was my goal).

    Jim


    Sometimes with Sonar when good reasoning fails, hitting it with a stick is worth trying...

    If it works, it works for me.

    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #19
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 06:32:15 (permalink)
    brundlefly


    If you don't track with PDC plugs, and/or are direct-monitoring through an eternal mixer, you might never have encountered either of these issues.

    This is the bit I still don't get, if as you say one is direct-monitoring and these issues do not manifest, why then does it not follow that the next best thing, virtually direct monitoring a synth on a different signal path to Sonar, would also stop these issues manifesting themselves?

    I'm just curious here because you are usually right on the money.


    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #20
    lfm
    Max Output Level: -53 dBFS
    • Total Posts : 2216
    • Joined: 2005/01/24 05:35:33
    • Location: Sweden
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 07:24:57 (permalink)
    jkleban


    So, I can't stand the fact that if I try and play a MIDI controller, triggering a VSTi in a project that is already mixed, that the LATENCY is unbearable without turning off all the plugins in every bin and which point the MIX is unbearable.

    So, I have an idea that I would like to run by you folks (and perhaps someone has already tried this). 

    What if I got a MIDI patchbay and took the MIDI output from my controller and send one MIDI send to the DAW to record the MIDI with the PORT muted so it wouldn't trigger anything on the recording, project DAW but just recorded the MIDI data in the track?

    At this point, I wouldn't be able to hear what I was playing which for me wouldn't work at all. However, I think take another MIDI out from the MIDI patchbay and send it to another computer which had the same VSTi's on it and I used this other computer to trigger the MIDI input to an instrument which would have very LOW latency.

    In order to hear both PC's audio, I then could send a stereo out from each PC to a mixer desk and hear both the mixed song and my performance in real time.

    The more I thought about this the more I realized I wouldn't need a very powerful PC to be the VSTi monitoring machine since all it would be doing is triggering one VST (stand alone) and sending its audio out to the mixer.

    So, I have a AXIOM 61 (old one) controller keyboard and was wondering if there exists a MIDI patchbay that can handle MIDI over one USB in and two USB outs?

    Thanks, and please let me know you thoughts,
    Jim

    PS - been thinking about this for quite awhile now but haven't yet tried it hoping that somebody on the forum has already solved this problem.


    A couple of things I find strange:

    #1. Something is wrong with your setup(computer+soundcard) if you get noticable latency
    All PDC used is used to line up that everything sounds in it's proper place.

    then you play to whatever you hear in realtime.

    This is recorded and place on the midi clip.

    As we discovered in some thread on Sonar 8 there is a bug in Sonar that is not displacing midi tracks according to PDC used, but a single change of ticks delay(minus or plus) on midi track would serve as a workaround.

    (this is sent to Cake bugtracker)

    #2. Why do you need to record with a full mix?
    Sound strange to me.
    A minimum of tracks for timing and music should really be all you need to record another track.

    If really needing more then make a track bounce or freeze these tracks. Then any PDC delay is removed.

    that's my view of things anyway...

    #21
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 07:43:15 (permalink)
    If I record using AUDIO input (an audio track) all is fine with monitoring.  My system is powerful enough that the audio latency is bearable.

    The problem comes with MIDI triggering a VSTi in real time.  The DELAY is unbearable. I do think that the UAD2 plugins I am using are adding to this delay (as has been documented) making matters worse.

    Bottom line is that using 2 PCs (mixed on the same desk), triggered by the same MIDI controller has done the trick for me.

    The second reason I want to record with an ALMOST full mix is I am using all VIRTUAL instruments (mostly recorded DI'ed) and all of the virtual amps and colorful EQ is what makes them sound like real instruments.

    Bouncing would have been another option but I would lose the interactive ability to adjust amp settings and other effects and processing since what I am doing is very precise.  The creative flow would have been buzzed killed to try and unfreeze and refreeze tracks.  Sometimes, I just want to replace 5 notes of a MIDI track but I want to play them and not edit (program) them to get the right feel.

    We all work differently, this workflow works for me and probably not other folks and this MIDI trigger delay was the only show stopper for me.

    Now, there could be something wrong in my setup but as an example, the project I am currently working on has 12 instances of Kontakt and a few other custom instruments (mellotrons, acoustic piano) and all the bass parts, guitars and electronic keyboards (RMI and ARP PRO)  have virtual amps. 

    One of the reasons that there are so many instances of Kontakt is that the guitar and bass parts are triggered with a MIDI GUITAR controller and the custom samples are each string, sampled on each fret so that the guitar and bass parts trigger the correct note depending on what string and fret were used on the controller.  Each string has its own Kontakt program to pull this off.

    It all starts to add up (the latency) with this much going on in real time and like I said, my DAW is fine if I record audio tracks, it is just when I try to monitor new MIDI tracks where this delay rears its ugly head.

    Jim

    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #22
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 10:48:23 (permalink)
    Jonbouy


    brundlefly


    If you don't track with PDC plugs, and/or are direct-monitoring through an eternal mixer, you might never have encountered either of these issues.

    This is the bit I still don't get, if as you say one is direct-monitoring and these issues do not manifest, why then does it not follow that the next best thing, virtually direct monitoring a synth on a different signal path to Sonar, would also stop these issues manifesting themselves?

    I'm just curious here because you are usually right on the money.
    The "and/or" construction I used might not have been the best choice here. To summarize, we have two issues:



    1. Plug-ins that require PDC add latency to all tracks, including live input monitored signals and soft-synth output.
    2. MIDI recorded to a PDC-delayed playback reference is not compensated, and will lay down late in the timeline.


    Now, obviously, if you never try to track with plugs that need PDC, you'll never encounter either of the above issues (at least not because of PDC).


    And if you use either the PDC Override for input monitored tracks (and the plug is not on the monitored track), or you use one of the "parallel-host" solutions discussed above, you can eliminate problem 1.


    But nothing can stop the MIDI from being laid down late when you're recording to a delayed reference. You'll always have to do something after the fact to re-align or compensate the late MIDI recording.








    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
    #23
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 10:55:17 (permalink)
    Thanks for the clarification.  That's how I understood it.

    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #24
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 11:07:50 (permalink)

    It all starts to add up (the latency) with this much going on in real time and like I said, my DAW is fine if I record audio tracks, it is just when I try to monitor new MIDI tracks where this delay rears its ugly head.



    I'd really like to get to the bottom of this. It doesn't make sense. Adding processing load to a DAW will not increase latency. It will just cause higher and higher CPU load until you start getting dropouts, and have to manually increase your audio buffer to lower the load. Other than manually increasing the audio buffer, the only thing that will add latency is a plug-in that needs delay compensation, and in some cases, this delay can be variable depending on plug-in settings.


    But if you can record live audio without added latency, then there must not be any PDC happening, and you should be able to record a soft synth without latency as well. Just as with other forms of processing load, if rendering the soft synth audio is too much of a burden for the processor, you'll get pops/crackles/dropouts, not added latency.


    If it's true that you can monitor and record audio in these projects without latency, but not soft synths, I have to think there's some configuration issue or bug causing it. It's not normal.


    EDIT: The fact that MIDI is not laying down late using the parallel-host setup also suggests it's not a PDC problem. One key test would be to record MIDI without paying any attention to the delayed soft synth audio - that is, silence the soft synth, and just hit the keys on the beat as you hear it - and see if the MIDI lays down in the right place.
    post edited by brundlefly - 2011/08/02 11:14:23

    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
    #25
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 11:19:19 (permalink)

    #2. Why do you need to record with a full mix?
    Sound strange to me.
    A minimum of tracks for timing and music should really be all you need to record another track.


    I agree with this.

    To my way of thinking, it matters not one bit that the rest of the track is fully mixed & finished.

    It didn't start off life that way - it probably started with the basics of drum/bass & a melody line or something and this base was used to build on.

    This approach to song structure has worked well for thousands of musicians/composers and also I suspect, the OP as well.

    So, why abandon this idea simply because your song is nearly "finished".

    It clearly isn't finished as he now wants to overdub new material, so why not overdub under the same conditions as all the other overdubs?
    post edited by Bristol_Jonesey - 2011/08/02 11:20:33

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #26
    Jonbouy
    Max Output Level: 0 dBFS
    • Total Posts : 22562
    • Joined: 2008/04/14 13:47:39
    • Location: England's Sunshine South Coast
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 12:09:06 (permalink)

    Why should it matter to anyone how somebody else sets up their way of working?

    The good news is that Jim has found a way of working that suits him on his particular stuff.

    Brundlefly's curiousity as to what the specific causes and conditions of a particular phenomenon are are understandable, but this idea that somebody else should adopt a particular way of working because somebody else does it that way dumbfounds me.

    I also normally have a lightweight project for tracking and sound generation with a bounce of the main mix as a guide for subsequent tracks but I can understand wanting to groove along with the active mix project also tweaking as I go.  It's called creative freedom.



    "We can't do anything to change the world until capitalism crumbles.
    In the meantime we should all go shopping to console ourselves" - Banksy
    #27
    jimkleban
    Max Output Level: -64 dBFS
    • Total Posts : 1319
    • Joined: 2008/11/09 09:42:45
    • Status: offline
    Re:Midi Monitoring Idea 2011/08/02 18:27:29 (permalink)
    Well, I don't understand the inner working of SONAR as well as any of you.  I just want to hit record and work.  I only delve into this when it stops "working". This method stopped working for me right around the time I decided to go the UAD route.

    If I disable all the plugins (that BIN command to turn off all effects of this type, or whatever it says) totally eliminates and noticed delays. But the tracks are so processed (since thay all are VSTi, they need a lot of TLC to make them all sound like that they have come from the same space in time) that when the plugs are disabled, the instruments don't even sound like the same instrument.  Imagine a DI'ed guitar sample just playing back with no processing.. not only does the volume go WAY DOWN, the space become empty and I have a hard time playing while fitting the performance into an imaginary space.

    OK.. I actually understand why someone wouldn't do it the way I do it and I respect that opinion but please try and understand that there is a method to my madness as well.

    I thought I would just share my thought on how to eliminate the MIDI delay for however the problem might arise for someone to save them the time of trying to come up with a work around from scratch.

    I should just render the VSTi tracks with no processing and post that so you all can hear what I mean and then post the exact same project with the plugins turned on and you will instantly understand where I am coming from.

    If that would help, I will gladly accommodate this demo.

    Jim

    The Lamb Laid Down on MIDI
    www.lldom.com
     
    Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R)
    Apollo Duo (via TB)
    UAD Quad
    UAD Duo
    WIN 8.1 x64 with 32 GB Ram
    4 SSD for programs and sample libraries
    Splat (latest version)
    #28
    Jump to:
    © 2024 APG vNext Commercial Version 5.1