For years … wait no… deceade ! i hope hitpoints will improve in cubase and now nuendo.
it’s always crappy.
1- Why, when i enter audio edit, do i have to click twice on Edit Hitpoints arrow for it to work ?
2- Threshold works terrible. Whatever the setting sometime you clearly see some audio below the Threshold getting some hitpoints. Or some tails having undesired hitpoints.
3- I never get a hitpoint at the begining of the file if the time between start file and first transient is below Minimum Length (like if file start was a first hitpoint !)
4- To increase minimum length to max you have to scroll mouse so high in the screen that… you have to let go and do it a second time !
5- Minimum Length is not long enough ! Detection is so bad that you would hope at least to get rid of undesired hitpoints with minimum lengh feature. But 1sec is nothing when you work for sound field recording or sounds for sampling purpose. 10sec would be a good start !
6- having to clic tinny arrows on top of the ruller to lock / deactivate hitpoint is not easy when you work on full window.
7- not beeing able to auto add offset +/- to detection is sad.
8- why can’t we edit multiple regions at once ? we have to go out of edit and… start all the settings and clickings, zoom again on next region. Because what ever the “Edit active audio event only” hitpoints only affect the region you are editing. Not all selected.
9- oh funny last one : first hitpoint of your audio file is always ALWAYS under the “event start” display so you need to zoom to work on it
(event start wich is by the way the most annoying feature of audio software ever. Never used this thing and always have to remove it. export multiple file in mono and there’s one that has an event start different then all your other audio files. so when you import all those files… one is offset by the event start anchor ! appened to me on a show with pultiple channels couldn’t understand why i had a delay on one channel !)
10- i think there’s already so much going wrong with hitpoints that i feel bad adding this last one : why not “hitpoints at zero crossing” option ? just saying.
11- (can’t stop) is there a zoom preset and shortcut in sample editor ? missed that one. Because yeah doing all this messing around and no zoom preset doesn’t help.
so… yeah. There’s so much missing that every time i need to edit samples (even huge quantities) i prefer to go do manually exhaustive repetitions rather then hitpoint detection and random adjustments everywhere.
i was using protools 10y ago and remember transient detection and “remove silence” function much more efficient.
am i doing anything wrong ? please help.