Will.

5 minutes ago, David Baay said:

But I don't see how that relates to the independence of Patch Points and Aux Tracks. 

Because the send does not create the input as it should its rather linked to the interleave and not the input. Whereby the interleave in the Input shouldve been linked?

No? 😕 Am I incorrect? 

3 minutes ago, David Baay said:

This may or may not be unexpected; 

Yes, I have. Its why i created this thread. 

When sending a mono (interleave) send to an Aux and you switch the Aux to mono and engage its phase invert button it doesnt cancel out entirely - as what it should. 

This means: The mono input on the Aux does not fully collapse the two channels into mono. 

9 minutes ago, David Baay said:

Yes, a Patch Point is essentially just  a stereo 'pipe' 

Got it. 👍

10 minutes ago, David Baay said:

Some confusion may arise 

There's plenty, but not from what it is and how it works- rather from its carrier. 

15 minutes ago, David Baay said:

but the two objects are really independent of each other.

Not quite. 

53 minutes ago, David Baay said:

The Patch Points that connect sends/outputs to Aux tracks are inherently stereo,

So basically its just a locked duplicate channel thats panned L-R in Cakewalk that are being fed/patched into the Aux. 

I have been reporting this issue before and it fell on deaf ears. I'm well aware there's a small team though - and it is why i'm repoting this again. 

This happens in every project I do when doing cuts and cropping a file. It will line up a few measures and later in the TV it automatically happens again. It is so faint if you do not listen for it you wont notice it, but when you do - you'll pickup the timing issue.  Check the video. 

2 hours ago, Bristol_Jonesey said:

Can you elaborate on this?

I find what you're saying/asking is confusing

It is simple. Changing the Aux input of a send does not follow the rule of the input change. Switching the input between L/R/S bring no change to the strip. In my studio DAW: When doing a stereo send and change the input of the bus to mono - it creates a mono send.

It is extremely important to know that you have to create a Bandlab Account and not mistakenly going to the old cakewalk.com website.

Create one by click the orange link seen here

https://www.bandlab.com

Or . . . 

Go to the Help Tab in the DAW and click on Sign-in and create your account from there. If the in-app method fails (which often does and for some reason only accept the entry after three continuously attempts) go to the official website in the link above.  

Am I correct to assume that Cakewalks Audio, Aux and bus tracks are duplicates of one (the same) Audio Track within itself? This is noticable on sends and inserts. The input of a send does not correspond with that of a send. 

Cant this extra Outs that CbB creates when inserting mono instruments be removed by default? Cakewalk is the only DAW that does this and its ANNOYING every time!  @#$%! 

On 8/21/2022 at 6:00 PM, Cactus Music said:

USB mikes that don’t come with ASIO drivers rarely work with Cakewalk. They are designed for Podcasting not recording. Even if it works the tracks will record very late on the timeline. 

This is highly incorrect. I have 4 USB mics and two 3.5mm jack mics that works 100% perfectly with CbB without the "Late recording" issue you're mentioning in my laptop with Asio4All with Windows 10.  I have never had an issue with these mics. Shockingly some of these are in the same ballpark as my 2 phantom mics. 

I use the usb mics on preamps and for backing vocals sometimes even on drums because they sound much cleaner and fuller. Each frequency at 20hz - 20khz. 

Just two weeks ago I captured the room reverb of my kitchen with a $30 M800 and a no name $20 podcast mic both with a 3.5mm jack and used it in a track. The reverb came out sounding sweet like a "Vocal Room Plate." 

What David said. 

Also, you're putting an EQ after the limiter on an already "Mastered" track as you've said.  So there are no ceiling to limit these spikes.  

Then of course: In order to use the pro channel EQ you have to engage the Pro Channnel, which is moduled after real console channels. So you will always have a slightly boost in +dB. 

Its pretty straight forward. You want to be on M:B:T

I went through every tab and menu to look for this, but it does not seem like CbB has this feature - so here goes. 

Feature request to flip/mirror/tilt the automation that has been drawn in. The picture below shows a mistake on the second Automation Lane. It was suppose to "Mirror" the top lane. 

This could be maybe done by right clicking on the "desired/highlighted" nodes and choose to Mirror/Tilt/Flip. 

