CA-2A ACT bug

Author
Post
Essentials Only Full Version
Loptec
Max Output Level: -72 dBFS
  • Total Posts : 948
  • Joined: 2011/02/07 13:29:01
  • Location: Sweden
  • Status: offline
2013/01/27 05:42:50 (permalink)

CA-2A ACT bug


Just tried to control the new CA-2A with ACT and it's behaving strange.
I'll report this, of course, but I'd just like to check if anyone else got this problem:

When inserting the CA-2A into a track (PC or VST) nothing happens when turning the hardware knobs.

To get ACT to work with the PC-module I have to:
  • record/insert some audio to the track
  • play and stop the project once 
  • deactivate and reactivate CA-2A with the modules blue on/off button by clicking it with the mouse. Using the hardware button for this won't work
  • now the ACT starts working



To get ACT working with the VST-version I have to do the things mentioned above except deactivating/reactivating it

SAMUEL LIDSTRÖM

DAW: Sonar Platinum (64bit) with Melodyne Studio - Controllers: Roland VS-700C, Cakewalk A-500 Pro, Yamaha P90
Desktop Audio Interface: RME HDSPe RayDAT - Laptop Audio Interface: RME Babyface Pro

#1

1 Reply Related Threads
    Loptec
    Max Output Level: -72 dBFS
    • Total Posts : 948
    • Joined: 2011/02/07 13:29:01
    • Location: Sweden
    • Status: offline
    Re:CA-2A ACT bug 2013/01/27 05:48:49 (permalink)

    hm..
    just discovered it's the same with the console emulator modules..

    I have to (with a mouse click) deativate / reactivate them to get them to react to ACT

    Guess it's an ACT-bug more than a bug in CA-2A..

    SAMUEL LIDSTRÖM

    DAW: Sonar Platinum (64bit) with Melodyne Studio - Controllers: Roland VS-700C, Cakewalk A-500 Pro, Yamaha P90
    Desktop Audio Interface: RME HDSPe RayDAT - Laptop Audio Interface: RME Babyface Pro

    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1