Search found 62 matches


Re: Mac-osx to win7-64 bit migration

after so many usage mac osx I'm thinking of upgrading to Win 7 64 bit.
prices of apple in value performance no longer justifies the cost of a mac ... :?
I ask you of the forum .... :roll:
Tips for a daw with cubase 7 on win 7 64 bit.
components, the stability of the system, your impressions ...
Help me
thanks :D

I did this exact thing for these exact reasons.

Zero regrets.

The performance boost you'll enjoy is on 6 fronts:

1) It new hardware so it's of course faster than what you currently have.

2) Price-performance is better with PC. Whatever you get with the money you spend, it'll be faster.

3) Modern CPUs are very overclock friendly. Motherboards from, for example, ASUS, come with built-in overclock profiles that can be chosen with a simple menu selection in the BIOS. So your faster hardware will be faster still, because Apple doesn't provide any tools to overclock. Can you overclock a Mac? Sure, but it's tricky and unsupported. With the right Motherboard purchase from ASUS, they'll actually support you OCing it. They have a phone support of technicians called "Overclock Engineers" (I'm not making this up) that will walk you through it for free. It has to be on their "OC Supported" list -- so call them first and find out which ones are.

4) Cubase performs faster, all things being equal (same hardware), under Windows.

5) Windows ASIO performs better at low latencies than OS X Core Audio -- this is well documented over at Dawbench (an old article but still applies)

6) VST Plugins, by many 3rd party vendors tend to be more optimized than their AU counterparts. The affect of this can add up. I have not heard any complaints of the reverse being true, but there are probably instances.

The net effect of all of this will astound you.
by Jalcide
Fri Dec 20, 2013 2:29 am
Jump to forum
Jump to topic

Re: Can Cubase 7 use all 12-cores on the new Mac Pro

Planning to get the new Mac Pro, but the clock speed vs cores are a bit confusing to me. Is there official statement from Steinberg about this?

So if I were to get the 12-core, would Cubase 7 use all those cores or would it be a waste of money? Would the 12-core run more plugins, VST instruments and audio tracks than the 6-core with higher clock speed?

Yes, Cubase will "use" all the cores.

On these PC DAW choices, Cubase is second only to Reaper in its ability to scale across processors. Sonar is the worst at this. Studio One is in second to last place.

On Mac, this changes to somewhat of a tie between Logic and Cubase (Logic winning most of the time), Reaper still taking first place. Studio One last in place.

This was sort of a quest I was on last year. I recreated a very large project in all these DAWs.

Even though Reaper won, I just couldn't use it as my main DAW for nitpicky reasons.

Anyway, the real answer has to do with how you use your DAW.

For example, in Sonar, if you use many live effects on the stereo bus -- what it considers a "serial signal path" -- it will only process what can fit in ONE CORE. It can't split that up across the other cores, free as they may be.

Reaper, in this same example will do it perfectly due to how it does its "audio buffer scheduling / slicing."

Back to Cubase: I'm not sure, but it seems to do better than Sonar in this use-case but not as well as Reaper. So I'm not sure how much it suffered from this limitation that's confirmed in Sonar.

What's not a "serial signal path" from the DAW's standpoint? Well, that is probably unique to each DAW. For Sonar it's been confirmed that any VST instruments on individual tracks, escape the serial path and are now considered on "parallel signal paths" and then, in Sonar, can use other free cores.

How is this in Cubase? I was never able to really get an accurate answer.

One thing is probably true: while there are confirmed cases (Sonar) of DAWs, in certain use-cases, that can't muli-core scale, is the reverse true? Are there DAWs in certain use-cases that can only use part of a core and then seek out an unused core to jump to? I really, really doubt this. So...

To err on the side of caution, I think it would be better to have few, faster cores than more slower cores -- all things being equal. Obviously, in situations where the sheer number of cores provides more, total processing capacity, it has the potential to be a more capable machine.
by Jalcide
Fri Dec 20, 2013 3:05 am
Jump to forum
Jump to topic

Re: Coming to Cubase 7.5 from Nuendo 6 -- it's even darker.

I, for one, won't be fully satisfied until the UI for Cubase is so dark and neon-y, that it could pass as screen graphics for the upcoming TRON 3 movie. :mrgreen:

I think you just need to turn down the lights in your studio.

Kidding aside, what "buttons," specifically, are you wanting to brighten? I don't have a solution, I'm just curious.
by Jalcide
Tue Dec 17, 2013 9:09 pm
Jump to forum
Jump to topic

Re: Mac-osx to win7-64 bit migration

The main thing is to try to be as platform agnostic as possible, so I can be flexible. What really matters is getting the job done and paying the bills, folks. :) I couldn't care less about a silly Mac/Windows fanboyism on either side.


This is the quote of the thread. ^

(The fact that Cubase is dual platform has been a big factor in why I keep landing back in its seat so squarely, year after year.)
by Jalcide
Sun Dec 29, 2013 8:33 pm
Jump to forum
Jump to topic

Re: Mac-osx to win7-64 bit migration

Happy new year to you, too, and all! All unfortunate to be reading this thread. We, the mangy, disheveled, misfit, caffeine-wired, platform-debating, hunkered over our computers when we should be out, music computer nerds. :lol:

My New Year's wish is that this thread stay in 2013. :lol:

And if anyone has any tweaking tips for Mac, I'm all ears.

Boot Camp ?

Oooowwww, BOOM. :lol:

Sorry, couldn't resist and am totally kidding.
by Jalcide
Wed Jan 01, 2014 12:35 am
Jump to forum
Jump to topic

Re: c7.5 is absolutely ROCK SOLID

The most stable Cubase I've had in years. I'm quite happy.

How stable is it? Really stable when you consider what it has to contend with.

Stable doesn't have to (and can never) mean "perfect." No DAW or any software is 100% free of bugs even when it controls 100% of the code. Cubase has to host all our beloved 3rd party plugins, from all parts of the globe, from all manner of software developers with their own level of expertise, skill and ways of coding. With multiple formats of those plugins, no less. In dual platform, no less. We won't even mention audio interfaces, drivers, or the OS and its layers, itself.

No technology service guarantees 100% up-time. Not even Tier 1 technology providers that get to enjoy multiple levels of redundancy, that a single computer does not.

Even the hardware is not 100% crash-free at a quantum physics level. Naturally occurring radiation and cosmic rays will statistically crash a computer with non error-correcting ram as much as once per month, per gigabyte (if left on).

For our modern computers, which many of us leave on for days at a time, with our non-server-grade, non-error-correcting memory (just about all of us here), this would translate into 32 times a month (for a system with 32 gigabytes), or about once a day, that we could statistically expect the computer to potentially crash, regardless of software ("potentially," because not all ram errors would result in a crash, but many do).

I've even had hardware sequencers lockup and require a power cycle.

A DAW would certainly be in a top ten list of the most sophisticated desktop software products created by humans. I put it at the top of that list, due to how many 3rd party programs it hosts and the real-time, latency-oriented nature of it.

So, yes, Cubase is pretty darn rock solid from where I sit. I'm in awe at how many plugins it juggles and how little it crashes.

iTunes crashes more than Cubase for me. Which gets funnier the more you think about it.
by Jalcide
Sat Jan 11, 2014 7:06 pm
Jump to forum
Jump to topic

Re: Perceived Loudness and Mixdown Levels.

Not providing enough dynamic range for the mastering process is bad. Also, but not often discussed, providing too much dynamic range and not enough peak control on individual stems, is also not usually good.

A balance is usually best.

This is DnB not a -85 SPL film score. :D

But even a -85 SPL (K-20) film score needs dynamics and peak control. You can imagine how much anything else might need -- a lot.

Many engineers, myself included, have moved to K-Metering for tracking, buss / stem dynamics and what comes off the 2buss.

Alternatively, you can use Dorrough loudness meters, as its "20" and "14" are very compatible with K-20 and K-14, in terms of RMS weighting and min/max values, peak ranges, Crest and overall ballistics.

Bob Katz, "Loudness War" Grandfather, has even said that he would be delighted to get K-20 stems (that would naturally sum a few db hotter). K-20 is surprisingly "narrow" compared to how untamed tracks can often end up.

