Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by scook

  1. None the less, it is typical of the response given when this request has been mentioned in the past. One of the biggest changes that has happened since 2014 is the reduction in size of the development staff. Sometimes "small changes" like this one can consume a surprising amount of development time. Usually I don't post in feature request threads. I made an exception this time to offer the suggested alternative that has been mentioned in the past. Had there not been an alternate solution, I would not have posted here.
  2. It is difficult to provide an exact value for the MIDI playback buffer for all users. Fortunately, too high a buffer does not cause problems. A high value may be noticed as a slight delay when starting the transport. To deal with dropped MIDI notes, start at 500 adding increments of 250 until the problem goes away. Some get by with the default, some at 500, some at 750, some use values in the thousands.
  3. Clips are created based on the space between notes. A new clip is created when there is more than one measure between notes. A note less than one measure away is added to the closest clip.
  4. The PRV works with clips at the track level. It does not recognize take lanes. One thing that may make working in the PRV easier is enabling "Hide Muted Clips" in the PRV View menu. Note: this does just what it says, it hides muted CLIPS not muted take lanes.
  5. The only settings I see which diverge from defaults are the enabled "Key Aftertouch" and "Channel Aftertouch" in MIDI Playback and Recording Preferences. This is pretty strange. I am assuming recording fails this way with a new project and just a MIDI track. If so, may want to involve support.
  6. I am not sure. IIRC, Presonus made some firmware changes a while back when they dropped VSL support. These changes may prevent using older software. Not sure if it affects your device. This would be a question for Presonus support.
  7. Yes I still recommend using the tool I wrote (see the link in my previous post) to avoid having to edit the registry directly.
  8. It may be instructive to see the MIDI setup in CbB preferences. These are pretty big images so, in order to post legible copies use an image service such as imgur.com and post links to the images. If the CbB MIDI indicator is flashing, it may be instructive to record some of the data and review it in the event inspector. There are some filters in MIDI playback and record preferences so, these may need to be reviewed along with the other preference settings.
  9. The AudioBox should be able to run in ASIO mode. Make sure the driver is current. The latest driver was released a few days ago. If this does not work try all the other driver modes. MME is the poorest performer.
  10. The support response is similar to the instructions for the last versions of SONAR https://www.cakewalk.com/Support/Knowledge-Base/2007013392/SONAR-2015-Clean-Install-Instructions updated for CbB. Step 5 is a little mangled though. It should be These registry entries are for CbB only and do not affect SONAR installs. In fact, the link I provided shows the registry entries for the last versions of SONAR.
  11. The Surge team is also working on creating Surge modules for VCVRack.
  12. These are fine suggestions for new projects but do not address the OP's problem. If the OP cannot find their copy of the Amplitude 2 installer and the installer is not available from the manufacturer there are few options for working with existing projects.
  13. Unless you explicitly delete the folders in %appdata%\Cakewalk, the category database and user files will be untouched. The uninstall process does not remove user data.
  14. After everything is installed, the Command Center is not necessary unless something gets messed up and needs to be reinstalled. Removing the Command Center does not free up much space (<100MB). If you have not archived the installers from the Command Center cache, this is something to do that will free up quite a bit of disk space. The default for the download cache is a hidden folder - "C:\ProgramData\Cakewalk\Command Center\Downloads"
  15. The Cakewalk Command Center like all Cakewalk products are not being maintained. That said, the Command Center is useful for installing and activating SONAR Home/Artist/Professional and Platinum. All of these have plug-ins not bundled with CbB. All the plug-ins bundled with 64bit SONAR may be used in CbB. Some of the later plug-ins bundled with Professional and Platinum require those products be installed for their installers to run.
  16. Keep in mind, users who stay current receive an update installer that only works on the previous production install. The update installer is not a full version,
  17. something to try Shutdown CbB rename %appdata%\Cakewalk\Cakewalk Core\TTSSEQ.ini Restart CbB and review MIDI I/O device settings in preferences
  18. This is typical of the replies from the devs to this request, from http://forum.cakewalk.com/FindPost/3030072 Noel wrote It may be the best solution for now
  19. The Add Track menu and inserting from template do not recall assignable controls. IOW, only methods that add synths using the insert soft synth options dialog can recall assignable controls.
  20. It looks just like it should when using the small transport module. Select the large transport module. Module size may change automatically depending on the module and control bar settings. May want to review the links I provided above.
  21. Like most of the modules, the transport module displays different controls based on the size of the module in the control bar. It is possible to lock down the control bar to prevent the modules from changing size. Right-click a module to see the available settings.
  22. Cakewalk can wrap one or more plug-ins in an FX Chain. An FX Chain preset has buttons and knobs that may be mapped to the controls of the plug-ins in the chain. An FX Chain preset may be load in the FX Rack and ProChannel. The FX Chain UI display is determined by where it is loaded. Regular plug-ins added to the ProChannel are automatically wrapped in an FX chain.
  23. For some material the Radius algorithms may be a better choice.
×
×
  • Create New...