Cubase is a complex beast, but I've found that it pays off in huge ways once you get a grip on what's happening. It can be as simple as any DAW on the market, or as complex as you want it to be. Between the macros and Logical Editor, I've found nothing that I can't do. The Logical Editor blows away CAL. Just having an actual built-in audio editor is amazing, and with ASIO-Guard invoked, I can run 20 to 30% more virtual instruments under Cubase than I could in Sonar. It's not a program where you want to stumble around and figure out what's happening. Invest in some of the tutorial programs online, and you'll be up to speed in less than a week.
 
One of the gripes people had with Sonar is that there really were no big names using the program. You had some higher profiles on music for games, but even the biggest one was using Sonar 5. Cubase is used by a myriad of professional composers and musicians.
 
For a good overview of the capabilities of Cubase, scroll to the bottom of this page and check out Season 1 of Junkie XL's tutorials. The guy composes for huge films, and has a lot of peripheral equipment :
 
http://www.junkiexl.com/tutorials/
 
 

KHS

soens
Would you let a doctor operate on you blind? "I can't see what I'm cutting but don't worry. I know I'm cutting something..."
 
If I can't see it visually, it aint happening.

That comment only tell that you have absolutely no idea what you are talking about..

Actually, it's a perfectly reasonable analogy. Your response, on the other hand, is unnecessarily combative and unprofessional. Please, keep your comments productive. We are here to help our colleagues out of an unfortunate situation - not kick them when they're down.

KHS
 I said he had no clue because the slip editing method is actually how many pro producers are doing it.

You don't have to be a mathematician to know that many is less than all. Just because the producer of the moment does something a certain way, doesn't mean my particular project will turn better (or even as good) by using that same method. 

If you need to have the tail of a guitar blending in with next part, it's no longer a single guitar and should be done on 2 tracks.

Change the word should to could and you'll have a valid statement. If you haven't heard the project, you're in no position to make blanket statements about the best way to handle that particular production.
 

Same with the more obvious overlapping vocals. You should always keep them on separate channels, else your compressor will slam it on the overlapping part and thus making it hard to hear the words.

Change will to might and again you'll have a valid statement. Yeah I know I'm picking nits but nits matter when it comes to this stuff. You simply don't know what vocalist is doing in each overlapping part nor do you know how the compressor is set. It might slam when they overlap. But not everyone uses compressors set to stun on all vocal tracks no matter what so then again, it might not slam the compressor at the overlap. And even if it does push the compressor a bit more at the overlap, how to do know that won't turn out to be desirable in that particular application?
 
Everything you're suggesting makes good sense for production general rules of thumb. But audio production is not one size fits all. Experimentation and alternative methods need to be an option if you're building a production tool that a wide swath of people will find value in. At least in my opinion.

For 8.5, it was on one of the final installation prompts. For 9, now that you mention it, I don’t recall seeing the prompt either. [I haven’t upgraded to 9.5 yet.] If it’s not there anymore, you’ll have no choice but to install and disable or remove it.

For instructions, try this link out: https://www.kvraudio.com/...iewtopic.php?t=393887. It speaks of both, disabling and removing. Disabling is probably the safer route. I’m on a phone and can’t do much better right now, but there are other discussions that speak of the necessity to restore the driver when updating Cubase. If you’ve disabled the driver, it’s just a matter of restoring the respective file.

husker
Just curious, why disable it at all?  Why not just choose the correct Asio driver for your interface?  That is what I did.   Maybe I'm missing something. 

Thats what I did. Just go with the install defaults and change it when you open it. Worked for me

That may make some sense I guess.   I just rebuilt my Daw with Cubase.  Didn't even bother to install any Cakewalk products. 

In the audio program preferences you will have a choice as to which ASIO driver to use. As the other thread bearers have contributed, just choose the native driver for your device. Same for Samplitude, initially it appeared I would only have a choice of their generic driver, but in preferences, I easily could choose what I thought I wanted.

I did run some latency tests on the genetics and the native. All were within a msec or two. I find even with the native driver there is the occasional hangup switching from one DAW to another.

I have a strange thing with Cubase.  I created a simple project.  I dragged an MP3 into one track, then I set up a second audio track for recording.  I ended up recording three lanes.  They all have audio on them.  I can switch among the three takes with the S button on each lane and they sound as expected.  But no waveform appears visually anywhere on the track on on the three takes.  The waveform does appear on the MP3.  See the picture below:
https://drive.google.com/...6ZVTR/view?usp=sharing