It takes a surprising amount of dynamics and peak control to get to K-20, even as wide as it is (and it's the spec for film, the widest of them all).

For DnB that's a bit too wide of a dynamic range, in my opinion. I would suggest K-14. James Wiltshire, and his engineering team, also recommends K-14 and has an excellent video discussing this:

Brainworx (Plugin Alliance) -- experts in the mastering process -- talk a little about this on their BX_Limiter plugin product page.

I also do modern electronic music styles, and lately have been enforcing a strict adherence to a "warm" K-14 stereo mixdown (pre-mastering / pre-pre-mastering) and it's working wonders on all my new stuff. Night and day, actually.
by Jalcide
Wed Jan 15, 2014 11:36 pm
Jump to forum
Jump to topic

Re: Perceived Loudness and Mixdown Levels.

very useful post that is, mate. cheers. when you say you like to make you mixes on the warmer side, what kind of PL are you looking at for your bounce before you send it to be mastered?

Thanks, glad to chat about this. It's my favorite engineering topic right now.

The K-Metering system has a small margin of wiggle room in it (not much). One can just tickle into the "yellow," for the RMS part, or could push it hotter well into yellow and pumping ever so slightly into the "red" zone (only during the loudest parts). I tend to do the latter.

Yes, my bounce / mixdown is K-14.

I do my own mastering, been studying it as a somewhat serious hobby for over 20 years now, and have a second, dedicated computer as a real-time master chain that i can mix into at the touch of a button.

It has several stages, each doing a small bit, until it levels up to the target "DR" number (Dynamic Range). I usually target around DR8 to DR6 for my final.

I've been studying a lot of Beatport releases, to see where they fall. I'm seeing a trend in the last year of somewhat of a Loudness War de-escalation. Some artists that were doing tracks as loud as DR4 in 2012, have pulled back to DR6. I think the faster tempo music trend (134 BPM and higher) is helping. Faster tempos can mean less sustain on a kick. Less sustain on a kick can yield a high DR number (more dynamic range). The "Trance-ification" of Electro and Progressive House, for example (or, the other way around. A.k.a. "Trouse"), is bringing those DR numbers up a bit. I think more artists are getting educated about it, as well.

So, K-14 is way, way more DR that one needs for these genres. K-12 might be better, but K-14 works well because it's more friendly to input modeled plugins, at its natural signal strength, without having to gain it down.

If you did K-12, you'd probably want to drop the gain a few db before hitting modeled plugins (unless you wanted the effect). Also, some mastering engineers might find K-12 a bit too hot for their liking. So unless you're doing it yourself, K-14 would be more compatible with most ME's workflow and signal chains.

I experimented with K-20 and also "18" on Dorrough meters and finally landed on K-14. There's a certain quality to it that just lends itself well to electronic music.

I think part of the reason is that it's a really hot "18" and -18db signal level is what most of these plugins model on the inputs. So, it just hot enough to tickle the circuit-modeled saturation on the plugins, but not too much.

Also, K-14's peak control tends to play nice with buss compression. It triggers it enough to get some desirable pumping, but is controlled enough to keep it consistent and polished sounding.

K-metering also speaks about the overall tonal balance and in some ways is a very good guide to how the track is equalized. In fact, a tilt EQ in one direction or another can often be what's needed to hit the desired target dynamics.

In other words, it's hard to screw up a K-14 mix, tonally, cuz when you do, it jumps out of the K-14 spec toward K-12 (or in the other direction of K-20).

Get some good meters and study your favorite artists and mixes. Then a/b with your mix, with a rough "mastered level" dialed in, and compare against the same meters -- use your ears and your eyes. Then, when you remove those limiters and it returns to K-14, you'll know what the mix should sound like at K-14 and will have more confidence that it can, in fact, get to the DR8 to DR6 territory. Don't expect to do this with one plugin or one stage. A few stages, each doing as few db as possible, is what will get you there (and what the ME will be doing).
by Jalcide
Thu Jan 16, 2014 7:38 am
Jump to forum
Jump to topic

Re: C7.5 Multithread processing performance experience?

This topic has been discussed quite a bit lately. You may find some additional food for thought here:

I share my thoughts on it, as well.

The short answer to the question is that there is an inherent battle, competing forces, between an architecture that's been built to favor low-latency, and one that's built to "schedule audio tasks" across multiple processors (cores). Each DAW does it differently. Cubase's roots in the low-latency end of this spectrum is why those of us who favor more plugins over low-latency, are feeling unsatisfied.

There are other DAWs that have chosen a different design, that suffer less, but more in other areas and vice versa. Cubase was second in my test of DAWs I own (in multi-core scaling).

VEP on the same machine circumvents the issues because it gets its own cores to work with and has a different audio engine design than Cubase.

Cubase's anwser to all this is ASIO Guard. Clearly, not as aggressive as many of us would like, but it's version 1.0.

Hopefully, awareness, like these posts, will bump it up on their priority list.

I think the future is definitely one that requires ASIO Guard to be in a "Reaper" ballpark of how it schedules audio slices across cores and makes more use of modern, multi-core CPUs. Cubase does use them, but is hampered by its ASIO, ultra-low-latency roots.
by Jalcide
Wed Jan 22, 2014 7:01 am
Jump to forum
Jump to topic

Re: Cubase 7.5.20

I bet we see a farewell to the legacy MDI window system and a complete revamp in v8.0. Just a hunch.

My guess is that it will continue to become more of a scalable UI, like the console is becoming, have full touch support and lots of flexible, dockable areas. Floating windows and z-order will still be present, but a focus on a more modern, z-order-less workflow will be the focus.
I look very forward to this !!! I really wish for more tight midi especially using VSTi to route midi signals and be tight for very fast beats

5.5.20 so good news.. thanks for listening to us SB!!!

:mrgreen: :mrgreen: :mrgreen: :mrgreen:

ps I bet most of the fixes are related to Windows, but other wise 7.5 is so stable I cannot come here and compain too much cus busy mixing music><

Timing-wise, for audio, Cubase should be sample accurate at whatever sample rate it's running at and would null-test, no?

For MIDI, internally, it's something outrageously high like 1920 PPQN, since like the late 90's at least, I think. Automation, as well.

I think the only "timing" thing (not really a timing thing), and that plagues all modern DAWs, is the whole VSTs rendering slightly different each time, which is why a lot of producers bounce to audio (and why Cubase's missing "Bounce In Place" feature continues to be high on the wish list). This is an issue inherent with most plugins, themselves.

Describe more of your timing problems, I bet it's a non-cubase issue (DPC latency checker issue, perhaps). I bet it's VST multi-rendering (or freezing) phase issues.

Try printing those tracks to audio and I bet the issue goes away. Or, try triggering raw samples via MIDI without any effects, I bet it nulls consistently.
by Jalcide
Sun Mar 16, 2014 8:11 am
Jump to forum
Jump to topic

Re: Cubase 7.5 MAGNETO II sounds wonderful!

I just tried Magneto II against a drum buss -- it's good!

A very smooth, clean drive.

It won't get "nasty" (in a good way) like the Waves J37, but if a more subtle, woody drive that leaves the low-end mostly intact is needed, it delivers warm, crisp character.

I'll definitely be using this.

Thanks, Freddie for bringing attention to this!
by Jalcide
Tue Dec 24, 2013 8:26 am
Jump to forum
Jump to topic

Re: 7.5.20 Impressions...

Guess I have some digging still to do.

Yeah, I'm attempting to solve all my 3rd party plugin issues once and for all. New computer just for DAW, fresh Cubase install. Testing each plugin, one by one. If it crashes during install, use, during scanning, during plugin window updating or on close of Cubase, that it, it's gone. I will do zero troubleshooting on it. Cutting my losses and moving on.

So far, I did find one rotten apple in the bunch. Loved that plugin, too. :cry:
by Jalcide
Thu Apr 10, 2014 6:58 pm
Jump to forum
Jump to topic

Re: 7.5.20 Impressions...

@Jalcide - out of curiousity, which plugin was that ?

Mathew Lane's wonderful, DrMS spatial processor (basically a M/S control on steroids). Version 4.0.1; Windows, 64bit VST version; running under Windows 8.1 x64.

Such a great plugin, but I do have many other plugins that offer enough methods of M/S control, to cover my bases.

It'll probably take a few more days, but glad I'm doing this exercise.

Btw, this is under 7.5.10. I'm doing this refresh before the 7.5.20 update so that I have a clean 7.5.10 to revert to if .20 causes problems.

Painstaking, but once it's done, it's done -- I'll never have to do this again, cuz I've got a system in place now to image my drive before each update.

That's exactly what i done last year , no other programs on my comp apart from Steinberg Cubase and Wavelab, Halion 5 , automap , UAD and a few very good plugin's and i have ZERO issues with loading and saving . Best move you'll make ;-)

Great to hear. Yeah, that's what I'm thinkin'.

Time to cull the herd and start from a place of known stability.

A computer that one has to update for work and other things is almost impossible to "snapshot" in a way that could actually be restored to, without too many other considerations. But a dedicated DAW computer -- no problem. Nothing important happens on it except the project files and sound libraries, which are saved on other drive(s).
by Jalcide
Thu Apr 10, 2014 7:13 pm
Jump to forum
Jump to topic

Re: 7.5.20 Impressions...

Great to hear. Yeah, that's what I'm thinkin'.

Time to cull the herd and start from a place of known stability.

A computer that one has to update for work and other things is almost impossible to "snapshot" in a way that could actually be restored to, without too many other considerations. But a dedicated DAW computer -- no problem. Nothing important happens on it except the project files and sound libraries, which are saved on other drive(s).

Im still running the same machine as you and because it's so dedicated , no other Daw software to conflict with it runs like a dream , no crashes , i use Camel plugin's and Alchemy , Sugar Bytes , Ill formed ,sonic charge , fabfilter and this 3770k with 32gb and SSD's and this thing flies for 7 hours a day ;-)


Cubase, since 7.04 has been amazingly stable for me, 3rd party plugins aside. But I'm looking forward even more stability with plugins and peace of mind when updating. Waves v9r15 took me out of commission for several months. I was especially busy with day job, so it worked out, but I can't let that happen again.

Ha, just noticed Waves release v9r18 yesterday. Here we go again. This time, I'm ready!

I need to update my signature, this new dedicated DAW is actually a i7 4770K. Too early to tell, but it looks like it will be beating my overclocked 3770K, even without much OC -- slightly. I think the floating point is getting better with these new processors (finally). The 3770K is still a beast though, no need to upgrade for that alone.
by Jalcide
Thu Apr 10, 2014 8:50 pm
Jump to forum
Jump to topic

Re: If you like the 7.5 update...+1 this and reply


The usual false starts with 3rd party plugins and prefs, but sorted itself out. A timely release, core-oriented, strategic step forward for a reasonable price.
by Jalcide
Thu Dec 05, 2013 5:35 pm
Jump to forum
Jump to topic

Re: 7.5.20 Impressions...

All I had to do with Reaper was download the White Tie Imperial Theme.

If only Cubase looked like that, genuinely thinking of jumping ship after seeing this.

Yes, it's very nice. As are a couple other themes (RADO is another one I'm using).

The problem is that it has zero hope of ever becoming "resolution independent" across Retina (and PC equivalents).

Not a big issue now for most of us, but it already affects Apple / Retina laptop users.

I'm glad to see Cubase taking these future-proofing steps toward a true, scalable, razor-sharp, resolution independent UI, but there are tradeoffs: growing pains.

A lot of the complaints about font sizes and clarity are likely a causality on a larger battle Steinberg is waging for us, behind the curtain.

I know it's not an easy battle for them, as they used to be king of the pixel-perfect font thing (one of the reasons I gravitated toward earlier versions) -- so their designers definitely "get it."

Having the pixel-perfect, almost photo-realistic look and having resolution independence is really hard problem to solve.
by Jalcide
Tue Apr 15, 2014 3:50 pm
Jump to forum
Jump to topic

Re: Side Chain architecture question

I create SC "broadcasting" arrays of group channels, usually about four of them: SC (Part 1), SC (Part 2), and so on. Each feeds into the next to create a single long chain of side-chains. The 4 chained channels just null-terminate (they don't connect to an audible output). This gets around Cubase's horribly arbitrary and outdated 8 send limit.

The 4 new group channels (that act as one), each with its 8 slots for sends, combine to a total of 32 sending areas.

Now, just send your kick to the SC (Part 1) -- it will flow through all 32 slots. You'll have 32 slots to play with, to send out to the various group channels and stems with your Pads, Noise washes, Risers, etc. I mean, a little SC on just about everything, is not off the table. :mrgreen:
by Jalcide
Sun Dec 29, 2013 10:09 am
Jump to forum
Jump to topic

Re: 7.5.20 Impressions...

Are you guys still talking about the freakin' mixer?! (kidding) :D

I'm finally back up, on 7.5.20 with my new DAW build.

I had to do a from-scratch install of everything (you know how long that can take) in Windows 8.1, only to find 8.1, several plugins and Cubase wouldn't play nice.

So, I had to start all over from scratch with Windows 7.



But, it solved most of the 3rd party plugin problems.

Since Microsoft doesn't sell Windows 7 anymore (except in some "replacement parts" department) it's nearly impossible to find a non OEM version of Windows 7 in the wild. So, I had to use the license from one of my other computers (that would be fine with my Windows 8.1 license). So, I had to setup another computer, too.

At some point there's gonna be some music making here, I think. :D
by Jalcide
Thu Apr 24, 2014 2:33 am
Jump to forum
Jump to topic

Re: How do you use dual monitors and Cubase?

Monitor 1 (first half of image) upper left and part of lower left: track metering (enabled via a send I put on each track).
Mon 1 upper right: track editor.
Mon 1 lower: arrange window.

Mon 2 (second half of image) upper left part of it: transport. Below that Mix Console for viewing VSTi's and FX.
Mon 2 upper right: meters, lots of meters. The first column of 6 Dorroughs are what my final 6 stems are, pre-fader; second column, post-fader.
Mon 2 lower: the final 32 stereo stems / subgroups.
Mon 2 far-right-side strip top and bottom: meters showing stereo mixdown, some gain structuring and a final Dorrough showing what goes to my real-time mastering chain (it also has the "2bus" inserts on it -- buss compression, limiters, etc.) That's on yet a 3rd monitor.

If anyone is interested, here's the full image:
by Jalcide
Sun Aug 17, 2014 4:36 pm
Jump to forum
Jump to topic

Re: Cubase 7.5 / 8 - 'Unlimited' Inserts


If I need that many effects, I just bake it into the part. Plain and simple and no drag on the CPU. I don't want them to alter the mixer if it is going to cause me any problems. They changed it a lot recently. For gawds sake just leave it alone. This is like picking at a scab. It's complex enough!

They've already laid the foundation with the new Mix Console's expanding / collapsing sections. So we already know how it would work. It shouldn't cause much confusion. I'm sure it could default to showing only 6+2 slots, like it does now.

As for drag on the CPU, that's what the freeze button is for. That way, we get non-destructive and don't have to print the effects AND get CPU freed.

And for those of us freezing, the number of inserts we current have is only 6 (six freezable).

Put a 3rd party virtual console at the end (common), now it's 5.

Put a 3rd party peak-check-limiter before that (also common), now it's 4.

If it's a vocal (or bass), or a synth part with untamed dynamics (pretty much every channel I deal with) an 1176 + la2a combo is common (and awesome) one-two punch for controlling dynamics. Now only two slots are left and we haven't even started with the real, unique, creative sound design stuff.

Basically, this pattern is common enough for me that I feel like I start with really only two insert slots to "go crazy" with.

And this doesn't even allow inserting meters or gain staging plugins. Ideally, I'd like to have a trim plugin between each plugin that doesn't offer its own output volume so that I can hit the next plugin the way I want -- not even possible in Cubase when I'm left with 2 inserts after my bread-and-butter plugins.

I've resorted to using Magma and it's a royal pain seeing "Magma" in every channel and having no idea what is what. And it uses more CPU.

Cubase is the only DAW in the world with so few inserts.
by Jalcide
Tue Aug 19, 2014 7:06 am
Jump to forum
Jump to topic

Re: [Solved / Unconfused] Set Definition from Tempo Confusio

Here is the recipe, to clarify, so that it might help others:
To tempo adjust a, say, a 127 bpm (even when it drifts and varies slightly) audio file to a 125 bpm project:

1) Import the audio file / drag to an empty track.
2) Select it and choose Project -> Tempo Detection...
3) Change that first time signature marker that gets created from its default 1/4 to 4/4 (if appropriate).
4) Temporarily change every other track in the project from Musical time base to Linear time base.
5) Select the audio file track and choose Audio -> Advanced -> Set Definition from Tempo...
6) Deactivate that new Tempo Track and/or delete all the events on it and set it to the original (or desired) tempo.
7) Change all the tracks back to Musical time base (as appropriate).

