msmcleod

In this case you should use Copy Special / Cut Special / Paste Special , and ensure tempos, markers and key/meters are checked. Ripple Edit All causes everything in the project (including other clips) to move along with the thing you're moving. In the case of Ripple Edit All Delete, everything in the project in that time range will be deleted, and the gap it would have left is closed up.

I regularly switch between my RME and my Focusrite Scarlett 18i20, and also occasionally my Yamaha 01X. The way I do it is by making a backup copy of the following in %APPDATA%\Cakewalk\Cakewalk Core : AUD.INI Cakewalk.ini ctrlsurface.dat INSTRMAP.INI TTSSEQ.INI I've got a set of backups of these files from when Cakewalk was configured for each interface. When I want to switch, I close down Cakewalk, copy the relevant backup back to %APPDATA%\Cakewalk\Cakewalk Core , then restart Cakewalk. You could easily make batch files and put them on your desktop to do this for you.

The Export Audio dialog respects selection, so if you've only got the end fade out selected, that's all it'll export. For a complete song export, either select nothing (CTRL + SHIFT + A), or select everything ( CTRL + A) before opening the Export Dialog. Personally, I prefer to go with no selection when using the Export Audio dialog.

Do this: Select all the clips you want to delete automation from From the main menu: Edit -> Delete Special Uncheck everything apart from clip automation Click OK.

Articulations are not sent 'on the fly' every time the now time is moved. This is intentional so as not to flood the MIDI queue with events during editing. Articulation events are only sent if the transport is engaged (i.e. playing/recording/scrubbing), or when you click on an articulation section. If you want an articulation event to be sent when editing, click on that articulation section in the PRV.

Yes, something definitely up here. We'll look into it. In the meantime, a workaround is to ensure you give each clip a unique name in the clip inspector.

Thanks for reporting this @Toy - we've identified the cause of this issue, and it's been fixed for the next release.

This certainly isn't normal. The only time I had this level of instability was when I had OneDrive watching/syncing my project folder. Disabling OneDrive fixed it for me, but actually all was needed was to ensure that my project folders & global audio folder were excluded from all cloud sync apps / virus checkers / incremental backup processes. Cakewalk needs exclusive access to your audio files when doing any audio clip operations like transposing or moving a clip. I can't say whether this is the cause for your instability issues, but it's worth checking.

You're better opening the project directly within Cakewalk, by selecting "Browser BandLab Projects" from the File menu.

@jkoseattle - I'll do my best to explain... As you know there are 3 types of tracks within Cakewalk: - Audio Tracks - MIDI Tracks - Instrument Tracks An instrument track is actually just a combination of a MIDI track and an Audio track, where the clips view shows the MIDI part, and the track view shows the Audio part. The inspector shows an Audio/MIDI tab so you can get more granular control, but behind the scenes there is actually two separate tracks. A Simple Instrument Track is an instrument track whose MIDI channel is set to Omni (i.e. all MIDI channels). A Per-Output Instrument track is an instrument track with the MIDI channel set to a specific channel. Other than that, they are exactly the same. What Append Instrument Track does, is take the next highest available MIDI channel and the next highest available Audio Output of the current synth, and assign them to the new instrument track. So if your existing instrument track is set to MIDI Channel 1, and is getting its audio from Synth Audio Output 1 L&R, appending an instrument track will create a new instrument track wired to the same synth instance, but set to MIDI Channel 2 and sourced from Synth Audio Output 2 L&R. You can keep on going until you run out of MIDI channels or available synth audio outputs. TIP: Although you can use Append Instrument Track on an existing Simple Instrument Track, it's usually inadvisable, unless you first change the MIDI Channel of the existing simple instrument track to Channel 1. You can do that in the inspector, when the tab is set to MIDI. That way, the MIDI channel / Synth Audio Port assignment will match up as you continue to append tracks. You can also fix-up the MIDI Channels afterwards if you forget. When using Append Instrument Track on an existing split instrument track, it does the same, except you get a separate Audio / MIDI track created. But the same thing happens: the MIDI track gets the next highest available MIDI channel, and the Audio Track gets its source from the highest available synth Audio Output. Of course, as I mentioned in an earlier post - you still have to map MIDI channels to audio outputs internally within the plugin itself. For synths such as Kontakt, you may also have to create the audio outputs within the plugin. Append Instrument Track is greyed out if you've run out of MIDI channels or you've run out of synth spare synth audio outputs.

