There is nothing better than being at the beach and watching Chris Selim Cubase mastery. If I had an extra beer, the whole experience would be on another level. Thanks Chris.
Hi Chris. Great tips. I've been using all of them for years and they sure save time. Some interesting things to note: 1. On the mix console, holding Shift & Alt automatically enables a non-latching Q-link. No need for a key command. (Unless you prefer it latching). One of the best features. Works not only on faders but also on inserts, sends, eq's, etc. 2. You can hold Shift while increasing/decreasing faders to have "fine" control changes. That also works on pretty much everything in Cubase. Plugin param's, EQ's, sends, etc. 3. If channels are truly linked, (say 8ch's of drums) you can hold Alt while increasing/decreasing faders and it will then only adjust that channel and not all of them. Almost as if they are not linked. You could maybe share on Macro's also. That's currently my #1 tip. I have a key command that executes a macro which, duplicates my selected audio track with all its current settings, removes all the track content, disables record arm on the track and enables it on the new track, takes my transport line back to start and renames the channel. This is something I personally do frequently when I do a lot of vocal takes to have them on separate channels. (I'll be glad to share that macro) Love your videos and how you present them!!
Those are great tips, thanks for sharing :-) Feel free to share this macro if you want. I'll make a Macro video and share yours at the same time :-) info@mixdownonline.com
I like this, great info but, when I upgraded to 10.5, this was the first thing I did, FIGURE IT OUT, in reality it didn't take to long, maybe because I 've been using Cubase since I jumped into digital recording. So those of you new to Cubase, Chris is giving you some very practical info here, info that will go a long way in achieving your recording, mixing and mastering endeavors. Learn the in's and out's of your software and you will have a much easier time designing your consoles (templates) for your work flow. This is the great thing about Cubase, you can customize it to whatever task you are trying to achieve. In other words, you can have multiple consoles in different configurations. How much would that have cost in the 70's? Great job as always Chris.
I use the import from project after i export all tracks dry to copy over effects and automation to a full mixing project so i have all tracks dry if i need them and a dedicated mix session. Big game changer!
Dear Chris, the video is priceless, thanks a lot! Could you please explain what’s the difference between Q-linking channels vs doing same thing with VCA?
Here's a video I made a while ago about my recording template ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-sarNPZSWedE.html. Let me know if you want me to add anything on a new video
Awesome tips 👍 been using cubase since version 3 and still finding useful tips. Keep up the great work. Would you consider showing a stream start to finish of your mixing progress? Would be good one to watch 🙂
Thanks you so much!! How do you narrow the tracks on the mixer to fit more channels on please? I tried to zone my group tracks as you have just informed how but I'm left with no visible channels?
Hey Chris, I was wondering if there was a way to automate the process of cutting audio clips by dtecting silences and after creating cycle markers on the resulting clips with names for export. I'm a sound designer for games and I often have to export multiple regions and automating this process would speed up my workflow so much. Thanks Chirs and again thaks for the awesome videos
Thanks Chris. Can I ask on here if anyone knows what the name of the command is (in key commands) to scroll the mixer across to home/end. Can't for the life of me find it. Many thanks!
Hi Chris, concerning TDR Nova, you talk about in another video, from their link www.tokyodawn.net/tdr-nova/ is not possible to download it; I use Windows 10, 64 bit version 2004. By clicking on the Windows installer and accepting the license agreement nothing happens...
Hi Chris. Thanks to your Cubase Course and previous videos I use nearly all these tips. Apart from my Steinberg CC121 Controller the most recent improvement to workflow when using Cubase (and other programs) is using an Elgato Stream Deck (15 button) - the great thing is it has a Cubase Plugin that can easily be added and you no longer have to remember all the short cut keys (definitely helpful as we get older!!). www.elgato.com/en/gaming/stream-deck
A question about the visibility sidebar: I noticed that if you hide channels, they will still be audible even though they are hidden. Is there a setting that will automatically mute any channel that you want to hide or do I have to mute the channel first before I make them invisible? (basically putting them in storage)
Latency is not something that you can fix on a bus track. It has to do with the buffer size. Here's a video related to latency ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-RuOn6qEs4z4.html
Additonal TIPP: For those big projects use CONFIGURATIONs in the mixer !!!! ..., maybe set it up for every group of instruments and assign a shortcut to every group! (mine is "altGR-shift-1" , "altGR-shift-2" and so on for groupe-1. groupe-2.... )
Gerhard Binkele yep, I have several configurations on key commands, e.g. for viewing only audio tracks or fx/group channels. I wish I could save those configurations globally instead of only per project.
@@Am6-9 and there is one problem with it: if you add one new track to an existing configuration then it is added to all configs and you have to delete it each one by hand separately if you don't want it in an config. That's not the behaviour I'd like to have. That should be fixed in an update!
hey sir I have question I am currently using cubase 10 . I have monitors and headphone connected to my interface but how can I turn the monitors off while recoding in daw .I go and unplug my monıtors when I record please help :D
Regarding key commands, I once wrote a little web app that can read Cubase’s key commands (the config file “key commands.xml”) and display a nice web page of all currently configured cubase key commands, grouped by section. Maybe it’s useful for someone else, too: janminor.github.io/cubase/CubaseKeyCommands.html (You can find the "Key Commands.xml" in the cubase preference directory as described here: helpcenter.steinberg.de/hc/en-us/articles/115000245510-Preferences-of-Cubase-and-Nuendo)
Man, you got the colors all wrong! Guitars are yellow, lead vocals are red, background vocals bright pink, basses are light blue. Everyone knows that 😛 Well, with everyone I mean me...
@@mixdownonline Well if other people can use cubase without having as much trouble as i did, good. I switched to studio one because its allot like cubase, but without all the headache that Cubase gives you when you have big projects. I have not used cubase in quite a while, but i don't trust that software. When i used it, I had constant crashes, backups, and under the hood problems when recording. If any one is having similar problems, this is probably the cause... I troubleshooted allot to try and fix the problems i was having, but i couldn't fix it because it was a software problem. My projects can easily get ALLOT of tracks, each with their own vst instruments, plugins, Eq's, and what ever else i want to throw in. When projects get big the software would start to have weird artifact-ing. Suttle popping or static at random times. Tracks were not properly taking recorded audio and using the plugins correctly. After posting on forums and even talking to Steinberg to try to figure out why this was happening, I found out it was because the software was not using 100% of my CPU, even though it was acting like it was. For some reason the software would only use a specific amount of CPU, regardless of available CPU power. The software was bottlenecking itself for some reason. Even with freezing my tracks and trying to manage CPU as much as possible, it was never enough and just a huge headache. It wasn't because of poor recording or what ever anybody else on the internet always points to first, it was the software having to much to process even though there was more then enough processing power. And this was with a machine that was top notch at the time. If i remember right, the only better CPU available was the thread ripper when it came out. I haven't had any of these issues with studio one. Studio one has a performance meter right at the bottom to see how well your machine is handling all the processing, which is the most important thing when it comes to the DAW you are using. I felt like i was always fighting with this software because of the software. Good luck using Cubase for digital music production on an average computer. It has been like 6 years though... maybe its actually usable now.