The imported audio file should now lock to the tempo (as well as all the other tracks).

Keywords: tempo detection tempo match tempo matching tempo editing tempo map tempo mapping beat detection beat matching detect tempo tempo lock analyze tempo audio warp time warp timewarp audiowarp audio warping sync out of sync timing off time base timebase tempo-varying fixed beat beat locking
by Jalcide
Wed Aug 27, 2014 1:20 am
Jump to forum
Jump to topic

Re: CPU Usage

It's based on overall "ASIO performance" which is based on Cubase's ability to "schedule audio packets" across available CPU cores.

Enabling ASIO Guard helps in most cases. ASIO Guard is similar (speculation) to Logic's "hybrid" audio engine. Basically, some sort of pre-rendering happens to tracks that aren't "live / real-time."

Increasing the audio interface's buffer is the main way to improve this. Latency is the tradeoff.

The job a "audio buffer (packet) scheduling" is a complex one that all DAWs do slightly differently. It's a tradeoff of raw latency vs. ability to splits up the job across more cores.

Factors in the signal chain such as "serial" vs "parallel" chains, factor in. Live effects on the stereo bus are usually examples of the "serial chain" and tend to be the hardest to split up across cores, for most DAWs. Reaper being the exception.

Individual VSTi channels, that feed into the stereo bus, are often examples of "parallel" chains for some DAW (notably, Sonar). They can often be split across cores more easily (again, Sonar works this way).

The Reaper DAW is an example of a DAW that does the most aggressive "slicing up" of the scheduled audio packets across all cores, and is why it will utilize the most of a CPU of all the DAWs (and therefore most closely matches the Task Manager meters).

Cubase, especially with the new ASIO Guard, probably comes in second place.

As ASIO Guard improves, the VST performance meter will start to more closely match the Windows Task Manager meter.
by Jalcide
Wed Aug 27, 2014 1:33 am
Jump to forum
Jump to topic

Re: Generic Remote Problem

Generic Remote, depending on the ORDINAL POSITION of Group Channels and tracks, instead of some internal ID of that object, is just poorly executed coding best-practices.

Those objects should be key'd off an internal id, not an ordinal position.

There is no defending this.

It will surely change.

in the meantime, enjoy creating robust "static" templates with hundreds of unused group channels and you'll be fine. :roll:

But really, you will be.

Anything new "to the right-hand side" of the generic remote consideration, that's added, won't affect the ordinal position limitation.

So you can still grow your project, just not the Group Channels.

And, the good news is that Cubase handles all those "dead" dummy channels (that mostly go unused in such a bloated temple), without much CPU hit.

Such is the life of Generic Remote users.
by Jalcide
Sun Sep 07, 2014 3:50 am
Jump to forum
Jump to topic

Re: Backing up Cubase Projects to the Cloud?

Do I need some kind of server tech?

Yes. A Network-Attached-Storage device, is just that.

Think of it as a personal, local "cloud" of your very own -- that you control and with no size limits or monthly fees.

BTSync will run on the NAS and on your DAW (with internal or external drives it uses), keeping the NAS in sync with your DAW projects.

The NAS will also run services like Crashplan at the same time, so that it can upload those synced projects to a proper fee-based, online, offsite backup.

You might look at the ReadyNAS line of NetGear NAS products. I think both BTSync and Crashplan will work on the ReadyNAS OS (it sits on top of Linux).

Or, maybe there is a service pre-built into NetGear ReadyNAS that may work for you. I have not reviewed them myself, but there are a ton of them. I think Dropbox, Owncloud, etc. are available on ReadyNAS (as well as BTsync and Crashplan).

Or, roll-your-own NAS with linux, and any "cloud" type apps you like, if you're up for the technical rabbit hole.

I think these devices start around 130 bucks.

I'm simply using another PC with VNC (remoting software) and BTsync and Crashplan, because I already have a rack of PCs for audio, video and 3d rendering.

But a proper NAS is the "right" way to do it in 2014.
by Jalcide
Sun Sep 07, 2014 7:36 pm
Jump to forum
Jump to topic

Re: Problem with ADAT optical

I can at least confirm for you that I've sucessfully synced two Focusrite audio interfaces via ADAT without doing anything special except for setting the master unit's Focusrite driver to sync source "internal" and the slave unit's sync source to "ADAT."

I suspect it's not a setting in Cubase.
by Jalcide
Fri Sep 12, 2014 4:46 am
Jump to forum
Jump to topic

Re: Daylight saving changed = Cubase plugin rescan [again]

Hi there.

Majority of all plugins you referring to I haven't even heard about?

Like I said earlier I only use x64 plugins from major leading 3part manufactures like NI, Spectrasonics, WAVES, Steinberg, Nomad Factory etc. = zero problem with rescan.
I can rescan all day long in my studio without any issues.
I have also plugins from other serious minor manufactures like example Voxengo and LiquidSonics. All those manufactures have serious programming skills and all their plugins are build with help of C++.

So think twice before you install anything to your setup.
Its better to have 3 or 4 "real" legit bought professional plugins that work and sounds great then to install amature, free vst plugins that you can find by the thousands at KVR for Free.
I'm not saying that all are bad plugins because they are free but majoirty are actually just junk. Why do you think they are free?

So if you stop add free, crap and old x32 plugins to your setup you will not have these kind of problems. Adding cracked plugins are even worse.

I'm just saying so nothing personal aimed at you. I just referred to you post here but there are many other posts like this at other forums too. I just saying what all these problems come down to.

Best Regards

Not bad suggestions at all. Thanks for the reply.

I'm 100% 64-bit, too. I have the the main ones you mention, as well. All working fine. Of Fxpansion, only DCAM Synth is crashing, the others are fine.

Tone2 has been a repeat offender on my system, for some reason, for over a year now and they haven't updated in quite a long time, so I'm just cutting my losses on those two synths.

Spire self-resolved after a couple reboots.

There were also a few plugins that crashed and/or reauthorized, but ended up working after several reboots.

I do think the VST 2.x spec's validation, combined with all these roll-your-own authorization schemes is a slightly brittle system. The rescan tends to shine a bright light on it.

I do have a lot of plugins, I guess percentage-wise, only a small amount balked.
by Jalcide
Fri Nov 07, 2014 8:00 am
Jump to forum
Jump to topic

Re: Why Can't Cubase 7 Do Something This Basic?

I just gave a detailed answer on how to do this, on your other post:

Btw, can I make two humble and friendly suggestions?

First, a better post title may have been "Can Reaktor Send MIDI to a Synth in Cubase?"

Me, the person with the answer, almost didn't click on your post (you lucked out).

If I had seen "Reaktor" in the title, I would have clicked on it for sure.

Second, two posts asking the same question within a few days of each other is redundant.

Better to post one, well-named post and "bump" it yourself (add a new reply to it), if you have to.

by Jalcide
Fri Nov 28, 2014 6:36 pm
Jump to forum
Jump to topic

Re: Cubase 8 - coming soon?

The upgrade and authorization itself is very simple and straightforward. Also, it will not overwrite your current 7.5 and you still run 7.5 even after 8 has been installed.

So it won't interfere with your Cubase settings in 7.5, but also will not transfer over your old settings. So, you'll have to set up the VST Connection settings, audio interface in/outs, MIDI ins/outs, windows, preferences, colors, etc.

I'm sure there are clever ways to copy pref files over, but I wouldn't do it. Just start.

Thanks Jalcide,

So could I simply install the UPGRADE to ARTIST 8.5 and then uninstall my copy of ARTIST 7.5? Because I would not be requiring the latter anymore.

Also, do you think it will affect JBridge and my Groove Agent? Or will this need to be configured again please?



I would recommend leaving 7.5 installed for the following reasons:

- To ensure you can open any previous project (8 should be fine, but you never know).

- In case you need to reinstall the 8 update, having 7.5 may be required (I'm not sure, but to be safe).

- To help troubleshoot anything weird happening in 8, having 7.5 to test in would be helpful

- To avoid inadvertently uninstalling any shared content.

- And because content aside (which you could manually delete), it doesn't take up that much space.

Sorry, never used JBridge or Groove Agent, but there must be a way to export from GA.

That said, Steinberg is notorious for making it difficult to "get at" stuff. I'm not sure if there are prefs related to GA that would be lost (but could probably be moved over from an Xml file).

Not sure about JBridge, try searching Gearslutz and KVRAudio forums, but if it doesn't work, for some reason, there are many other options (DDMF Metaplugin, VSTForx, Nomad Factory Magma, Blue Cat Audio Patchwork).

If you find out anything, be sure to report back in the new Cubase 8 forum.

by Jalcide
Fri Dec 05, 2014 8:41 pm
Jump to forum
Jump to topic

Editable Frozen Files

Studio One style Editable / reversible frozen files.

But with one key attention to detail that Studio One overlooks, thus rendering the feature potentially useless.

Make sure that unfreezing preserves the Ghost/Alias/Shared MIDI clips and doesn't flatten them.

Ghost/Shared MIDI clips represent a lot of work and important structure to the project. To flatten them is tantamount to data loss during a freeze process.

The freeze process should not cause any form of data loss.
by Jalcide
Sat Dec 06, 2014 5:41 am
Jump to forum
Jump to topic

Re: CMC not fully supported in Cubase 8 !!

I just tested in 7.5 and it functions the exact same way: Arrange window needs focus.

May I humbly suggest, in good fairness, that you consider putting a [Solved] in front of the title. :)

Let's save our CMC abandonment anxiety wrath (for now) and hope that by the time our pitchforks and torches and sharpened and lit, we'll be on Cubase Pro 22, where the preferred method of input is holographic gesture and thought-control. :lol:
by Jalcide
Fri Dec 05, 2014 10:15 pm
Jump to forum
Jump to topic

Re: CMC not fully supported in Cubase 8 !!

It works for me, but only when the Arrange window has focus.
Could that be the issue?
Was that required in 7.5?
by Jalcide
Fri Dec 05, 2014 9:47 pm
Jump to forum
Jump to topic

Re: CMC not fully supported in Cubase 8 !!

I haven't update yet but I definitely will as soon I got the time.
Hopeful perhaps this Sunday. I'm really amazed what Steinberg has added to Cubase PRO 8.

Anyhow I have a question about the CMC Series. I have all six controllers and I wonder if CMC "lights" work in Cubase PRO 8 too? I heard that VCA faders doesn't work and get recognized with CMC FD and SSL Nucleus. I bet Steinberg fix that, not directly a show stopper for me. No lights on the CMC-controllers would be a more serious problem for me compare to the VCA faders doesn't get recognized.

Thanks in advance!

Best Regards

Hey, Freddie.

Yup the "LED Dimmer" checkbox is still there and works in Cubase Pro 8. I have all the CMC units and they indeed become softly back-lit, just like before.

by Jalcide
Sat Dec 06, 2014 7:26 pm
Jump to forum
Jump to topic

Re: Bug? Or Designed by Mephistopheles?

Yeah, I haven't found an acceptable way to minimize (and then restore) Cubase Pro 8 on Windows (7).

Clicking on its main icon (collection of windows) in the task bar doesn't work like with single-window applications, where you can easily toggle between showing and hiding the app.

There is no minimize in the title bar.

Right-click minimize puts it into the corner of the screen, but still leaves some VSTs visible (Like SPAN). Then once you give the background focus it does disappear, but then leaves redraw bugs on the screen that won't go away; the playhead line.

Then when you restore by clicking on the icon in the taskbar it comes back not not all of it. :lol: :roll:

