-
Posts
9,681 -
Joined
-
Last visited
-
Days Won
27
Everything posted by scook
-
While it should still work as an external editor, newer versions of SpectaLayers support ARA2. Whether using SpectraLayers as an external editor or a Region FX, the Melodyne processing will have to be committed before additional processing or rolled back and performed after using SpectraLayers.
-
If running CbB stay away from Ovox for now
-
How to use Addictive Drums 2 in Cakewalk by Bandlab
scook replied to Creative Sauce's topic in Tutorials
I noticed in the YT comments someone mentioned using the master.ins as an alternative to a drum map. This has always been an option but alternate note names had to be set every time the track was opened in the PRV. With 2021.06 alternate note names in the PRV persist per-track making this an attractive option. I created an AD2.ins from my master.ins it is available here -
I mostly use VST3 plug-ins but still install both. Yeah, it can run into a few GB of disk space with hundreds of plug-ins but nothing like the space required for audio data used in projects, sample and loop libraries. There are still a few things VST3 developers are slow to adopt. One I experience is sending MIDI CC data from a plug-in, a VST2 feature added to the VST3 spec around a year ago. Still waiting for this to get added to the plug-ins. Here is another example of a missing feature
-
Is the deal with Objeq Delay one of the personal offers in your account? If not, check the upgrades and offers section on your registered products page.
-
The Master, Preview and Metronome are part of the basic template. If the Metronome bus is not there, to use the audio metronome the audio must be assigned to a bus or hardware output in preferences. The Preview bus is used to audition audio clips in the media browser. The preview may be reassigned using the menu on the media tab (B in the image below) Having separate buses for the metronome and preview gives each its own volume control.
-
Keep in mind, some of the elements in CbB today were not part of SONAR when the Logic theme was created. These elements will show up as unmodified in Logic although had they been around when the theme was created they probably would have been altered to suit the theme. For example, in the changes for 2020.04 all would likely have been modified. Logic probably started out as a copy of Tungsten. Like all dark themes some unmodified Mercury bits look OK, others may lack contrast or look out of place. Regardless, if it works for you, that is all that matters.
-
All their VST plug-ins have resizable screens. They are not stretchable but have 6 fixed selections. Quite an improvement over the original plug-ins. The upgrade is free but not the easiest to get.
-
HELP!! I tried to move my Cakewalk to my D Drive! But now nothing works!!
scook replied to Alicia Anthony's question in Q&A
The best way to move programs is reinstall. Most programs (especially ones with installers) write into the registry. Cakewalk is no exception. There are numerous entries containing paths. Moving the program without updating the registry causes the program to fail because the paths in the registry are all wrong. There is a clean install process for Cakewalk that will allow you to reinstall the program and, if desired, install it in an alternate location. This does not affect projects. Of course, for the uninstall process to work, the program must be where it was originally installed. If you prefer, you can try directory junctions. After disk cleanup they are your best friend when it comes to freeing up space on a drive. They allow you to move folders to different drive but the OS and programs still believe they are in their original location. Read up on the DOS utility mklink with switch /j I can help with specifics if necessary. WRT Cakewalk. while I would not move the program folder, it should be possible. Try using directory junctions to create the links back on the system drive. For example, if the "C:\Program Files\Cakewalk" folder was moved to "D:\Program Files\Cakewalk" open a command window as administrator and type mklink /j "C:\Program Files\Cakewalk" "D:\Program Files\Cakewalk" -
I doubt much has changed since http://forum.cakewalk.com/Are-there-any-Band-Labs-plans-to-create-a-more-modern-script-language-m3778540.aspx The set of CbB users who want to program solutions is far outweighed by the set who just want to make music. The included scripts written in CAL were mostly replaced with built-in functions and MFX plug-ins. For most users, time is better spent learning these features than messing with CAL. If you want to use a different language to manipulate MIDI try AZLua.
-
I am not sure where you are attempting to paste the elements. I locate the image of the element in the center of the theme display (not the item in the tree on the left) and use its context menu. It does not matter when the theme was created the editor shows all the elements in the current Mercury theme with changes based on the user theme loaded. Greyed out elements in the tree are unmodified. Don't forget about the help. It is 26 pages of useful info about the editor.
-
Morton's list looks like all the changes made to CbB, Some are image size changes (they must be updated to display correctly) Some are new images, They will show in Logic as Mercury elements (IOW as the original image), these are optional but in most cases, the Tuncury version, if it is different than the original should be closer to Logic). There might be some changes made to SONAR after the Logic was made, IDK. There were very few image size changes in SONAR but there may be a couple of new elements. I would not worry about them though. Bottom line, if something does not look right, compare the two themes.
-
Make sure both instances of the theme edit show the appropriate theme name in the center top of the Window header Both themes should have the same context menus.
-
That's right
-
I just looked at the Logic theme by Rflint on the old website. It looks a lot like my Tuncury theme with mostly SONAR Tungsten colors, the flat buttons replaced with dark grey versions of the 3D buttons from Mercury and blue accents. You might save some time by looking at Tuncury, at a minimum, the new elements will be very close to the correct colors should you copy the need elements into Logic. Using this as a guide to the new elements open Logic in one theme editor instance open Tuncury in another copy the new elements from Tuncury into Logic save-as Logic under a new name.
-
You can use the hardware faders in console view, the volume control in Windows or the audio interface but most of the time you really want to check and set a level in the DAW using a master bus.
-
That's right. The only difference between the "Master Nus" and the other buses is the "Master Bus" has "Set as Default Bus" enabled. There can only be one default bus. When adding audio and instrument tracks to a project their output will automatically be set to the default bus if one exists. I have created my own project template and set bus B as the default and renamed it Master That said, any bus may be set as the default and may have anything for a name. I am pretty sure all the project templates included with CbB designate bus A as the default and use the name "Master"
-
The last version of SONAR with a status bar display was 8.5.
-
The image above with the MIDI track 1 in the inspector, shows a master bus setup in the project. It does not show up in the track inspector for a MIDI track because MIDI tracks do not contain audio. They contain MIDI data. Here is a little more info about the "Master Bus" The "Master Bus" provided by the project templates supplied with CbB is just a regular bus with its "Set as Default Bus" option enabled. When creating projects without a CbB supplied template, it is up to the user. While not required, it is a good idea to have all audio/instrument tracks and buses ultimately route though one bus. To add a "Master Bus" to a project that does not have one already setup: Create a bus Right-click the bus header in the track view and select "Set as Default Bus" and optionally rename the bus. any new audio/instrument tracks will automatically point to this bus. To change the routing on existing tracks/buses: Select all the audio/instrument tracks (note MIDI tracks do not route to audio tracks or buses) While holding down the CTRL key set one of the selected tracks and change its output to the default bus. Select all the other buses and perform the same CTRL/output assignment on them too Buses are at the bottom of the track view in a separate pane and in the middle section of the Console view. Shortcut SHIFT+B and a button at the bottom of the track headers in the Track View toggle the bus pane
-
Resource planning and management is not a one-size-fits-all proposition. Discussing machine specs without knowing the application, projected lifespan and budget is not very practical. One reason, I try to avoid these threads. A DAW builder like @Jim Roseberry may have some suggestions.
-
The Inspector is showing track 1, a MIDI track. The Track Inspector shows different information for MIDI tracks. Review the link above about the Track Inspector. MIDI tracks do not have an audio routing, their output usually goes to a software or hardware synth for processing into audio. In the image above, the MIDI track is routed to TTS-1, the GM soft synth bundled with CbB. Somewhere in the project TTS-1 is setup as the input to an audio track (or the MIDI track may be routed to an instrument track, not the best idea but it works). This track will have a second strip showing the track/bus in its output.
-
On reflection, I wonder if the OP is more about single keyboard shortcuts than specific UI elements. Be aware, the program uses single key shortcuts. Most of the keyboard shortcuts are documented here. The link is also in the program help menu. Few shortcuts are hard-coded or reserved. Most may be disabled or remapped to different key combinations.
-
The panel on the left by default is called the Inspector. The default pane displayed in the Inspector is called the Track Inspector. From the Inspector link above The "related question" is about views in the MultiDock To adjust the size of the MultiDock when it contains views like the Console, try keyboard shortcuts D and SHIFT+D
-
Most of this is wrong too but I will leave it for others to decide for themselves.