murat k.

Yes, I shared links because I wanted to point out that it's one of the most anticipated features.

Once it's implemented, I think it will be a big step forward among the other DAWs.

And I also remind you that BandLab has a huge sample library but it's not directly usable in the Cakewalk. 

So when they implement the Built-in Sampler, making it available with the BandLab Online Sample Service will be also a great approach.

And this the looping feedback for the Feedback Loop:

9 minutes ago, msmcleod said:

You can't stop the playhead moving in Cakewalk

For now, but you can make it can. And it would be great to see that kind of a feature in the Cakewalk.

I prefer not using Inline PRV because of this:

PRV has no issues, we need the same note drawing standard in Inline PRV.

Just now, Byron Dickens said:

This is the equivalent of you claiming that your car is defective because the starter grinds if you turn the key while the engine is already running.

No it is not like that and I already found what causes this error and told the solution:

On 11/13/2022 at 9:54 PM, murat k. said:

This problem is happening because between the track change, there is a time you select no track, but at the same time you send a MIDI event. When there is no track focused, the software sends the MIDI Event to all of them. This is why we hear that sound when playing notes and changing tracks.

So when there is no track is focused, the rule to send the MIDI Event to all tracks, changed with to send the MIDI Event to none, it will fix this issue.

Another way to fix this error can be temporarily disabling MIDI send while track changing. It can work however it will not fix it from the core.

Some people here think like "So we should work like that." No, you shouldn't. There is a better way.

This perspective never helps Cakewalk's development. 

If there is a better, more efficient or errorless way; this is the way, not the other one.

8 minutes ago, Byron Dickens said:

That's not a software error, that's user error.

😄You appear again.

On 12/8/2022 at 12:40 AM, SirWillyDS12 said:

If you would stop playing the keyboard before you change tracks wouldn't this effectively stop generating the midi events which would in turn send no midi events to any track?

We shouldn't have to change our way of work because of a software error, but the software should run without an issue as possible it can.

Reminder.

👏+1

On 12/4/2022 at 11:20 PM, RBH said:

but typing in a value  (  or more typically - just doing + 1 - + 2 etc ) would far easier

Press Enter.

6 hours ago, hadada said:

I wouldn't write something like this, which is hard to read. And changing the clef should solve it.

When you work at a wide range it will not solve it. If this thing only needed for key switches, Articulation Maps in Staff View can help him, but not solve the issue.

The issue can also be resolved by adding extra staff depending on the pitch range of your work like this:

Also, this topic is about improving Staff View. I think the best help would be supporting his idea without leaving the concept.

4 hours ago, hadada said:

If just the keyswitch problem, why not create a midi track to store them, or to use articulation maps.

Also he said that he is not using PRV and already requested Articulation Maps for the Staff View.

Using Articulation Maps for keyswitch is a good advice though.

He is just talking about this thing:

The space between the tracks can be dynamic as regards to the highest or lowest note in the track. 

21 minutes ago, sjoens said:

One doesn't expect a tool's behavior to change when moving from one Pane to another.

This behaviour changes exists to help productivity so I expect it. What I don't expect is when it does the thing it shouldn't do like mentioned in this thread:

Smart Tool is not working as expected in PRV when drawing modulations. However same tool works as it supposed to be in Inline PRV.

13 hours ago, David Baay said:

 The Draw mode of the Smart tool will do it if you hold Alt.

2 hours ago, Promidi said:

holding ALT while single clicking in the Controller Lane will place a single controller event.

Please hold ALT @David Thiel.

Also Willy's unique advice reminded me a long awaiting request called "Negative Measures" can be seen in the Timeline of this image:

I hope it will be implement and we will get more freedom in the Timeline.

So I'm wondering can we call it a bug? 

We can't nudge the frozen clip unless we split and merge the Instrument Track, or select MIDI from PRV.

I think this is an issue needs to be fixed.

56 minutes ago, SirWillyDS12 said:

It's the new frozen track, the Un-Nudgable... 😃... So I believe I know what is happening here... You are clicking on the new Audio clip in the track view and that doesn't select the track, can't Nudge... The underlying "midi track" in the instrument track which is now frozen is the original track and is not selected when you click on the new audio clip... If you open up the Piano Roll View with the Track View also visible you will see it... When the underlying original midi clip is selected (as long as the entire track is not selected...) you can Nudge the poor little "sucker" all over the place, Numlock and all and it doesn't "un-select"... Both the original midi and the new audio both move...

