Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by scook

  1. May be confusing WDM and the newer WASAPI modes added to Platinum. As a rule, a manufacturer supplied ASIO is still the best choice but feel free to try the other driver modes.
  2. Chances are the effects unit's latency varies depending on its settings. This could prove challenging when using it as an external insert.
  3. Leave Platinum in place so that Cakewalk by BandLab can use the plug-ins and content bundled with Platinum. CbB installs like an upgrade to SONAR with in its own program, content, and user folders while updating the shared utilities. Instead of CCC, CbB installs and activates using BandLab Assistant. The instructions for upgrading are here.
  4. The theme editor program was not modified for 2019.01. There were changes to the resource files used by CbB: 3 New colors under Theme > Browser > Plug-in Browser Plug-in Tree Text (used for tree, VST3 and DX labels) VST2 Text 32-bit Plug-ins Text A Ripple Edit Button image was added under Theme > Track View After CbB 2019.01 is installed, these items are available for edit in the Theme editor. Rarely, if ever, should changes to the CbB UI require updating the theme editor program. The theme editor is a tool allowing users to make and store changes to the base resource files (a.k.a the Mercury theme) in special files called user themes. As BandLab releases updates to the resource files the theme editor will reflect those updates.
  5. The default location for user themes is "C:\Cakewalk Content\Cakewalk Themes" If "Cakewalk Content" was installed elsewhere, the "Cakewalk Themes" folder will be under the alternate location. For the themes to appear in the theme drop down in preferences, copy the theme files (extension .sth) into the "Cakewalk Themes" folder.
  6. AFAIK, the last official word on the subject was posted in this thread.
  7. Not exactly. Drum maps can route each MIDI note number to a different output. It is possible to have up to 128 different output assignments in a MIDI track.
  8. Unlike lenses which are global, screensets are stored with the project. It is possible to import screensets from another project but this will have to be done for each project.
  9. CbB contains a time-limited trial version of Melodyne Editor.
  10. Dropping a file from the Browser or the OS onto an existing project imports the file. Dropping a file into CbB from the OS onto the CbB background (IOW space not containing a project) opens the files.
  11. If a project contains no audio clips, the sample rate is read from preferences. Only when a project contains an audio clip does a project sample rate get set. The Change Audio Format dialog modifies existing audio data in the project. As a rule this is not necessary. While all the audio in a project must be the same sample rate, projects can contain audio at different bit depths. Changing the Record Bit Depth is all that is needed to change project bit depth. Record Bit Depth is a global setting that affects all future recordings in all projects. As a rule, this value should be set to the audio driver bit depth.
  12. In most cases opening a MIDI file in CbB is preferable to importing the file. Importing MIDI strips tempo data. Once a file is opening in CbB make sure to save it as a Cakewalk project or any non-MIDI data that is added will be stripped and the file will be saved as a MIDI file. Upon opening a MIDI file, if no MIDI output devices are selected in preferences, TTS-1 will automatically be added to the project and the project will be setup ready to play.
  13. This is probably a bug but a little different than reported. Notice when entering the Notes field in the Notes tab, OK and Cancel buttons appear at the bottom of the field. Clicking OK sets the project dirty flag. Once OK is clicked in the Notes field editor, trying to exit the project will prompt to save changes.
  14. On a 2 drive machine leave it on the C drive. Systems with more than two drives may benefit slightly by moving the picture cache to a non-system drive other than the project drive. The setting for the picture folder is in preferences right below the Global Audio folder setting which should be on the same drive as project files. I prefer to use directory junctions as described here to make these changes rather than messing with the defaults in preferences.
  15. I believe GeneralMidiSMFs setting in TTSSEQ.ini determines whether or not initial program change data is displayed in the event list. By default, this value is set to 1 causing the DAW to create a GM setup measure which is not displayed in the event list. Instead, the data is displayed in the track controls. From https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=MIDI_Files.6.html
  16. scook

    White Dots on Audio Tracks

    AFAIK, there is only one direct reference to the Clips Pane Ellipses in the documentation. They are displayed in the empty spaces to the left of clips in a project. Their absence indicates there are no clips to the right in the track. Also a handy indicator that audio loops are broadcast waves instead of regular wave files when imported at their timestamp.
  17. The forum automatically resizes uploaded images. Using an external link preserves original image size. There is a 50MB quota for uploads. To manage images, click on the user menu in the upper right of this page and select "My Attachments."
  18. The first error is unrelated to the other two. I have seen a few suggestions as to the cause of the "not enough memory" message. This thread contains a few idea. Not sure there is a single cause for this error. Errors 2 and 3 are audio device related. In this case, it appears to be a usb connected microphone? The second message is the result of the third. The device either does not have an ASIO driver or the driver is not installed. As a result, Cakewalk cannot communicate with the device. To remedy the third message either chose a different driver mode in preferences ,install the manufacturer supplied ASIO driver or ASIO4All. Note: ASIO4All has been known to cause problems for some users. Problems that can only be fixed by removing ASIO4All from the machine. Once Cakewalk can communicate with the audio driver, the silent bus error will probably go away.
  19. Ripple editing works on single or multiple tracks. The caution is because it is easy to affect multiple tracks accidentally especially when it is not turned off immediately after use.
  20. There may be a dialog from the scanner waiting for user input. Check the Windows Task Manger. The vstscan.exe may be stalled. There are notification preferences settings for newer versions of CbB but I do not believe they will affect Platinum.
  21. BandLab has never directly addressed "why" but they have made it clear on more than one occasion that CbB will remain free. Here is an example where Meng states: So, the basic product is free (similar to what Cakewalk started doing with SHS) but there are plans for paid add-ons.
  22. scook

    Importing audio

    Might help to make an example clip available for download.
  23. scook

    Freeze/Unfreeze

    Depends on the Track FX setting in freeze options. Right-click a snowflake for the context menu to access the freeze options dialog.
×
×
  • Create New...