-
Posts
9,681 -
Joined
-
Last visited
-
Days Won
27
Everything posted by scook
-
Really should not put synths in audio FX racks. Years ago this was the only way to add synths to projects but that changed long ago.
-
In the standard header above every VST plug-in UI is a VST2 or VST3 drop down. In that drop down is an Enable MIDI Output option. Enabling this option will cause the plug-in to appear in the input drop down of Instrument and MIDI tracks.
-
Feature suggestion: organize plugins by folder tree
scook replied to Rodrigo Elesbao's topic in Feedback Loop
Code-wise using existing features is the easiest. Re-integrating old code or adding a new sort option is not the easiest thing to do. -
Feature suggestion: organize plugins by folder tree
scook replied to Rodrigo Elesbao's topic in Feedback Loop
Losing the original "Default - All Plug-ins" layout in August 2016 was a big problem for me and I did let Cakewalk know about it. I would not mind if Noel added it back. My VST2 folder tree is ready for it to be restored. The VST3 folder tree can be a mess as many manufacturers dump their files in the root C:\Program Files\Common Files\VST3 and provide no way short of manually moving the files after installation. I suppose they are relying on DAWs using category tags. At least CbB supports modifying the tags. -
What to do with the dmp file
-
Confused about where/how to store project audio files
scook replied to Billy86's topic in Cakewalk by BandLab
Per-project audio folders are the default and the audio folder for a project is directly below the project file(s). Projects may be on any drive the PC can access but it is best to have the Project Files and Global Audio Folder preferences set to an internal drive. Failing to use an internal drive can result in losing preference settings. If the Project Files and Global Audio Folder paths cannot be found on startup the program silently reverts these settings back to factory defaults. This usually means one internal drive stores most of the available projects. The folder where these projects are stored should be the path in Project Files in preferences. When creating a project the default layout keeps all the project files in one folder like this example using a project called "My Project" Project Files (the path defined in preferences) Project Files\My Project (the folder created for the project) Project Files\My Project\My Project.cwp Project Files\My Project\Audio (the per-project audio folder) Depending on usage there may be more files and folders in Project Files\My Project. Copying/Moving the entire project to a new location is as simple as copying/moving the My Project folder. The "Save As" function can be used to copy a project to a new location too. This function can create the project copy using just the audio clips referenced in the project. This may result in a smaller overall project by skipping audio deleted from the project. The "Save As" function can bring all audio into the project directory structure for project make without a per-project audio folder. There is no need to change the default Project Files setting to open a project located outside the default Project Files path, just navigate to where the project folder is located and open the project file. The Global Audio Folder is used when working with a new project that does not have a name and it sill may be used for temporary files (I have not checked how and when temp files are created in some time). I usually create an Audio folder in the "Project Files" path defined in preferences and use it as the Global Audio Folder. -
Feature suggestion: organize plugins by folder tree
scook replied to Rodrigo Elesbao's topic in Feedback Loop
Category tags are a VST3 feature. When the default changed in August 2016, Cakewalk created a database of category tags for its DX/VST2 plug-ins and many 9rd party plug-ins. Still there are quite a few plug-ins that do not have categories setup in the database. Regardless of the plug-in format, users may create and change the categories as they see fit. A plug-in may have multiple tags or no tags (in which case the fall into the Uncategorized folder). If one cannot remember where a plug-in is located in a layout, there is a search option just above the layout tree. Partial name searches can be very effective. -
That is good news. The important clue was the plug-in working in an existing project. This reduced the problem to a display issue not a functional problem with the plug-in.
-
If the plug-in works in any project, the plug-in is installed and working. Is the plug-in listed in the Plug-in Manager? Look in the excluded list by checking "Show Excluded"
-
I have no idea what this is. If FX box is the FX Rack (A and B in the image below point to effects plug-ins in FX Racks), this is to be expected. While one may add instruments to the FX Rack, this has not be common way to use synth plug-ins in many years. How are you testing the synth? The preview buttons at the bottom of the synth UI, a MIDI clip or input from a controller. Which method are you using, the edit buttons at the top of the plug-in UI, clicking the channel strips in the plug-in UI or the bank/patch drop downs in the track inspector/header
-
Is it in the Add Track menu? (see link above)
-
The error seems to indicate regsvr32 was not run from the "C:\Program Files\Cakewalk\Shared DXi\TTS-1" folder. If it is not run from the folder containing the dll, the fully qualified path name must be used. It is extremely unusual for a DX plug-in to go "missing." What lead to this conclusion?
-
Feature suggestion: organize plugins by folder tree
scook replied to Rodrigo Elesbao's topic in Feedback Loop
This was the default layout for VST2 plug-ins until August 2016 when the new Sort by Category/Manufacturer/Type layouts were introduced. Prior to August 2016 DX plug-ins were sorted by manufacturer and VST3 were sorted by Category. It is still possible to create a custom layout to mimic the OS directory tree using the plug-in manager but custom layouts do not get automatically updated when changes are made to the plug-in directories. -
Thanks for stopping by.
-
http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Troubleshooting.34.html There is also an optional click behavior setting http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x1893B
-
Workspaces can affect the Views menu. Here is the Views menu when running the Basic workspace Here is the Views menu when running the Advanced workspace
-
Just to make sure it is really not there, TTS-1 should be the default synth in the Add Track - Instrument tab. Scroll down to the section called To create Instrument tracks and follow the directions.
-
Probably the result of the Workspace setting. Change the setting to None, Advanced or create your own custom workspace.
-
No, the plug-in is not available separately. It is a DXi so is not scanned by the VST scanner. It is registered during installation with the Windows program regsvr32.exe The default install path is C:\Program Files\Cakewalk\Shared DXi\TTS-1 If the TTS-1.dll, tts-1-param.dat and help folder are in the TTS-1 folder, one could try manually registering the plug-in by opening up a command shell as administrator in the TTS-1 folder and type regsvr32 TTS-1.dll The other way to restore the plug-in is uninstall and re-install CbB.
-
It is a very tiny subset of what a full audio editor can do.
-
http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Troubleshooting.33.html
-
MIDI: Possible to edit time values for groups of notes?
scook replied to Michael McBroom's topic in Cakewalk by BandLab
The Event Inspector supports a several ways to including percentages, ticks and the time used in the OP -
Inserting Melodyne in the track FX rack is NOT a clip effect. The clip based method Noel was referring to is using the plug-in as a Region FX. Here is a recent post about using Melodyne as a Region FX
-
I downloaded TAL-BassLine-x64.zip from https://tal-software.com/products/tal-bassline The zip contains a single file - TAL-BassLine.dll - the VST plug-in. After copying it into the scan path, the plug-in scanned OK. Both of the plug-ins mentioned should not be a problem. You may want to run a VST Reset and generate a scan log to see what the scanner is doing. To run a reset, open VST Settings in Preferences verify "Scan in Sandbox" and "Generate Scan Log" are enabled then click the Reset button. When the scan completes there should be a message telling you where to find the log.
-
Cakewalk 2019.11.b63 periodically hangs (freezes)!
scook replied to Czeslaw's topic in Cakewalk by BandLab
The procedure to report this type of problem is covered in this thread