msmcleod

@Ronny.G - We've fixed the issue with templates that you reported in your first post. This will be available in the next release. Your latest issue sounds like it could be different, but it could also be related to the original bug... did you load any track templates in this project? The original bug means that the MIDI ports are in a strange state after importing the template. This might explain why you cant change the ports after importing. For the moment, I'd advise against loading/saving synth templates with routing until the next release. Routing from hardware MIDI ports should be fine, but if the template contains MIDI routing from synths within the template, that's where the issue arises, and it pretty much messes up all the ports. Like I said though, it's been fixed for the next release.

Whilst this is true, it basically boils down to this: 1. Take a note of the measure the clip ended on before you change tempo 2. After changing tempo, you want to stretch it so it ends it on exactly the same measure as it did before. This is why I recommend slip editing to end exactly on a measure boundary before doing the stretch. As a general rule, the bigger the change in length, the worse the quality is going to be. There are different stretch algorithms that do a better/worse job depending on the type of material you're stretching. Also there's an offline / online method - where online is what you'll hear doing what is showed in my video, and offline is what is used when using bounce to clip(s) and exporting. By default, the online algorithms are quick but average in quality. It's designed to make editing quick. The default offline algorithms are slower, but much better quality. There's nothing to stop you changing them to be the same however (i.e. make both online/offline the slower, high quality versions). You can change the methods in preferences:

For non-groove clips, this is what I'd do:

My thoughts exactly. I rarely need to display them, but when I do, I need to be able to scroll them. Especially on my RME, which has 17 of them.

I normally use the Event View, and insert it right at the top of the list.

If all your audio clips are groove clips, all you need to do is make sure your Now time is at 1:01:000, and change the tempo in the transport module. The groove clips should automatically change to the new tempo.

@Mike1212 - There's an extra function that was added that won't be in the help: Holding M1 and pressing the Plugin button will switch to the Synth Rack, allowing you to control synth parameters. The synth rack is a "Mix Strip" in the same way tracks, buses and mains are. Navigation works in the same way to plugins on a track or bus, but it navigates through the synths within the synth rack. The best way to envisage it is to see the synth rack as a special track, with a collection of synths as opposed to a track with a collection of effects.

This is likely to be due to limitations of layer functionality in MIDI tracks. If you put each clip is in it's own lane (so they're not overlapping), does it behave correctly?

The overlay just ensures the buttons on the X-Touch match what Cakewalk expects. As far as I can tell, the X-Touch has all of the Mackie Control buttons. The X-Touch Compact, X-Touch mini and X-Touch One have less buttons, and may not directly map to what Cakewalk expects. Documentation for the buttons can be found by pressing F1 when the Mackie Control panel is up ( Utilities->Mackie Control 1 ), or alternatively you can open the help file directly - "C:\Program Files\Cakewalk\Shared Surfaces\MackieControl.chm"

The inability to select is just down to zoom level. You can always just use the track select to select everything. The split tool isn't available when the edit filter is set to envelopes, as you can't split envelopes - which is what you're editing. The reverting back to clips mode bug is a tricky one. It's reverting back way after the operation has finished.... we're still looking into it.

Thanks @rfssongs - this has been fixed for the next release.

Is the MIDI Driver mode the same in Platinum / CbB ? It maybe that you've got the MIDI driver mode set to MME in SONAR and UWP in CbB? Check your settings within Preferences->MIDI->Playback and Recording. Note - you can't change this while you've got a project loaded, so go to preferences as soon as you've launched Cakewalk.

While Drum Replacer is primarily used for replacing drums on a single track (i.e. your snare track, kick drum track etc), you could duplicate the track or clips and isolate each drum on the duplicates. You may get better results applying some additional EQ to each duplicate to try to isolate the drum you're trying to replace before running it through Drum Replacer.

This was the page I saw it on: https://www.manualslib.com/manual/1908369/Novation-Impulse-49.html?page=8#manual

Just had a quick look at the manual. It mentions the other MIDI ports in the Control Surface setup. It looks like the Impulse only supports HUI, which might work with the Mackie Control if the protocol is set to HUI (beta). If you're not going to use it as a control surface, I'd just have the first MIDI IN 1 / MIDI OUT 1 ports enabled.

When keyboard controllers have more than one MIDI port, usually the first MIDI port is used for the actual keyboard, the sustain pedal, and the modulation / pitch bend wheels. Any additional MIDI ports are normally used for faders, transport control, or any additional controllers your keyboard may have. The idea being, that you can assign MIDI IN 2 / MIDI OUT 2 to a control surface (e.g. Mackie Control if it has Mackie emulation, or Cakewalk ACT ), but still use MIDI IN 1 for recording normal performances. A third pair of MIDI ports might be used for changing the settings of your keyboard (i.e. assigning control surface mode, or assigning CC values to faders etc). You should check the user manual for more info.

@Astraios - thanks for the report. It looks like this only happens when drum maps are in play - we'll look into it.

@Ferenc Hegedus - this has been fixed for the next release. It was caused by a couple of other fixes: - Moving partial selections were not being cropped - Moving step sequencer clips were being cropped In the next release, you won't need to mess with Non-Destructive MIDI Editing. As long as the clip was fully selected when you move it, it'll retain its original length.

I tend to use linked MIDI clips when I need to do this - i.e. create a new MIDI track, and copy the MIDI clips as linked clips to the new track. The new track is then routed to the additional synth. That way, altering the original will automatically update the linked clips. This also allows you to add MIDI FX or articulations to the linked track to make further alterations without affecting the original clips.

If you're using Articulation Maps, once you've imported/defined your map they're there forever. You just need to add it to your project. From then on you just draw the articulation over the parts where you want the notes repeated an octave higher. Right clicking the articulation and selecting "Apply Selected Articulations" will convert them into real notes allowing you to alter velocities etc, or you can right click on the header and apply the whole group or every articulation in the track. It really couldn't be any quicker. I've attached the articulation map used in this video. Also, there's no reason why you can't add extra articulations with a lower velocity - i.e. "+ Octave Lower -16 vel" so you don't even need to tweak them afterwards. If you've defined lots of velocity variations, you can right click->Reassign to pick a different velocity version until you get it to what you want. Add Extra Notes.artmap

That's an interesting idea - so basically a meter showing the difference between post clip gain & pre-fader. I've no idea how useful this would be in a practical sense though - unless the only thing you have in your fx bin is a compressor. It does raise a thought about maybe being able to patch a reduction meter between any two places in the signal chain. That would mean you could put it "around" a specific compressor plugin, or any group of plugins. It would also have to cope with increases in volume, not just reduction. Still not a trivial piece of work... but worth a discussion.

Putting your computer to sleep rather than turning it off is likely to cause problems. When awaking from sleep the state the audio driver thinks the audio interface is in, is quite often different from what it actually is - and this is what is causing the weird sound. You're lucky it doesn't just crash. This is completely down to the audio driver implementation, and nothing to do with Windows or CbB. The same applies for hibernate.

I requested this a while back before I was a staff member... now that I've looked at the code, I realise why we don't do it - VST / DirectX doesn't natively support it. The only way this could be done, would be to allow the binding of a meter to a VST parameter chosen by the user (assuming of course the VST in question actually exposes the meter position as a parameter). This is not a trivial piece of work, and throws up a bunch of issues like how to define/map the meter scale etc.

Changing the name in the clip properties pane within the inspector will change the name for all selected clips: