murat k.

On 9/6/2022 at 10:19 AM, sjoens said:

When clicking the Cakewalk by BandLab ▼ tab above in Chrome browser, the dropdown menu frequently disappears before I can select any links. Eventually it does work.

Change your mouse. Your left click is double clicking it.

And also working horizontal/vertical flip, stretch, duplicate commands for automation nodes.

1 hour ago, David Baay said:

Assuming you use Always Echo Current MIDI Track, it's not a good idea to change tracks while performing because the synth on the track you're "leaving" can be left with stuck notes due to missed note offs or pedal-up controllers.

Of course, I use "Always Echo Current MIDI", otherwise I can't make sound audition by only changing tracks. Stuck notes issues can be fixed easily by sending MIDI CC commands to the synths during the track change. 

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.

Actually it always happens, but it's related to the changing tracks and notes frequency. 

I mean when you play the same note and change tracks, it doesn't happen, and it can be a workaround.

But when you play a melody and change the tracks at the same time, POM!

By the way playing means not playback, I mean playing the notes on the keyboard and changing tracks. It is not always happening but when it happens the same horrifying sound be heard everytime.

While playing a MIDI or an Instrument track, changing tracks cause all MIDI tracks to play together at the same time which makes us hear an exploding sound .

We have to stop playing then change the track to get rid of this issue, which is not a convenient way when making sound audition.

7 hours ago, scook said:

Something like the navigator pane?

It's more like a folder overview which contains the whole project. Main idea is finding the right time without having to scroll the view.

When working in a big project we can't see all tracks all the time because some tracks just have to out of view when we scroll. But we need to see them for timing purposes.
Track folders have an overview feature but they don't have capability to be visible as a reference all the time.
If we could see a timeline aligned overview as a reference at the top as an "Project Overview Track", it would be helpful.

6 minutes ago, murat k. said:

You can see it when you apply AudioSnap to an audio file and select "Groove" Render Method.

Of course you have a privilige to check the source code as well @msmcleod. 🙂

7 minutes ago, msmcleod said:

There are a number of reasons why stuttering could occur, but it's important to understand the difference between "Online Render" and "Offline Render".

When you stretch clips in the clips view and play them back it's using the "Online Render" which is designed to be quick, but not for quality.  The idea is that you can quickly get it to the length you need, and then commit the changes using the "Offline Render" method - which is slower, but much higher quality.

"Bounce to Clip(s)" will commit the stretch using the Offline Render method.

Of course, you could just make the Online method the same as the Offline, but this means all of your edits will be much slower.

No, I tried every one of them and the result didn't changed. Groove Clip use a setting regardless of any Stretch Methods in the list. It use only "Groove" Stretch Method. You can see it when you apply AudioSnap to an audio file and select "Groove" Render Method. The same stutter errors happens at the same BPM just like with the Groove Clip. We need a preference to change Groove Clip's render method:

14 minutes ago, pinguinotuerto said:

The tedious part is the individual notes themselves and the specific names.

Uhm. I didn't thought that way. Entering drum names always an issue in every editor if you do it from scratch. Maybe you can use Step Sequencer Templates instead of  Drum Maps. I only use Drum Maps to create Step Sequencer Templates in a fast way.

By the way the one you asked can already made by someone else:

https://drive.google.com/drive/folders/1cGzf0mE012jIWq0wu4duF8AtHH5yL6xi

No it's not. Just use Ctrl+Shift to change all selected inside the editor.

And yes, it's all about the transients. Algorithms just creates transients for that audio file with the selected render setting.

40 minutes ago, Herbert Zio said:

I referred to Groove Clip's "Stretch To Tempo", if some setting in "Stretch Methods" could solve the stuttering problem that occurs when using Groove Clip.

@msmcleod Said that after using the "Groove Clip" it could be some transient that got out of place when using the Stretch Tempo in the Groove Clip, and the problem could perhaps be solved by editing through the "Audio Transients" of the track which would basically be using AudioSnap to relocate Transients that are outside the grid.

It's about the algorithm Herbert. If you change the render algorithm to "Groove"  with the same audio file you'll see the same stutter with the AudioSnap just like the Groove Clip.

I've just made a feature request: https://discuss.cakewalk.com/index.php?/topic/51192-groove-clip-stutter-issue/

