Jump to content

sjoens

Members
  • Posts

    3,316
  • Joined

  • Last visited

Everything posted by sjoens

  1. I have all the Sonars installed and have had stuff go sideways when uninstalling older ones after installing the latest so concern is valid. There are common files all Cakewalk installs handle so if one is uninstalled it may remove some of those files. However, CbB installs with very limited plugin set - so probably not an issue if uninstalled. If still concerned I would simply delete the files, not uninstall them. I've learned to never install older Sonars after newer ones - even with minimum install to just get plugins can disrupt the newer versions, which then have to be reinstalled to fix issues. Regardless if you uninstall CbB or not, Sonitus presets will get overwritten so save any custom presets thru the Export function before installing new app. No. Projects will carry over without need to do anything. They can be opened in any Cakewalk version but older versions will warn you it was saved in a newer version and may not have some of the features it was last saved with. No. Unless you changed some hardware then it will give you options. No. Plugins are in a common folder. However, you can temporarily rename all the common "Shared" folders so uninstall ignores them.
  2. Agreed. That was just my thinking on the matter since most of us can't and probably never will be able to "simply write a CAL script". There is documentation out there on how to do it from probably 20 years ago? I can't even figure out Articulations so it gets filed under: Outcome Not Justify Time Spent Learning. Searching for CAL info I came across an old thread about AZSlow's AZ Lua that does CAL type routines.
  3. Yes but most users won't do that. Instead they'll just pass if they can't interpret the lingo or even figure out what it's for. They're basically macros that, at least for some, should've been integrated into the DAW itself. I think as MIDI editing becomes a thing of the past for main stream users, CAL may be completely abandoned down the road.
  4. Obviously I would have no clue what the initial values are (unless they're all the same) so I would want them all to adjust randomly between the low and high value I set for them. VARYVEL does work when they're all set to 100 but it's another step to remember before using it. I'm sure most of the old CAL's could be revamped to work smoother as some others don't work so well if at all like UNDUPE which others have updated or replaced (CleanTrack.cal by "sping" undupes and unoverlaps). Biggest issue I have with CAL is the unintuitive descriptions on some, like: "Window for time identity: [0 ]", or "Padding in Ticks: [2 ]". I have no clue what that means or what value to enter.
  5. To me no one set "does it" so I usually mix and match. SI Drum Kit, Session Drummer 2 & 3, Addictive Drums2 all came with various versions of Cakewalk. I've also collected various samples off the web. Dimension has drum samples & kits too, if you have it.
  6. Thanks guys. I was dealing with a series of notes that already had various velocities and I think that was confusing the CAL giving me an erroneous low value. As David found, it seems to work better when the entire selection is set to 100 first. I have 2 ea. from 1991 and 2011. They look identical in Notepad. VARYVEL 1991.CAL downloaded from Mudgel's collection VARYVEL 2011.CAL from SPlat & CbB Today at least the 2011 version seems more consistent not requiring values to be reset to 100 before a 2nd or 3rd change while the 1991 version does??
  7. Funny they have 2 for the price of 1. Ctrl-Shift-B is now Bounce to Clip(s)...
  8. Trying to set a series of velocities with VARYVEL but it defaults the lower value to 50 no mater what number I enter. It worked for a time with 89 but now it also reverts it to 50. Is there another CAL that does the same? [SOLVED] Set all notes to 100 before running CAL.
  9. Like this thread.... is now discontinued.
  10. Aim Assist Line IS a dotted line. You can change the color in Preferences or Theme Editor.
  11. For some reason that wasn't working yesterday but the plugin name was shown for each list. Today it's working but there's no plugin name on the Sonitus lists like there is for every other plugin. Seems there's also a preset list for each version of Sonar, and the universal one you referenced.
  12. So I'm curious what happens when a preset is saved in the header panel as I don't see physical evidence anywhere and they aren't saved in the INI file. These seem to disappear during an update as I've lost all I saved that way.
  13. What Save-As to a new folder does. Having several project iterations in the same folder confuses which audio goes with which iteration. OTOH, saving each iteration to it's own folder recreates used audio files each time. 20 + iterations per project can really load up a HD that way.... I have over 60 for some .
  14. More obvious is Recycle Bin which affects all HDs on the system. Some say don't worry about deleting them as 10 GB is nothing on high volume drives. But when multiple folders behave this way they can add up. Besides, 10 GB is just enough to redline a drive close to capacity..
  15. Actually, Theme Editor isn't needed at all as it accesses the same color source as Preferences>Customization>Colors list and some are even duplicated there. Most /if not all/ colors are stashed in the main exe file and can be offered in Preferences as they were before the X series. I would like to see a more complete and user friendly format to the color list in Preferences and leave Theme Editor to graphics only. Where the two overlap, one can override the other.
  16. Keeping the original files intact after editing has saved me a time or 2, so I wouldn't want the Pro Tools way... unless it allows for retrieving the deleted files from the trash bin.
  17. Thanks for reviving this topic or I would have never known. Once rendered, cache files are useless, right? So why keep 'em.
  18. When using Per-Project Audio folders... 1. If you Save-As to another location it will create it's own folder. You can then delete the original folder with all the extra audio. 2. You can also save the project where it is and go to Utilities>Clean Audio Folder..., click Find and safely delete the files listed. 3. Project>Audio Files shows which ones are used. Any not listed can be deleted. Be careful tho. AFAICT they are permanently deleted and don't go in the Recycle Bin when deleted inside CbB/Sonar.
  19. Too late now but, did you try a system reset to earlier date? I would have uninstalled the apps installed just before the trouble began.
  20. Windows or CbB? For CbB, probably not unless you saved it when it was downloaded. I'm still on it for that reason. Support might send a link. FWIW Win 11 gave me nothing but trouble, brand new system... total chaos. Took a year of updates to get it mostly settled.
  21. AFAIK Sonitus FX are part of the main program and will overwrite existing files. Once you create a preset you can add it to the list by clicking Presets > Add Preset or Preset Manager... type a name and choose what list it goes in and it will be added to the INI file and show up in the dropdown list. Now you can either save a backup of the INI file to replace the updated one or... In the Preset Manager you can Export presets to their own INI file that won't (or shouldn't be) overwritten during an update (if they are then save them somewhere else). After an update you can Import them back into the list. Click the ? or Help button for more info.
  22. This is when it usually ends up in Background processes column which is below the Apps column. If it's not there either then a plugin may be preventing it from opening. Try opening in Safe Mode (hold Shift while opening) and say NO to all plugins. If it opens then reopen it saying NO to each one at a time until you find the culprit..
  23. Check Task Manager if CbB never fully closed or is running in Background Processes. Happens here all the time and I have to log out of Windows or reboot to clear it. You could also try End Task, but that never works here.
  24. 2 options I've used: 1. Put lower notes on a 2nd track where they can be controlled separately when needed. This can be done by recording each track separately or cutting & pasting to another track. 2. Delete lower notes after recording them when they conflict with or duplicate more important instruments. (easier when they're on a separate track.) Or 3. which I haven't tried - if you have split keyboard setting - set each half to a separate track/channel and record it all at once. There is also a CAL script for moving selected notes to another track, I think.
×
×
  • Create New...