Will.

Who thinks a strictly dedicated "Master bus" without the two pan pots, that sometimes causes problems, would be a great addition to the DAW -- with only the Mono/Stereo interleave dead center?

I think your "Dim solo" is on in the control bar. https://www.cakewalk.com/Documentation?product=SONAR X3&language=3&help=Playback.15.html

Bingo! Like I said, your interface/Asio drivers need to be Sync'd with that of your hardware. Set those back to 256KB and just fiddle with your ASIO buffer size under "DRIVER SETTINGS"

All the way and so is the output Craig. Even when I route it to dedicated mono channel it's still there ONLY when I move close to the monitor speaker. I can feel the vibrations too in the woofer. If I sit in my sweet spot, I can't hear it. Weird! Can the cause be from unbalanced cables perhaps? That's where me head is at right now.

I'm gonna try to keep this short and direct. Here it is, I never get true " Mono Pan" in Cakewalk. There's always a little bleeding on the opposite channel - even when the illusion of "True Mono Pan" is being projected. With other DAWs this is not there. Hence - I have to add, this is only noticeable when going really close to the opposite speaker/channel. It was never an issue until I had my wallet placed on the right speaker and had it fell off behind, when I first noticed this. Since then its been bothering me. Anyone that can help me with this.

Try to keep your system smooth. You can try some of these steps below. https://discuss.cakewalk.com/index.php?/topic/16404-solving-known-issues-please-try-this/ Remember, your system needs to be treated just like your car - it needs to be serviced. Every 3 months, I'd clean my fans, CPU fan and rams - also check my CPU if it needs more Thermal Paste.

