Jump to content

sjoens

Members
  • Content Count

    340
  • Joined

  • Last visited

Community Reputation

92 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Gotcha. It actually shows in CbB Tungsten but not Sonar Tungsten. Sonar TE doesn't include it so Sonar Themes are OOL.
  2. Not sure about "post-2020.04" as even SPlat fails to show it in anything other than Mercury. Please explain how and where we can add it.
  3. I've always wanted to make a book like yours but don't have the time. You've undertaken a huge task so community help helps us all. Hard part is knowing what not to include as Cakewalk & TE both include abandoned graphics from pre X series.
  4. Make sure Track View > Options > Meter Options > Record/Playback/Bus meters have Show labels checked or you won't see the scales or their backgrounds.
  5. Works here in both CbB/Theme Editor and Sonar/Theme Editor. Can't say why it's not working on your end. They only work on audio/instrument tracks with "segmented" meters. Not on MIDI tracks. Not on non-segmented meters. The number scale is colored in TE by Theme - Meters - Segmented meters - VU Tick Marks (Segmented).
  6. Location for Vertical & Horizontal Meter Scale Backgrounds on pg17: Background VR, pg17 & Background Fill, pg18 may be abandoned carryovers from previous versions.
  7. Characters used in DOS level file management have always been forbidden for general file/folder naming, like \ / : ? " < > |. Alt code characters, like "▲" that can be used in file naming should also be usable within Cakewalk. At least I don't see a reason why they couldn't. Cakewalk track names are not files and all the forbidden symbols above can be used there. In my case, Cakewalk is replacing the symbol "▲" with a "?" (a forbidden character).
  8. It may or may not be a bug tho. According to the online help, Trimming is for individual clips while Bouncing is primarily for joining 2 or more clips together. Splitting a single clip in 2 without providing a gap between them may be why Trimming isn't working here. Even so, Bouncing works on single clips the same way Trimming does. Removing empty tails. If you simply Bounce instead of Trim, it works with one step.
  9. Yes, but I always use "snap to"... At least, someone's always telling me to.
  10. Not sure why, but... When 2 clips butt against each other, like in your example, you have to Bounce to Clip(s) When 2 clips have empty space between them you can Apply Trimming or Bounce to Clip(s) I almost always use Bounce either way
  11. 1. Create midi clip 2. Quantize 3. Bounce or apply trimming 4. Copy +1 for the long awaited Ctrl+D!
  12. To see if I'm reading you right, I just renamed a file on my desktop with "▲" in the name. It took. Then I copied the file to another location and it copied it with the special character intact.
  13. Request to allow alt code symbols in Track View/Console View track names, like arrows: "▼" (alt+31) & "▲" (alt+30). They can be typed in but don't remain after saving & closing the project. Open the saved project and the symbol is replaced with "?"
  14. For variants just upload a separate zip folder with the extra knobs & faders. Then the user can customize his own theme & save each one the way he likes. +1 for Knobman! 😁
×
×
  • Create New...