Search the Community

I installed the free u-he plugins yesterday and the one in the title causes CbB to stop responding and crash with no error or apparent issue showing. You don't even have to load the plugin. Simply having it in your browser and interacting with the browser causes Cakewalk to hang. The other plugins don't have that issue and Triple Cheese works normally in REAPER and Cubase LE 10.5.

So, there was an issue with my UI at first. I figured it was because my version of Cakewalk was out of date, so I decided to update it. When I went to Bandlab Assistant and tried to update it, however, it was stuck at "installing." I did some searching, and decided that the best course of action would be to uninstall and reinstall Cakewalk. I backed up my vsts, and uninstalled cakewalk, making sure not to delete shared files. Once I tried to reinstall, however, I ran into the same problem as before, with it being stuck at "installing." At this point I am frustrated and confused, and I am desperate. I see on some forums that you can install it manually by finding the exe file in the system folder. I check there, and sure enough, I find a file called "Cakewalk_by_BandLab_Setup_27.01.0.098_r1.exe" which gives me a sense of relief. I try to open it, and it says "the file or directory is corrupted and unreadable." Under it is another exe file, "Cakewalk_by_BandLab_Update_Setup_26.09.0.006.exe", and I try that one despite being out of date. The wizard fires up, and I select my language, but I am then met with another message saying "This installer requires Cakewalk by Bandlab version 2020.08." My computer is up to date and my drivers are good. I'm confused and nervous, as I have sunk a year and a half on this program and I do not think I would realistically be able to learn another one any time soon. Does anyone have any idea how I can fix this?

There seems to be a bug with the MIDI program change message in Bandlab. I have a MIDI .cwp file that works correctly with my old copy of SONAR 7 but it doesn't work with Bandlab. Both use the same default general midi .ins file. I checked the MIDI being sent to my external synth using MIDI-OX. Bandlab sends an extra PC message, C0 00. This causes the program change to be overridden and always changed to the first patch. SONAR sends the message correctly.

I can only assume this is a bug, as ive tested it in every way possible, an no-one else seems to have a solution. Automation lanes sending MIDI CC to external gear are delayed ONLY when recording a sequence to an audio track. So, for example, I have a midi sequence sequencing a MODX, in addition to this, I have an automation lane controlling filter cutoff. If I monitor the audio track the MODX outputs to and hit play, everything is in time, the filter opens when i want it to, HOWEVER, if I then proceed to arm the audio track to record, then hit 'R' to start playback recording, the automation is late, delayed by about 1 or 2 bars (at 128 bpm). I have also included an image for reference to explain what I mean: using the image as reference, the red lane is the filter cutoff for the midi sequence (green notes). If the audio track for the external synth is monitored, and simply 'play' in cakewalk is hit, the gear is sequenced perfectly, that curve is at that exact point, HOWEVER, should the audio track then be armed for recording, and recording started using the midi sequence, the automation is sent late, approximately where I have marked. Ill include an example of the 'late' automation: late_automation.mp3 Combined with this image, you should be able to hear the difference between when the automation is sending, and when it should actually be sent. the filter should open up BEFORE the lead starts playing, as sequenced (and which it does do if you simply hit play and monitor the audio), however, it doesn't, as can be heard, it opens AFTER the lead starts, which is later than it is sequenced. This ONLY happens when recording the audio from the external synth when sequencing it from cakewalk. I have checked everything, timing offsets, buffer sizes, nothing is wrong, I even looked at the midi events cakewalk is sending, and the times for the start and end of curves etc... for envelopes are sent at exactly the right time (though, I was using the cakewalk event viewer). This is also not exclusive to just my MODX, every synth I have ever sequenced with cakewalk has experienced this. I have tried multiple different audio drivers, including those for the interface in the MODX, with no change. EDIT: So after some digging around, it turns out this happens ONLY when a count in for recording is set, this suggests to me its unintentional, and certainly a bug, but should also be a quick and easy fix.

I was wondering if I should make this post or not, but it has run its course. There are some issues with the notification system that make it unusable and getting more in your way than anything: - When you click on the bell to see which notifications you have, clicking on any of them automatically marks all the others as read. That makes notifications semi useless, as now you have to remember which notifications are new and which are not simply because you chose to see one. - If you click on the bottom toast to see a notification you just received, it's not marked as read on the bell. While that might be a desirable feature, it may lead to user annoyance after they either went away for a while or weren't paying attention, see a notification on the bell and it's from a message they've already looked at or responded to.

