I would encourage new Steinberg users to drop by the lounge https://www.steinberg.net/forums/viewforum.php?f=198
Tell us who you are, what you do, in what area of the world you live.
If you have some music to share, “Made With Steinberg” is the place to discuss, praise or get help with a song. https://www.steinberg.net/forums/viewforum.php?f=219
There has been more chatter in general forum the past, but the Signal to Noise ratio was getting out of hand.
I think the moderators are doing a great job, keeping threads On Topic. That also makes it easier to search for solutions, when a problem arises.
Hope you all are going to have a great time here, Welcome.
See you in the Lounge.
I’d say you need at least a month to get your “sea legs” here for prior Sonar users. Cubase is pretty broad - but it’s UI conventions for interface elements are quite different than the “Windows Standard” conventions of Sonar.
Case-in-point: I finally decided to investigate visibility “Zones” in the visibility inspector. I tried like mad to click on the “dot”, but nothing happened. So, it’s over to the manual (no proper help file) and there it says to drag the dot “to the left” or “to the right”. So I tried dragging. Nada. Zip. Zero. I scratched my head for a minute before an idea popped up. Lets try clicking to either side of the dot - Bingo! So, the manual wasn’t much help, and there’s nothing about that “dot” user interface element to even suggest that it’s a toggle control. So whenever you hear some hipster rant about UI skeumorphism and claim that it limits creativity, you’ll know he’s full of beans. Flat design is simply a stylistic decision that may or may not contribute to a better experience. It’s been a few weeks of little trials like that. Still, I’m more than happy with Cubase - just thought it would be easier to transition.
I hope to be finished replacing the tailgate/hatch on my car tomorrow then I’ll finish building my new PC and look forward to the delights of installing win 10 from scratch. It was the free update from win 8.1. I’ve been told it’s as simple as installing it then contacting MS by phone for activation.
Then onto installing all the software and Plugins. All the sample libraries are Ok. This is finally be an exclusive DaW and multimedia workstation. Woohoo!
Hello, unfortunately, I don’t believe there is a setting to automatically stop playback. I did a search as you have done and I found nothing except for the workaround. It’s frustrating but I’ve gotten into the habit of stopping playback.
It depends on whether you consider these a single control with three states, or a group of three radio buttons. If the former, there’s nothing to indicate it has three states. If the latter, there’s nothing to indicate there are three radio buttons. Even flat design needs minimal clues.
I’ve been familiarizing myself with Cubase 9.5 Pro over the past month or so and I’ve made the switch officially. I’m liking it. I am curious about 64-files. It seems Cubase can’t read them, is that something known already or am I experiencing an issue?
I have tested this directly with an audio wave file I export at 64-bit from Sonar.
I then import it into Cubase and you can see the container of the waveform but no waveform, rather a message that says it can’t reconstruct the image, along those lines. I go back to Sonar and re-export the same exact audio file at 32-bit, re-import into Cubase and works totally fine.
Hi, one of the newcomers moving from Sonar to Cubase here.
A question about groove quantisizing. I have been using several .grv format files in Sonar for years (not just the ”Cakewalk DNA Grooves-grv” that came with the software, but others I have bought elsewhere) and now I’m wondering if there is a way to use them in Cubase. For a while more than a decade ago, I used Cubase (probably version VST32 5.1 or something like that) and I seem to remember using my .grv’s back then. Can’t seem to find a way in Pro 9.5 or any mention online or in the manuals. Any pointers? Thanks.
So far Cubase can do all and more that Sonar did. Learning all the different terminology and work flow will take some time, of course. One thing I can’t find is how to reduce the track depth so I can see all of them on the screen. I’m sure it’s possible…what is the terminology? Sonar had a keyboard shortcut of “F” to enable this. Very useful.
CTRL+Up/Down arrow should increase/decrease track height. I say should because I remapped my keys ages ago and sometimes I can’t remember which ones are default and which ones I overwrote.
In the keycommands list are a bunch of zoom options for doing more global settings quickly. There are also a couple of height to data and height to name commands. And, you should look at Zoom Zap, it’s kind of a "zoom toggle thing that’s cool when you are doing fine edits.
Thanks JM…the command I’m looking for is one that decreases all the track heights so that they fit the screen. If there are 3 tracks, their height is reduced by just a little so they fit. If there are 10 tracks, their height is reduced by a lot so they fit. One command. It would seem that there is such a thing in keyboard shortcuts called “agents:show all channels/tracks” but it does nothing that I can see. Must be a command for the visibility panel.
Your solution takes too much time because you have to click on each track to get them all to fit. What I’m looking for is a “one key” solution. I’m surprised if Cubase doesn’t have it. More likely that I don’t know what to call it to look for it in keyboard shortcuts.
I primarily work with 64 bit WAV files in Cubase and never had a problem exporting them for use in other programs like Sound Forge. It’s a standard non-proprietary file format. Maybe Sonar is not exporting them correctly?
Odd. I imported the same 64-bit file into Reaper and Studio One without issue.
EDIT: to be clear, I’m only referring to importing 64-bit wave files into Cubase. If somebody can confirm that Cubase indeed doesn’t work with 64-bit floating point wave files. Because I’m noticing in the export, unless I missed something, I see options for 32-bit float as the highest bit depth, not 64. (I think you might have been referring to wave-64 file, being proprietary to soundforge should open fine. But I’m referring to 64-bit float wave file format).
So I’m going to assume Cubase is just not capable of working with 64-bit audio files. As I mentioned, upon import of an identical file, one 32-bit version of it and one 64-bit, the 64-bit doesn’t load properly or playback. Also the option for 64-bit lacking in the export window as well clinches that this is not a bug most likely and just an inability. I’m still really enjoying Cubase. I think this capability one takes for granted because sonar had it for so long.
About over a month ago when I first started hearing about Cakewalk possibly shutting down, I prepared exports of all of my audio tracks within many Sonar sessions. I’ve always worked with 64-bit, 44.1 as my standard and so these files were exported as such. Of course I would have preferred not going through and converting each file to 32-bit but it seems that’s my last resort.