Helpful ReplyMidi "latency" test? Help!

Author
dougalex
Max Output Level: -86 dBFS
  • Total Posts : 244
  • Joined: 2003/11/18 14:22:24
  • Status: offline
2018/03/05 22:11:12 (permalink)

Midi "latency" test? Help!

Could someone perform this test for comparison:
Only 2 tracks in Sonar, one audio track with mic input, one midi track with controller (I use Oxygen 61) selected as input
Put mic very close  to keyboard (1 inch away) 
Record both tracks, making single key presses, hitting key hard enough to make a noise when the key pressed
Switch the time ruler to milliseconds so you can easily compare the timing difference in milliseconds. 
 
My midi is 20 milliseconds later than the recorded sound of the key press noise
What is your results?
(I thought the midi track would, if anything, be slightly ahead, or at least equal to the timing of the recorded audio BUT RECORDED MIDI NOTES WAS 20 MILLISECONDS AFTER THE RECORDED AUDIO. I do not understand how this is happening. I have newer pcAudioLabs computer and tested with keyboard controller plugged directly into computer with 6 foot midi cable)
 
 
 
 
 
 
 
 
#1
chuckebaby
Max Output Level: 0 dBFS
  • Total Posts : 13146
  • Joined: 2011/01/04 14:55:28
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/05 22:38:37 (permalink) ☄ Helpfulby Steev 2018/03/07 18:39:27
You should probably establish some base specs before anything.
What OS are you using ? What kind of soundcard are you using ? Which version of Sonar ?
This sounds like the tell tale signs of latency to me.
Even midi needs a good soundcard no matter how new the PC.
 
Latency is Latency. If its windows 10, if its Sonar platinum (updated within the past year) Try using WASAPI mode.
If you have no soundcard (using onboard) try ASIO4ALL or I would suggest getting a budget soundcard.
Anyone doing any serious (or even amateur) recording now a day has a break away box with a soundcard.
Its not just for multiple inputs. Its the drivers for the unit which prevent latency.

Windows 8.1 X64 Sonar Platinum x64
Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
Focusrite Saffire 18I8 - Mackie Control
   
#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 "latency" test? Help! 2018/03/05 22:51:32 (permalink) ☄ Helpfulby tlw 2018/03/06 19:32:00
Hmmm... this reply was showing a couple minutes ago, but I think making too many small edits after the fact got it whacked; so I'll re-post:
 
Assuming your audio record latency compensation is dialed in, MIDI transmission delays will usually result in recorded MIDI being 3-4ms behind audio. The very old MOTU USB interface I'm using right now is the worst of any interface I've ever had at about 5ms. The best I've ever seen was about 1.5ms for the MIDI ports on an E-MU 1820m PCI.
 
If anything, record latency compensation will usually be a little less than required, so an error there will actually tend to reduce the time difference between simultaneous recording of audio and MIDI like that, but if you're over-compensating audio latency for some reason, that could make MIDI appear to be late. Otherwise, that much MIDI delay would point to some sort of driver/hardware issue.
 
The first thing to do is ensure both Manual Offset in Audio preferences, and Timing Offset under Sync and Caching
are zero, and then calculate and set the correct Manual Offset for record latency. The easiest way to do that is to use the free CEntrance ASIO latency tester to measure actual round-trip latency, and then then set Centrance Measured - SONAR Reported as the Manual Offset; usually not more than 40-50 samples or about 1ms.

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
dougalex
Max Output Level: -86 dBFS
  • Total Posts : 244
  • Joined: 2003/11/18 14:22:24
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/05 22:54:47 (permalink)
I just want to clarify
You did understand the MIDI is late, not the audio, right?
 
Edit: After reading again, I guess you did.
 
FYI
Audio interface: Behringer X32 Rack USB Card
No midi interface, USB connected direct to computer
 
Thx
 
#4
chuckebaby
Max Output Level: 0 dBFS
  • Total Posts : 13146
  • Joined: 2011/01/04 14:55:28
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/06 13:45:13 (permalink)
Comment removed.
 
 
 
 
 
post edited by chuckebaby - 2018/03/06 21:39:50

Windows 8.1 X64 Sonar Platinum x64
Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
Focusrite Saffire 18I8 - Mackie Control
   
#5
Steev
Max Output Level: -84 dBFS
  • Total Posts : 314
  • Joined: 2006/02/04 08:24:08
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/07 18:43:46 (permalink)
Not a MIDI problem. You need a low latency audio interface.

