Hitpoints why is audio detection so weak ?

Diskussionen rund um Nuendo 8.
Post Reply
sylvainmoreau
Member
Posts: 394
Joined: Sat Aug 11, 2012 11:05 pm
Contact:

Hitpoints why is audio detection so weak ?

Post by sylvainmoreau » Sun Jun 24, 2018 1:58 pm

Hi,

for years years years i hope that hitpoint detection in cubase then nuendo would work. But let's face it. It's super crap.
even with a clear drum track you get get hitpoints randomly and have to adjust manualy.
here i'm working with an audio file from boom library. so it's clearly 4 booms with high transient spaced with massive silence.
whatever the threshold / minimum length setting i'm faster doing it manualy.
this threshold thing makes me crazy. sometime you move it but i mean clearly you see the file is BELOW the threshold and still (!) nuendo drops a hitpoint there. then when you what to edit hitpoints it's a nightmare where you have to click this little tiny arrow lock/ disable hitpoints.
Protools for years has this simple function where you press a shortcut and cursor move to next transient super efficient.
and i remember the "remove silence" (?) from protools where you set threshold and actually see the waves BELOW threshold beeing left. then you could auto add offsets and more.
also why is Minimum lenght limited to 1s ?!? at least for sound filed recording it would help to have settings to 10sec where you leave space in your take for room and silence.

.. maybe i'm doing something wrong. tell me. oh of course if you use "beats" it works better.. but still not good enough.
so i end up doing cuts with low zoom, then zoom max and "locate next event" to adjust.
nuendo 10.2.0 / rme fireface 802 / rme Fireface UC/ W10x64 / 16ram / i7 2600k / P67A-UD3P-B3 / AMD Radeon HD 6800 Series


Post Reply

Return to “Nuendo 8”

Who is online

Users browsing this forum: No registered users and 1 guest