Jump to content

Search the Community

Showing results for tags 'bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News & Announcements
    • Product Release Info
    • Frequently Asked Questions
  • Cakewalk Products
    • Cakewalk by BandLab
    • Instruments & Effects
    • Feedback Loop
  • Community
    • Content
    • Tutorials
    • Songs
    • General Music Discussion

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

  1. Hi¡ I'd like to submit what seems like a bug in my opinion in the latest update of Cakewalk by Bandlab. I have a track effects bin with multiple eq plugins of the same brand (fabfilter). All of them have some automation info embedded into their respective automation lanes. The thing is that whenever I delete one of these plugins, the automation info on the other plugins of the same kind and brand gets deleted as well. If it were only the automation info pertaining to that specific plugin, there would be no problem; this would be normal behaviour. However, the issue is that it deletes the automation info pertaining to the other plugins as well, the ones which are not being deleted. I have found a workaround this problem by copying the automation info of all the track to another track and then pasting it back again to the original, but it would be great to have this bug fixed as it's probably not to hard to do so. Thank you.
  2. Hi all, Hope you're well. I've started encountering a bug whereby if I try and save track templates, Cakewalk will crash. If I then try and import these track templates it will give an error message about truncation. It doesn't seem to make any difference whether i'm saving a single track or several - it will just take varying lengths of time before it closes. The project template itself has a fair few buses and is approximately 250 tracks in total, but I don't think there's anything ridiculously complicated in it. On an older version of my project I was able to save track templates of various sizes - so this appears to be a new bug or there is some sort of inherent corruption in the project file. Any idea how I can troubleshoot this further or should I just raise a support case directly with Bandlab? Many thanks for your time. Matthew
  3. 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!
  4. 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.
  5. 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
  6. 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!
  7. 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.
×
×
  • Create New...