msmcleod

Thanks for this @Adam Biser - I've identified the issue and fixed it for the next update.

The web based BandLab DAW doesn't support video, however if you're running Windows 64 bit ( version 7 or above), you can use Cakewalk by BandLab to download your BandLab project and add a video (Cakewalk supports a video track). This thread highlights the new BandLab integration for Cakewalk: It's worth mentioning however, that: 1. Cakewalk is a DAW, not a video production suite. The intention of the video track is to score music to video - not to produce videos. 2. You need to ensure that the correct video codecs are installed in Windows.

@Adam Biser - I can't seem to reproduce the overlapping articulation issue, though I can obviously see the result in the attached project. Can you post a version of the project before you did the operation, along with details of exactly how you selected, copied (or cut) and pasted? As there's so many different ways to do this (e.g. drag drop, from the menu, CTRL +X, CTRL+V etc), using the exact steps will hopefully lead to a repro. Thanks.

The settings are sored in flash memory in the nanoKONTROL 2, and no, they don't need any button dance when starting up. Once you've configured it, it should just work from then on. @Dav Mar - up until recently, the Korg USB MIDI driver was not compatible with Window 10 2004 / 20H2, which meant the editor wouldn't work properly (you'd make edits, but they wouldn't be saved to the device). I believe they've now got updated drivers on the Korg website. Personally, I've removed the drivers from my Windows 10 boot and just use the nanoKONTROL 2 as a class compliant MIDI device. This works fine, but you can't use the editor. I've got a Windows 7 boot that has the old drivers & editor on it if I ever need it though.

It could be something like a virus checker trying to access the WAV file while Cakewalk is trying to finalise the file after recording has stopped. Have you checked that all of your Cakewalk project & audio folders are excluded from virus checkers, OneDrive and any other cloud-sync apps?

It's not asking you to create a bundle file. The cwp file is referencing audio files in the "D:\Bundle Files SONAR\Toy Cantando\Serie 2 Patita Lulu\0207 Balones Perdidos Piratas" directory. It can't find that directory, so it asks you if you want to create it. Once it's created, it then (unsurprisingly) can't find the audio inside it.

The Mackie Control support was developed by Cakewalk in association with Mackie, at around the time the original MCU came out (I think it was around 2004/2005). With the exception of the faders and transport controls, most of the MCU's buttons were "up for grabs" and Mackie worked with the major DAW developers at the time (Cakewalk included) to come up with overlays that better reflected the functionality provided by each DAW. The result was that each button had a different function on each daw, and common functions such as looping were controlled by different buttons between DAWs on the MCU. Since then, the majority of control surface manufacturers have decided to provide emulations of the Mackie Control, rather then opt for their own protocol - however most of them lack the all buttons provided on the original MCU. Up until the demise of Cakewalk Inc., most of these control surfaces provided a SONAR mode which sent the correct button combinations to achieve the desired function in SONAR and Cakewalk. Some control surfaces such as the PreSonus FaderPort series, and the Korg nanoKONTROL series still provide a Cakewalk/SONAR mode, so users should have no issues using those surfaces using that mode. The Behringer X-Touch (the largest one), seems to fully emulate an MCU - it has all the buttons, and you can buy Cakewalk/SONAR overlays for it. This should also work fine with Cakewalk. But unless a control surface specifically says it supports Cakewalk, do not assume that it will work. This is especially true for the single fader controllers, where one button press on the controller actually sends out a combination of button presses to the DAW. Unless they're sending the button presses Cakewalk expects, it's not going to work.

That decision was made before I joined the team. I don't know the reasons behind it.

Yeah, I do this too - especially when switching between laptop & desktops. I tend to use loopMidi as you can rename the ports so they even look the same.

From what I remember, the Window and Strength parameters give you similar functionality: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.39.html

FWIW - in this scenario I use one of the two workflows: 1. Use SHIFT + double click to maximise the waveform, then either SHIFT+double click again or CTRL + ALT + Z to minimise. 2. Open a new screenset and use SHIFT + double click on the other screenset. I can then switch between screensets quickly using keys 1 through 9.

You need to turn the groove clip back into a normal clip. Select the clip and right click "bounce to clip(s)"

Yes, this is exactly what the issue is. You need to use 64 bit DLL's.

I'm not sure why this should be happening, but you shouldn't need to restart Cakewalk to get it working again. At most, just switching the audio engine off and back on again should do it: Is it possible it's just a UI glitch? In other words, does Cakewalk continue to record on those channels?

