Sonar/Spectrasonics controller conflict

Author
SToons
Max Output Level: -81 dBFS
  • Total Posts : 478
  • Joined: 2012/05/14 15:21:14
  • Status: offline
2012/05/14 15:52:35 (permalink)

Sonar/Spectrasonics controller conflict

There seems to be a major issue using cc# in Sonar to control Spectrasonics products (Trilogy, Atmosphere). I want to control the filter parameters decay, sustain and release. They use cc# 98, 99, and 100 and will not respond. All other parameters automate fine like filter attack (cc# 97).
 
At first glance it would appear that since Sonar uses cc#s 98, 99, 100, and 101 for RPN and NRPN that it uses them to the exclusion of users and virtual instruments. This as a fairly significant issue (well, for me anyways...what is a synth bass with no filter control - good luck getting Chemical Bro's bass sounds etc.) and I'm surprised it hasn't been addressed in the many years that Trilogy/Atmosphere have been out. There have been a few threads but no one seems to have pieced together the actual problem yet. For example:
http://forum.cakewalk.com/tm.aspx?m=708291&high=trilogy+filter
 
Can the cc# Sonar uses for RPN/NRPN be altered with a statement in an .in file or something? How can I workaround this issue? Very frustrating!
#1

0 Replies Related Threads

    Jump to:
    © 2025 APG vNext Commercial Version 5.1