Will.

37 minutes ago, murat k. said:

Request Number 14 Update:

While waiting The Developers to release the new big update, I wrote a script for Bringing Color Menu Over The Clip with Autohotkey. The script clicks the background color setting in Clip Properties and brings The Color Menu over the clip. It works when you use The Inspector with it's default location but you can change the click location to anywhere if you want.

If you don't know about Autohotkey. It is easy to use, just install Autohotkey, load the attached file by double clicking it and press F12 when the clip is selected in Cakewalk. You can change the shortcut key by changing the beginning of the script.

Color Menu Over The Clip.ahk 297 B · 0 downloads

I don't see how it will improve the DAW. 

Nothing wrong with the request though, there might be others that will enjoy the feature with you though. 

5 hours ago, Lord Tim said:

Let's take CbB out of the equation for a second.

We can't do this, cause I've tried another DAW, nothing like that happen. 

5 hours ago, Lord Tim said:

On the other hand, if there is audio happening in the silent channel when you look at the WAV then you can work backwards through CbB to track down when that begins.

Bingo! There's nothing on the opposite channel on the WAV when you export, but Cakewalk projects sound coming from there. I even tried looking into "DIM SOLO," made sense at the time lol. Fiddled with PanningCompactLaw as well it was on "False." Checked my panning law too. It's set to "0db Center, Balanced Control." 

One answer I'm not getting is if anyone else hear this when they go close to their monitor of feel the woofer doing something? 

3 hours ago, twelvetone said:

I was going to say Offset is on...

Even if you create a fresh project, copy some audio in a mono track and pan hard?

 

It's off. Was one of the first things I had checked. 

10 minutes ago, Craig Anderton said:

Is there a mixer applet in the background?

Interesting. Does the windows 10 one counts? Plus, the motherboards onboard updated version - which is MSI. 

Hope this got some attention. Clicking to get to a certain plugin, is irritating. Why can't we just scroll through the plugins with the Mouse Wheel? 

I guess you're right - think i'm going to give it that 70's feel. 

15 minutes ago, Teegarden said:

I'm confused: so the advice from the CbB release is wrong (that leads to 512 KB Playback and 256 KB Record with interface at 256 KB (only one setting possible for both Playback and Record so it can only be in sync with one at a time)?

Next to that I thought that for playback during mixing (especially with extensive projects) it's even better to use 1024 KB or higher driver buffer size (meaning that after tracking you always need to increase driver buffer sizes for mixing and vice versa) 

LOL. You're reading to much in what is being said. You don't touch anything under the "Sync and Caching" TAB. 

ONLY IN DRIVER SETTINGS TAB.  Here's mine 

Picture 1:

Only set these settings to taste. 

Picture 2: 

Don't change anything here as what was said to you and what's explained in the Documentation. 

Also make sure that you choose your hardware driver (Should be ASIO) under the "Playback and Recording Tab."

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? 

18 hours ago, david40 said:

This is really weird. I have a song that has only 4 tracks, but if I mute all 4 tracks I can still hear a version of the song playing. I can't figure out where this music is coming from.

Any suggestions??

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 

20 minutes ago, Teegarden said:

Thanks for all the feedback! 
I found out that I've changed the setting myself long time ago, when I started to get pops and cracks. It was advised by CbB in the Version 2018-09 release notes:

"To optimize playback and reduce the potential for dropouts or audio glitches, we recommend a Playback I/O Buffer Size value of about 512 (KB) if you are experiencing any performance problems. You can change the Playback I/O Buffer Size value in Edit > Preferences > Audio - Sync and Caching."
 

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" 

19 minutes ago, Craig Anderton said:

Is the track interleave set to mono?

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.

4 hours ago, Bassfaceus said:

cakewalk BB is pausing at "creating UI" so is it something with WIN 10

and the way its handling my graphics?

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. 

4 hours ago, John Vere said:

Now all this above is related to recording audio. Midi is different. 

Midi latency can be caused once again by the entire system. 

 

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. 

57 minutes ago, Josh Wolfer said:

I'll take that over "WTF is this garbage", any day

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

1 hour ago, Teegarden said:

My bad. I wrongly assumed that in order to change the buffer size you needed to enable caching. Clearly you can change the buffer size without that.

I noticed that playback was double (512 KB) the size of the record (256 KB) buffer size. Is that standard for CbB? Do you know why making them both the same size has a positive effect on latency or is it just by trial and error that you found it to be 

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. 

1 hour ago, Josh Wolfer said:

O. M. G.

Once again, whenever I think I know damn near everything about cakewalk, I learn something new.. this is awesome. Thank you!

Priceless reaction. 😂

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

31 minutes ago, Teegarden said:

I checked this to see if it could be another tweak for my system. The CbB reference guide says:

"Enable Read Caching and Enable Write Caching. Choosing either of these options lets Cakewalk use the Windows disk cache while reading or writing audio data. Cakewalk will usually perform best with all caching disabled, which is the default setting. If your computer has an older IDE disk controller, or a disk controller that does not use DMA transfers, enabling caching may improve Cakewalk’s audio performance."

It seems to me that it is better to not use this option on a relatively new PC.

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? 

24 minutes ago, msmcleod said:

We'll look into it. In the meantime,  you can always delete the remaining nodes in a second pass.
 

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!

52 minutes ago, Simon Wilkinson said:

Lol, I appreciate the help Will!

Trying to speed up my workflow by using a MIDI controller but I feel like I should just work around it for now and get stuff down.

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. 

1 hour ago, Simon Wilkinson said:

Before my middle-age turns to senility and becomes its own landmark node  

Lol. 

On 10/15/2020 at 9:40 AM, Simon Wilkinson said:

I don't have anything like that under Prefs/Control Surfaces:

 

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.  😣😢

On 10/11/2020 at 12:24 PM, Emmanuel Cervetti said:

One shortcut to Increment or decrement per-selected-notes-velocity ( without to have to zoom and meticulously verticaly grab and drag  up and down... very annoying and the main time loss in my worklow)

 

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.