So what was the point trying to "correct" what I said, if you're jut gonna repeat it in different words. Just like buffer size "Direct Monitor" also has an affect on certain machines with latency. I had the problem with a laptop I was using on the road. It was an i5 4th gen if i'm correct - if not older, with a standard 500GB HDD, 8GB ram with Windows 10 (Can't remember which build,) My Solo gave me latency with direct monitoring on. Yes, you're spot on on few things you've mentioned, but I think it was time wasted. Until we know the specs of the system and hardware used by Konskoo, there's no way to claim an answer. Right now, you have to assume that he is using "Asio4all." Different setups, totally different problems and approach on latency. Before the interface and a upgrade on the laptop (with a group that hired me everytime the went on tour,) I ran a successful on-the-road setup for demo projects, with only a USB midi, USB Mic, with the laptops onboard recording interface to record guitars, a pair of Alesis 3 monitors; using Cakewalk Sonar LE and only ASIO4ALL, with the buffer size set to 1024msec and Playback buffer at 256KB and guess what? NO LATENCY.

Yeah! The "Wednesday, Thursday and Friday" confusion suck! ??

If the buffer size is too low, you may encounter errors during playback or may hear clicks and pops. If the buffer size is set too high while recording, there will be quite a bit of latency which can be irritable. It's hard to say with minimum specs given. There can be numerous reasons - out-dated windows drivers is one of them. Cakewalk sets both Playback and Record I/O to 256KB by default, so set it back to 256KB. There might be a clock sync issue with your system? Try to reset your configurations in preferences and update your drivers. Your ASIO drivers needs to be sync with that of your hardware - that's why it is important to update to the latest Asio drivers, I think it's v4.65 for focusrite -- nowhere near the studio right now to check.

Priceless reaction. ? Yeah! Seems like we either learn new stuff or arrogantly forget the power and flexibility this DAW holds.

No - That's not what I said. Don't enable it - think there's misunderstanding some where. Don't tick any of those boxes. Set your "ASIO driver" under "Driver Settings" to the same value as your Playback and Record I/O buffer size. Dont enable read or write Caching.

On a typical 32 track, mine takes about 10sec with my own template with the plugins bypassed - that's how I saved it. Keep in mind though, your anti-virus software also play a small part in this. It does a quick check before the program opens -- and runs a scan while the projects loads, slowing down the DAW's project scan.

I find that syncing my Playback I/O buffer size and Record I/O buffer size with my Interface ASIO driver, eliminates latency for me - with all FX enabled. To do this: Go to preferences /hit "P" on the keyboard. Under the Sync and Caching TAB you will find the default size of 256KB by Cakewalk. Set your ASIO driver accordingly and find the setting that works best for you. For me the default setting works perfectly. Set my Focusrite Scarlett Asio Driver the same - that gives me 4.3msec of 256samples with Effective latency at 48khz/Stereo at 4.3msec.

Hi all. Need some answers; suggestions and perhaps general ideas/help. So, I've just started working with a group of senior members doing "classic rock." As I go through sorting and grouping certain tracks like percussions; guitars; strings and leads, an old favourable approach popped up, as I'm writing down idea's - and one them are volume ride. Question: With today's "modern" demands on taste and feel, do we still ride the volume up between 0.5 to 2db at the chorus with Rock?

Awesome! Hope this will help @Simon Wilkinson who want's to make use of this with his X-Touch control surface. I'm comfortable with adding them in manually - prefer it that way. Really appreciate the help @msmcleod Thanks.

@Simon Wilkinson I've found something that might help a little bit. After writing in your automation with your midi/control surface, choose the "Erase Tool" by using shortcut "T" on your keyboard, or scroll up to the "Tools Module" ~ OR ~ just hit F10, Press Ctr+Alt to select the nodes within the envelope "bounce the clip" and drag over the nodes you want to remove. The only problem is you have to "Bounce" the clip every time. That might be a bug. @msmcleod Can you help with this perhaps to check if it's a bug or not? Ps: Correct! Precision is key here. So you have to be zoomed in a bit. NOPE! THERE'S A BUG!

I need to look more into this at the studio I work at. They use 5 DAWS and CbB is one of them. Sorry I couldn't help with this. I was so sure that it was possible. Lol.

Yeah - I just checked now at home. There's nothing like that. I might be mistakenly thinking of another DAW where you can even it out just by holding a key down. What if you landmark your automation nodes under the Customization > Snap to Grid TAB? Then try and hold down either Shift; Ctrl or Alt individually or combine them as you write in your Automation? Just trying to help with some idea's - I swear I've done something like this. Just not sure if it's with Cakewalk? Urgh!!! Middle-age is creeping up on me - sigh. ??

Keyboard Shortcut: TAB: Go to the next note event in the current track. SHIFT+TAB: This will allow you to go back to the previous note event in the current track. Ctrl+Num 8 and Num2 will transpose the selected Note/Chords. Num8;2;4 and 6 alone will increment and decrement a note.

Isn't there a setting under control surfaces in preferences for this? I think cakewalk sets this to default for "surgical" writing purposes. Will have to look into this when I'm at studio again. I don't have a control surface at home.

The "mic fader" you're looking for (assuming you're using a USB mic as described in your post,) is in your windows sound tab. Look it up. Get a volume that you like and keep it there. 14% should be enough if you're on windows 7. Have no idea if windows 10 fixed their issue and it's compatibility with those usb mics.

This is purely a windows issue. I have a friend with basically the same specs (just two gen lower.) Normally what happens is, for some reason when the DAW does crash (which is often caused by a free or old 3rd party plugins) windows keep a copy open. To get rid of this. Ctrl+Alt+Del will bring the task menu, where you'll find Cakewalk to still be open under the progams tab. Make sure your playback and hardware buffer size are sync'd with that of your interface. By default cakewalk sets this to 256ms both playback and hardware. Lastly: Make sure windows is up to date. Follow steps below. Follow step 2 and 4 - especially if you're running Windows 10 build 2004 (Which is also the latest version.) It helps a lot.

Totally hear you Glen. My concern with this is (as I've said in a previous thread on this,) that it does not project the image the same for all forms of devices when using a surround bus in that sense. I've experiment with it before, gave it to a client and certain elements didn't come through on a device she was listen on. That's my issue with using a surround bus, with this idea. Most clients get's their tracks played on radio. Plus, i don't have a surround setup to hear the image in - so i'm a bit cautious and staying away from that buss, after one incident. ?

The link should be right now.

Should be right now.