Steev on Bandlab.com
 
Custom built workstation. Windows 10 Pro x64.
 
SONAR Platinum. Cakewalk by Bandlab.
Sony Sound Forge Pro 10, ACID Pro 7, Vegas Pro 11
Pro Tools.
 
ASRock 990FX mobo, AMD FX 8370 8-Core. 16 gb DDR3 PC1866 G Skill Ripjaws X RAM. AMD FirePro V4900 1gb DDR5 accelerated graphics card. 
Behringer X Touch DAW Controller
Focusrite Scarlett 18i20 gen 2, OctoPre Mkll
Western Digital 500GB SSD bootdrive,  WD 500GB 10k rpm VelociRaptor for DAW projects . 2x1 TB WD Caviar Black SATA3 storage drives
 
#6
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/07 19:36:27 (permalink) ☄ Helpfulby Steev 2018/03/08 14:52:39
And of course you are probably aware that having certain plug ins active cause midi to be late. 
If I hear midi latency I always by pass certain effects like the LP Multi band for one. 

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#7
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/07 22:02:18 (permalink)
dougalex
My midi is 20 milliseconds later than the recorded sound of the key press noise
What is your results?

Discussed many times, but since you ask explicitly I answer explicitly
 
Here is my setup and all relevant settings (check what you have there, if you still have the question, let us know these settings):
* Sonar Platinum 2017.10, running on Win10 64bit
* RME Babyface pro as the audio interface
* MPK Mini as the MIDI controller
 
Settings in Sonar:
* audio:
- Driver Mode: ASIO
- ASIO buffer size: 256
- ASIO reported latency: Input 6.3, Output 6.7, Round trip 13 (575 samples)
- Sync and caching (Record Latency Adjustment): Manual offset 0, Use ASIO reported latency 575 set.
- Project clock source: audio
* MIDI:
Audio / Sync and Caching / Full Chase Lock, Timing offset : 0
 
Project:
- one audio track, input from Mic
- one MIDI track, input from MIDI Omni
(NO FXes, NO SoftSynth)
 
After recording both tracks in parallel: recorded MIDI notes are at the loud part of the recorded click (~2-4ms after the beginning of the signal, depending from how "fast" I was pressing keys).
 
--------------------
 
INDEPENDENT from real latency/delays, Sonar RECORD Audio and MIDI with compensation by what it think the latency was. The idea: you play/sing along already recorded material, so you play/sing "late" in absolute time. Sonar compensate that by putting recorded material in the time line BEFORE the time it really receive the signal.
 
--------------------
 
So, if you have problems:
* check all mentioned settings, may be you will see something unusual
* do audio loopback tests. Described at many places. Simple one with special program, to check that reported latency is correct. If you have only 2 inputs, record mono source and in parallel the loop throw Sonar. If you have more then 2 inputs, the best approach is to record "stereo" input with the same signal on both channels, one channel directly and another "looped" throw Sonar back to the third input. Check that Sonar aligns recorded audio properly (independent how big the latency is). If something is not right with automatic settings, you can adjust manually (Manual offset)
* finally, you can manually put MIDI where you want it with Timing offset option.
 
--------------------
Note, that several times I had real MIDI delay from my DP and e-drums (at the same time, my Keystation and MPK Mini was working without that delay). Rebooting the computer was solving that problem. I still wonder how that is possible.
 

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
#8
BRainbow
Max Output Level: -83 dBFS
  • Total Posts : 399
  • Joined: 2004/03/14 01:39:12
  • Location: Honolulu, Hawai'i
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/08 01:16:38 (permalink)
I don't play live much and I have limited enough chops that my own timing is usually worse than reasonable latency-related offset.  But when I get latency problems with recording audio or MIDI, and I can't cure it with buffer tweaking, I fix it after the fact.  These are all pretty obvious fixes but they work for me.
 
1.  I have accepted that MIDI-driven audio from an external source (and sometimes internal) will always be a bit delayed.  I just drag the recorded audio clip back a few point to line it up.
 
2.  If the MIDI notes played on the keyboard/controller are late arriving and/or being recorded by SONAR, I do the same thing with the recorded MIDI clip, just drag it back to line it up with the measures.
 
3.  If I suspect a soft synth is delayed when playing recorded MIDI notes which themselves are properly timed, I freeze or bounce to an audio track and do the same thing.
 