Not a huge deal, but while the Bakers are being so attentive to us, I figured I'd ask. I fat finger the automation lanes button all the time. I mean to open up the comp lanes. And when I do this and quickly click it again to un-show the automation lanes that I never wanted to see in the first place, Cakewalk creates a volume automation envelop and leaves it in track view. I really don't need to see volume envelopes until I get to the mixing phase and I want to create fader automation. And I don't really want to see unnecessary automation lines on the track view. It'd be nice, if you open the automation lanes and close it without actually having any fader envelope nodes defined (leaving it in automation "jump" mode for the entire project), the track view continued to not keep the fader automation visible. I know, I'm being pedantic. But I do this all the time. Never hurts to ask. On a side note, if the take lanes and automation lanes icons were more visually distinct, like they were different colors, I'd probably discern between them more easily. But ever since their inception, I click the wrong ones constantly. So I don't think my brain is going to stop. Cheers. 3E476386-5DE6-4558-A557-126280C87FED.MP4

Since no one answers me about my previous question (https://discuss.cakewalk.com/index.php?/topic/25244-some-keyboard-shortcuts-stopped-working-in-prv-not-docking/), I am obliged to open a new topic. Please, could anyone tell me how to roll back to a previous version? I just want a version that works,,,

Running 09.2020 for now. Have a project with about 13 instances of Dimension Pro. Tried adding an instance of Chromaphone 3. Appears to add ok, but as soon as I go to play the project I get a crash. Dimension Pro 64 is showing as the source of the crash. You can see the crash occurring here as it occurred during a live stream: https://www.twitch.tv/videos/813105494 After that I tested something else. I opened an essentially blank test project with no instruments loaded and then added Chromaphone 3. The project played fine. I then closed the test project and went back into my main project and tried to play it, I got another crash even though Chromaphone had been loaded to a different project! I'm assuming there's some memory mishandling here, but I don't know if it's a Chromaphone or a Cakewalk issue. The fact that I experienced this issue with something occuring in one project affecting another led me to believe it was a Cakewalk issue. Cant add minidump for now as it exceeds the max attachment size but can provide if needed.

Bouncing multiple tracks to a created mono track sometimes gives you all the tracks mixed to a single mono track, sometimes gives you a number of tracks mixed into the single mono track selected and a new mono track that contains the rest. There's no way to turn this behavior off. Changing interleave or setting the destination track to stereo or mono doesn't change anything. Even if you set that bounce to stereo, it will do the same thing, except the tracks will be stereo. The only way to make the feature do what it's supposed to do is sending all the audio to a bus and bouncing that bus to a track. Then it respects what you have set on the settings. Aux tracks exhibit the same bug.

I have a particular use case and I'll do my best to explain it. I'm working on synthestration and my track structure looks as such: a Track folder with a bunch of instrument tracks in it Track folders labeled with a "version" of the score I'm working on. within these version folders are MIDI tracks that correspond to the available instrument tracks in the "instruments" folder. I make big changes to the score periodically and I essentially just duplicate the "version folder" which contains the midi tracks and continue from there. Yes, I could keep these version iterations in their own project files, but I like to have quick access to the previous versions. Loading in a ton of sample libraries in/out just to hear previous version, is not ideal. Also, I like being able to compare notes and harmonic structures, all in the same project. And midi data is small. This shouldn't be a big deal at all. The Challenge I'm constantly soloing out different groups of midi tracks in order to hear how they're playing with each other. When I solo a midi track(s), it works exactly as you'd expect. But when I unsolo the midi tracks, I get no sound, because the source Instrument track remains solo'd, but there are no corresponding midi tracks to feed the instrument track. I have to go to the console bar and click the solo button to un-solo everything and now I'm back to normal. This is unideal. What I'd like is that if you solo a midi track or group of midi tracks that feed an instrument track, upon un-soloing the last midi track that feeds the instrument track, both the last midi track AND the instrument are no longer solo'd. This would have a much more pleasant work flow. Here is a clip to show the issue directly: clip.MP4

Trying to score a short video. Created a video track, thumbnails are visible when I choose them. However like others on this forum before, 'Open Video View' does nothing. I've been through Workspaces - Video View is not available anywhere. The 'Advanced' Workspace setting, where Video View at least used to be an option, (and others have solved this problem), does not appear anywhere. In no Workspace setting does a video option appear, including Custom and the 'Track Control Manager'. No video option in the views tab either. It used to be under the Lyrics view. I've also changed around all of my monitor/display settings, in case the Video View was docked somewhere I couldn't see. That's not the problem either. Maybe there's a master UI panel that I'm missing, where I choose the view options that are available overall? Any help would be appreciated. Thanks!

I've been using Cakewalk for decades and I've lost count the number of times I copy a group of clips, tell the DAW to paste to a certain time/point, yet the group never pastes properly! Say I want them to start at 6:00, most of the time the paste puts them starting at some seemingly random point after 6:00. Please fix this once and for all.

Anybody experiencing problems with the magic tool when comping? (version 26.11.0.098) It's always worked flawlessly but now clip resizing seems to have acquired a bug. It happens when I have "cut" a clip with the magic tool in comping mode (which works fine). But then when I move the borders of the clip in the track lane (by floating on the crossfade and moving the mouse vertically until it becomes the "comped clip border moving" tool) and resize the clip with click and drag, CW often shrinks the clip on the right side, leaving a hole between the right side of the clip and the next clip. It doesn't happen all the time. but quite often. I have no special settings different than what I've always used (auto crossfade, haven't touched anything related to the arranger etc), nor touching any key modifier when dragging to move the clip border. If I use the "comp" tool (as opposite to the magic tool in comp mode) all seems to be fine. Anyone else seeing this?

