Jump to content

scook

Members
  • Content Count

    6,551
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by scook


  1. 42 minutes ago, Mike Z said:

    VST scan.jpg

    The scan path in this image really needs a clean up.

    By default "C:\Program Files\Cakewalk\Shared Plug-ins" does not contain VST plug-ins and should not be scanned. It is a bad idea to add VST plug-ins to this path.

    "C:\Program Files\Common Files" contains a lot more than VST plug-ins and is an unusual path to add to the scan path. This also causes the paths  "C:\Program Files\Common Files\Celemony" and  "C:\Program Files\Common Files\VST3" to be scanned multiple times, a bad idea. Really should try to limit the scan to folders containing VST2 and VST3 plug-ins and avoid needlessly scanning folders.

    "C:\Program Files\Common Files\Celemony" is an odd path to have in the scan path. It may contain some binaries but the VST3 plug-in is in  "C:\Program Files\Common Files\VST3"

     

     


  2. The easiest way to install and activate products with Cakewalk Command Center aware installers (2015-2017) is by using Cakewalk Command Center because it automatically activates after installing.

    The manual activation process in the Z3ta+2 documentation installed with the plug-in.


  3. 29 minutes ago, Billy86 said:

    Unless, in my experience, they’re on a second monitor, where they disappear behind, in my case, the console I have open there, when I open a second plug-in. If you don’t reopen them once they duck behind, they’ll keep piling up out of sight. They will all stay open if they’re all on the one monitor. This has been discussed on the board, but if there’s a fix, I’m unaware of it. 

    This only happens if one chooses to float views while using one monitor.

    Leave the views in the multidock and dock the multidock.

    The views may be resized, even maximized and the plug-ins will float on top of the views.


  4. 6 minutes ago, notato8 said:

    The only issue was that it doesn't have MIDI in; I could work around this by monitoring my keyboard's actual audio while still recording MIDI input directly through my laptop, but I would much rather be able to hear whatever midi instrument I'm playing instead.

    It does not matter how the MIDI data gets to the DAW, the audio from the soft synths return to the interface just like the audio from a mic or guitar when monitoring through the DAW.   To hear the synth audio while playing make sure the instrument/MIDI track has input echo enabled.


  5. Yeah, the ability to run multiple devices is not something manufacturers keep secret.

    If their devices are designed to run together, it will be documented and included in their marketing material.

    The opposite is not true. IOW, don't expect manufacturers to go out of their way to document their devices are not designed to run together or see that as a bullet point in their marking material.

    • Like 1
    • Thanks 1

  6. Different interface same discussion

    The bottom line is if interfaces can be aggregated, the hardware documentation will cover how to do it.

    It takes a specially designed ASIO driver (ideally although other driver modes may work) and a way to sync the devices to the same clock.

    This is something hardware vendors who support the feature document.

    Any audio or MIDI interface changes will likely require adjusting projects to suit the new hardware.

    • Thanks 2
×
×
  • Create New...