Great work! Thanks for sharing David!

Thank you for the sheets 🥹

That spreadsheet is incredibly helpful. Thank you so much for making it!

The explanation of negative track delays was stunning. The idea about database very useful. Thank you so much for this content.

Nice. Thanks for the template!

Very useful tips, wow, thank you!

That´s a perfect xplanation of humanity in virtual instruments!!!Thanks David

Wow, what a wonderful contribution to music producers everywhere! 😊All I can say is THANK YOU, THANK YOU, THANK YOU!!!!! 😁

David thank you for your selfless contribution. You are one of the lights beyond the tunnel.

You know... The reaction I see in your video at 3 min 21 sec is exactly what I experience these days! That's why I was looking for how much delay to use with my OT Berlin CAPSULE Vsti's and that's how I came across your video. Very useful and this is the first thing I will try. Thanks! 🙂

Formidable, merci ! ❤

So glad to see you advocating the use of quantisation and negative track delays! I learned it from a composer of friend of mine and this is what I have been doing since that moment. Also, I actually remember one of your posts on Perspective from a couple of years ago, I believe, where you advertised you were putting together that sheet with negative track delay values per library

I'm a keyswitch guy myself, and this is probably the best argument I've seen so far on utilizing single articulation tracks. Super helpful, too - very much appreciated!

Wow! This tip about negative delays was exactly what I needed to hear! Thanks so much! 🤩

Thank you for your work!

As a beginner, that is good to hear especially from someone achieved like you are. Valuable advice! Thank you David 🙏

With the popularity of the google doc and the thread on VI CONTROL , I’m still surprised that some of the developers haven’t chimed in and just offered up the exact values for their libraries and instruments. It’s surprising how many still don’t list it in the manual. Good video and great initiative to set up the document in the first place 👍

The negative delay database is great, I found out about it last year on a VI Control post. Thanks. :)

Thank you! This was really awesome. You’re great at explaining things! I’ve known about quantizing for a long time, but the missing factor, negative track delay, is a key concept I missed. Thanks again!

Bit late to the party but been using your spreadsheet for a while so massive thank you for that - has massively simplified my template. I use multi-outs in SINE or Kontakt and apply a MonoDelay in Cubase on those outs. I set the track delay to the longest articulation attack, and set the MonoDelay to the difference of the track delay minus that that articulation's attack. Same principle as the CSS Control Panel I wrote, just in audio rather than midi.

Everyone using virtual orchestral instruments (or some other VT's) really needs to know about this!

this blew my mind so much, would have absolutely never thought that different articulations will have the need for different predelays

Really helpful - thank you David. I heard about negative delay from (your pal) Anne Dern and now you. Relieved to hear this latency is a thing, and not just me being hopeless! Cheers from Wales, UK.

Nice work explaining this!

Great video and the database is a great idea!

Great video and INCREDIBLE resource, I've been looking for a resource like this. Thank you so much for the work put in here to share this.

Thank you for this! And for sharing that spreadsheet! Figuring out delay times drives me mad; I'm terrible at it. Amazing to be able to reference a good starting point.

David, once again thank you for this information, your ideas on working on the grid make so much sense, especially when doing orchestral scores. thank you for the negative delay sheet.

Thanks that was very useful and informative! Well done

Superbly explained! huge thanks!

Huge thank you!

Thankyou David for this... my strings were tending to be haphazard as I struggled to cope with the delays... this is a great help

Hey David, Thank you from the bottom of my heart for the Negative Track Delay Database and this video. Both are extremely helpful! 🙏 Just subscribed to your channel. Great content here! :) All the best, Frank

I like this guy. Gives his heart as well as his music.

Its very helpfull ! Especially for Berlin stuff (in my case) Thank You. If i may maybe You could make some short video about how to fix latency problems in CSS. Some tiops ,tricks, advices. I know there is some script like CSS control panel but dont know how to set up correctly. Greetings

Honestly so well explained and clear, thanks for sharing the database as well David.

Omg, I love you for sharing that spreadsheet! ♥ I was beginning to mentally prepare myself to find out myself, but the ones I use most are already listed. Thank you!

Thanks for the tips, and negative delay data base. Very helpful info.

I’m new to your channel, but I wanted to thank you so much for all your hard work on this database. You have a new subscriber.

Great video! Audio Imperia’s approach to this problem is quite brilliant and is their libraries biggest selling point imo :D

Great video thank you

Great information and so well presented..Thank you David!

Thank you!

Thank you very much for sharing this information! I found it extremely useful and generous of you to give of your time and sharing the spreadsheet - greetings and thanks from England! 🙂

Great video David. Always felt guilty about using quantise......Not anymore👍

Super awesome video...Ty David, stay safe!!!

SO grateful for the database you created. I wish I would have had this all along - thank you!!

I think this is a really good video making some excellent points, which I generally suppport, however, a couple of additional points I would like to make. Regarding notation - most played in stuff looks schozoid with messes of hemi-demi- semiquavers, on first review in nation software, but you can use display quantize to show a simplified version without changing the "played in" feel, in many notation packages. Even if your notation package does not support this feature, a common practice is to make a copy of your scored notes and then mutilate these to look legible and sane as notation. Secondly, I think that the "humanised" element of actual performances, is not simply random errors. Careful listening might find, for example, that a player might naturally hurry towards a phrases crescendo, or go rubato intentionally during a legato phrase. Whole orchestras also breathe to a conductors elbow. Eliminating this (mostly unconscious) humanised timing by quantization, then expecting later to reproduce it with DAW randomisation so called " humanize" fuctions, is not really replacing like with like, though it is of course better than rigid muzak timing. Even so, I still agree that there is stil a lot to be said for quantization though, especially if your goal is not a midi performance but a liegible score. Quantization definitely reduces mud. Lastly, for performing a take, I always consider going to my sound device and short latency beyond it's normal settings. Even if your DAW produces pops and clicks, after recording the latency can then be set back and the pops will disappear.

