Jump to content

murat k.

Members
  • Content Count

    376
  • Joined

  • Last visited

Community Reputation

155 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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. 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:
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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:
  10. 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:
  11. 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.
  12. 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.
  13. 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.
  14. 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.
×
×
  • Create New...