Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

96 Excellent

Recent Profile Visitors

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

  1. Did you check the output port in the Sysex View? I use Sysex since always and it works fine. If the setup file that you are sending is the same as always, it should work as always. The most obvious reason for it not to work is that you are sending it out of the wrong port. All that about "standards" makes no sense. Cakewalk just sends the sysex info, doesn´t care about its content. Patch/Bank change formats are a whole different kind of midi message that has nothing to do with sysex.
  2. He is using a virtual MIDI cable
  3. Open the Sysex View and check that the sysex data are being sent to the right port .
  4. From the Release Notes: "The previous Large mode for the Select module is now the Medium mode."
  5. Recently a guy here reported to the police that his home had been burglarized, and among the stolen items he listed four kilos of weed. He got in trouble. 🤦‍♂️
  6. I am not a big jazz fan, but first thing that comes to mind is Around Midnight, when Coltrane comes in.
  7. Not quite. https://www.statista.com/statistics/442354/music-genres-preferred-consumers-usa/
  8. Once you have the Alesis connected via MIDI, you need to assign the .ins definition file to the port and channel(s)it is attached to. Go to Preferences>Midi>Instruments, click on the Define button, and it will open the "Define Instruments and Names" dialog. Click the Import button, and navigate to find the Alesis.ins file. Import that, close the dialog and now in the Instruments right column you should be able to find your Alesis. Link it to its port and channel in the left column, and you are set. Now when you open the Patch and Bank selectors in any MIDI track with output to that port and channel(s), your instrument´s patches should appear listed, the drum names should appear in the PRV, if available in the .ins file, and the CC numbers will also appear in the PRV assigned to the actual controller names.
  9. I can not check now, but I think that this might be saved with a track template. I tend to insert instruments with track templates, so they come with their color, icons and even favourite presets.
  10. As @scook says above, that behavior can be changed. Anyway, if I understood correctly, the OP complains about the FX windows closing every time he starts or stops the transport, not only VST but Pro Channel FX as well.
  11. If you want to see clip borders clearly in the PRV you can if you change the clip´s background color. That shows in the PRV. If you are using Tungsten, clip´s default background color is about the same as the PRV background, that is why you cannot see it. What you can not do at the moment is hiding the other clips. Your problem with looped clips is a matter of design. In CbB you can roll a groove clip across a few bars and edit some bars without changing all the repetitions. That is very useful if you want to make variations. If you want to change all of them you need to do what you show in your animation, that BTW can be done faster if you hit CTL-L to unloop it and then again to loop it , and then roll it out again. Not a big deal for me, but of course to each their own. If you do not want to do that, you have other option, that is using linked clips. Linked clips will reflect any change that you make in one of them, and you do not need to have them one after the other, not even in the same track.
  12. That is exactly what the Arranger Track is for. What is wrong with it?
  13. I cannot reproduce that. Plugins stay open here until I close them, no matter what I do. Same with Pro Channel FX. Maybe you could describe step by step what you do, including your screens setup, if you open the Console View docked, floating in the same monitor, or in a second monitor.
  • Create New...