Thank you. I noticed the zero crossing was not selected when you were editing hitpoints. What effect will turning it on have on hit point detection and creating events? The premise is that we want to avoid clicks from non zero edits. For drums, if I leave zero crossing on it results in events with different start/end points. This then requires fussing at high zooming to edit events but gives more natural results. If zero crossing is off, it creates equal events, but then it is necessary to use fade in/out to make events start and stop at zero, and some events need to be lengthened or shortened to avoid weird edits, like when an early bass drum hit occurs. I’ve not found a way around this.
The Zero-crossing setting doesn't appear to make any difference to the hitpoint creation (or the event cuts made as a result of them). Generally I'll worry about clicks later on in the editing process, once I have the edit and the timing sorted out, as typically you can sort this out with a minor change in edit location - often they'll get sorted as part of the edit anyway, and I usually find it's a low proportion of them that either cause an issue (whether by the nature of the edit itself or by using crossfades), and when they do it's usually pretty quick to sort out, particularly using the edit tool to trim both clips at the same time.
Do you find that Cubase does a good job of picking out the big hits? I always find that the first one in the audio file is way early as well as some random ones throughout the file. I'm on Cubase 10.5, so maybe this is something that's been fixed in 12?
Hi thanks for the tutorial i think this might help for applying cuts to multiple tracks, but its not exactly by normal hitpoints though its kind of hitpoints with the quantize panel th-cam.com/video/IsbBKXV9h3s/w-d-xo.html
I am working with fast double kicks and hitpoints are not picking them up properly. Is there a way to use a transient designer before hitpoints section? Thanks!
I'm not aware of one - I'd try this by applying the process to a copy of the track and if I got a good result then applying that to the original. If you can send me the track you're working with I'd like to hear it and see what I can come up with.
Thanks for the suggestions, I'll put them on the list. MIDI Transformer is briefly covered in next week's video, but a full one will make sense leading on from that.
This is great.. thank you.. Question for an upcoming video. I want to kick in an effect based on the loudness of a vocal or any other track.. The side chain reacts exactly in a opposite way... For example, I like to add more distortion to a vocal as louder it is. Would be great if you can make a video about.
You can add hitpoints using ALT + Click near the top of the editor area. You can disable a hitpoint with shift + click, but not actually delete them. HTH.
Thank you. I noticed the zero crossing was not selected when you were editing hitpoints. What effect will turning it on have on hit point detection and creating events? The premise is that we want to avoid clicks from non zero edits. For drums, if I leave zero crossing on it results in events with different start/end points. This then requires fussing at high zooming to edit events but gives more natural results. If zero crossing is off, it creates equal events, but then it is necessary to use fade in/out to make events start and stop at zero, and some events need to be lengthened or shortened to avoid weird edits, like when an early bass drum hit occurs. I’ve not found a way around this.
The Zero-crossing setting doesn't appear to make any difference to the hitpoint creation (or the event cuts made as a result of them). Generally I'll worry about clicks later on in the editing process, once I have the edit and the timing sorted out, as typically you can sort this out with a minor change in edit location - often they'll get sorted as part of the edit anyway, and I usually find it's a low proportion of them that either cause an issue (whether by the nature of the edit itself or by using crossfades), and when they do it's usually pretty quick to sort out, particularly using the edit tool to trim both clips at the same time.
Doing the lords work here 👏
Do you find that Cubase does a good job of picking out the big hits? I always find that the first one in the audio file is way early as well as some random ones throughout the file. I'm on Cubase 10.5, so maybe this is something that's been fixed in 12?
Superb, very helpful indeed these videos! Many thanks! 👏👏👏
Hi thanks for the tutorial
i think this might help for applying cuts to multiple tracks, but its not exactly by normal hitpoints though its kind of hitpoints with the quantize panel
th-cam.com/video/IsbBKXV9h3s/w-d-xo.html
I am working with fast double kicks and hitpoints are not picking them up properly. Is there a way to use a transient designer before hitpoints section? Thanks!
th-cam.com/video/wcDX8w2AdT0/w-d-xo.htmlsi=waFhaHz7XdNTp9GP
Try this video mate, different approach to the same outcome.
I'm not aware of one - I'd try this by applying the process to a copy of the track and if I got a good result then applying that to the original. If you can send me the track you're working with I'd like to hear it and see what I can come up with.
Hi ! Can you make please some videos for :
- expression maps
- midi tronsformer
- add insert fx in mediabay preview
- spectralayers
Thank you 🎩
Thanks for the suggestions, I'll put them on the list. MIDI Transformer is briefly covered in next week's video, but a full one will make sense leading on from that.
This is great.. thank you.. Question for an upcoming video. I want to kick in an effect based on the loudness of a vocal or any other track.. The side chain reacts exactly in a opposite way... For example, I like to add more distortion to a vocal as louder it is. Would be great if you can make a video about.
I shall look into that!
Hello , thanks for your video. Is there a way to manually remove o add some of the hitpoints?
You can add hitpoints using ALT + Click near the top of the editor area. You can disable a hitpoint with shift + click, but not actually delete them. HTH.