Search found 33 matches

I gotta be honest and say that -- while I would LOVE an internal replacement for the very clunky Vocalign -- I do not want any more new things like this from Steinberg at the moment. I personally want them to put ALL their efforts into the actual program/bugs/usability of C7/N6 at the moment.

This is really odd -- it's incredibly stable on my PC and I use almost exclusively 3rd party VSTs and VSTis on really huge sessions -- a LOT, from a lot of different companies. C 7.5 has been mostly perfectly stable for me (no more or less than 7, which was also very stable).

I wonder how we can find out why it's stable for some like me and not at all for others like the OP here?

It's truly an immense problem when doing mission critical editing/timing (i.e. with clients in the room -- I now use Pro Tools when I'm doing major timing adjustments with multi-tracked instruments like drums). Pro Tools timing stays perfect and intact during both playback and export, which is exactly how it needs to be. Period. It should not be any other way!

I would wait for Bitwig, which is coming out pretty soon. It takes what's great about Live and (from what I've seen so far) mixes it with some of what's great about DAWs like Cubase. It'll be the first version when it comes out, so we'll have to see what it's like for composing. No worse than Ableton, that's for sure. I'm also not sure that it will be as deep as Cubase in some ways. But I'm personally evaluating other DAWs to switch to, and am very interested in it.

I was thinking about getting Ableton too, until I saw feature request forum on the official Ableton forum. Reading through it I kept saying to myself "what? it doesn't have THAT ?!". Its just missing so many essential Cubase features there's no way I could ever switch over. I will say the two main features I really want from Ableton Live in Cubase is their macros (stackable quick controls maybe?), and something similar to Live's session view (at least an advanced Arranger Track).

I agree, and won't be switching to Live for those same reasons. That said, the workflow for some things in Live makes Cubase feel like ancient software, which is why I'm looking forward to what Bitwig might offer. The majority of major label songwriters I write with are on Live, and seeing them work I can see why -- it's simply lighting fast to get a song going and arrange/re-arrange/etc., compared to old school DAWs like Pro Tools and Cubase that are long in the tooth and have very fixed/linear ways of working that require a lot more clicking and fiddling in general.

For the final album cut mixing they will usually go into Pro Tools (Cubase for us), since Live is not as fully developed that way for someone who does very deep and complex mixes, though it does have some automation features that are much faster and more efficient than either Pro Tools or Cubase.

I'm sure some of you have seen me *witch* about the fact that Cubase doesn't seem to dump memory in between projects. To clarify: Let's say I have a large project that uses a lot of RAM/VSTis, etc., and then load up another large project. Even though I have 12 gigs of RAM in my PC, Cubase crashes. I remember a moderator commenting once that it was because of an issue with the VST3 system, which doesn't dump its memory from project to project if Cubase remains open, though I could be remembering wrong. This has been an issue for years now, and it's unacceptable for a pro piece of software to have to close the entire software then reopen it every time I want to load in large projects when I have an existing one open, or when I have closed the the existing project.

I have clients in here sometimes, and they have more than a few times asked me why I need to close Cubase then reopen it when going between large versions of a score, or different songs. Is there something I'm doing wrong, or a setting I can change, or something else I can do about this that I'm missing/don't know about?

Hit the following in order, in Cubase: Device Setup, ASIO (whatever the name of your interface is), Control Panel, then go to the Global page. All of it is done in Cubase, based in one window (the Device Setup window). If your interface has this option, it will be there.

Don't know why Cubase doesn't do this, but certain projects have very specific quantization settings with swing, etc., and it makes very much sense to have those settings be saved and then load up with every individual project.

MIDI notes, on both instrument tracks and instruments in the rack, often don't play right away on the first note of playback (of parts already recorded). On some instruments they do, and sometimes on the different instances of the same VSTi. It makes composing way too much of a hassle, and is such that I am going back to 7.5 (this only happens for me in 7.5.10).

Even more strange: When I open up any of the MIDI tracks (that are having initial playback problems) in the piano roll editor, they all play back fine, even when they're not soloed.

This happened a little bit in 7.5 with Retrologue and Padshop, but now it's happening with many other VSTi's, including some 3rd party ones. Man, it's a very, very frustrating experience these days with Cubase. The beta-testing shop is broken. :-(

Unfortunately we don't enjoy the amazing support (both in the official forum and their individual customer support) of DAWs like Reaper. 'Tis a bummer, indeed...but my guess is that they simply don't have enough staff, or enough money for enough staff, or who knows what.

