Jump to content

sjoens

Members
  • Posts

    3,017
  • Joined

  • Last visited

Everything posted by sjoens

  1. You say goodbye and I say hello... ?
  2. Funny, I use the same screenset for almost every project....
  3. Then there's recording an acoustic jumbo with a Lace single coil DI and miked at the same time into separate tracks. The Lace gives it a unique sound all its own. So fun! As long as you have the equipment, the options are all but endless.
  4. I'm lost after 6 button states. Don't know how else they could handle this one but to me there's just way too many variables to know what's going on with it.
  5. ... in the Message Formatting header. Including BLACK.
  6. That's one thing that needs fixin'. You can change them in the Inspector by deselecting the default "Use Track Colors". BUT.... It's a pain changing them back everytime you bounce 'em.
  7. @Colin Nicholls For some reason the HUD Menu button only turns blue for the Draw Tool, not for the Smart Tool. This is probably by mistake since the main CB button turns blue for both.
  8. Some notes: pg.17, 2. Control Bar: Control Bar / Collapsed Vertical Background: There is no reference in YLIP for each modules' "Icon", which is editable. Control Bar / Collapsed Vertical Background Left Grip: Control Bar collapsed & not locked. Control Bar / Collapsed Vertical Background Left: Control Bar collapsed & locked. pg. 19, 2.2. Tools module: Track view / Focused Track Text: Resolution button text when Smart Tool & Draw Tool are active. You can add here or on pg, 15: Global / Alternative Text #2: Resolution button text when Smart Tool & Draw Tool are NOT active. Control Bar / Menu Button: State 1 = Smart Tool & Draw Tool are NOT active. State 4 = Smart Tool & Draw Tool are active. (HUD = as described on pg. 20 & when Draw Tool is active ) State 5 = no project loaded. ( all "disabled" button states are used when no project is loaded) HUD text color not changeable?
  9. "C:\ProgramData\Cakewalk\Command Center\Cache\images" They are "Rapture" icons. I'm missing the CA2A image for some reason.
  10. It seems Cakewak runs BEST on a system running only Cakewalk.
  11. I just launched CbB right after booting up and it never opened. Turns out it went directly to Background Processes, it's favorite hiding spot these days. For me it's almost always an audio or USB conflict.
  12. My Multidock is at Top. It can be sketchy at times but you can drag Inspector & Browser out into their own window, then to redock, you can hold them where you want them to go (the area turns blue), either under/over, or beside Multidock. Once you have it, save a screenset # and you can always call it up when things go wacky. You can search Multidock in the online or pdf Help.
  13. Depends how your screenset is arranged. I dock Inspector & Browser under the Multidock so they only appear with Track View. That way Console, PRV & other views get full screen width. I & B keys won't work If you dock Inspector & Browser aside the Multidock, they will always be available whatever view you have open. I & B keys work.
  14. NICE! (where'd ya get 'em?)
  15. Speak of the devi.....
  16. If only the "Don't Crash=1" line worked. ?
  17. Not a big deal but... the small Transport Module would look much better if the display data was centered better in their respective areas.
  18. Still a mystery why an old web home page would show up where it was clearly never intended to.
×
×
  • Create New...