Then, it's a game of "find the hidden window" by trying to see which window didn't restore and needs to be clicked on in the taskbar icon preview thing.

If Minimize All is chosen -- yay! all the windows go away and no redraw bugs -- but now all bets are off, there're chores waiting when you return: opening each of your Cubase windows, one by one.

Pretty maddening.
by Jalcide
Sun Dec 07, 2014 12:22 am
Jump to forum
Jump to topic

Re: Bug? Or Designed by Mephistopheles?

MickGael wrote:^^ 100 times this.

Hehe, thx.

Maybe you should change the title to something like:

"Minimize Bug? Or Designed by Mephistopheles?"

(btw, love that reference. lol)

So that it's more descriptive, but also stands out.

It would have some nice alliteration to it. :)
by Jalcide
Sun Dec 07, 2014 12:36 am
Jump to forum
Jump to topic

Re: re horrible AERO theme


It's bad enough I'm considering running Stardock's Windowblinds to see if it's at all compatible in a way to reskin the window chrome.

If I have any success, I'll report back.
by Jalcide
Sun Dec 07, 2014 12:39 am
Jump to forum
Jump to topic

Re: Editable Frozen Files

CubeDAW wrote:I agree. At first I thought it said "Edible Frozen Flies."


I hear the lemon-lime flavored ones are quite tasty.
by Jalcide
Sat Dec 06, 2014 7:58 pm
Jump to forum
Jump to topic

Live and Mixing Latency ASIO Guard Info Panel

It would be nice to have a clearly viewable area (perhaps in the Transport or Arrange window info strip) or a standalone window (resizeable / configurable) that shows what the current DAW latency is, ASIO latency and the combined total.

Show in both milliseconds and samples.

Both as live input (via ASIO Guard 2) as well as for non live inputs for general mixing.

Also, it would be nice to show which plugin is the current bottleneck (has highest latency).
by Jalcide
Tue Dec 09, 2014 3:25 am
Jump to forum
Jump to topic

Re: Still a maximum of 8 inserts per channel?


Pro Tools has 10 (!) inserts - for all (!) FX (incl. Phase, Gain, Lo/HiCuts, EQ etc <= as separate insert plugins!
And no one has complained about that.
Nonetheless, a few years ago PT has only 5 (!!) inserts...


Strictly speaking, Cubase has 18 FX (Pre section Hi/LoCuts, Gain, Phase, + 8 Inserts, + Channel EQ, + Strips....) = per channel.


There is a pretty huge difference between 6 (freezable) inserts and 10. Those 4 extra inserts would solve 80% of the issues I bump up against.

It's not unreasonable to have (brands of one's own choosing): console emulation, channel strip, peak-check-channel-limiter, virtual tape.

Now we only have two slots left.

It's not uncommon to use yet another compressor chain of an 1176 and la2a after the channel strip, so there's your "two more" with now all six freezable slots used up. So forget anything creative or crazy on top of just getting dynamics and EQ dialed in.

Oh, and forget trim controls between those plugins -- so hope the input drive modeling and gain staging works without intervention.

If I had 4 more inserts , in this example of six filled, that would effectively solve my issues (trim plugin gottchas aside).
by Jalcide
Wed Dec 10, 2014 6:41 am
Jump to forum
Jump to topic

Disable Track Should Disable Post-Fader Inserts

If saving CPU is a goal of the new Disable Track feature (and it is almost primarily), then it's incomplete by not also powering off the Post-Fader inserts.

If I have to do that manually, anyway, it sorta defeats the point of having the feature.

It also creates workflow issues when re-enabling disabled tracks. One has to remember if the Post-Fader inserts (that were manually disabled to save CPU) were supposed to be powered back on, or if it was just testing an idea and therefore disabled by choice.

In this small way, Disable Track is tantamount to a sort of "data loss."

I have a ton of volume shapers and filters in Post-Fader slots that are often experimental and in various states of powered on or off. So, Disable Track makes me have to write down or remember their states. Which I had to do before, anyway, for manually powering off all the plugins, but Disable Track is a missed opportunity to solve this problem, by remembering the states of everything before it disables.

I had a "you have to be kidding me" moment when I realized it missed precisely what I was hoping it would do. :lol:
by Jalcide
Fri Dec 12, 2014 7:44 pm
Jump to forum
Jump to topic

Enable/Disable Selected Tracks

Complete the singular "Disable Track" and "Enable Track" feature by adding a "Disable Selected Tracks" and "Disable Selected Tracks."

Also, these would get added to the Project menu which would have the desired side-effect of exposing them to surface controllers.

This feature idea was actually spawned from my desire to map "Enable Track" to a button on my QC controller. I was sad to learn it's about the only Cubase feature in this category not exposed via the Project menu yet.
by Jalcide
Mon Dec 15, 2014 7:46 am
Jump to forum
Jump to topic

Re: Is Reaper Any Good Compared to Cubase