EXAMPLE:

I know we can highlight only the bottom or top nodes and just drag them up or down to be mirrored/flipped/tilt, but the link that holds it together when doing this drag feature are not very reliable or strong. It sometimes jumps its own way and often grabbed the rest of the nodes too. 

Sounds like you're getting what is called dropouts. That being said: Do you get a little blue window in the right bottom corner when this happens? 

10 minutes ago, Base 57 said:

Can't you use the "Audition" function (Shift+Space) for this? The loop will still be an 1/8 note long but only the selected clip/s will play, regardless of the length.

No. 

57 minutes ago, Noel Borthwick said:

We can consider reducing the minimum loop size below 8th notes. 

Thank you. Appreciate taking time in considering this. 

57 minutes ago, Noel Borthwick said:

A DAW needs to do a lot more setup for looping 

Cant you just remove the limitation on the snap from the end of the looping marker, because the start of the loop marker works in milliseconds. Most DAWs i'm familiar with works this way. Cant it just mirror the beginning?  Asking.  

2 minutes ago, marled said:

but at least it works.

Yes, I too have to rely on workarounds as well by using third party samplers, but why should that be, if the only thing preventing this from being done in the DAW - is the snap of the loop playback? It can at least snap to ticks. 

EXAMPLE:  Let's pretend this was an actual problem in the sample. 

Here I have a Closed hat. I only want to listen to the slightly darker (also known as the dynamic region) highlighted area, but I cant. The loop points/markers end - stucks at a 1/8th of a note. So, listening for headroom when doing comping on the attack without the use of a compressor is currently impossible. 

The size of this sample is a 1/16th of a note in the measure.

8 hours ago, Noel Borthwick said:

Um you can do as much surgical editing as you need. Looping is not intended to be an editing tool.
Use normal snap and zoom with the sample ruler to do surgical edits. Please move this to a different thread since its not related to this release.

Noel how are we suppose to locate and hear the playback in a rapid loop to tame or add to a comping section if it doesn't go smaller than a 1/8th of a note?  You cant hear the actual "perfect" headroom in the comping with this limitations on the loop points/markers? This is especially true on letters suck as S,T,K,B,P or the spike on a Snare. Advance editing is where we do vocal comping on these problem issues before I add any process effects. You get artists that do not want their vocals to go through any pitch correction vsts - so we have to rely on comping to keep the vocals natural tone and pitch in letters, and words. The less workarounds you use the more you retain that natural elements of the data.

To argue this is actually disappointing, seeing it is extremely crucial edits. 

1 hour ago, Noel Borthwick said:

There is nothing to fix because it isnt a bug. It is intentional that the loop length cannot be made smaller because there are problems rendering tiny loops. In any case there is no musical value in setting loops that small.

It's a shame. So that means you're going to limit and prevent us from doing surgical comping edits? got it . . . perfect! I don't believe anyone render these small samples, but what we do in fact do is - we use the loop point markers to surgically locate the precise area to do a cut. 

1 hour ago, marled said:

This is also a problem if you have a plugin that has a learn function and the area is too small (e.g. a drum hit)! I've had such a conflict several times.

Hopefully, it will get fixed for the next release. 

18 hours ago, Richard Mynderup said:

When bouncing a midi track that starts on measure 2 to it's audio track, the music on m. 2 of the midi track ends up starting on m. 8 of the audio track.  Don't recall this as a problem before.  Appreciate any help.

Thanks,

Richard

Very long user of Cakewalk/Sonar

The midi/clip data you want to bounce always needs to be highlighted in order for it to always align up. 

Have any of you tried to delete your current "saved" kbn file - not the Sonar key assignments.kbn file.

Copy your current ssved keybinding file and paste it in a safe location and delete the original. Close CbB and create a clean template. Re-assign a few shortcuts, hit apply, okay and relaunch Cakewalk. Confirm if that worked. 

On 8/21/2022 at 3:37 AM, msmcleod said:

Right - understand.  It looks like the minimum length of the loop is clamped to 1/8th note. This is what is causing the jumping.

Correct. Would appreciate it if we can finally fix this.

I did report it here many versions ago - more than twice, but never gotten a positive response.