Actually, it's probably the opposite... i.e. using "Set" may introduce duplicate tempo entries at the measures/beats - which is fine - they'll stay there as long as you don't edit the tempo envelope. So multiple uninterrupted "Sets" one after another will be fine. Editing the tempo envelope is likely to remove those duplicates, which makes it harder to then use "Set" afterwards. As Cakewalk is essentially M:B:T based, the tempo map is central to all time calculations in Cakewalk where absolute time is involved (which is basically all the time). Keeping the number of entries in the map to a minimum is crucial for performance reasons.

If all you have is jumps, then essentially they are the same in that the tempo at any point in the timeline will match. That doesn't necessarily mean however, there is the same amount of tempo entries in the tempo map as there is in the tempo list (although if they indeed ALL jumps, then it's likely they will be the same). 1. If you created a bunch of nodes all at 120bpm in your envelope, there would only be one entry of 120bpm in the tempo map (the first one) as there are no changes in tempo. For the most part, only tempo changes are written back to the tempo map. 2. When you create a curve or a line from one tempo value to another, individual tempo jumps are inserted into the tempo map to reflect the changes in tempo over the course of the shape (in a similar way to how it looked before if you were to draw a line or curve in the old tempo view). The resolution of the tempo changes is governed by the TempoMapDecimationResolution initialization variable (defaults to a 16th note). What you see in the tempo inspector is the start and end tempo, and the curve type. What is in the tempo map, is lots of individual tempo changes. However... the above is only true when you edit the tempos inside the inspector/tempo track, or use "Insert Tempo Change" or "Insert Series of Tempos" commands. In these cases, you're working on the tempo track envelope and the tempo map is then rebuilt from that envelope. If you're using "Set Measure/Beat at Now", or using any of the tempo extraction methods (e.g. dragging a clip to the timeline, extracting the tempo using audio-snap, or using "Fit to Improvisation"), then the reverse is true: those commands work on the tempo map first (like they always did), and rebuilds the tempo track envelope from the tempo map. Given the above, if you're using "Set Measure/Beat at Now" then it's important not to edit the tempo yourself between setting measure/beats - just continue setting the beats and trust it to do its job.

The Set/Measure Beat At Now functionality has not changed in any way. It still modifies the underlying tempo map in the same way as it did before. The only difference is that now the tempo track envelope is reconstructed from the underlying tempo map after the Set/Measure Beat at Now command. Do not confuse the Tempo List in the Tempo Inspector with the old tempo map. It may look the same, but it isn't. The Tempo Inspector shows a list representation of the envelope nodes, not the tempo map.

It's working for me.

We don't have the TTS-1 source code. TTS-1 is a Roland product.

You probably need to add the Native Instruments VST installation path to your VST Search path within Preferences->File->VST Settings. It's normally "C:\Program Files\Native Instruments\VSTPlugins 64 bit" Then click the Scan button on the same page.

Thanks @Promidi - we've found the cause and fixed it for the next update.

@John Vere - @scook is correct here. The Record Bit depth is the bit depth the WAV files will be recorded at, which is totally separate from the Audio Bit Depth in your driver settings. You can set your audio bit depth to 16 bit, and still record a 24 bit file - it'll only be 16 bit quality though. The audio bit depth of interfaces (for recording) is slightly misleading in any case.... AFAIK... and maybe this has changed... but, most AD converters are pretty much 20 bit in any case simply due to the limitations of the hardware. They use 64 x, 128 x, or 256 x oversampling to mitigate this to some extent. The DA converters in most modern interfaces are pretty spot on though. When audio interfaces say they're 32 bit, that usually means they're sending/expecting audio data as 32 bit words. It doesn't necessarily mean that they're actually sampling incoming audio at 32 bit accuracy.

I took a look at this earlier on - it is a bug. While its true that in Windows there isn't any way of truly distinguishing between hardware MIDI ports (although Cakewalk does try its best to get around this by also using the device name), this is not what is happening in this case. The issue is that it's losing the internal MIDI device ID of the soft synth when loading the template. It then gets that mixed up with the real hardware device ID. Disabling the MIDI output of synths that you don't need MIDI output for will go some way to mitigate this issue.

Quick groups work on visible items (so you don't end up changing something you can't see and are unaware it's been changed), so this is expected.