I use Reaper as part of a real-time signal chain (it's got its own dedicated screen, even) and it has a lot going for it.

Mainly, the most muti-core efficient audio engine of any DAW. You'll get more tracks and real-time effects than any other DAW (literally). I've tested them all.

It loads projects insanely fast. It makes you wonder what in the world is Cubase doing when loading (even Cubase 8).

The interface, not the parts you can customize, are just too fugly and unintuitive.

A simple shift of a track forward / back in milliseconds requires one of its stock "scripted" plugins, in an ugly, bright grey, Windows 98 looking, separate popup window.

Everything feels like that to me in Reaper.

Very pretty skins available (mostly by one dude who has long since moved on from maintaining them or creating new ones), but not for much of the underlying parts and UI can be skinned, so it always feels inconsistent and kludgy.

MIDI features are no where near Cubase or Logic (this is the part where a hardcore Reaper user would tell me of some ugly, kludgy, 3rd party javascript plugin maintained by a teenager in Croatia that will do what I want. :lol: )

There's always like a huge list of updates, frequent updates, and new features and yet somehow, none of them ever seem to get me interested in switching to it as my main DAW. They're always very techie, fussy and seem to only excite the hardcore Reaper community -- which is HARDCORE and awesome.

And not techie in the good way. Not like Reaktor, Molekular, Logic Envirnoment, Cubase Transformer, MAX / MSP, etc.

Just ... fugly, awkward, techie. Like in that middle-finger kind of way that software that's trying to make "a statement" against corporate can be.

I think Reaper is 80% steered and tested by its community.

The other thing I just can't get past with Reaper: It still can't remember the window z-order of plugins on launch. That's a deal-breaker for me, as I use a lot metering and such, and pack in a ton of stuff that is window overlap sensitive.

It's a tough crowd, too. I posted on the forum about this shortcoming ... not one single response. No +1, nothing. :lol:

Very loyal and hardcore community (which I respect a ton).

But I swear, with some of the testing and animated screencast posting, etc. that community engages in ... some of them, you'd think it was their day job, they can't be makin' much music. Just sayin'.
by Jalcide
Fri Dec 19, 2014 4:38 am
Jump to forum
Jump to topic

Export Audio Mixdown Progress: Show Filename

Show the filename during the mixdown to assist in the engineer multitasking in preparation for the mix to complete.

E.g., looking at another screen from another computer for the file ... what file again, exactly?

Seeing the filename in the dialog would not cause any harm and would only be helpful from a workflow standpoint.

(Also, fix the progress bar so that it actually works)
by Jalcide
Sat Dec 20, 2014 9:31 pm
Jump to forum
Jump to topic

Re: How many actually use the Cubase EQs?

I don't use them, they're no where near precise, deep or featured enough, nor enough of them, for the kind of sound design I do.

If they added a tilt shelf, I might find a use for them.

And since I need a dedicated eq anyway, I don't bother cluttering my project with them.

They do have a nice, crisp, clean and distinct sound to them. I can always tell (or think I can) when someone does a Cubase EQ based filter sweep in electronic music. It does have a certain personality, I think.
by Jalcide
Tue Dec 23, 2014 5:37 am
Jump to forum
Jump to topic

Re: update or replace motherboard?

i would not advice any automated driver detection, since most of them i have seen ar all malware or close to that.

Why should you need a detection tool ?
The site is quite clear in what is needed for that mobo:

kind regards,

thanks for your answer roel, I did go to the site, when I click on the W7 64 bit area there is "a million" things there , some in red (which is scary) am i supposed to download them all ? do i install them in the order they are listed or does it not matter, you see my dilemma...I'm a "puter" idiot :?

best, Kevin

The best drivers are the one directly on the Asrock site.

I've never found order of installation to matter.

As long as you download the drivers in the correction section of the website, it's hard to screw up the installation.

I have two Asrock motherboards myself and have never had an issue with installing their drivers.

Just install some stuff, reboot, install more stuff, reboot, etc.

The BIOS (now called UEFI) updating with newer Asrock motherboards is even slicker. They have a fancy new feature that will download it and flash the UEFI directly off the internet from the UEFI, itself. It doesn't get easier than that.

I would do the UEFI first (if you are planning on doing that). Not a problem if you don't, just a good practice.
by Jalcide
Tue Dec 23, 2014 5:49 am
Jump to forum
Jump to topic

Re: Cubase 7 sounds better than 8 here at first sight

:lol: This thread ... Every year.

If DAWs are accurate enough for scientific signal analysis, and they are, they're accurate enough for our distortion pedals, noisy pickups and edm soundpacks. :lol:

Unless a project is nothing but rendered audio with pretty basic plugins, no two mixdowns will render precisely in the same version of Cubase.

Our modern, analog modeled plugins are rendering things like "loose resisters" these days (Softube reference).

All that said, I had an initial impression that Cubase 8 sounded better with my Cubase 7.5 project. This is of course not the case, but our minds fool us like this.
by Jalcide
Tue Dec 23, 2014 6:00 am
Jump to forum
Jump to topic

Re: What is threshold to trigger a clone?

But what are people's thoughts on how much it should take to trigger making a bit-for-bit clone? For example, before each weekly Windows update? Before installing a new UAD plug-in? Every 'X' days just because?

Thanks for sharing your thoughts.

I keep a dated log of what I've updated or changed since my last bit-for-bit bootable backup.

For me it's simply, when enough changes I'd need to perform on the bootable backup, to get to current, induces a "groan" even thinking about.

I've found this to be about a dozen items (a dozen plugin updates).

And then I always make a bootable clone right before a major release (e.g., Cubase 8).

If three months go by, but there haven't been much plugin updates happening, then I'm cool with not doing another backup.

In fact, the advantage to this is that it's even safer. Because in the event something unknown, but lurking, happened between my last image and current, I wouldn't want to unnecessarily capture it.

So wait as long as possible within your confort level of recreating the steps to get to current.

And if you keep a log, make sure it's not on the drive in question. :D

Here's an example of my most recent "logs" (what I had to recreate):

Changes to DAW1 since it was backed up on 2014.12.22 to "DAW1 BACKUP1" (the currently most recent backup):

2014.12.24 Updated Meldaproduction plugins to v8.10; Updated Valhalla DSP Valhalla Vintage Verb to v1.5.0; Arturia V Collection, installed / Updated to the V4 Collection; Installed latest eLicenser

2014.12.26 Installed Vengeance VPS Scope (Free X-Mas Gift, requires 1 Vengeance product to be found)

I've had this list get pretty long, this was such a recent backup that it was easy to recreate the steps to get to current.

Keeping logs like this helps in judging what would be too much of a pain to recreate.
by Jalcide
Mon Dec 29, 2014 6:36 pm
Jump to forum
Jump to topic

Re: Snow Leopard won't let Cubase Pro 8 run!

I don't think Steinberg should have to support anything an OEM doesn't (in terms of OS).

The real problem here was Apple arbitrarily and artificially crippling first generation Mac Pros, where they need not have.

It was a greedy decision.

I went through this saga with my very capable (to this day) 2006 Mac Pro Quadcore, with over 16 gigs of ram on it.

What especially sad is those 2006/2007 quad core Xeons were way ahead of their time in terms of floating point performance (what real-time plugins want).

That, and the fact that Intel had not, until only very recently, made significant improvements to floating point in their consumer-grade processors, puts that 2006/2007 Mac Pro on almost equal footing with 2010/2011 consumer-grade CPUs (in terms of floating point).

I had a real-time mastering chain running on my Mac Pro that only, finally, after many years later, would an inexpensive 2011 quad core PC could finally run the exact same chain.

It's still to this day very competitive at DSP.

C9sus4, you may want to consider running Reaper on it (which IS supported) and using it as a real-time FX chain (into Cubase), like I did.

Find and old MOTU audio interface with ADAT (or similar), and you have 4 stereo external FX to matrix between it and your new Cubase machine.

Or, use just its built-in 2-channel optical to offload your stereo buss and mastering chain duties (like I did).

Think of it as racks of gear in a shiny case. :D

Reaper runs insanely good on it and will really take advantage of all the cores.

[Note: There's a pref option in Reaper to use multiple cores for real-time processing (i.e., not during playback).]

by Jalcide
Tue Dec 30, 2014 10:45 am
Jump to forum
Jump to topic

Declutter/Clarify Mix Console Channel Selection Hitarea

I seem to always not select the channel, first time. I click on the "wrong thing."

I click on the Stereo/Quadro number area (why is this not a valid hitarea?)

Or I click on the Color Selector.

An Alt key for the Color Selector not only seems like a good idea to help solve this issue, but it's consistent with how the Arrange Window works.

Or I click in the Fader area, forgetting that for some reason it doesn't select the channel either, but instead moves the fader (with no Undo!), even though the fader, itself, wasn't clicked on.

The only other valid place to click is the Meters. Maybe it's just my brain, but I seem to have an aversion to clicking on them. Maybe because, when I do, there is a visual flicker that doesn't happen when clicking on the Channel Title for selection.

Bottomline: I don't feel like there is ever a correct area to select the channel. I always seem to have to think about it. And when I don't (brain focused on music) I often click in the wrong areas.
by Jalcide
Wed Dec 10, 2014 8:11 pm
Jump to forum
Jump to topic

Best Feature of any DAW: Save New Version

The Save New Version is the best thing that's ever happened to me, music-wise in the past decade.

I don't mean this as a back-handed compliment to Cubase. It's true with any DAW (trust me on this).

The fact there is a simple "Save New Version" in Cubase, without trying to be too fancy (i.e., delta versioning, like in Studio One, etc.), and the fact it's mappable to physical button that I can press with my left hand while my right hand is mousing around, is single-handedly allowing me to move forward with my music.

Between Cubase crashing, plugins crashing and my over-clocked PC crashing, because ASUS can't seem make it simple to OC, even with all its attempts at simplifying over-clocking. (My next MB may not be an ASUS). I have an equally taxed ASROCK that doesn't seem to blue-sceen, despite is terrible UEFI.

But I digress.

Computers, DAWs and all the moving parts exceed the most complex "sequencer," multi-track tape machine, SMTPE sync, and racks of external gear, I ever had in the 80's and 90's.

Thank you for "Save New Version."

I have Save New Version mapped to F3 on a backlit, Steinberg CMC AI controller. F4 mapped to Mixdown. Simple.

The fact the music keeps playing while saving in the background, is not lost on me. Again, thank you, Steinberg. It means a lot. Saving shouldn't come with any penalty.

If this feature ever goes away, I'm going back to 4-track demos using a drum machine and a keyboard.
by Jalcide
Sun Jan 04, 2015 2:02 am
Jump to forum
Jump to topic

Re: Cubase 8.0.5 is out...


Here's the executive summary: We all need to lower our expectations and be more realistic about what is possible.

For why I think that, read on...

First, thank you Cubase Team for releasing "early and often" (so to speak), rather than waiting for more fixes to be completed.

Hope you keep this trend going, despite the (understandable) backlash.

To me, this update is a real measuring stick. Here's why I think that:

Software development is really hard and requires essentially unfair personal sacrifice. And not just a "push," but sustained and ongoing pain that never ends. It's a way of life.

I've been in this business a long time and this remains true.

No amount of company Kool-aid drinking will make it happen faster. Stuff gets done when it's done.

Deep inside each developer is something they'll never admit to their boss, when their boss talks about getting stuff done faster because of arbitrary release dates and the financial pressures that drive them (the thing, at the end of the day, only a boss really can care about, truth be told). That thing is: "Understand, but that's YOUR problem."

The developer is already making a full sacrifice (and then some), if the company can't harness and harvest it, it's its problem, not the developer's.


When an end-of-year holiday software release has bugs, it's to be expected. Marketing desire will always outpace personal sacrifice. It's baked into the raw economic physics of it, itself.

One could argue to do otherwise shows lack of passion / ambition.

So I don't think Steinberg should be faulted for pushing for a release or even having bugs in it.

All that said, there is one thing that will push a developer even past this high level of personal sacrifice into a sort of inhuman "overdrive mode" (not sustainable even by those without families): Post-major-release bugs and poor craftsmanship. Because that IS the developer's problem.

It is fair to for a developer to feel this way even after being pressed to do more feature-creep? No, but I guarantee you every developer feels it and responds to it and takes it very personally.

Now to my long-winded point...

This 8.0.5 release demonstrates the true capability of the Cubase development team. We get to witness it in near real-time. 8.0.5 was pushed hard to get to. It certainly had at least one or two senior developers via "email-only" as they tried to enjoy their holiday.

What it tells me is this: Cubase is very complex software; decades mature. We're glad to see the update, but disappointed almost none of the "things we wanted" were not addressed.

It also tells me we all need to lower our expectations and be more realistic about what is possible.

This is specialized software that only sells so many units. For the Cubase team to scale up, just doesn't seem likely.

I think if there is one thing that Steinberg could do, to meet us halfway, it would be this:

Create a feature and bugfix voting area for obvious non-NDA stuff. Obviously, Steinberg would not reveal its "surprise" features that highlight a major version release.

I'm talking about the known issues and really low-hanging-fruit features that would complete an obviously incomplete feature already released.

Then, there is no amount a criticism that can be waged except on we the users, ourselves, for voting for the wrong thing.

I just think Steinberg needs to grab the reins and control the "conversation" more. Paradoxically, a bug and feature voting area would give them a platform to do it.

Right now, it's a one-way conversation.

And it would let we the users, put our voting where our mouth is.

I.e., a person voting for every feature, effectively nullifies his/her vote. Picking and choosing carefully what to vote for, should somewhat quell even the loudest among us.

It should be more, "why aren't people voting for this more?" not, "why wasn't this in a given release."

I think it would also highlight some silliness in our requests. Like, surely there would be more votes for Render In-Place related features than boring old window management stuff, but clearly, the window management fixes needed to be addressed asap. Stuff like that.

Again, thanks for the .0.5 release!

Happy New Year, all.
by Jalcide
Thu Jan 08, 2015 6:38 pm
Jump to forum
Jump to topic

Cubase Caught Red-handed

Once again, DAW crashing supplants music-making.

It's always a mystery with too many moving parts to lay blame with any confidence.

Not this time.

I caught it with a nanny cam -- a disk image !

Problem: Suddenly, inexplicably, Cubase 8.0.5 stopped loading project files; crashes at about 10% during the loading process.

Could it be a third party plugin? Nope. Nothing has changed since my disk image backup (which works and loads the same projects fine).

Confirmed by disabling plugin folders; still crashes.

Could it be a Windows update? No. I've disabled automatic everything. No updates have happened since the backup.

Could it corrupted prefs? Nope. Disabled and Trashed prefs and it still crashes.

Could it be a corrupted project file? Nope. Projects load fine on the backup image taken just days ago.

What about a plugin corrupting something on the file system level? No, I don't use any plugin that writes or reads from the drive, and no presets were saved or loaded from any plugin since the backup. The plugins were sandboxed to memory only (and no corruption occurred, because the projects load fine from the Cubase image backup).

Cubase has not crashed since the backup.

Cubase has not hung or crashed when quitting.

My computer has not crashed, rebooted or reset since the backup.

My computer doesn't do anything at night. No disk cleanup, virus scanning, updating. Nothing.

What about a disk error? Nope. This is Samsung Pro 840 SSD, practically immune to such things as long as there was no power failure during a write operation. And there is no indication of any problem, otherwise. Also, project files and sound file are on a separate SSD. And again, they all load fine from the backup. Also, those drives have the write cache disabled to prevent any corrupt should there be a power failure.

How about a memory error cause by cosmic rays (this is a real thing). No, because the project loads fine and no pref change writes (or even prefs reads/edits) happened since the backup.

Memory has also been tested, passed, and is premium grade.

SSD health is perfect.

Nothing has been installed since the backup.

Nothing has been updated since the backup.

The only operation that has been performed on the DAW since the update, is using Cubase (and without any anomalies).

BUSTED , Cubase. I caught you this time.

Cubase did something to trash Cubase, there is no other logical explanation.

No big deal, I'll revert to the image backup only a few days old and carry on.

But geez, there needs to be a more robust handling of Cubase's internal affairs.

This is a rare, undeniable case of catching Cubase going from, working, to not working, over the span of 5 uneventful days where only Cubase was being used.

It's Cubase trashing Cubase, somehow. It's not cosmic rays, the OS, brown-outs, prefs, 3rd party plugins, hardware failures or any manner of project-level corruption.

It's Cubase caught red-handed doing something .
by Jalcide
Sat Jan 17, 2015 12:03 pm
Jump to forum
Jump to topic

Re: ATI Radeon or Nvidia Geforce?

Waves plugins (and Fabfilter plugins) + recent Nvidia drivers = system-wide video-related slowdown when audio engine plays to about 3 frames-per-second. It's related to OpenGL and both of those plugin developers use it.

Basically, the UI becomes unusable.

It's a known bug.

Resolved by using March 2014 Nvidia drivers (for sure, others may also work).

It may be fixed in the most recent drivers, I'm not sure, the issue scared me off from choosing to update.

For these reasons, any recommendation for Nvidia for digital audio, is unenthusiastic to say the least.

I never had an issue like this with my old ATI/AMD graphics cards.
by Jalcide
Tue Feb 03, 2015 9:27 pm
Jump to forum
Jump to topic

Re: ATI Radeon or Nvidia Geforce?

If Cubase came from using the legacy GDI video API (before Direct2D / Windows 7), which it most certainly did, it's either still using GDI today or, most likely transitioned some or all of it to Direct2D calls which are highly compatible and interoperable with GDI.

If so, then a video card's GPU will assist with Direct2D calls when drawing all primitives (lines, rectangles, etc.).

I suspect Cubase 8 sees some small UI performance gains when paired with a reasonably modern card it's happy with dirver-wise.

This is for Windows. I think OS X and its OpenGL is hard to avoid these days; stuff is gonna get accelerated without too much work from the coder. Less of an issue with Mac, anyway, as the platform video choices are narrower and mostly meet a minimum spec, with driver issues more stabilized.
by Jalcide
Thu Feb 05, 2015 9:22 pm
Jump to forum
Jump to topic

Re: EDM Producers: what is Cubase lacking most for you?

Edit: 0) Just learned of an issue that, if true, will be at the top of my list: Sample accurate automation! Appearently, sound card buffer size changes, change where automation aligns, slightly. If so, yikes!

1) Number one feature: Stability when projects get large -- they will. No excuses, no finger-pointing, just do whatever it takes to treat 5gb+ projects a like first class citizen.

