murat k.

I need to change Fade Line color and FX Header color on the Clips. When it's implemented it needs to be for both selected and unselected situations to work for any situation.

Normally we use Shift key for sensitive controls in the Cakewalk. But it doesn't work on automation. The Shift key works for horizontal or vertical restrictions when moving automation nodes. So there could be a keyswitch for sensitive controls when we are moving automation nodes. Alt key works for Drawing nodes. Alt+Shift key works for Line Drawings. So I suggest Ctrl+Shift key for sensitive controls about node editings. Also it will be great if it will work with also single or multiple Clip Gain controls as mentioned in this topic:

Changing clip gains with the Ctrl key is a very useful feature. By this feature we change the clips gain individually without revealing the Clip Gain automation lane. But it doesn't work for multiple clips. So I suggest Multiple Clip Gain control on Ctrl+Lbutton drag over the clip.

Autocrossfade is a great tool. Moving a clip over another clip, and adjusting the crossfade position with crossfade move tool is great. But if we remove an autocrossfaded clip to a non-crossfade necessary position, the last crossfaded position is remaining over the clips.

These accidental changes are happening because controls of the Console View are responding hovering over mousewheel actions. If there was option to activate the controls only after the selection, these accidental changes would not happen. When you select a slider or knob, a rectangle is appearing around the control like this: I mean if mousewheel would respond only after that, it would prevent us to make any accidents on Console View. This is the core of your problem. When it will be implemented, your problem will be gone and you won't care about that kind of accidental changes or need individual display changes anymore.

But yes. @sjoens is right in a way. There is an issue about creating a new Take Lane when overlap. After the expand of the Take Lanes, if you collapse Take Lanes and make another overlap. No new Take Lane is creating. Expanding the Take Lanes breaks this feature.

It should be. There is an issue in the software. That's why this topic is created. Documentation is clear. Tracks and Take Lanes are different things. You are just mixing them up.

No. Anything you enter is a take. You don't have to use record button for that. This can be correct if a take lane was created only after when you record. But any event you enter creates a Take Lane. The documentation is correct. When the clips overlap each other, a Take Lane is creating. It happened because you tried it when the Take Lanes are expanded. When they are expanded you are directly moving a clip to a Take Lane. So DAW thinks that you are making this move intentionally. Yeah it can be but with small numbers over the Take Lane icon. Not this way.

The problem is that button is not changing it's state everytime as it supposed to be. Because Means: If you drag a clip on to the project or create notes on PRV or Staff View, or even you create an event with the Event List, that button do not change it's state. But if you drag a clip to another track, Take Lane button of the dragged Track becomes that dim lit state. That button should be at dim lit state all the time when there is a clip on the track. That makes the confusion.

It is an indicator for there is a clip on the track. Means there is an existing Take Lane. But If you don't want to see semi-lit anymore just:

Reminder.

If there is an existing clip on the Track the Take Lane icon should be seen at the semi-lit state when the Take Lanes are collapsed. Creating a clip without the Record command seems not obeying this rule. To get rid of semi-lit states of the Take Lane icon simply change the Show/Hide Take Lanes image from the Cakewalk Theme Editor. (Preferences/Themes/Edit) You can replace it with this image for to remove semi-lit Take Lane icon for the Tungsten Theme:

And the FXs on the Audio Tracks will be handled by the same BandLab VST as Audio FX. There are some VST Instruments which are capable of using as a VST FX. BandLab VST will be one of them. It will be used as both FX and Instrument.

Correction: I mean about exporting "Cakewalk Bundle" file from the BandLab Mix Editor. Cakewalk Bundle files includes packed Audio Files which are in the Cakewalk Project Folder. Cakewalk Project Files doesn't have audio. The process will be: Do what you want in the BandLab on your Tablet. Then export Cakewalk Bundle file from BandLab. Open Cakewalk Bundle file on your PC. Cakewalk will automatically see all the Audio and Instrument Tracks and load BandLab VST as a Synth. All the FXs and Instrument sounds will be recognized by the BandLab VST. Continue to work on the project.

I mean we need a BandLab VST Instrument in the Cakewalk and besides with that we need a Cakewalk File Exporter in the BandLab. Because we need FXs and Audio Files with the export to hear the same sounds in the Cakewalk. MIDI Export can not handle all that stuff. But Cakewalk Project file can.

But having a VST Instrument only will not make a complete migration from BandLab to Cakewalk. Because we may have audio files in the project and the editor also have a built in sampler which will not be handled as default by BandLab VST . And also we may have Audio FXs on the tracks. So we need a Cakewalk Project file exporter in the BandLab Mix Editor besides having a BandLab VST Instrument in the Cakewalk. After the export when we open the file, we will see the Instrument tracks which they use the BandLab VST as a Synth with the Audio Tracks. Audio FXs in the project and the used samples with the built in sampler can be handled by the BandLab VST. So there is no need more than that. There is already finished and working stuff going on in the Mix Editor, so it will be easy for the VST development process rather the creating from the scratch.

This thing can be achieved by simply routing Banks and Patches. All the BandLab sounds we use in the Mix Editor of BandLab will have unique Bank and Patch numbers. And this information will write in the MIDI files in Export from BandLab. When we import the MIDI from BandLab to Cakewalk and then insert the BandLab VST Instrument for Cakewalk, same information will be recognized from the VST then it will load every sound automatically.

+1 Definitely. When I move my music from BandLab to Cakewalk I always have trouble with the sounds. Some sounds I want to change but some of them I like it and I want to keep them as it they were. And also I want to continue to work on the notes so audio stems will not work at this point. If we had a VST which have BandLab sounds in it and compatible with the MIDI exports from BandLab we would continue to work without an issue between the two softwares.

no. this can be achieved by simple automation. there is no need to change an old code. you're just adding something to existing ones.

It is easy feature to implement. It just bumps specified amount of bars back from now time to hear the song before the record. Liked it.

I already tried. DM is the right thing when you want to start something personal to avoid pollution. And there is no need to start a fire after a finished thing. That can also make a pollution too.

We are all friends here Steve. I'm not trying to win a game or something. If we had in a game here we would all in the same team, we use the same DAW. You took it personal from the beginning. That's why you behave like that. If you read everything after a while you'll see them with a different point of view.

I think I get the problem here: You have a thought that I'm trying to claim you are wrong. I'm just clarifying things. From the beginning there is nothing about you. It is about the topic we talk. I read your posts and find the issues and pointed at you. There is nothing unrespectful here. You should re-consider of respect meaning of yours. And this is not a game.

Actually I'm having no problems with the icons because I get used to it. But is there a confusion, yes there is. If there were no confusion this topic and previous discussions never be created and the people, including you, won't change an icon on your Mix Module. PDC and FX buttons shares the same logic and so the same issue. So if you say for one of them you say for the other one too. If we get rid of the confusion, this can be achieved by sharing the same logic for the icons. This is my solution. And if developers also thinks there is a confusion, there is an open door to change.

🙂I think you're missing my point Steve. In the previous discussions Noel admitted that it's confusing. So this means icons of the Mix Module can be re-taken by the developers. And I think the developers can make a clear consensus with each other from the discussions we had here.