Another obvious trick if a soft synth is lagging when you are trying to record with a MIDI keyboard is to record while listening to the keyboard's own internal sound that matches your desired soft synth, instead of to the soft synth itself.  The attack and response will be fast and you won't be thrown off by any latency delay.

Cakewalk (forever), Two WIN10 64-bit DAWs: home-brew ASRock x299 Taichi / i7 7820x w/ 64GB RAM and ASUS X99A-II / i7-5820K w/ 32GB RAM, ZOOM UAC 8, Mackie ONYX 1640i FW Mixer/Interface, Mackie ONYX 1200F, Avalon U5 PreAmp, NI Komplete 11 Ultimate, EastWest Composer CloudX, Yamaha MOTIF XS8, Ensoniq SD-1 and ESQ-1, Korg M1rEX, Yamaha TX-81Z, Roland D110, Line6 HELIX Rack and Native, POD HD-Pro, POD Farm 2.5, Yamaha NS-10 and Presonus Eris E8 monitors, Yamaha Disklavier Upright Piano, mics, guitars, basses, and the cutest little tambourine.
#9
57Gregy
Max Output Level: 0 dBFS
  • Total Posts : 14404
  • Joined: 2004/05/31 17:04:17
  • Location: Raleigh, North Carolina
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/08 01:37:54 (permalink)
Also, if you know what the difference is, you can set one of your 'nudges' to that value and easily fix the late (or early) clip.

Greg 
I am selling my MIM Fender Stratocaster HSS, red and black. PM for more details.

Music Creator 2003, MC Pro 24, SONAR Home Studio 6 XL, SONAR  X3e, CbB, Focusrite Saffire, not enough space.
Everything is better with pie. 

http://www.soundclick.com/bands/default.cfm?bandID=609446
http://www.reverbnation.com/#!/gregfields 
#10
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/08 17:08:26 (permalink)
FYI.. out of curiosity I plugged a mike in and performed the key click test, I had to zoom waaayyy in to see it was a little late I think it computes to around 2 ms. This was using a Roland A 41 USB. 
 
The amount of delay the OP is getting I'll put my money on a plug in.
I think normally with no plug ins involve the Midi latency of most systems is between 2-5ms. And I do believe this is 100% to do with the midi diver and the controller itself.
If you notice, some controllers come with Factory USB midi drivers, and some just use a generic driver. I am convinced midi USB drivers are just as important in the same way Audio USB drivers are to a systems performance. Then there is the internal workings of the controller itself. Not all are created equally just like audio interfaces. 
Manufactures never post this information. 
 
I know for sure my Roland keyboard is more responsive than my Akai Synth Station or my Yamaha drums.   And for sure my Yamaha Drums the latency is very noticeable as a digital delay if you monitor the VST and the brain. So I only monitor the brain while tracking. I don't have that option with my keyboard controllers as they have no internal sound. I really don't "feel" any latency while tracking with headphones with either keyboard and generally my notes land within a 1/64 of where they belong. 
This is not the case with the Yamaha drums as the timing is always out.  I will test my other 2 controllers  to see how they stack up. I even have an old Korg poly 8000 midi keyboard I could try.  

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#11
kzmaier
Max Output Level: -81 dBFS
  • Total Posts : 461
  • Joined: 2010/10/18 08:20:01
  • Location: Rochester, NY
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/08 18:00:38 (permalink)
I wish Cakewalk had a calibration capability which could synchronize (or report) audio, midi, and virtual instruments as needed.  I can live with vst effects latency's as I do all my tracking before adding effects.
 
Just a thought...

Best Regards,
Ken
Bandlab Cakewalk - i5/8G Focusrite Scarlett 6i6 / Boss gt001
 
www.reverbnation.com/kzmaier
 
 
#12
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/08 18:31:23 (permalink)
It's not a problem as long as your aware of the limitations  which is complicated  by all the things involved. 
 
Above was mentioned the audio loopback test which I think everyone should try and especially if your using a so so audio interface. I ran a thread a few years ago and a bunch of folks tried it using different interfaces. The conclusion was almost all name brand audio interfaces using ASIO report properly to Sonar so your timing offset will not need manual adjustment. But using any other audio mode will always result in late overdubs. Some ever reported audio arriving early. 
 

 
For those who have never done this it's easy. In the above example
I took a midi drum  track (Track 1)  and froze the synth ( track 2). 
This gives you an audio track with a nice easy to see transient spike. 
Patch your audio interface output back to an input using a sort patch cable.
Insert an audio track ( track 3)  and set its input to the input you patched as the source and arm it for recording. 
Make sure INPUT ECHO IS OFF. 
play the song and set your levels. 
Record the new tack.
Now zoom in and see if it lines up with the original audio. 
Try the test using different audio interfaces ( track 4) and in different modes. ( track 5 and 6 ) 
You can clearly see why we don't want to use anything but ASIO mode. 
 