Selecting all MIDI in the PRV with the Freezed Audio in the Track View can also work to nudge freezed Instrument Track. Great observation Willy.

But the Numlock thing still exist. Because the default shortcuts use number keys for Nudge, when the Numlock is off these keys turns to alternatives and these keys won't work for nudge.

Directly saving Busses as Templates from the Bus Pane without having to use a Track with sends as a dummy.

I've found one been requested years ago but it's not under the Feedback Loop, so I decided making a new one here, instead of making a reminder.

12 hours ago, Berggren Beats said:

Thanks everyone for your replies, this community seems nice and helpful

 

As someone pointed out, I needed to have the track selected as well as the freezed clip in order to nudge it. When I select a normal non-freezed clip, the track automatically gets selected. This seems not to be the case with a freezed clip.

I also noticed if I make copies of the freezed clip and place them later in the timeline, I can only nudge these one time and then the track gets deselected. So in order to nudge these clips more than once I have to select clip, select track, nudge.. select clip, select track, nudge.. and so on.

This isn't really a huge problem for me but I'm curious to why I have to take all these extra steps to nudge freezed tracks and, in this particular scenario, why they just can't behave like non-freezed clips?

This issue happens with only Instrument Tracks. There is no nudging issues with Freezed Audios. So a little workaround seems fixing this issue.

Right Click on the Instrument Track then select "Split Instrument Track" before the Freeze, then "Make Instrument Track" by selecting splitted Audio and MIDI, it will nugde.

But don't try to nudge below the zero point, because 

On 1/15/2023 at 2:41 AM, SirWillyDS12 said:

It is Un-Nudgable...

Sorry Willy I can't help myself 😄

20 minutes ago, David Baay said:

I mis-read SirWillyDS12's comments, including "I start all my projects at measure two" as being from the OP. The OP hasn't really made clear where his clips start or which direction he's trying to nudge.

Just a little logic can help to get it:

On 1/13/2023 at 9:33 AM, Berggren Beats said:

I can move it by clicking and dragging with the mouse

I also told the solution:

19 hours ago, murat k. said:

Just turn on Numlock. It will nudge.

Just a little more careful reading , that's all we need in this forum.

3 minutes ago, David Baay said:

I'm not seeing a problem nudging frozen audio clips earlier when MIDI from which they were generated starts at 2:01.

Possibly you're are actually selecting a time range all the way back to 1:01 by selecting the track rather than just the clip...?

But I'm curious why such a high buffer, and why so much latency at that buffer size (1024 samples is only 21.3ms at 48kHz). Was 75ms calculated or measured?

Moreover I'm curious why latency has any bearing on freezing virtual instruments which is an offline process not subject to real-time latency.

There is no issue with nudging. He is just talking about  you can't nudge a clip to a position below the zero point which nobody tries except him I guess.

6 minutes ago, Byron Dickens said:

IT IS NOT A BUG WHEN YOU DON'T LIKE IT THAT THINGS OPERATE THE WAY THEY ARE DESIGNED INSTEAD OF THE WAY YOU WANT!

Calm down Lord Byron. 😄  

25 minutes ago, msmcleod said:

As far as bug concerned, there are a lot of posts complaining about bugs which aren't bugs at all - it's just users complaining that the software doesn't do what they expect, either because they don't understand the feature, or it doesn't work the way they want it to work.

When saying "general" it was  also containing feature requests. When you respond a feature request by a workflow which is not a quite efficient way, it disappoints me. Because I am expecting from you to prefer the best and efficient way. When you share a cumbersome way, sorry, I cannot accept it as a solution, it is a workaround. You have power to change things and make things better in the Cakewalk. So I expect from you prefering the most efficient and innovative way, because only with this way we can make an improvement.

This talk is out of topic right now. If you want we can continue this talk in this topic because it is directly related to it:

2 minutes ago, msmcleod said:

I can't reproduce the issue here. Stretched clips are snapping fine for me.

Same here. You can take my comment as general. I prefer a solution from you like: "This will come up in the next update" instead of a workaround. 

Actually this happens sometimes but in general you share workarounds, when a normal user does that it is OK, but when you do that, it makes me think that way.