swamptooth

cparmerlee
I have a strange thing with Cubase.  I created a simple project.  I dragged an MP3 into one track, then I set up a second audio track for recording.  I ended up recording three lanes.  They all have audio on them.  I can switch among the three takes with the S button on each lane and they sound as expected.  But no waveform appears visually anywhere on the track on on the three takes.  The waveform does appear on the MP3.  See the picture below:
https://drive.google.com/...6ZVTR/view?usp=sharing

https://www.steinberg.net...hilit=waveform#p702280

Lots of people are having this problem.  Here is the official workaround:


https://helpcenter.steinberg.de/hc/en-us/articles/115001765010-Cubase-9-5-waveforms-are-missing
 
Basically the issue only happens with 16-bit recording.  I normaly record 24 bit, but evidently I had some defaults set up for 16 bit. 

swamptooth

cparmerlee

swamptooth

cparmerlee
I have a strange thing with Cubase.  I created a simple project.  I dragged an MP3 into one track, then I set up a second audio track for recording.  I ended up recording three lanes.  They all have audio on them.  I can switch among the three takes with the S button on each lane and they sound as expected.  But no waveform appears visually anywhere on the track on on the three takes.  The waveform does appear on the MP3.  See the picture below:
https://drive.google.com/...6ZVTR/view?usp=sharing

https://www.steinberg.net...hilit=waveform#p702280

Lots of people are having this problem.  Here is the official workaround:


https://helpcenter.steinberg.de/hc/en-us/articles/115001765010-Cubase-9-5-waveforms-are-missing
 
Basically the issue only happens with 16-bit recording.  I normaly record 24 bit, but evidently I had some defaults set up for 16 bit. 

this has been resolved with the 9.5.1 update.

Thanks.  Evidently Cubase doen't have any automatic updater or notification.  If there was a notification of the update, I missed it.  All is well after the update.

anydmusic

cparmerlee
Evidently Cubase doen't have any automatic updater or notification.  If there was a notification of the update, I missed it.  All is well after the update.

I received a notification in the Cubase Hub on startup...

OK.  I guess I need to pay better attention.

Frank-US

JohanSebatianGremlin

Anyway now on to my question. Is there a setting to make playback stop at the end of the project? I've looked but can't find one. I asked over at the cubase forum but got no response yet. I've searched at the Cubase forum but only found threads that offered workarounds. Does such a function exist in Cubase?

Go to menu "TRANSPORT".
Under "PLAY PROJECT RANGE" you will find several options for start and stop of your project.
While one key command (alt /spacebar) is already available you can choose any short cut for the other options in the "KEY COMMANDS" window. Always the latest action is displayed there.
 
Cheers,
Frank

I appreciate the help Frank. Unfortunately, 'stop at end of project' isn't one of the options on the Play Project Range menu. Looks like there's some possibility for a workaround such as 'stop at next marker' once I figure out how to do that. I tried inserting a marker at the end of my current project but playback kept right on going so obviously I'm still doing something wrong.
 
One of the other Sonar features I will sorely miss is the ability to use CTRL-Spacebar to stop playback and remain at the current position when return to now on stop is set in preferences. Handy to have it return to now/start on stop most of the time and still be able to stop playback and keep focus right where you stopped on the fly when you want to quickly fix something.

bwbalint
@bwbalint
 
It appears the preferences/set up folder  '%AppData%\Steinberg\Cubase 9.5_64\' can develop an anomaly.  Steve from the Steinberg/Cubase 9 forum had me delete this folder and let Cubase rebuild it on the next start.  This has fixed the problem at this point without having to delete everything and then start over.  sounds very similar to the one *.ini file in Sonar that can become corrupt.  Although I do forget it's official name.  

Trashing preferences is a common solution. It's a good idea to save a copy of it while it's working great in case you need it in the future. 

Resonant Serpent

bwbalint
@bwbalint
 
It appears the preferences/set up folder  '%AppData%\Steinberg\Cubase 9.5_64\' can develop an anomaly.  Steve from the Steinberg/Cubase 9 forum had me delete this folder and let Cubase rebuild it on the next start.  This has fixed the problem at this point without having to delete everything and then start over.  sounds very similar to the one *.ini file in Sonar that can become corrupt.  Although I do forget it's official name.  

Trashing preferences is a common solution. It's a good idea to save a copy of it while it's working great in case you need it in the future. 

Yes.  I did save a copy just in case trashing it wasn't corrective.  A good trashing was what was called for, so then I saved the new preference file.