I see. I hadn’t tried it yet. When I get a chance I’ll see if making one of the old-school device panels works. I think controls made in those show up as a VST parameter?
OK, I tried it with a simple MIDI device panel for CC91 and CC93.
Modulator doesn’t see “MIDI Device Automation” tracks at all 
It doesn’t see MIDI tracks either. We still have the old MIDI LFO insert though. It does essentially the same thing.
Fortunately these can all be considered minor bugs imho. Nothing where the entire program needs to be rewritten or anything like that.
I suggest you make a issue report for each of the issues separately. Yeah its a lot of work, but unless you do so Steinberg wont take a look into these unfortunately (its also a forum rule when reporting issues).
The clip gain video is not very clear though, don’t really understand what the issue is there by looking at the video alone.
Been using it for 15 minutes and I already have a list of like 5 issues to report… and I didn’t even use the new features yet.
I skipped C13 but luckily many issues from my C12 list have been fixed since. (because yes I read the changelogs even if I don’t use the version 
)
Now I have to review the whole list and create a new updated one I guess! It seems like the devs have put their hands on the list because I have seen some fix in the changelogs for some issues that very few people reported.
If they finally want to work hand in hand with us users then it’s all good.
3 Likes
Exactly this. Step sequencer and drumtrack were my favorite new features. After playing with them for 15 minutes, i was alreafy disappointed due to the lack of usability and features. They are worse than any 10$ plugin out there.
to add to the list for pattern sequencer:
Groove presets cannot ne used (where else if not for drum programming) only swing
No undo/redo
No copy paste on lanes
All tools are not working, eg muting a step, selevting etc
Patterns and events cannot be copied to other tracks
Drum track
No auto assignment of individual outs for drumpads
80s style gui, not resizing
Requested a refund immediately and it went through already. Feeling good now having dodged this marketing bullet.
Even worse, those are bad design decisions and not even bugs, so will never be addressed. But at least we have the 4th implementation of a half baked beat designer now. Literally it’s just putting beat designer into the lower zone
The existing drum event could incorporate all that, cubase is really losing focus by constantly adding so badly implemented features independent of existing functionality.
3 Likes
I thought maybe I had buyer’s remorse so sat down with 14 again last night to give it another go with fresh eyes. Unfortunately nothing had changed for me so I’ve just requested a refund too.
In previous updates I found at least one function that I used. I’m using literally nothing in 14 and it feels less stable that 13.0.42 which is where I’ll stay for the foreseeable future.
C14 is worth it for the modulators. Routing an envelope follower to a MIXBOX filter when playing guitar is pretty awesome.
The new FX, sequencer and Drum track won’t get any use for me.
Steinberg please address the key issues and requests on this forum in a C14 update that would be much appreciated.
I don’t understand. If you guys are so picky about when/if a dev team is worthy of a payday, why not wait a small time period to get the free time limited demo key?
Personally, I’ve preferred using plugins on a lean DAW anyway. I never understood the big deal over a ‘sampler track’ and ‘beat engines’ when Groove Agent driven by the diamond drum editor has been part of the bag forever (and one can actually go logic editor happy on such tracks), is much better, it lives out of the way unless you want/need to use it, and had the time spent adding a ‘special track’ been devoted to improving GA and marketing it as an attractive/viable plugin for ANY DAW instead…people would have ‘more options’ for a ‘leaner/meaner host environment’.
Still it is what it is, and it’s piddling money compared to things like tuning a piano, guitar strings, reeds, drum-sticks/heads, etc.
It’s even difficult to go hear 2 hours of live music these days for less than $200.
1 Like
Yeah… maybe they rushed the release, which is such a shame because in theory, on paper, the upgrades are good… My project kept on crashing when moving the channels in the mixer… one of the reasons I upgraded because it was annoying being unable to do it… Turns out it’s worse now, because it crashes each time… great work
1 Like
It’s not a case of deciding if a dev team deserves a pay day. Well actually it kind of is as I’ll pay them when I use their product.
It’s a case of spending money on something I’ll never use.
It’s not how much money it is either, once again it’s spending money on something I’ll never use.
It’s like I bought a sandwich, sniffed it then threw it in the bin. It only cost £3 but it was a complete waste of money.
We all use Cubase differently. I use it as a MIDI sequencer and digital mixer. I never use VSTi synths or audio tracks. There’s nothing in 14 that has benefited my workflow.
I’ve learned my lesson, I should have used the trial instead of buying the upgrade. As it is I don’t get to use Cubase 14 but I also don’t have to pay for it so that’s completely fine. I’m happy with 13 and will continue to use that. I’ll download the trial of Cubase 15 next year.
1 Like
I think the idea of the new drum instrument is great. Groove agent is wayyyyyy to overcomplicated if only want to use it to play samples and edit basic things like filter, sample length, pitch and so on.
Also, integrated windows make sense to prevent overlaps.
The final implementation of the drum instrument is not that good though. Too many small things that are bad. Not going to list them now.
1 Like
For me as a primary Windows Cubase user (senconday Mac user) The fact that cubase loads quicker, has full dark mode menus, full lower zome mix with movable channels in the mixer, the new clip gain/range tools and flexible external FX routing is enough to warrant the upgrate price alone.
I won’t use modulators or the drum machine much either but I"m glad they’re there for the users who can make great use of this.
M
1 Like
I paid them many years, every update, unseen - for a long time.
Wrt StepSequencer and Drumtrack at least, to be honest, such an experienced/large company not being able (or in this case not wanting) to develop something at least on par with other competitors or 3rd party products - this was done half baked by intention to have some buzzwords for their update and Steinberg was hoping to get away with it.
Furthermore, all those side-implementations are dead from start (so many examples like arranger track, midi plugins etc) and will receive absolutely no functional updates down the road.
There are multiple implementations for the same thing meanwhilst, Drum Editor, Beat designer, Step sequencer, Groove agent. With a bit more effort this could have been combined/extended into something really useful and competitive - a real DAW functionality, something with a strategy and future.
I felt somewhat scammed by their half baked implementation - its just not competitive and as such useless for me - at least partly I want the existing DAW to function better than before with updates, not letting everything die and pile gimmicks for sales. Happy to pay development any day, but won’t pay for this proceeding to go on.
1 Like
As I said I own Cubase (10.5), it’s an old love so I’m checking what is going on. I’m using Studio One and Ableton now. Not perfect but reliable.
LOL I just found out Drum Machine is just a bland copy of some Groove Agent code. Also here, Pads cannot be assigned to an output unless a sample is assigned. This is absolutely killing workflow, since one wants to set outputs for the 16 pads upfront - have everything nicely set up, not at the moment I drop a sample on the pad. What a useless piece of sw.
1 Like
I don’t think it’s that simple. I understand the frustration, but at the same time I don’t feel anywhere close to being ripped off. I can take a demo for a ride and decide if it’s worth $99 to stay up to date or not.
In contrast, I can’t do a darn thing with quite a lot of ‘other software’ if I don’t give them my bank account number, and agree to let them auto-draft three times that amount, either in one lump sum, or over a period of 12 months! To be honest, I don’t see the update/upgrade cycles of those products being all that superior. I am having ‘issues’, and ‘expenses’ incurred if I choose to ‘stay up to date’ with those options just the same. Some releases add considerable value to my personal studio, and others do not.
I do believe there might be some marketing pressure to pile these wiz-bang features on, and if it sells copies why not? Investors aren’t going to pour money into R&D teams that isn’t ‘leading to profit’.
Still, the past 3 - 4 years have been much deeper at Steinberg than tacking on shiny new gimmicks. It’s been a pretty intense ‘engine overhaul in process’ since the last Dongle-Ware releases.
Ditching the dongle alone meant they had to redo darn near everything! All of the instruments, the effect plugins, their libraries, the stores that sell them, the data servers that manage them on our systems, and more.
There are significant deep engine changes in the gap from Cubase 11 to Cubase 14. There have been huge changes in the tools used to compile and prep everything for distribution. Apple has forced the industry to abandon binaries that work fine on 99% of the existing systems in the wild with their native silicon (Rosetta won’t be around forever…Apple doesn’t want to license rights to put it directly on the chips, nor to keep supporting software emulation), and more.
Since Steinberg has had to redo so much from the ground up anyway, they’ve also taken the opportunity to support yet more processors and OSes.
The dongle is gone now.
The ‘grand old DAW’ has made considerable shifts towards ‘newer technologies, and ways of doing things’, while also attempting to maintain high degrees of legacy support.
The foundation is now in place for entirely new Notation/Engraving technologies.
Steinberg is taking a quality hit on a few things right now (mainly in legacy support areas)…it’s true, but at the same time they should be establishing a position to not only ‘catch up’ with some of the newer ideas and workflow options, but ‘leapfrog over them’.
It’s a rough patch right now I think as the industry tries to move beyond the limitations and expectations of 50-year-old platforms and protocols.
Computers are being designed differently now. The OSes are changing, and the tools people use to develop software are changing. Some of the changes might well be stupid moves, but Steinberg doesn’t control all that. They do have to deal with it though.
7 Likes
Thanks for the important bug report,
Thank you for the important bug report.
I’m sick and tired of it!
Please also add a bug in the toolbox that comes up when you right click.
When I hover the cursor over the line tool or other tool in the toolbox, the dropout menus for straight and curved lines and curves do not appear.
This is a really bad bug that makes even basic functions unusable.
1 Like
Update: mouse roll-over issue… I noticed that when opening up Nuendo13 projects in Cubase14 there was no problem. Turns out midi controller mapping from Cubase13 was ng in Cubase14. Took the time to manually re-program the mapping then no further issue with mouse roll-over. Saving, exporting and importing midi controller scripts only blasted out the previous mapping but didn’t add any mapping to the controller. So it seems with each new version, midi mapping has to be re-programmed. (APC40 MKII)
1 Like
I find it hard to believe that all these issues being reported were not caught in Beta before release. I can understand missing some, but this is ridiculous, to the point that I’m considering missing a version if it carries on like this. Users do not expect to pay out money for a product full of bugs, not great for client retention or the brand.
3 Likes
Bug in the toolbox that comes up when right-clicking.
The dropout menu from the line tool no longer appears and I can’t select various lines. Are these not bugs but specifications?
Is it a bug due to my environment?
Is there anyone using 14 who says the dropout menu comes up from the right-click toolbox without problems?
1 Like