Kills me that v13 and older users are still SOL because this business models goes against the way it used to be w/ simultaneous updates.
They were limited to few but still felt like our purchase was solid.
No way I’m updating after trying the demo… It’s worse than 13 which is worse than 12 but IMO steiny knew that which is why they went against the normal update periods and doubled up.
I really hope these updates are working for people… because ignoring user requests eventually will come back and bite.
I’ve been successfully saving and importing my remote scripts in 14 ever since it came out. I had this same problem as you are with Cubase 13, but it’s fixed in 14.
Really like the audio segments selection feature, was not expecting something like that. And thanks for fixing the drum machine samples not previously saving to the audio pool.
I really would like to see the pattern editor advanced for melodic use too, Just being able to reverse the vertical order of notes would be a great addition. Or even if we could have presets for the lane setups would be nice.
Update seems nice and stable to me, which is always a bonus! Cubase 14 has a really nice feel to it overall in-fact, just want to say it’s been brilliant to use so far!
Audio Segment Detection will operate well on my system using the CTRL and SHIFT Key until I glue parts together on arrange page and then it stops working on those parts. (Audio Segment Detection)
I thought it might be because they are ghost copies of something but they still be altered if copied until glued together.
Might just be me, appogies if thats the case.
You have to open the part in the audio part editor e.g. by double clicking it. Then you get access to the events inside again and segement detection should work there.
I’m happy for those who feel this is a great update.
But as a producer who never use Score nor the pattern editor I feel there’s not much for us…
Many of the 100+ issues or feature requests that appeared in a recent wishlist post haven’t been addressed.
I’ll be digging deeper over the weekend and will keep engaging with the great community here, love you folks.
And already looking forward to the next maintenance update …
The audio detection range tool thing is a cool idea but doesn’t work that well. With pretty much everything it just starts at what it thinks is a transient but even with drums that do have massive transients it still manages to leave a slice of audio at the start of what you’re wanted to reduce the volume of. Sorry I’ve just woken up so not wording this well but yeah, basically it will not intelligently detect ‘‘full’’ pieces of audio. Even with silence before it. I imagine this will get teaked in another maitenence update. a great feature and very smooth looking too which is always nice. I look forward to it working well. For now, the improvements with clip gain that 14 brought right of the bat will suit me happily.
Is it not supposed to be different to hitpoint/transient detection though?
I think it’s purpose is to look for context within the audio clip to help us highlight words, phrases and complete drum hits. So where a word could have multiple transients it would select it as one.
I’ve not tried it enough to know if this is the case or not, but that’s how i’ve interpreted the information they put out. Because we can already do transient/hitpoint detection.
As the gain envelopes have not curves, there needs to be a bit of a threshold around the sections too, so we don’t get artefacts - that’s the biggest concern for me.
Oh, go on then… post a couple of (close-up) screenshots of what you mean, could you please.? As @skijumptoes suggests, the killer will be if any audible artefacts/glitches are being created because of it.
(Still haven’t updated yet; got some continued work come in, that I will finish with current setup first…).