Lots of good fixes, and just as stable as before (which is a good thing). Well done, Steinberg. And THANK YOU for a button for "Automation Follows Events". Little things like that help with workflow. We still need less clicks overall, especially in the mixer, but hopefully that will happen in the next update. The eye candy stuff is not to my favor either, but I'm used to the mixer now and simply am hoping for further refinements.

Of course, there are plenty of things still to fix, but this does has a lot of much-needed improvements. I hope that in the next update we will not need to still turn off ASIO Guard for some specific VSTis -- unfortunately that problem is still there, in that the notes don't often play right away with many VSTis that have ASIO Guard on.

Yes, I tried it the day it came out. Fantastic ideas and workflow -- even in the beginning I was zooming around incredibly fast on it, and it's very modern and up-to-date with the way its windows work, and other areas that make for super fast workflow. However, it's still in its beginning stages and is not ready for prime time yet, as far as I'm concerned. There are some bugs (naturally) and some features (such as multi-output for non-Bitwig VSTi's and support for VST 3) are not in there yet. They will be, just not yet. But in many ways it's "new world" thinking, and it's super fast and smooth, though not as deep as Cubase in some ways (such as complicated mixes, and some more). I do think that Cubase could borrow a lot of the forward-thinking features in it, though, without a doubt.

The funny part is that the interface wastes more space, and provides FAR less information. I don't loath the "look". I loath the functionality. I want to look at the mixer and see the information.

YES. You nailed it. Way too much clicking and fussing about to see all the things you could at the same time on the previous version's mix window. Clicking all of the time is not "pro" in any way, shape or form, especially since it doesn't need to be that way. It looks fine -- it's just not designed well in that way right now.

And - for the record - people like Tp3 are not trolls. They have an opinion. Someone is not a hater or troll if they simply disagree with your opinion. Period.

Because it complicates matters. Just set auto-backup for every minute if you are making that many mistakes. I don't need it and I don't want it. It just adds things to the undo list I will never need.

Aaaaand again: it has nothing at all to do with "making that many mistakes". Come on, now.

If you read what people have been posting here, you will see very clearly that we're proposing a separate undo list for the mixer, or the ability to hide mixer undos from your main undo list. Then you'll never have to use it if you don't want to, and the very large majority of users who would want it will have it.

Man, forums are weird places. :D But I'm done here. I'll place my bets that Steinberg will at some point listen to the huge amount of requests for this over the years!

This has been a long, long, long requested feature, but to bring it up again:

PLEASE let us see the names of our Sends in the automation lanes. With projects that have large amounts of sends, this becomes a gigantic issue that very much impedes workflow. There's a good reason why so many have requested this simple feature over the years. Please fix this as soon as possible. Thanks!

This is an area in which Pro Tools and many other DAWs are superior to Cubase.

Here are two solid ideas to implement this now:

1. " Mixer Undo" with a separate "Mixer History" and a mod-key undo/redo -or-2. "Mixer Undo" inside the regular history with the option to "hide" the contained "Mixer data".

The ability to undo moves, etc., in the mix console window is a professional standard and an absolute necessity, especially because of how easy it is in the new mix console GUI to accidentally change things. Please bring this to the next update. Thanks!

Due to the new way the new mix console is implemented, it's far easier to accidentally move a fader, send level, etc., etc., than it was before. Aside from that, undo for the mix console is something that has been long overdue, is very often requested here, and is very much needed in order to compete with DAWs like Pro Tools and others. In the Cubase thread many people had the fantastic idea to have the mix console undo history be separate from the project window, and to be accessible by a mod key for undo/redo.

Undo/redo for the mix console is a 100% must for Nuendo 7. Thanks for listening!

I don't mean this in an aggressive way at all, but Pro Tools 11 gets more and more attractive from a GUI perspective (it's very professional-looking and very consistent, with just as many functions), as Cubase gets more fuzzy and inconsistent and illegible.

I use the pool far more than I use media bay (and I personally almost never use the newer inflated instrument rack), and to me it seems like a very wise choice to have the pool be visible as a docking window like it is Pro Tools. This is essential to the way many work in both post and music. All Steinberg would need to do is add it to the choices currently there (which are Instrument Rack or Media Bay).

I tired writing this, but ... why windows docking can't look and behave like Studio One 2 ? Why Steinberg want to do things better then it already exists and good working ? Is it an ego or something ?

This is what I never understood, either. Plenty of other apps (including plenty of other DAWs) have had great window docking and management for years, on various versions of Windows. Strange that Cubase has always had issues.