Later I tried this test using WASAPI. WASAPI Exclusive was about the same as using WDM mode The WASAPI Shared was worse. And I also tried ASIO4ALL and it performed very close to the same as ASIO mode. (Sorry my screenshot was held hostage by Photobucket) ,  So I use ASIO4all when I don't have a proper interface.  If your not overdubbing new audio it doesn't matter. SO those who work with pure midi could use WASAPI or WDM if their on board sound card supports it. Of course if you have an interface always use the latest ASIO driver.  

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#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 "latency" test? Help! 2018/03/08 22:01:24 (permalink)
Cactus Music
The conclusion was almost all name brand audio interfaces using ASIO report properly to Sonar so your timing offset will not need manual adjustment.



I've never seen a driver that reported sample-accurate input/record latency. All have some 'hidden' firmware/hardware latency that is not included, or they add a fudge factor and over-report. Most will be within 1ms, but if you want sample-accurate record compensation, you'll almost certainly need a Manual Offset. For ASIO, using the free CEntrance latency tester mentioned earlier is a lot quicker than re-recording and counting samples as you nudge the audio.

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
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/08 23:35:21 (permalink)
 This is true but generally ASIO is so close as to not matter to anyone but someone with obsessive compulsive disorder :) 
I'm trying to remember the calculations. OK found it. 
Samples divided by the sample rate= MS
 
So in my case my loop back was out by 22 samples so divided by 44.1 = .49 ms. 
So as I said we need to be aware of this but in most cases is not worth fretting over as most musical performances involve timing variation way beyond that. But a good engineer does need to be aware of those little details. 
 
And yes I keep forgetting about the Centrance utility. Does it work on W 10? 
I have it here on my W7 machine. 

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#15
dougalex
Max Output Level: -86 dBFS
  • Total Posts : 244
  • Joined: 2003/11/18 14:22:24
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 03:53:07 (permalink)
I hope it was clear
I was NOT using any VST soft synth
I was ONLY recording a midi note (WITHOUT ANY PLUGINS)
I recorded simultaneously:
a) Audio track recording a mic placed closely to capture the thump of me hitting the key on the keyboard,
b) Midi track recording the midi note of the SAME key press (no soft synth loaded at all)
 
I then zoom in to see if they are simultaneous and to my surprise (instead of the audio track being late) THE MIDI NOTE (the midi note "blob") IS LATE by 20 ms
 
Still do not understand why the midi note blob would appear later than the wave blob of the mic that is recording the thump of me hitting the key.
 
 
#16
bvideo
Max Output Level: -58 dBFS
  • Total Posts : 1707
  • Joined: 2006/09/02 22:20:02
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 04:09:05 (permalink)
Be aware that Sonar may shift the audio track earlier to compensate for the latency reported by the driver. Wrong report from the driver, wrong audio shift.
 
An experiment to try is to play a recorded MIDI track to your synth and record the audio, then see how the audio lines up with the MIDI.
 
FYI other audio shifts may be done whenever audio plugins anywhere in the project report themselves to produce latency.
 

W10 pro, Sonar Platinum, Alesis Multimix 16 FW, MOTU Express 128, Gigabyte Z370 HD3P, i7 8700K, 16 Gigs, ssd + 2 X 2T disks, D50-MEX, JV80, A90EX, M1REX
#17
dougalex
Max Output Level: -86 dBFS
  • Total Posts : 244
  • Joined: 2003/11/18 14:22:24
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 04:18:07 (permalink)
I just tried the same test again tonight
 
Same project, BUT NOW it is behaving as I expected it to: The "spike of the recorded thump of the key strike" and the "recorded midi blob" are essentially simultaneous.
 
I think azslow3 above mentioned reboot had remedied a similar situation where the midi was delayed.
 
So right now I am thinking my original weird results was a situation where I needed a reboot.
 
I will have to test again periodically to confirm.
 
THANK YOU FOR THE REPLIES! 
#18
Steev
Max Output Level: -84 dBFS
  • Total Posts : 314
  • Joined: 2006/02/04 08:24:08
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 11:08:09 (permalink)
What generation is your Oxygen 61? I believe they are up to Gen 3 now.
 
