Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by scook

  1. Here is why I believe this is not by design.

    After loading a project from the playlist.

    • Open the "Save As" dialog from the main menu.
    • Notice how the dialog is abbreviated. It looks like the "Save As" dialog called from the Playlist except for how the drop downs are populated. Close the "Save As" dialog.
    • Close the playlist.
    • Now open the "Save As" dialog again.

     

  2. Usually transport controls are setup using the control surface settings in preferences. I do not use a control surface, never have, so I will have to leave that for some one else to discuss. There are several threads about control surface setup. Maybe something in one of those will help.

    It is possible to create a custom shortcuts for transport functions. When using MIDI to create a shortcut it takes a note to bind to the function and either a note or CC (this is set at the top of the shortcut screen) to tell the DAW the next note is bound to a function.

    • Like 1
  3. First get a decent audio interface designed for DAW use with a factory supplied ASIO driver.

    ASIO4All is loading the Realtek WDM driver (which you could run directly from CbB using driver mode WDM) with some extra buffers presenting it to the DAW as an ASIO driver.

    If you do purchase an audio interface with a real ASIO driver you will need to uninstall ASIO4All to prevent conflicts with the real ASIO driver.

    • Great Idea 1
  4. After adding the plug-in to the FX Rack check "Enable MIDI Input" in the VST3 standard header above the plug-in UI

     

    WBoEAIf.png

    Then add a MIDI track setting the input to your controller, output to the plug-in and enable input echo

    The controller will now send MIDI data to the plug-in

    • Like 1
  5. "Save As" works the same as the later versions of SONAR Platinum. Here is a video using CbB 2020.01 showing project "sat" being saved as "satnumber 2." The video shows the following:

    • Starting with project "sat" notice the location of the project and audio files.
      • "D:\Cakewalk Projects\sat"  contains the project
      • "D:\Cakewalk Projects\sat\Audio" contains the audio
    • Click "Save As"
    • Navigate up one folder at the top of the "Save As" dialog in order to save the new project in "D:\Cakewalk Projects"
    • Enter the new project name and notice the paths at the bottom of the "Save As" dialog and "Copy all audio with project" is enabled.
    • Click "Save"
    • Closing then reopening the new project and verifying the location of the project and audio files.
      • "D:\Cakewalk Projects\satnumber 2" contains the project
      • "D:\Cakewalk Projects\satnumber 2\Audio" contains the audio

     

    g0fo4Dn.gif

     

     

  6. One of the motivations for Launchpad was project list management. While the only automatically managed list is sourced from the registry there is no limit to the size of the other lists used by Launchpad.

    To build up the favorites list, right-click an item from any of the other lists, such as the list of recently opened projects in the registry.

    A link to Launchpad and the discussion about it is here

     

  7. the plug-in may have failed during scanning causing it to be added to the Excluded List. To see if the plug-in is excluded

    • Open the Plug-in Manager.
    • Select VST Instrument (VSTI) from the Plug-in Categories listbox in the Plug-in Manager.
    • Click the Show Excluded radio button below the Plug-in Categories listbox.

    If it is there here is how to force a rescan of excluded plug-ins

    Open VST Settings in preferences

    • If the Scan Options drop down is not set to Manual Scan, temporarily set it to Manual Scan
    • Enable Rescan Failed Plug-ins (normally this should be disabled)
    • Enable Scan in Sandbox (this is the default)
    • Enable Generate Scan Log (this is disabled by default)
    • Click the Scan button
    • Disable Rescan Failed Plug-ins (and Rescan All Plug-ins if it happens to be enabled) and restore the Scan Options drop down.

    Check for the plug-in. If you have a lot if synths, searching is a fast way to check if one is there. Make sure to use one of the factory supplied "Sort By" layouts. In this case, search for m1

    If the plug-in is still not available. Review the scan log. There may be some clues in it.

    An alternative to scanning failed plug-ins is a VST Reset. This completely rebuilds the VST Inventory in the registry. To perform a reset

    Open VST Settings in preferences

    • Make sure Scan in Sandbox is enabled
    • Enable Generate Scan Log
    • Click the Reset button

    Review the scan log if problems still exist.

    • Great Idea 2
  8. 18 minutes ago, Matthew Simon Fletcher said:

    They will always go back to being piano notation

    If this refers to the keyboard on the left side of the notes pane bounded by C and F in the image below, this has never been saved between sessions. It always defaults to the keyboard image. A feature request to make this persistent has been around for some time. Drum maps are persistent.

    Views.05.1.png

     

    • Like 1
  9. Going at least as far back as X1 the DP expansion packs were bundled with SONAR Producer as separate installers. These installer are in your old Cakewalk Account either listed with the DAW or as Dimension Pro 1.5 for SONAR Platinum.

    I am sure the expansion packs are also still available in the old Cakewalk Knowledge Base.

     

    • Thanks 1
×
×
  • Create New...