* No step designer, apart from that abomination "beat designer" A good example of OLD workflow ideas stuck in the past. * Drum Maps - Have you ever tried creating one? It's the most arse-about-tit way of doing anything. * EQ - if you drag the nodes around enough, it'll lock you from actually clicking anything else until you move the node again. It can also become very slow, when right clicking on any preset to "view in explorer". It sometimes fails to save the changes correctly. * Media bay - needs a complete re-write, it's buggy sometimes when trying to batch change info on presents. It's ok if you're only using about 30, but as you build up your preset bank, the media bay gets VERY slow at saving anything new. * Track Presets Saving - The more track presets you save, the slower it becomes to save them and wait for them to populate the Media bay. The workaround is disabling all your track pre-sets before saving them. * Track Preset preview - loads instrument tracks and samples on. * Track Archives - pretty outdated method TBH, workflow could be better. * Track Presets - can't save FX, Groups & Folders. Has been patched (to fix the broken graphics of C10) but still has issues occasionally when triggering. * Expression Map Editor - Most long winded and tedious way of creating simple keyswitches. * Snapshots - NO automation data gets saved making these pretty useless if you're mixing and used automation on plugins (which is mostly every session) Makes no sense to me, just pool your funding and recourses into one product instead of borrowing features from one DAW to put in another.Īnyway, a short list of things that annoy me with Cubase. There doesn't appear to be much need in having two different DAWs that practically do the same thing apart from one is more media / game based. My point is they should just focus on 1 product. I agree there is a lot to like in S1 (and a few things I am not so enthused about), but I can't use it for anything VI heavy at this point without freezing tracks a lot compared to Cubase. The other thing I have noticed is the record armed performance of S1 with low latency enabled (which from everything I can tell is the only way to play using the buffer setting instead of the process buffer size) is quite a bit worse than C/LPX on many instruments I have tried.
So if you are not testing until failure, you may well think S1 is doing better than Cubase/Logic based on the meters. I will cruise along with an indicated 50-60% CPU load and then, bam!, a spike that causes overload. you are good until the meter bar gets very close to, or reaches the 100% limit (and then you get crackles or error messages). In the case of Cubase and Logic, the CPU performance meters are reasonably accurate, i.e. One thing to careful of is the CPU metering on S1. I have a few torture test projects that I have run until audible overload, and S1 5.1 always craps out quite a bit sooner than Cubase (or Logic in the case of MacOS).
CUBASE ELEMENTS PRO DIFFERENCE WINDOWS 10
I keep reading comments that S1 is CPU efficient but my experiments on both MacOS and Windows 10 indicate otherwise. I recon a few more updates this will be a very viable alternative. Yet to dive deeper, but already really enjoying the workflow. I prefer the chord track in Cubase as it has more options. You can disable tracks like cubase, but there doesn't appear to be a freeze function, (will need to check the manuel).
CUBASE ELEMENTS PRO DIFFERENCE INSTALL
Apparently there's a script users have made but I have no idea how you I install it.Īlso I can't find a way to batch save multiple channels as a preset in S1.
Something I do miss is pressing the middle mouse button to scroll around like youre using photoshop. You can create some seriously complex signal chains that would take ages to setup in cubase. The mixer is also has a far better workflow, no clutter and the signal splitter is an absolute game changer for mixing. Appose to manually draging MIDI or trying to use quantisation to humanise a performance. Much more intuitive and allows for more realistic patterns.
The step beat designer is also a blessing for percussion because you have control over the midi offset using velocity layers. The only thing I'd like to see is the switches displayed in the lane (like Cubase) and also options for program changes.ĭrum map editor is also way better and super simple to create maps quickly. So easy to set up maps and save them to the instrument. So far the keyswitch manager is way better than the expression map editor. Already a couple things I prefer from a workflow point of view, but there are also a couple things I'd like to see.
0 kommentar(er)