I'm currently working on a song, and for some reason, cakewalk decides to stop MIDI playback. Nothings wrong with the drivers, it's not an audio dropout either. The velocity bars just turned grey/gray... help? I've tried everything in the Cakewalk MIDI playback manual.

I downloaded Bandlab Assistant and updated it by clicking a green update button. It finished updating. Upon clicking a green log in button, nothing happens. Attached is a picture of what I see. I have uninstalled and installed again, but the same thing happens. I have Windows 10 and a 64-bit computer.

These days it's hard to record backing vocalists due to covid, so I purchased a new backing vocals synth (the engine is EastWest's Play 6.2) and I'm learning the ropes by trying it on a song I'm mixing. What I'm specifically doing is to automate the "volume" control of the synth so that I can control exactly where the sound fades. In order to do that, I add an automation envelope on the synth's "volume" parameter, and set up a simple 4.-nodes fadeout curve. This works fine. The problems start when I add 4 new nodes to create another curve: I can create the nodes alright, but I when I move the points, the previous nodes move or disappear. If I then move one of the nodes and undo, some of the midi data after the last node disappears! If I undo again (to the event where I have just created the last of the 4 notes), the data reappears. Here's the link to the Dropboxed video . The behavior is repeatable (even if open/close the DAW etc). Is it something in this project that's corrupted? Or anyone has experienced issues with MIDI automation? It's really the first time I use automation envelopes on MIDI tracks so don't know if it's known issue or something. Automation on audio tracks (which I use a lot, all the time) works just fine. Obviously there's other ways to do what I want , but it should work.. Thanks! PS: Cakewalk is updated to the last version (today's) but I experienced a version of the problem last week, with the previous version.

Hi! The following s a small thing, and hopefully easy to fix, but it always irritates the beejeezus out of me. Not sure if it's a bug or by design, but in the second case I'd ask to review the design 🙂 I am pretty sure it's been the behavior from Sonar times, but hopefully it's a simple fix. I use a two-monitors setup, and I have CW on the left monitor and undocked windows on the right one: typically for the console or the tempo map (full screen) or sequencer (typically a fit-size window). Of course a new project starts with the various windows docked, so I undock the interesting window (say the console), move it to the right monitor and maximize it. When saving the project, CW remembers this which is great. So far so good. However, I often compose ideas switching between a demo I build piece by piece in CW and some other application. Typically that's a text editor where I am writing the lyrics and updating them to find the best flow with the music, or a browser, whatever. In doing so, I often close the undocked window (not CW) on the right while it is maximized full screen. After a few minutes, I reopen the same window (say the console) using the keyboard shortcut (or the "Views" menu).. CW opens the window undocked, but immediately resizes it to whatever not-full screen size it had before being maximized. So I have to go and click to maximize it again. 😭 This thing can repeat itself dozens of times in a writing or mixing session, and its mightily annoying. It seems that the menu is opening the window and then for some reason issuing it a request to toggle its size from maximized to not maximized. Which makes no sense, no other program I use insists in returning a window in non-maximized state if it had been closed as maximized (within the same runtime session, of course, I would understand if I were closing Cakewalk), So, the request: would it be possible to fix that behavior, and re-open an undocked window in exactly the same state it was when it was closed? (if it was closed maximized, keep it maximized, if it was closed not maximized, keep it not maximized) I love CW to bits, but this would really make me love it more! Every single unnecessary click is incredibly frustrating when you're balancing a guitar in front of the desk and trying to focus on the music or the mix. If there's already a way to change that behavior, happy to be told of course! Thanks! -Cris

As described. Contradictory behaviour when using a drum map view in the piano roll. I'd really like to be able to use the Alt+Scroll shortcut to zoom while working with drum maps.

I made a selection somewhere in the middle of my project (control-A , then set the selection start and endpoints) and then on the video ruler right-clicked and exported video. H.264, quick audio bounce. What I got was the audio from the selection (middle of the project - correct) and the video was the entire original video (incorrect).

Hi, as recorded* in the attached video, horizontal scroll with my built-in Dell touchpad changes the view of the the clip pane and the ruler/timeline independently. If I don't remember to go grab the scroll bar, the UI may trick me. * w/ OBS 2020-10-12 10-46-37.mp4

I have a video open in a project, the thumbnails and frames as well as audio are working fine but the video view won't open. Clicking on the 'open video view' on the track and on the thumbnail does nothing, and the keyboard shortcut also does nothing. Restarting Cakewalk didn't work.

I have a project with 66 tracks, arranged into 13 track folders. As I was moving the last few tracks into Folder #13, and then clicking "Save", Cakewalk responded with "General Error" and I could not save the project from that point onward. So I went back to a previous version and tried again to move the un-foldered tracks into Folder #13, but this time, one at a time, and then saving after each move. I could move about 3 or 4 tracks this way until I hit "General Error" and had to close the project and re-open. After a few closes/re-opens, I was able to move Track 66 into Folder #13 and hit Save and it successfully saved. Folder #13 has 9 tracks. The most tracks that any of my folders contains is 14. If I am hitting some kind of Cakewalk track/folder limit, I shouldn't be able to bypass the limit by closing and re-opening the project. Something's amiss here.

Hi all! Can someone verify this bug? If you have a step sequencer part that you loop (by dragging it out horizontally), the vertical playback position indicator in the step sequencer window only scrolls by once, but not on any subsequent looped repetitions. One would expect the current position indicator also to loop in the step sequencer, so that you always see where you are, making it easier to program patterns. I'm still on 2020.01 due to intensive projects, but I haven't seen anything that indicates that this would be fixed in newer releases. Thanks for any help.

Experiencing some odd behaviour, while working with a project every things is all ok then for no reason I can fathom the panning on all channels stops working everything becomes centered mono. This is true for instrument tracks and recorded audio. Is this a known bug?, I have already rebuilt one project that this happened to, but now it has happened again. it is as though the signal path has become corrupted and everything becomes centered with no panning at all. Anyone got a clue? My projects are not easy to setup again and there is now no workflow just frustration.

First some config details of my PC which will hopefully rules out some possibilities (or explain the issue). i am running Win7. i am using the standard display adapter on my gigabyte motherboard, which is a standard Intel based screen adapter, and the stock display driver for it. i.e. nothing "weird" or extreme in my graphics. MOTHERBOARD: GRAPHICS: Every now and then, when I display the virtual keyboard, it comes out "miniaturised". Normally it looks like this, i.e. as expected. BUT sometimes, and I do not know how to force it to do this; i.e. I don't know how to repeat it, apart from hiding it and then re-opening it a few times and eventually it will fail. But of course, when I actually wish to use it, it comes out bad the very first time