2) Cubase needs more than 6 freezable inserts. Period. (And it needs more than 2 post-fader inserts.)

Sidebar / TL;DR: [This is not debatable. If you don't produce electronic music I don't wanna hear the mantra that 6 is enough for your recorded guitar -- it is. I don't wanna hear that more effects are bad engineering practices, they're not for newer dance genres that require extreme sound design. If you do produce electronic music and make this claim, I need to hear a link to your work and it better be of commercial quality and something modern and fresh one might imagine being sold in reasonable quantity on Beatport. A simple ambient track does not count. If you do, and it is, then please explain your workflow and I bet it involves lots of bouncing of audio. My argument revolves around not having to do that as much. If you're a "bouncer," great, then this feature doesn't harm you. There, I think I spared this thread from every indie rock guy coming out of the woodwork to proclaim 6 freezable inserts are enough for their overhead drums channel -- yes, it is. In fact, 3 inserts are probably enough. :lol: ]

3) Batch freeze/unfreeze. And its own "Settings Menu" like Render In-place has, so that one button (on, say, a surface controller) will perform the operation based on options set in its settings menu; i.e., no annoying dialog box / workflow stopper.

4) Render In-place needs:

a) Pre-fader option.

b) A Disable Track that disables all plugins (even post-fader inserts) and that doesn't cause crashing in subsequent freeze operations (a confirmed bug) and it also needs a menu item for it under Project so that it can be hardware surface controller initiated

c) A feature / option that remembers its first audio clip it bounced and will automatically replace it (and all its shared copies) on subsequent renders. Basically, make a change and have it automatically reflected across the entire project where that share audio clip exists.

5) Ability to rearrange frozen tracks. And unlike Studio One's implementation, it shouldn't flatten shared copies during the process. That's a destructive, lossy process that entirely defeats the purpose of its championed reversibility.

6) Add a feature to Track Versions that incorporates Automation. Without it, it's useless to us. We use automation on every track.

7) Remote Device Editor needs to not be tied to the "ordinal position" of channels. Adding a single channel breaks the Remote Device. It should be tied to some internal ID of the channel. This one simple "fix" would make Remote Devices useful again.

8) Automation needs real Bezier curve tools.

9) Better ways to implement VST2 compatible Sidechains, or at least a friendly way to implement the Quad-channels.

10) Options to remove all annoying dialog messages in favor of "Setting Menus" that provide options and defaults. Basically, anything that has a dialog box, that could conceivably be something someone would want similar defaults for, time after time, should be accommodated so that the dialog does not ever pop up (unless the user goes into prefs or settings to disable it or change an option).

11) Better support for Drag-and-drop of samples, MIDI, presets, plugins, etc.

12) A gain plugin. Some of us don't like to automate faders, use the Trim feature or use VCA fader groups, we just want a gain plugin to automate ourselves. We use freeware plugins, but it would be nice to have a stock one for this.

13) A "audio transporter" plugin with a transmitter and receiver to send audio from anywhere in Cubase to anywhere else (feedback loops and all).

14) An overhaul of the Audio Pool. It's bright, ugly, needs a better layout, more features and integration.

15) A smarter low-latency-mode feature that allows the user to choose which inserts to power down.

16) A simple way to power off (not bypass, power off) all inserts on a track (not Disable Track).

17) Better ways to multitask and cut and paste between two or more projects. It's not reliable now and no one with a real project of any size uses this.

18) Better ways to import/export tracks, channels, presets, mixer settings, etc.
by Jalcide
Wed Feb 11, 2015 8:41 pm
Jump to forum
Jump to topic

Re: EDM Producers: what is Cubase lacking most for you?

I had to actually look up what EDM means...

I'm proud that I didn't's on par with knowing all of Justin Biebers songs ;)

I suppose for EDM, you'd be better off with Garage Band & Fruity Loops, than Cubase.

Since you were upfront about having to Google it, I'll go easy, but let's set the record straight. :D

"EDM" is an unfortunate and recent moniker. Those who have been into "Electronica" (and all its sub genres), for decades, shudder when we hear it.