This has been mentioned since C7, and surprisingly was not remedied in 8. Seeing the values of things like input gain, LPF/HFP, etc., is integral to workflow, whether you're a pro or an amateur. Visual feedback is key to modern DAWs, and this is very easily fixable in Cubendo...just have the values not be a hover pop-up, but instead always be there.

Despite those who are not having issues (and I'm sure there are plenty, just like there are plenty who are), I agree that CPro8 was not ready for public release. As I've said before: new releases always have bugs, but CPro8 really ups the ante with more problems than I've ever had on any DAW on any computer. I'm glad some people are not having issues, but even aside from the "issues", there are so many new and old basic design flaws that have been mentioned over and over again for years and still haven't been fixed. Loading up multiple projects using large amounts of RAM?

I love Cubase and really want to keep using it, but for the first time I am considering something else, not fully because of features but because I want to at least support a company that cares for its users and doesn't release obviously half-baked releases like CPro8. I never had any of the major problems I'm having with any previous version of Cubase, on a variety of computers (7.5 runs great on the same computer, by the way).

Do I sound bitter? Yeah, I'm bitter! CPro8 was promising on some new levels, and now I won't even use it until it's up to par with the stability, etc., of 7.5 (which had many faults, too, few of which have been remedied). This is not how to keep a loyal customer base, in my line of work.

Since Cubase is considered a pro application, the ability to import Apple files is a gigantic necessity in a world where literally almost everyone I work with in both the post and the music world are on Macs (I'm in Los Angeles). Yeah there are workarounds, but in an expensive, pro app like Cubase 8 Pro, the ability to import ANY kind of audio file is very highly important.

This has been a longstanding issue...please remedy as soon as possible. Thanks!

Hi, I really think Cubase needs to have better automation settings. FL Studio's automation is way more powerful, and the DAW is wayyyy cheaper. Cubase needs automation controls more like FL Studio, so you can draw smooth curves, and adjust the curves easily. I use automation ALL THE TIME on almost everything it seems, and it would be a HUUUUUGE help. I've been considering just switching to FL Studio mostly for their power in automation.

Surely, other people must feel the same?

Yes, Cubendo's automation is way behind the times in many ways, indeed. We're hoping that Cubase 8 will come with up-to-date automation editing.

I know this has been mentioned a million times, but I'm doing it again after being frustrated for the millionth time this morning on a time-sensitive mix for TV.

It's a big mystery to me -- why would anyone ever want to not be able to easily and clearly see things like input gain, filter settings, etc.? It's so much extra fiddling and time-wasting in a gigantic mix. Please, please, please fix this longstanding design error immediately. Whenever I mix on my partner's Pro Tools rig I clearly see how much I miss it. There's not a single reason to have hovering over such values if we can clearly see them without, which we can be implemented easily in this mixer design.

I don't mean to be shouting, but as a hard-working professional, things like this literally make a night-and-day difference in big mixes (I'm talking between 150 and 300 tracks). And on small mixes, too.

EDIT: Yes, there is the option to right click and see an extra row with the values, which is good. But this makes the mixer even more cumbersome to navigate around, as it incurs even more scrolling than the current mixer design involves due to the extra rows. It's not necessary at all to do it that way. It needs to be clean and take up no more vertical space, and can easily be done that way.

People: It's not the speed of the parameter coming up when you hover that's the issue at all. The issue is having to make the massive amounts of extra mouse movement when you have a big mix and often need to simply look at the mixer and see things like input gain. If you don't need that, fine, but please don't hurt the progress of making this mixer better for ALL by saying that you don't see an issue for yourself. Having this as an OPTION affects you in no way, so why not help the huge amount of people who DO want it by not being contrarian? There are plenty of features people request that I never have a use for, but I keep my mouth shut. And there are plenty of existing features that I personally don't use. So what?

There's a reason why so many complain about the hovering thing: It's a significant step backwards from the previous mixer (and no, I do NOT want the old mixer back!) as far as being able to quickly see what's going on without having to fiddle and putz around with your mouse.

I agree completely with lukasbrooklyn on this. When I use Pro Tools, and also when I see my production partner using Logic, I see how the navigation with Cubase is definitely behind. It's just as you mentioned - pretty much everything navigation-wise can be done with one hand on the mouse on those DAWs (especially Logic) and the other hand on the keyboard.

This would only improve Cubase -- there's not a single reason to be against it unless you happen to enjoy more clicks and futzing for these kinds of things, regardless of key commands (I have tons of custom ones as well and use them all of the time)?