Search the Community
Showing results for tags 'bug'.
-
I just started a new project and am experimenting with Arranger. All was going well, it's pretty rudimentary at this point, but now I'm in a place where I try to Duplicate a section and Cakewalk crashes. It's pretty reliable. I'm a software developer, so I know how important it is to be able to reproduce a bug! If you can't do that, you can't find and fix it. So I have a ZIP file of my project if anyone at Bandlab wants to look at it. Right now it's super simple - a drum track and a rhythm guitar track. I wanted to attach it but it's larger than the forum will permit. I've been looking in vain for any place where I can report a bug; if anyone knows where I could do that, please forward this to them. Thanks!
-
Hi All, The title is a bit misleading after doing some work. Perhaps someone can enlighten me as to why I'm see this behavior . I just spent the last hour combing through the threads and reading the manual when I fixed my problem. Here is what I saw: I had "screenset" 1 set in a new project I started today. I was working with some samples using the "Media Browser". To make extra room, I had "removed" the "Help" module. This gave some room and left a module header bar that said "Help Module" and contained the ">>" marker (or button) that would allow me to collapse the "Media Browser. After working a bit I started to set up some screensets for my workflow and what I kept running into was a problem with screenset 1. I would collapse the "Media Browser", then switch to another screen, but when I came back to 1, the "Media Browser" would be open again. This started making me crazy as I knew that I was doing it correctly (or so I thought). What I discovered (just as starting this thread) was that IF you close (collapse) the "Help" module, the header remains on the screen to support the ">>" marker. If that condition exists and you collapse the "Media Browser" to the right side, then go to another screenset, when you come back the "Media Browser" is there again. It is almost like the screenset save is weirding out for 1. Well the "workaround" is to un-collapse the Help module (you can type "Y"), re-collapse the entire right side panel (including the Media Browser) using ">>", go to another screenset and "BOOM" it works now. How strange is that. The reason I went to this length to type this that I thing this my be a bug, but maybe not?? What do you think? I think it may be something that is not supposed to happen (i.e. a bug). I try messing with the workspace setting to fix it but that was not the problem. Syphus
-
Hello there. When I use "Cut Special" tool, even if the "Delete Hole" option is unselected, the hole is removed regardless. Am I doing something wrong or it is a bug? Thank you.
-
Hi guys, There was a bug a while back where projects would remap the midi inputs to another controller when you reopened the project, this was fixed, but now appears to be back again. The fix last time wasn't 100% fix either, it only fixed new projects, old projects would continue to map to a different midi controller. It's not the end of the world, but it is super annoying. What is worse though, is that sometimes the outputs map to a different soft synth, so if you've got a projects with 10 or so synths and suddenly all the midi tracks are randomly pointing elsewhere, it's a little tiresome to fix Cheers
-
I am completely new to the world of DAWs so apologies in advance for sounding clueless. I have just installed Cakewalk and I essentially cannot use it at all due to extreme lag with the UI. Anytime I click anything or even try to adjust the window, there is a 4-5 second delay before the action is registered. I am not sure how to fix this or even what settings I should begin to look into. To the best of my knowledge, all settings are at default, and my audio drivers are up to date. Does anyone have any idea what I might try to fix this issue? In case it is helpful, here are the relevant specs of my PC: CPU: AMD Ryzen 7 2700 RAM: 16 GB DDR4 3200 MHz Like I said before, I am completely new to this stuff so please let me know if there is any other information I can provide to help diagnose the issue.
-
When recording using the midi-keyboard, I found the following bug: The note key "Fa-1" does not work. And it does not work only in Sonar by BandLab. The keyboard itself, M-Audio Code 25 , is new and fully operational. Even when changing the octave, the note “Fa-1” does not work on another key. I am attaching a video in which this bug is visible and audible: 1 - The Sonar Platinum — works; 2 - In Cubase Elements 9.5 — works; 3 - In Pro Tools 12 — works; 4 - In Sonar by BandLab - DOES NOT WORK !!! What is the reason for this bug, I can’t understand!
-
At times I have the problem that the volume automation, and at times the automation of other parameters, is not being read, even though reading is enabled and everything. When playback is paused and I just move the playhead to a part with different automation values, they do change. But when I play through the part, the values do not change, and the automation is then also not included in the exported file.