To equivocate Justin Bieber to mainstream EDM may have some merit (and frankly is doing Justin Bieber a disservice in many cases), but is only a thin, superficial veneer into the world of so-called EDM.

There are old, jaded, intelligent and passionate aficionados of deep house and techno (to name two sub-genres) who are as sophisticated and nuanced a listener as would be found in any genre, perhaps more.

Audiophiles, high-end headphone and amp purchasers, vinyl browsers and project studio owners. The kinds of folks who buy lossless audio, start record labels, tech startups and can pick out not only the vintage drum machine that was used on a track, but whether it was recorded hot to magnetic tape, or not.

The really well respected and good productions are not done with Garage Band, and in fact push the limits of Cubase or any modern DAW.

A good, modern, respected piece of electronica can be as creative and complex as a film score + all the sound design for the sound effects of a feature film. The workflow, fx chains and track counts can be almost as high.

As for "Fruity Loops," while I'm not a fan of FL Studio myself, it's come a long way and is a force to be reckoned with.

While Ableton gets most of the spotlight when talking about EDM, only just recently becoming mainstream in America, it's been popular in Europe for decades, as has Cubase.

There are probably more electronic dance music professionals using Cubase, worldwide, than any other DAW.
by Jalcide
Fri Feb 13, 2015 6:01 am
Jump to forum
Jump to topic

Re: Mixer undo and unlimited insert slots.

It's just so strange that the inventor of ASIO and VST should have its flagship product limited to 6 freezable inserts + 2 non-freezable.

I really do think it's a corporate culture thing. The measuring stick being, if Cubase can produce a little 12 track indie rock demo for a corporate video, for the project managers at Steinberg moonlighting on it, after hours, mission accomplished.

I still can't help notice that those with more involved sound design needs, the signed, hardcore, professional electronic music producer using Cubase, seemed to have developed a laughably "destructive" workflow where everything is bounced again and again and again. Six freezable inserts is more than enough when it's multiplied by 3 bounces.

These guys have even said on camera, in their tutorials, etc. that they like "committing" via the bounce, that it helps push them forward. They love to drive the point home by deleting the original track.

There is a whole "staying tight on the grid with audio" philosophy that has sprung up to further embolden the practice.

And so no one complains.

The project managers moonlighting with their band on the side: 8 inserts are enough.

Even after this small band adds "a keyboardist" to the group, the technical demands increase by one stereo track. With maybe a little EQ and compression on it (if that). Done. They're never going to want more.

The attitude is further bolstered by professional audio engineers in the forums, again mostly acoustic oriented, who love to point out that "you're doing it wrong" if you need more than 3 inserts.

These guys have never had to make a layered, modern kick drum from sine waves in their life. They have no idea how complex the sound design can get on each channel.

Then we have the hardcore dance producer who bounces after each edit, who is still on Cubase 5: 8 inserts are enough.

The European psytrance producers still on Cubase 5, on ten year old computers, monitoring the mix on 50 dollar multimedia speakers -- veritable prodigies for doing so well with so little (and always proud to point out how crappy their setups are) -- are never going to want more. They'll still be on Cubase 5 in five more years. It's like their rite of passage; of due paying. They've mastered the art of irreversibility of audio.

What a weird skill to have to be good at when we have computers.

It's maddening.

There is no voice of reason in this fight, except this sad little thread.

I'd like to give in and join the crowd, just bounce after each edit and "commit," but I'm just not skilled enough for that kind of destructive workflow yet.

What's even more baffling is understanding why I cling to Cubase so much. I should be using Ableton or Bitwig.

It's just I've been using it since the '90s (and yet still suck enough that I can't "commit to the bounce"). :lol:

I guess I shouldn't quit my day job. :lol:
by Jalcide
Fri Feb 27, 2015 4:39 am
Jump to forum
Jump to topic

Re: Cubase Realtime performance penalty on upgrade from NVID

Just to add another voice...I'm also having issues with ASIO spikes in Cubase 8, and I have a Nvidia GTX760, so there does seem to be some issue with the two not playing nicely.

My symptoms seem to be just slightly different though, which is that everything works just fine when I first fire up Cubase, but then as time goes on, ASIO spikes start creeping in until every couple seconds, regardless of what I'm doing, the ASIO overload light starts popping on. The ASIO meter is bouncing up and down, the red light going on, and I could be just sitting there doing nothing. Not recording, not playing back, just sitting idle and this is going on. When I playback, it's clicks and pops galore.

This is resolved by closing Cubase (which crashes on close 90% of the time for me) and restarting. Then it's fine again for a while.

So now, I just figure when I start getting ASIO spikes, it just means I've been working too long and I need a reboot break! :D

I really hope this gets resolved soon, but in the meantime I'm going to try to remove some of the Nvidia software like GeForce Experience, etc. Maybe that will help...

Most likely not related to the video card. But yes, remove all the Nvidia bloatware.

I'd check to make sure a drive isn't set to index (for search results).

And do all these steps...

If after that it still happens, I'd check system services and any other startup or background processes.

After that I'd check audio interface issues (firewire / usb / drivers, etc.).
by Jalcide
Tue Mar 03, 2015 10:07 pm
Jump to forum
Jump to topic

Re: Thanks for the 8.010 release update


I was very glad to see Steinberg communicate the delay. It's easy to share updates when everything is going well. The true test is when things aren't.
by Jalcide
Thu Feb 19, 2015 11:24 pm
Jump to forum
Jump to topic

Re: Daft question about C drive recovery

Thank you jalcide..I'm of to buy an Icy dock 6 tray...Kevin

This is the one I have. Works with standard 7mm to 9.5mm drives (internal laptop sized, magnetic and SSD drives -- pretty much all 2.5" drives).

They also have a 4 tray model for larger drives. And a new 8 tray model for use only with slim 7mm SSD drives (most newer SSD drives are 7mm).

What's also great is the expansion a tray provides for sound libraries, putting in backup drives to copy to, different OS images, booting off "test area" images (for trying something before doing it for real).

They also make a great foundation for a super fast RAID (or a slower RAID for redundancy).

I love these things and have put them in all my workstations and servers (all of which happen to be rackmounted, but it works with any case that has a standard 5.25 inch bay.)

Your motherboard needs 6 SATA ports, of course (preferably SATA 6Gb/s -- a.k.a. SATA III). But as many as you can connect is fine. And if you need more you can buy an inexpensive SATA controller card.
by Jalcide
Fri Mar 13, 2015 5:37 pm
Jump to forum
Jump to topic

Re: 8.0.10 is here

Well, it doesn't work. I put txt in that folder and hear sound glitches, like waves plugins was corrupt and bad sound throu them... Oh Lord. Didn't try old nVidia drivers.

Bummer. Was worth a try. It's solved the issue on two different DAWs for me.

The text file fix reduces the GPU and CPU requirement of any loaded Waves plugins. I've haven't tested this scientifically, but I could swear it's noticeably freeing up some CPU for me (in addition to the "choppy GUI" fix).

It does lower the FPS of a bunch of Dorrough meters I have open, so it's clearly doing some tangible throttling back.

If you try the March 2014 driver fix, be sure to check "clean install" (and once again if you end up reinstalling the latest Nvidia drivers).

Also, be sure to uncheck all the Nvidia bloatware.
by Jalcide
Sun Mar 15, 2015 2:24 am
Jump to forum
Jump to topic

Re: Can someone explain to me how to backup to cloud or loca

I had a horrible experience when two hard drives failed at basically the same time. One was my main audio drive and the other the backup for it. Both were complete losses. Was willing to spend $3000 each to retrieve data but they were toast.

Now I use Carbonite to back up everything nightly. Have to shut that down while recording as it is a big hog when running.

$100 a year for unlimited storage. Seems way more dependable than a second drive that failed for me. And actually cheaper.

I am a PC guy so I am not keen as to Mac options.

Yikes, that does not sound fun.

Carbonite is good for your offsite backup, but you should really have an onsite backup, too.

That online backup at Carbonite is only as good as your "account" is good and its settings, now, or ever, don't cause an overwrite of some kind.

For example, I'm learning the hard way right now that all my Crashplan backups are at risk of being blown away during an "adoption process" to a new machine. It will probably be okay, but if a certain "key" is pasted in wrong, it's bye bye everything (and there is no warning or undo for it). It's kind of a terrible little gottcha over at Crashplan (love the service otherwise and do recommend it).

The point being, is that online backups have fine print and pitfalls, too.

I would seriously consider a local backup, as well (even after your recent failure of one).

The old military survival saying of "two is one and one is none." definitely applies to backups.
by Jalcide
Sat Mar 21, 2015 11:17 pm
Jump to forum
Jump to topic

Re: Crashing on freeze track

If you have any track in the project "disabled" (using the new "Disable Track" feature in Cubase 8), it will cause this crashing.

Btw, Steinberg mods, my issue in link above has been flagged as being a "duplicate" of the render-in-place crash. I don't think it's the same thing. I think it deserves its own tracking number (please see my original post above and consider categorizing it as an official bug, in its own right).
by Jalcide
Sun Mar 22, 2015 5:15 am
Jump to forum
Jump to topic