murat k.

I'm sure that everyone knows about it so it's funny that you think it wasn't thought. No. You will not opt to use a VST for that because it is not an option. You have to. But after the implementation, yes you can opt to use a VST for that.

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:

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.

No it is not like that and I already found what causes this error and told the solution: 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.

?You appear again.

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

Press Enter.

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.

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.

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.

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.

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.

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 Sorry Willy I can't help myself ?

Just a little logic can help to get it: I also told the solution: Just a little more careful reading , that's all we need in this forum.

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.

Calm down Lord Byron. ?

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: