Not that I can see. Nor the threshold of detection or anything like that
yes I believe that is how it’s supposed to work but it missed out the start of most things.
hmm… artifacts? I mean you’ll just have a very strange difference in volume. In some instances, creating the implication of a transient where one migh tnot have ever been as the start of the audio clip will be louder (if attenuating is what you were doing) than the rest.
Honestly it’s best to just try it yourself when you can but here’s some screen shots. One with vocals one with drums. It’s mostly like this. Or the detection will end prematurely too like on a kick that’s got some boom. So if you attenuated you’d had a quiet punch and then this ‘‘wHOOMPH’’ of the low end tail probably. yuck. Ah well. I’m sure I’ll still use it a bit here and there. The clip gain change we got already in 14 was great so yeah not really complaining. Just making it known that it’s not working as one might think.
4 Likes
Steinberg does not claim it to be fixed in any release notes. And a lot of people still reporting this a as new issue.
1 Like
Interesting, i’ve not had that occur yet but that’s a much cleaner audio file that i’ve been working with. Dare I say it, but they’re quite attractive waveforms you have! 
I don’t know if the zero crossing option has an effect on where it snaps?
You can drag the detection out if you keep hold of the mouse and drag, I don’t know if you’re aware or not? I have had to do that for multiple words.
For me the audio detection range is also hit and miss. Sometimes it catches everything and sometimes it’s leaving start of the word or drum hit. I tested voice and drum samples that are part of Cubase and those are very clean.
But in my experience, transient detection is also hit and miss, sometimes even when the start of the drum hit is obvious.
Not the end of the world for me, just confirming the experience of SamuelIanJones.
2 Likes
I’m on an Fader Mk1 and an older version software as they changed behaviour of the osd and the new behaviour is useless to me
After updating Cubase. projects were taking three or more attempts to open and console one software was causing the hang every time according the dumps.
I’ve rolled back for now but may well just give up on console one as I’ve gone from one issue to another with it and had to redo mixes so many times.
1 Like
Hey - thanks for posting back… I see what you mean; interesting…
As you say, I need to experiment myself really - hopefully at the weekend… 
Seems like some kind of threshold setting would be good to have for the Audio Segment detections?
A post was split to a new topic: Score Editor 14.0.20 update missing items
Excellent, thank you for that excellent job.
I can confirm the results above regarding the Audio Detection Range.
I have been trying different audio loops, with separate drums, bass, percussion, all of them quite clean, stero and mono, and the new tool fails detecting almost every hit or note, missing the beginning or the end of the hit or note.
It is funny because for an “imperfectly human” nude eye it is so simple and clear to detect where the note/hit begins and end, but the new tool in Cubase gets fooled all the time.
Theres is a provisional solution, however, which is to click and hold in order to select the missing slices of the note or hit you want to modify. This works pretty well so it prevents this new feature from being useless in its present state.
2 Likes
Drag-and-drop copying.
Where did the settings go to change it to something other than alt key? I have been having a lot of trouble doing that since 14.02!
I thought I could do it from the tools settings in the preferences before.
Can someone please help me?
BUG:
The update broke the recognition of my Softube TSAR1 plugins (ilok)
Got this error that no valid license is found.
The plugin, so the license, still works in my Wavelab 11.
Thanks for fixing it.
For now looking for a way to install the old version again.
kr
I have no problems saving remote scripts in Cubase 14 Pro (Windows 11)
Damn, Baby! You shoulda warned me. That’s just too much sexy for a .0x release. Cheers. (Assuming everything works as advertise. )
1 Like
Thanks for that workaround, @Santiago_Galan !
In terms of keystrokes, user attention requirements, etc. - does that bring anything to the table beyond what we had in previous versions of C14 - just use the range tool and adjust volume of the range with the little node at the top as in previous C14 versions?
Thanks!
Closing projects in Apple silicon is now 10 (?) times faster, thats really great.
Thx
Well, before you had to really select by eye from the beginning to the end of the note/hit, now with this new tool, Cubase does it for you, only that not in one perfect piece, as promised (yet) but in two or three slices. But it is really faster than the previous you mention.
2 Likes
For several years Cubase Pro (12/13/14.0.10) on my PC (Win 11) rarely shut down properly and on the next start I’d get the safe start option window/send the log file. It appears after this 14.0.20 update it closes down and starts fine (noticeably faster).
If this continues I will be very happy and the updates are very helpful.
1 Like