Database is great ! You also convinced me when it comes to keyswitch patches vs individual tracks ... thanks so much !

Thanks David, very helpful video and well produced too!

We need expression maps which have the negative delays baked in. Then we could use instrument trracks instead of MIDI tracks which many composers tend to prefer!

Excellent video! And very useful spreadsheet. Thanks for sharing.

Genius thank you so much, finally after a year I found your video, Its helps so much

Love your content and willingness to share. Thanks for all that you do.

Enormously helpful video! Thank you!

I really appreciate this information...... working on my template now.

This is an invaluable tool, thanks David!

Great video David thank you and thanks for the negative track delay database…awesome!

When I first saw this video title I thought, "Oh I know quantization and negative track delay. I don't need to watch this." Man was I wrong. Not that I don't know those things, but this video was incredibly useful for the explanations and reasoning of everything involved. Thanks!

You are amazing. I am looking froward for your new tutorial. No many contents have this value.

This video is awesome!

Again. Thank you for this video. It helps A LOT. Love the File on Google Drive.

You just validated what I've been doing for awhile!

Thank you for the job you’ve done to create this database.

Great work - thanks David!

Thank you, well made and concise! I had seen the thread on vicontrol first and some of your other vids, great resource! Are we going to get that follow up on varying delays within a single instrument library/patch? :D

Fantastic, I needed this info. Thanks!

Copy and paste...YESSS. After making Pop and EDM music for many years I just got into Orchestral music. I come from a world of quantization I never understand why musicians have an issue with something that is the de facto state in others genres. I love accidents with orchestration (because I am a noob) but not accidents with timing. As far as I am concerned perfect is perfect. I found your channel because of Anne's channel and I love your work. Thank you.

thx for the link. j.

the database is fantastic!

Gracias bro :)

Thanks for your efforts, the database is super. 🙏

Great stuff man! I'll definitely be updating my templates!

Fantastic! Thanks so much for this.

I really appreciate this video and the resource!

I really needed this video. Thank you David! 🎵

As a beginner, this was really great info - thanks so much!

Hello! I don't know if someone already mentioned it, but as for the doubt about where does a note start, there's a relatively easy solution I'd like to share with you: Use a spectrogram view instead of a waveform one! I've learned to understand spectrograms and it's honestly amazingly easier than guessing from viewing a waveform. Although I must admit that waveforms can be useful in some other situations too. Trust me, whenever you prepare your recorded samples for your library, this can probably be a life saver.

This is so fantastic! I’ve been bouncing to audio and using flextime on all of it. Takes f.o.r.e.v.e.r. I’m converting to negative track delays immediately 😁

This is awesomely helpful. Thanks so much!

I owe you my life.

incredible work, thanks a looooooot !

Very helpful. Thank you!

Amazing info!! Thanks

Thank you señor 👍😉. That was very useful 🙏

🙏

Hey David, I know in your video you mention that you feel it's best to have separate tracks for each articulation. I know in DP you can set a Delay for each Articulation in its Articulation Map. This works great and have started to add the info form your Google sheet to my Babylon Waves files. Works great. Since you made the video, have you been doing that at all?

Hey David. Thanks for this video. You mention for legato tracks that you usually have to nudge the first note to work. What amount do you nudge that first note?

I wrote to the grid in this manner and submitted some music to a company and they said it sounded "too quantized". Like, who GAF? The average person isn't going to know or care!

Thanks For the Cheat Sheet!!!

Ooof. I’ll be cursing how much time I spent setting up articulation maps. Have you ever experiments with one track to write the whole part and then it sending multi channel midi to multiple tracks with different track delays? Bless you for making that database bro.

Thank you for sharing your time and knowledge with us. Much appreciated. I was wondering if the use of negative track delays across most if not all of a session would add additional strain on the PC's resources. Considering that there is much more for the system to correct and keep track of.

You claim you had made a key command or shortcut for negative delay in Cubase! I can’t find that setting anywhere in Cubase, would you be able to explain how you did it?

Can you make a trailer of adventure video game?

I use native instruments in ableton and all I want to know if you have a sort of sample preset that has delay on it, how can you quantise that delay/ echo

going forward i'm only creating music with stuff that does not have offset delays.. i've had far too many long nights of headaches and motivation killing tedious work having to deal with them.. it literally destroys all my motivation to create music.

I find that negative track delays are very useful for shorts. Staccatos or Spiccs and stuff like that. For longs, I find my playing automatically adjusts to it. But yes I can see the advantages of being completely within the grid.

Hey David, love the Virtual Instrument Track Delay doc. How often to do you update it? Also, if there is only a negative delay in on articualtion and none in the adjacent ones, does it mean they others are the same? Example: CSW you have -60 in Staccatisimo but the cells for Staccato, Marcato and Susatains are blank.

Man, this was A.M.A.Z.I.N.G. Thanks a lot! Now, I have a question: How did you setup that macro for move the first note of every legato starting point? I find that very helpful. I'm in Logic, but maybe I could find a way to do that too. (🙏 I hope you can see this)

hi david, you are SPOT ON with this. there is nothing worse than a sloppy orchestra. I've work with enough musos in orchestras to know they strive for precision. and being in the room when the instruments recorded showed me how different they sound close up, without all the post processing . each brand of library has its own lag time time. CineSamples for me is hardly playable in real time so quantize and neg. delay after step input. then fiddle around a bit. Sample Modelling, on the other hand is quick enough to play live and on stage. best, j.