This sounds like a mismatch between the Windows Sound sample rate and Cakewalk's sample rate, when using the same audio interface for both Cakewalk and Windows Sound. Windows has a nasty habit of forcing the sample rate back to 48KHz. Either make sure the sample rate matches by changing your Windows Sound sample rate to match Cakewalk's, or use a different audio interface for Cakewalk if you have one.

@Keni / @gmp - The export dialog checks for duplicate filenames at the time you add the task. After that, there are no more checks. The task queue is designed to be run without any user intervention/interruption, so files will be overwritten if they already exist.

@jkoseattle - the console issue is not something we've seen before. Is it possible you're running out of memory? The East West libraries can be pretty big if you use a lot of them. Could you post your current machine specs, i.e. RAM, CPU + speed ? The other thing that could cause this might be a MIDI feedback issue if you're using any loop back devices?

It depends... if your pedal has a line level input, then you don't need a re-amp box. If it's just got a HiZ guitar input, then you will need one. Most of the time you can get away with a passive DI box rather than a dedicated re-amp box. You should be able to get a passive DI box for around €15 - €20.

PluginBoutique has been selling Melda stuff for years FWIW.

I've seen a few of these, as we worked with BablyonWaves to help them get these out, and a lot of work has gone into these. Some of the more complex libraries have far more than just simple key-switches.

Download the web-installer which will install build 16. This will fix this issue.

@jkoseattle - it sounds like you're using per-output instrument tracks. While Cakewalk will automatically assign the each track to the appropriate MIDI ports / audio outputs of the instrument, it's still up to you to internally assign the MIDI ports to Audio ports within the plugin itself. For example, within TTS-1 this is done here: Within Omnisphere: If you've forgotten to do this for one of the MIDI channels, and it's still mapped to the same output as MIDI Channel 1, then any audio volume changes on that channel will also affect channel 1's output.

They're stored here: %APPDATA%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts ...so you should just be able to copy them across. I suspect however, that the presets rely on each plugin being in the same location as it was on your old machine. For those that aren't, you'll probably need to re-categorise them.

We made build 16 due to a regression in the step sequencer, which the web installer picks up. The backend BL server hasn't been updated yet, which is why it's still showing build 15.

It's not a bug, it's working correctly. When you Ripple Edit All to the left, everything between the destination point and the start of the dragged selection is deleted, and overwritten by everything from the start of the dragged selection to the end of the project. What results were you trying to achieve?

Articulations aren't stored in the same clip as the notes, they are in their own single clip which always starts at measure 1.

Things to check: 1. You're using the smart tool, and not one of the others ( tip: F5 will engage the smart-tool, the other tools can be engaged using F6 thru F10) 2. All of the relevant smart tool functions are enabled: The other thing to check is that you've got the correct track active in the PRV track pane, and it's not locked.

@Andres Medina - can you PM me your project? I can't reproduce this issue.

For the most part this will work, however the "Extract Keyswitch Articulations" command may have unexpected results in some circumstances as it'll pick up the first articulation that matches that key. If you just happened to have another articulation overlapping that one in the same group, only one of them would win out either partially or wholly replacing the other. Also remember that you're limited to 255 articulations per articulation map, regardless of how many groups you use. There is however, nothing stopping you from creating more than one articulation map for the same instrument (e.g. one articulation map for "left hand" articulations, and the other for "right hand" articulations).