After applying "Stretch to Tempo" to an audio from the Groove Clip section, in some audios we hear stutter after lowering the tempo.

This happens because Groove Clip function is using one specific algorithm which is not work perfectly for all audio files.

If we could change rendering algorithm from the Groove Clip menu, we find the better one for that audio file and have no trouble anymore.

At the end the menu will look like this:

The discussion made previously in this thread:

I found out the issue. It's related to the audio and the algorithm together. 

I get stutter applied Audiosnap to an audio with the Groove and Percussion algorithm. And Groove Clip seems to use Groove algorithm as default. This is why I heard stutter with the audio when I use Groove Clip. It seems there is no prefence available for to change the algorithm that Groove Clip use. If Groove Clip section had a render method selection we wouldn't get any stutter with the audio by selecting the right algorithm for that audio.

@Herbert ZioI didn't get any stutter with the AudioSnap with any algorithm. But Groove Clip did that. How did you get stutter with the AudioSnap?

Are these features works different on different machines? Can it be @msmcleod?

15 minutes ago, Herbert Zio said:

But, it would be interesting to have a way to visualize and insert the decimal values in the Clip in the Clips Pane.

😄OMG. You were talking about that decimal thing. It was Milton's question. But now I get the point.

Still wondering. Why this makes stutters at the audio after changing the tempo?

3 minutes ago, Herbert Zio said:

In the clip properties in the Inspector.

Clip Properties > AudioSnap

Thanks Herbert but I'm having trouble when I use this feature:

1 hour ago, murat k. said:

I heard problems like stutter or repeats at the sound. It seems there is an unresolved issue at that feature.

I have no trouble with the AudioSnap:

1 hour ago, murat k. said:

By the way using "Audio Snap Auto Stretch (Follow Tempo)" function works without an issue.

38 minutes ago, Milton Sica said:

In the second option which was how I was using it, how to change the view of the percentage increase or decrease to have decimals?

OMG sorry. I just realized you asked it to Mark referring to this sentence for second option:

1 hour ago, msmcleod said:

If you want to change it from 110 bpm to 121 bpm, then stretch it as you did originally using CTRL + SHIFT + drag, but by 90.9%  - i.e.  ( 100 / 121 ) * 110

Still wondering why that feature is not working for me. Any thoughts?

8 minutes ago, Milton Sica said:

For me it worked perfectly.

Why it doesn't work for me? Any ideas?

8 minutes ago, Milton Sica said:

In the second option which was how I was using it, how to change the view of the percentage increase or decrease to have decimals?

Second option just makes audio follow the tempo. Percentage just shows the stretch percentage related to the original audio. These two have nothing to do with each other.

26 minutes ago, msmcleod said:

This is how to do it:

1. Select the Tracks/Clips you want affected by tempo
2. Open the Clip Inspector, and go to the Groove Clip section
3. Enable "Stretch to Tempo", ensuring the Original Tempo matches your project tempo
4. Change your project tempo, and the clips with "Stretch to Tempo" enabled will follow the project tempo

This will however try to preserve pitch.



If you want to change it from 110 bpm to 121 bpm, then stretch it as you did originally using CTRL + SHIFT + drag, but by 90.9%  - i.e.  ( 100 / 121 ) * 110

 

I tried your recommend and after the Stretch tempo and lowering the bpm I heard problems like stutter or repeats at the sound. It seems there is an unresolved issue at that feature.

By the way using "Audio Snap Auto Stretch (Follow Tempo)" function works without an issue.

And it's easy to select the affected audios with the "Edit | Select | All AudioSnap/Slipstreched" function with this way. 

By the way second one talked before in this thread 2 years ago:

New  Project File Window needs to be renewed. It needs two things,

1 - Resizable List Menu
2 - Subfolder Support

Now we can't access subfolders in the Project Templates directory from the menu.

And the Template List on the menu is too small. We can't change it's size.

At first I thought a Safe Mode with Sandboxing separate from the regular behaviour. But on the second thought I realized that we won't need Safe Mode. Because with the Sandbox Technology the DAW will be safe as heaven. It will be like all those naughty crabby plugins are buried in the sand in a box and problem no more, while we enjoy making music on a beach on a glamorous day. 😇