Do you have the latest drivers and firmware updates installed?
 
Is the Oxygen 61 plugged directly into it's own dedicated USB "2" port? Don't use a USB 3 port.
 
"ONLY USE MANUFACTURER'S ASIO DRIVERS FOR YOUR AUDIO INTERFACE THAT SUPPORT YOUR OS!"
 
Always record at 24 bit, and the faster the frequency, the lower the latency.
44.100 k/Hz highest latency
48 k/Hz typically around 2x lower latency and safe and stable for most computer systems
96 k/Hz typically 2x lower than 48 k/Hz, but can cause problems with a mid grade machine, you need a robust i7 grade computer with plenty of processing power to stay safe and stable.
 
Using hacked drivers to run an outdated 1st gen MIDI keyboard controller with Win 10 may make it work but can really slow it down.
 So can a cheap or old USB cable or unpowered USB hub sharing other devices. You can't always tell if a USB cable is faulty by looking at it, and cheap USB cables aren't always suited well to transmit MIDI data.
 
Have you tried running the Oxy 61 MIDI output directly through a standard MIDI 5 pin cable to a separate MIDI input on a separate interface? Make sure to choose/route the interface's MIDI out port as input for the MIDI track routed to the synth you're testing with. 
 Go into SONAR's control surface properties, Uncheck the Oxy 61 than hit Apply to disable it.
 This bypasses the Oxy 61 drivers entirely but still routes MIDI input for the keyboard and uses USB only for power.
 
You can easily test for any of these problems simply by disconnecting the Oxy 61 by unplugging it from the computer, rebooting Windows and testing with a different MIDI keyboard or virtual keyboard controller.
 
 If you get the same latency problems, plug the Oxy 61 back in, disconnect all other USB devices you absolutely don't need, reboot and test again.
 If that works, than something else is hogging and slowing down your motherboard's USB root hub that's not even related to MIDI or SONAR.. ??????
 
Good luck bro..
 
 
post edited by Steev - 2018/03/09 11:36:42

Steev on Bandlab.com
 
Custom built workstation. Windows 10 Pro x64.
 
SONAR Platinum. Cakewalk by Bandlab.
Sony Sound Forge Pro 10, ACID Pro 7, Vegas Pro 11
Pro Tools.
 
ASRock 990FX mobo, AMD FX 8370 8-Core. 16 gb DDR3 PC1866 G Skill Ripjaws X RAM. AMD FirePro V4900 1gb DDR5 accelerated graphics card. 
Behringer X Touch DAW Controller
Focusrite Scarlett 18i20 gen 2, OctoPre Mkll
Western Digital 500GB SSD bootdrive,  WD 500GB 10k rpm VelociRaptor for DAW projects . 2x1 TB WD Caviar Black SATA3 storage drives
 
#19
Billy86
Max Output Level: -83 dBFS
  • Total Posts : 362
  • Joined: 2015/03/06 16:03:26
  • Location: Seattle
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 14:33:40 (permalink)
Cactus Music
FYI.. out of curiosity I plugged a mike in and performed the key click test, I had to zoom waaayyy in to see it was a little late I think it computes to around 2 ms. This was using a Roland A 41 USB. 
 
The amount of delay the OP is getting I'll put my money on a plug in.
I think normally with no plug ins involve the Midi latency of most systems is between 2-5ms. And I do believe this is 100% to do with the midi diver and the controller itself.
If you notice, some controllers come with Factory USB midi drivers, and some just use a generic driver. I am convinced midi USB drivers are just as important in the same way Audio USB drivers are to a systems performance. Then there is the internal workings of the controller itself. Not all are created equally just like audio interfaces. 
Manufactures never post this information. 
 
I know for sure my Roland keyboard is more responsive than my Akai Synth Station or my Yamaha drums.   And for sure my Yamaha Drums the latency is very noticeable as a digital delay if you monitor the VST and the brain. So I only monitor the brain while tracking. I don't have that option with my keyboard controllers as they have no internal sound. I really don't "feel" any latency while tracking with headphones with either keyboard and generally my notes land within a 1/64 of where they belong. 
This is not the case with the Yamaha drums as the timing is always out.  I will test my other 2 controllers  to see how they stack up. I even have an old Korg poly 8000 midi keyboard I could try.  


