lychee

For my part, I don't really have any problems with the "new" Cakewalk interface. On the other hand, it might be time to rework the submenus. The cursors, buttons and co in Windows 95/Vista style are very dated. I also hope for the disappearance of the Vista Smartglass type frame when you reduce the working window to display several projects at the same time.

It is false, they survived: https://www.gibson.com/en-US/ But as I said above, for those like me who had subscribed to a lifetime subscription, we should have sued Gibson for deception on the goods. But asking Bandlab for a special price, No, I don't see how a contract with Gibson would concern Bandlab, Bandlab owes us nothing (rather, we owe Bandlab for saving our DAW).

Since we're bringing back the Sonar name, why not reintroduce an updated version of Studioware? A system with modules, like FL Studio's Patcher?

I also bought the Sonar lifetime subscription, but that was under the Gibson era. I don't see why Bandlab should honor a contract I made with Gibson, we should have sued Gibson at the time. I understand Bandlab wanting to do business with the DAW they bought very expensive in the hands of Gibson, and besides I never understood Cakewalk's free policy, even if I took advantage of it. Me, I'm willing to pay to thank the saviors of my DAW, but I'm also willing to change DAW if they goes into a subscription policy at all. Sorry, I just skimmed the thread, I don't know if the question is decided?

Thank you @DallasSteve, your thread allowed me to understand (even if it was not the goal) how to enter midi in Ovox, via the vst3 button. I think it will also help me on another plugin with which I have the same problem, but this time to send midi.

Hello. I recently became a user of the Reason environment, and I use the Rack under Cakewalk. That's how I discovered the power of a modular interface that creates interactions between different plugins. I know that there are this kind of interfaces in several DAWs, like Bitwig, Ableton Live, FL Studio ... but it is lacking in Cakewalk, or in a less extensive way. I thought it would be cool to evolve Cakewalk's FX Chain in this direction and allow it to accommodate instruments, midi plugins ... to create more complex things. Yes, I already have the Reason Rack and I know that there are alternatives (VST host), but Rack only takes compatible plugins and it's always better to have something integrated into your sequencer. If the developers hear me, what do you think of my idea?

Ok, it works perfectly now, but it's weird, I was sure I had tried this before. Well anyway it works, thank you mr msmcleod, and be careful if someone walks around with a sword saying "there can be only one". 😄

Oh ! A guy who followed the same route as me looks like? I started to compose my first sounds on Atari / Amiga and Protracker, then on Octamed (which could play both the samples of the usual trackers, like the midi) before coming to PC with Cakewalk. Surely there are programs for converting tracker files to midi, or is there a modern tracker called Renoise that maybe can play and convert these old files.

OMG! me who thought I was one of the oldest guys on this forum, you just showed me that this is not the case. Even your headphone is almost as old as me. 😅 I started the adventure in the 90's with Cakewalk Express, then I got down to business with Cakewalk Pro Audio. The only thing that I regret and that I find that we have taken a step back is the stopping of Studioware. The possibility of creating your own interface to control your external midi machines, but what a genius idea! If there is one thing that I would like the Bandlab team to re-integrate and in a modern way, this is it. In any case, happy to count you among the Cakewalk users, long life to you and to CbB!

Thanks for wanting to help me @Will_Kaydo, but apparently that's not it. This effectively opens the part of the track dedicated to automations, but when I close this part, I no longer see all the automation contained in the track and which should be visible on a single line with the note information. Automation track open: Automation track closed:

Hello. I have a classical music project that I have been working on for several weeks, it has a lot of complex automation curves. One day, without my noticing it, all these curves disappeared from the main window, but are still activated and visible if I open each automation icon of each track. Everything works fine, but not seeing them in the main page, it's annoying and disrupts my workflow a bit. Am I unintentionally doing a keystroke again and making these lines disappear, or is this really a bug? I did not find in the settings the way to make them visible, please help me. For information in case it is a bug, I use the last version dated Cakewalk (2021.01 build 98 64bit). Edit : I just found out that the problem is with Cakewalk as a whole, not just my current project. I must have done a bad manipulation, but which one?

Hello. Again I have the same problem with the automation curves when using fast rendering of my music. When I try to output my music as MP3, Cakewalk lowers my expression automation line to zero and messes up two other parameters making them orphan. I have a feeling that this is going to be difficult to fix, but I send you my saved file with and without the bug, hoping that you will find the solution. Cordially. Without Bugs.cwb With Bugs.cwb Without Bugs.mp3 With Bugs.mp3

Heeeeeeeeelp, I'm on the verge of hanging myself! I don't know if it's my machine or if it's Cakewalk, but for a while now I have encountered big bugs in the automation curves. I was doing a brass track and I was starting to draw a CC expression curve directly from the clips menu. At one point I clicked to make a right angle and there the program took me out of the track. When I wanted to come back to it via clips, the program tells me that there is already an expression track, without however being able to access it. I tried to make it appear via the automation lines button, but that created a lot of automation lines except the one I had already drawn beforehand. Before that on another project, I encountered the same kind of madness, except that this time I had created several automation tracks, whose content no longer appeared in the "automation lines" view. I'm not also going to tell all my stories of buggy or orphaned curves ... but you just have to remember that there is really something wrong on this side. Here is my brass file, hoping you will find where the problem comes from. I will try to reproduce the first problem I encountered, to also send you the file. In The Stone.cwb

Thanks guy (or girl, who know)! 😅

Thanks @Promidi but I know about it, and you will notice that my thread is almost 2 years old now. 😆 I am really happy that this feature has finally been implemented, thanks to the Bandlab team.