Czeslaw Posted Sunday at 03:48 PM Share Posted Sunday at 03:48 PM Hi all! Please... How to make Midi and Audio clip start to sound later by 50 ms, without moving them along the line of time? Thanks in advance! Link to comment Share on other sites More sharing options...
Max Arwood Posted Sunday at 04:13 PM Share Posted Sunday at 04:13 PM 1) Sonar has this feature built into it. It is there for shifting slow attack strings so the timing feels correct. 2) you could add a time alignment plugin. Several companies make them. 3) If you need this frequently, you should look up the nudge feature. It can easily shift + & - amounts. Link to comment Share on other sites More sharing options...
Czeslaw Posted 21 hours ago Author Share Posted 21 hours ago (edited) Thank you! But I do not understand points 1 and 3. And I'm talking about Cakewalk by Bandlab. Edited 17 hours ago by Czeslaw Link to comment Share on other sites More sharing options...
Max Arwood Posted 14 hours ago Share Posted 14 hours ago #1 would be to upgrade to Sonar because it has the feature you want already built into it. #3 Nudge. Look it up in Cake help file. It will show you how to set it up and how to use it. Or google “cakewalk nudge” Link to comment Share on other sites More sharing options...
57Gregy Posted 9 hours ago Share Posted 9 hours ago On 5/4/2025 at 11:48 AM, Czeslaw said: How to make Midi and Audio clip start to sound later by 50 ms, without moving them along the line of time I don't see how you can do this without physically moving the clips. Maybe a delay which allows you to set 'dry' and 'wet' conditions, i.e. the delay is set for 50 ms with the original, uneffected audio 100% dry so it's not heard, and the delayed audio is then heard later. Is there even a delay which can do that? 1 Link to comment Share on other sites More sharing options...
mettelus Posted 7 hours ago Share Posted 7 hours ago I admit I was a bit confused by that comment as well. Just a word of caution... the whole purpose of the timeline is so you can visually track when events occur... if you start using other methods to "nudge" them, you will need to drill into each one to find out what is going on. Far better to be able to look at something and know when it starts and stops in relation to everything else. Here is the documentation on configuring Nudge Settings (you can easily set one of the 3 options to 50ms). Nudge physically moves the event, which you will actually prefer long term. To drill in (and set) Nudge preferences: In CbB... Edit->Preferences (default shortcut is P)... on that pop up, be sure "Advanced" is checked at the bottom, then on the left pane... Customization->Nudge. By default, the nudge commands are assigned to the number pad (1, 4, and 7 to shift things left/earlier (by nudge 1, nudge 2, nudge 3).... 3, 6, and 9 to shift things right/later (by nudge 1, nudge 2, nudge 3)). The values you set in preferences will be the default, so 50ms for "nudge 1" will shift the selected event 50ms earlier (with NumPad 1) or 50ms later (with NumPad 3). Visually you will have a much better time tracking things if they land on the timeline precisely when they start/stop. Link to comment Share on other sites More sharing options...
msmcleod Posted 5 hours ago Share Posted 5 hours ago For audio clips, you've got 2 options: 1. Nudge the clip by 50ms; or 2. Put a delay effect in your FX bin. Channel Tools has the ability to delay tracks by small amounts, both in ms or samples. For MIDI clips, again 2 options: 1. Nudge the clip by 50ms; or 2. Use the Track Delay in the inspector. CbB only allows this to be specified in ticks, whereas Sonar you can specify the delay in either ticks or ms. For CbB, this means calculating the equivalent ticks value for 50ms. There are 960 ticks per quarter note, and tempo is specified in beats (quarter notes) per minute. So: 1. Multiply your tempo by 960 to give ticks per minute (e.g. 120bpm x 960 = 115,200 ticks per minute) 2. Divide by 360,000 to give ticks per millisecond (e.g. 115,200 / 360,000 = 0.32 ticks per millisecond) 3. Multiply this by the delay time in ms, e.g. 0.32 x 50ms = 16 ticks. So a delay of 16 ticks at 120bpm is 50ms. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now