I have a Roland TDK11 kit. Curious to know how you are able to monitor your Yamaha’s brain while tracking. Are you recording Yamaha output (audio? Midi?) along with other tracks in Sonar? How do you listen to both Sonar output AND direct monitor your Yamaha at the same time? I’m midi-triggering Addictive Drums 2 via a Focusrite 2i4.

Windows 10 x64 on a Dell/Intel i5, 500 Gig SSD, 32 gig RAM, Focusrite Scarlett 2i4, Sonar Professional, Melodyne 4 Assistant, Kurzweil SP-76 stage piano, Baldwin RP 100 digital upright, Novation Impulse 25, Breedlove Pursuit Concert Acous/Elec, Fender American Standard Tele, Fender G-DEC 30 modeling amp, Sigma DM-5 Acoustic, Ovation MCS148 Celebrity Acous/Elec. Mandolin, Roland V-Drums TD-11KV, AKG P220, Yamaha MG82CX mixer, KRK Rokit 6 Powered Monitors, PreSonus FaderPort
#20
57Gregy
Max Output Level: 0 dBFS
  • Total Posts : 14404
  • Joined: 2004/05/31 17:04:17
  • Location: Raleigh, North Carolina
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 15:03:19 (permalink)
"I have a Roland TDK11 kit. Curious to know how you are able to monitor your Yamaha’s brain while tracking. Are you recording Yamaha output (audio? Midi?) along with other tracks in Sonar? How do you listen to both Sonar output AND direct monitor your Yamaha at the same time? I’m midi-triggering Addictive Drums 2 via a Focusrite 2i4."
 
I don't know how Cactus does it, but I monitor all my MIDI instruments through a mixer.
Audio output of instruments is plugged into the mixer. Audio output of the interface is plugged into the mixer, too.
post edited by 57Gregy - 2018/03/09 15:52:42

Greg 
I am selling my MIM Fender Stratocaster HSS, red and black. PM for more details.

Music Creator 2003, MC Pro 24, SONAR Home Studio 6 XL, SONAR  X3e, CbB, Focusrite Saffire, not enough space.
Everything is better with pie. 

http://www.soundclick.com/bands/default.cfm?bandID=609446
http://www.reverbnation.com/#!/gregfields 
#21
Billy86
Max Output Level: -83 dBFS
  • Total Posts : 362
  • Joined: 2015/03/06 16:03:26
  • Location: Seattle
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 15:45:43 (permalink)
Of course! The answer is right in front of my face: my 8-channel Yamaha mixer. Doh!

Thanks for the brain jog. Must be lack of coffee. 😳

Windows 10 x64 on a Dell/Intel i5, 500 Gig SSD, 32 gig RAM, Focusrite Scarlett 2i4, Sonar Professional, Melodyne 4 Assistant, Kurzweil SP-76 stage piano, Baldwin RP 100 digital upright, Novation Impulse 25, Breedlove Pursuit Concert Acous/Elec, Fender American Standard Tele, Fender G-DEC 30 modeling amp, Sigma DM-5 Acoustic, Ovation MCS148 Celebrity Acous/Elec. Mandolin, Roland V-Drums TD-11KV, AKG P220, Yamaha MG82CX mixer, KRK Rokit 6 Powered Monitors, PreSonus FaderPort
#22
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Midi "latency" test? Help! 2018/03/09 15:53:25 (permalink)
I am a Noob, so I can play on TD-11 with AD2, even with audio output throw TD-11 (build-in Edirol). The last option is not really convenient, a bit too much latency. But throw "real" audio interface, it is ok for me.
 
When I had one of that "WT... is going on?" moments with MIDI latency, a friend was visiting me. He (also hobbyist) has not played with AD2 before, so I have switched on my system. He has tried with the conclusion "sorry man, but that is no playable...". I have tried myself - really "no go".  I have turned on my DP and I could barely play it with TruePiano. I can play slow peaces with up to 30ms latency, but this time it was more. I took my MPK mini and surprise, the latency is as usual. I had no time for investigations, so I have turned the system off. Later, after turning it on again, everything was working properly again.
 
I am a kind of unlucky with music setups. Strange things happened exactly at times when that was more or less critical. Like continuously crashing with my notebook VS-20, after 2 days working fine and just several hours before I had to use the setup (that can be called lucky moment, that has forced me to buy RME which was a good move). Sonar has reverted to demo mode in the middle of video tutorial recording (which I do not do often). MIDI latency, when someone is visiting me. Etc.

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
#23
Jump to:
© 2024 APG vNext Commercial Version 5.1