murat k.

If this issue is not as described here for everyone, they can share screen recordings. Additionally, I expect the developers to fix this long-standing issue. @Noel Borthwick@msmcleod@Jonathan Sasor

This issue, which is unrelated to the zoom value or the end of the clip, occurs in both version of Cakewalk. In the PRV, the length of the last drawn note is memorized, and this length is automatically repeated. However, in the Inline PRV and Drum Pane, the length of the last drawn note appears momentarily, and if the cursor does not reach the half of the note being created, it snap backs, and the note is created with a length of 2 ticks. This issue seems to be caused by a legacy piece of code likely related to the Drum Pane. What needs to be done is this: The rule causing the note to be created with a length of 2 ticks should be removed. That's it.

What frustrates me is not only the fact that a problem that has persisted for years remains unresolved, but also the lack of a community that understands and supports its resolution.

Another issue that has not been fixed for years. Will any steps be taken to solve this issue, or are we expected to just accept living with it? By the way, the same issue also occurs in the Drum Pane when 'Show Durations in Drum Grid' is enabled. It seems that the Drum Pane and the Inline PRV share the same old problematic code; they need to function like the PRV.

Actually, the only advantage Mac has over PC is energy efficiency. Beyond that, it lacks flexibility and confines you to its ecosystem, effectively tying you down. He believes Cakewalk will not be used in the future, and investing time and energy into such software is not the right approach for his business. It’s sad to see a piece of software, mismanaged for many years, being abandoned one by one by its small group of supporters. Despite all the mistakes, there is still ongoing development with some positive aspects like performance improvements. In fact, all the issues concerning Cakewalk’s future could potentially be resolved. It just requires taking the right steps, but given the management and direction up to now, I must admit I have my doubts.

Usage could be as follows: Dragging and dropping an Audio file from the Media Browser or File Explorer onto the Step Sequencer will create a new Row. Along with this, an Audio Clip will be created at the Now Time in the focused Audio Track or in a new Audio Track. Additionally, Right-Clicking on an existing Audio Track will show an option: "Convert Clip(s) to Step Sequencer." This single command will convert both Audio and MIDI Clips into Step Sequencer Clips, eliminating the need for a separate "Convert MIDI Clip(s) to Step Sequencer" command. The target file should be replaceable with another file at any time if needed. There could also be an option to choose whether the files are read from their original location or from within the project.

I've noticed that people generally envision a Built-in Drum Sampler when it comes to the limitations of the Step Sequencer. But that’s not what we actually need at the first place. One of the most significant limitations of Cakewalk in creating Loops is the inability to dynamically generate Loops with Audio files. We’re forced to use Drum Samplers for this, but it doesn't have to be that way. All that's needed is to allow the Step Sequencer to directly read Audio files. This would let us replace the target file whenever we want and change Steps as we wish. In addition, unlike MIDI views, we’d get direct visual feedback through audio patterns. What’s being created is merely a repeated pattern of the waveform image of the target file. Each time a new step is added, only this pattern will be recreated, not the audio waveform itself, ensuring efficient performance. This feature not only addresses a major limitation in Cakewalk, but also boosts our workflow efficiency without the need for another tool. Additionally, it is easier to implement than a Drum Sampler and offers capabilities that a Drum Sampler cannot provide.

For a start, it would be enough if the Step Sequencer only reads WAV files in the assigned steps, without the need to link the loaded WAV file to any MIDI note—this would meet our needs sufficiently. However, with the new Built-in Sampler feature in Cakewalk, this functionality could be much easier than before to implement with MIDI support in the initial phase. Basic additions can make a big difference; other controls can be added over time. I don’t think anyone expects a full-featured Drum Sampler right from the start. The goal here isn’t so much to compete with other DAWs, but rather to make our DAW more practical and enjoyable for making music.

By the way, I really like not only the request itself but also the way it was presented. It directly expresses the topic.

Not constantly. Only with those who are off-topic, or those who claim it's hardly off-topic. My general advice: please, if you're not going to contribute to the topic, choose to remain silent.

Yes, you're right. Not everyone knows that Session Drummer can be used as a Drag-and-Drop sampler, but everyone who uses it does. However, Session Drummer isn’t relevant to the topic here, especially in a discussion about using Samples directly in the Step Sequencer, not Samplers. Giving off-topic advice hurts the discussion of the main subject. Therefore, it would be more helpful if we try to focus on things that support the original poster's request as much as possible.

Everyone knows that this can be done with the help of a Sampler Synth; here, the aim is to use a Sample directly with a Step Sequencer. This can be achieved by selecting a Sample via Drag-and-Drop from the Browser or using the File Explorer in the Step Sequencer menu. Additionally, any existing Sample in the Project can be used in the same way through Drag-and-Drop. Depending on how these files are added, they can either be read from their Original Locations or integrated into the Project Folder as soon as they are added.

Briefly, this feature ensures that the tracks you exclude remain hidden when using the 'Unhide All' command. Otherwise, you'll need to restore the view using the view preset each time and continuously update your view preset whenever there’s a change. When added, it will look like this in the Track Manager.

@msmcleodAs I examined it a bit more, I realized that the confusion here actually stems from the difference between the command in the right-click menu and the command we use in the shortcut. The command in the right-click menu is effective for a single automation, while the shortcut provides a global snapshot option for all tracks with the write-enabled parameter active. For the shortcut, a modification could be made so that if it’s not write-enabled, it only takes a snapshot for the focused automation. This way, we wouldn't need to enable write every time we use the shortcut. I would also like to remind you that the newly added 'Left Click Sets Track Focus' global option in Cakewalk Sonar should also work for Automation and Take Lanes. Since we're talking about an issue with an automation-related command, and I've caught you here, I hope you can address this feature as well. :)

Nice! When this feature is implemented, it will provide you with an additional layer of view preference, serving you much better in your workflow. While thinking about this topic, another specific example came to my mind. For instance, you've created an arpeggio consisting of single long notes. You want to use these arpeggio notes as they are played, but since you might want to make changes later, you decided to duplicate the original track with the long notes to keep it safe. You may never need the duplicate, but who knows? By excluding this track, you can keep it within the file, and even when using the 'Unhide All Tracks' command, it will remain invisible. Use cases can be varied. However, I hope everyone has understood that this feature and its benefits address an important shortcoming in the track view experience and simplify view-related tasks rather than complicating the situation.