Please take a moment to vote let us know how you feel on the latest one!
Here's the result of our first poll ~40 pro users:
60% felt the app was acceptable or better but 40% felt it was flaky, at best.
The following discussion regards a topic that is relevant to Cubase 7 and it's professional users.
Cubase is an amazing DAW. Like all programs, it has a number of issues that need to be addressed. The amount/severity of issues may differ greatly on a per user-basis, based on their needs from the application:
It -seems- like 'recording engineers' (people who work primarily with pre-recorded audio) like the direction of Cubase more than people like me who are 'composers' or 'orchestrators' (people who create structures from the ground up -inside- Cubase.) The vast majority of improvements seem to be for people who are taking a 'song' or big sections of content and then massaging it into shape. More of a traditional engineer or producer.
But for -me- who -composes- in Cubase and want to very quickly try ideas, jettison them; edit the -structure- itself, the more features Cubase adds, the -slower- the workflow the basic operations of 'ranges' and 'windows' and 'key commands' have not really been improved in a decade. A decade.
ufoqbase wrote:people not affected are probably not a complete Cubase users [sic], I may think most of Cubase users could be happy with Cubase Artist or Cubase Elements especially under Windows. Because massive use of plugs and tracks creates a lot of crash reports and performance issues... Im force [sic] to remain on Cubase 6.5 under osx.
This thread is written as a query to the professional film/TV composers who use this app as their main DAW: that means, if you're reading this, you're a user of Cubase that demands top performance from your DAW.
Your avg. session stats reflect the baseline for modern film/TV composing: hundreds of MIDI tracks, a couple dozen inst. tracks, complex routings, etc.
As a pro-user, you require a robust app for your everyday work. The questions are:
1. Which factor best accounts for the lack of highly-user req. FR (feature request) ports and bug fixes in Cubase 7.X? (Please place your answer in the above poll)
2. What 3 issues stop Cubase 7 from being a near-perfect solution for you, a modern film/TV composer?
Let's have it out in the open: nothing more/less than an honest assessment of peoples feelings about this app and those responsible for it's development. If that's not relevant to Cubase 7, I don't know what is. (The last rating thread was moved to the lounge: viewtopic.php?f=198&t=51788)
Less marketing talk, more bugfixing. Less money rasing, more FR porting!
The following are a collection of posts and threads that address some of the most-wanted/ignored features. Feel free to add to this.
- • [Poll] Would you like to see true Bounce-In-Place in Cubase? viewtopic.php?f=182&t=43826 , Bounce In Place like "Bitwig" viewtopic.php?f=182&t=52338
• Anyone noticed slow project file saving? Cubase7.5 viewtopic.php?f=181&t=52069
• Layout and windows for multi-monitors: focus, always on top viewtopic.php?f=182&t=52062
• Cubase 7.5 Excruciating load times viewtopic.php?f=196&t=51381
• 7.5 keycommand focus viewtopic.php?f=180&t=51515
• Preserve mono tracks with Channel Batch Export viewtopic.php?f=181&t=51400
• Power Management - Monitor sleep not possible viewtopic.php?f=181&t=31145&hilit=monitor+sleep , Monitors don't go sleep after destined time in C7 anymore viewtopic.php?f=181&t=38605&hilit=monitor+sleep
But since 7.5 release, I have seen here :
- Again, a drastic increase of project loading times (and I thought that it couldn't get worse...),
- Projects .cpr file size of some users here growing from 600 kb (with 7.0.6) to... 4.5 Mb ! ,
- Content download and installation issues,
- Anormal spikes here and there with still as much resources used as before if not worse for some,
- And another feature removal without warning : no more grid when using freewarp.
And beside this (among several others...) :
- Still the dreaded and unavoidable white masked timeline cursor which, as I'm more than 50 years old, appears as two vertical lines without glasses, no matter the width set for it. A workflow killer by itself...
- No UI regressions fixes : still no replacements for the preferences settings that were in both 'Appearance/General' and 'Appearance/Work area' pages (the latter has just disappeared from 6.5 to 7), especially the ones involving the grid, the buttons and work area brightness. This with others UI quirks such as the behavior of the R/W buttons of the FX/Group tracks when narrowing them.
And, last but not least, the brand new preferences color scheme, which is anything but practical : you can't even copy a color from an item to another and there is not even a way (AFAIK) to do a savable basic palette of colors in it, this to avoid the more or less erratical clicking, trying to pick up the right color tone needed. But there's so much to say about all the UI regressions...
- No fixes for Generic Remote definitions in order to clearly support both :
+ soft takeover. It works, but only if you accept to edit manually the generic remote definition xml file. In other words, this feature is unavailable, using the UI of the 'Device setup' window and not documented...
+ NRPN support : this one is completely broken and I had to find a clumsy workaround using different MIDI channel number for each control to be able to use my MPD32 endless knobs. I sent a support ticket to Steiny about this more than one month ago, and still waiting for any feedback...
This without talking about the still channel dependent layout, which means that you better think of it twice, before trying to add or remove a channel/track if plug-ins are involved in the currently active GR definition...
- No fixes concerning the key commands behavior issues with the MixConsole focus,
- No improvement of the RCE (absolutely useless with generic remote handling ; this thingy was naively one of the main reasons to purchase C7, one year back...),
- No improvement of the ASIO guard,
- Still the same click fest in the MixConsole,
- Trackpresets are still unusable with multiouts VSTis.
So, basically, more or less useful features added again, leaving more and more things half-baked, this with unwanted regressions and changes. Seems like Steiny is engaged in a headlong rush and I'm increasingly fearing what the future will bring.