Jump to content

Devils

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Devils

  1. One common point of trouble I've found that causes this error is my RAM. The fix (for me) has worked every time.  

    Power down computer. Unplug from wall. 

    Hold power button down 30 seconds. 

    Open computer case, remove RAM. Clean contacts on each stick with rubbing alcohol if dirty. 

    Blow dust from RAM sockets.

    Reinstall RAM. 

    Dunno why this works but it does. 

  2. 3 hours ago, Devils said:

    When in ACT and using an x-touch mini to open & close previous and next plugins in a track strip..... this display pops up on "Tube Saturation"..... it isn't a problem and doesn't cause  problems... but is this supposed to be the way it looks or no? Or is it what the Roland / Cakewalk midi controller would show on it's display? 

    CBL Track Tube saturation image.PNG

    I bet @azslow3 has some answer to all of these strange GUI's

  3. Hi "CAKEWALK" people... why are we stuck with a 20 yr old "ACT" midi interface that destroys all creativity when it has only a 50% chance of working,

    What the hell? Cubase and the rest have modern and functional qualities that allow for functional midi control surfaces. I love the way ACT works, when it works. 

    So, why after so many years hasn't this been turned into the BIGGEST SELLING POINT for CBBL?????!!! Software to hardware communication is 99% of ALL YOU HAVE TO DO!

  4. ACT has been "broken" for years. It is probably (for me)  the most frustrating part of using Cakewalk By Band Lab. Using a "FaderFox PC12" & "Behringer x-touch mini" and ACT  is great.... when it works and  then those presets i create completely vanish by the next restart or project. The amount of time it takes to get it all set up, just right and then it all vanishes.. painful. 

    FaderFox-PC12 w CakewalkByBandlab.jpg

×
×
  • Create New...