MIDI Chorus and Reverb settings in Track Inspector are not saved in exported MIDI file

Author
dbenus
Max Output Level: -90 dBFS
  • Total Posts : 18
  • Joined: 2010/06/27 06:00:41
  • Status: offline
2018/03/14 15:00:10 (permalink)

MIDI Chorus and Reverb settings in Track Inspector are not saved in exported MIDI file

Hello,
 
In Sonar Platinum:
The MIDI Chorus (CC93) and Reverb (CC91) settings for each track in the Track Inspector are not saved (or cannot be restored) when exporting/importing MIDI files.  The settings come back up reset to 0 when I reopen the MIDI file after saving it from a CWP file.

I had this problem before and the support team (when they still existed and responded) helped me resolve it. But I recently had to uninstall all previous versions of Sonar and Platinum to resolve an issue with it taking forever to boot up; now this controller problem has reappeared and I can't find the previous correspondence from support and can't remember what I did to fix it.
 
It worked fine in all previous versions of Sonar (X1, X2, etc.), but not in Platinum.  While working with tech support, I tried to restore to previous updates of Platinum, but that didn't help.  I vaguely remember that it may have been some kind of change in settings in the Configuration or Initialization files, maybe having to do with Legacy, but I can't for the life of me remember exactly what the tech had me do.
 
Help?
 
Thanks,
 
David Benus
 
HP Elitebook 8760w
Intel Core i7
24GB RAM
500GB SSD drive on C:
Roland OctaCapture
 
post edited by dbenus - 2018/03/15 17:24:56
#1

16 Replies Related Threads

    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    I meant... Sonar Platinum DOES NOT save ProChannel MIDI Conroller settings 2018/03/15 15:38:45 (permalink)
    Sorry for the type on the subject line.
    I meant that Platinum deosn't save ProChannel MIDI controllers 91 and 92.
     
    Now it comes to me that I think one of the support techs had me change a setting the in the initialization file, but I can't for the life of me remember which and to what.
     
    Anybody?
    Thanks.
    #2
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: I meant... Sonar Platinum DOES NOT save ProChannel MIDI Conroller settings 2018/03/15 16:23:30 (permalink)
    Sorry, can not help.
     
    But you really mean Chorus and Reverb set in the Track Inspector are not saved (or can not be restored) when exporting/importing MIDI files.
     
    That has nothing to do with ProChannel, and for sure not with ProChannel modules.
    I guess most people are reading you question as "Remote control for ProChannel parameters are not saved into MIDI files" (so you get no reply).

    Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
    GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
    RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
    www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
    #3
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: I meant... Sonar Platinum DOES NOT save ProChannel MIDI Conroller settings 2018/03/15 16:26:27 (permalink)
    THANKS!.  I'll re-post.
    #4
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 16:32:43 (permalink)
    Please do not create another thread. Edit the OP and change the subject. While there are a couple of threads from other userID with almost the exact same wording. They failed to post a solution.
    #5
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    PLATINUM: MIDI Chorus and Reverb settings in Track Inspector are not saved in MIDI file... 2018/03/15 16:41:43 (permalink)
    Hello,
     
    In Sonar Platinum:
    The MIDI Chorus (CC93) and Reverb (CC91) settings for each track in the Track Inspector are not saved (or cannot be restored) when exporting/importing MIDI files.  The settings come back up reset to 0 when I reopen the MIDI file after saving it from a CWP file.

    I had this problem before and the support team (when they still existed and responded) helped me resolve it. But I recently had to uninstall all previous versions of Sonar and Platinum to resolve an issue with it taking forever to boot up; now this controller problem has reappeared and I can't find the previous correspondence from support and can't remember what I did to fix it.
     
    It worked fine in all previous versions of Sonar (X1, X2, etc.), but not in Platinum.  While working with tech support, I tried to restore to previous updates of Platinum, but that didn't help.  I vaguely remember that it may have been some kind of change in settings in the Configuration or Initialization files, maybe having to do with Legacy, but I can't for the life of me remember exactly what the tech had me do.
     
    Help?
     
    Thanks,
     
    David Benus
     
    HP Elitebook 8760w
    Intel Core i7
    24GB RAM
    500GB SSD drive on C:
    Roland OctaCapture
     
    #6
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 16:42:41 (permalink)
    Ooops.  Sorry.  Missed your post while creating a new one.
     
    #7
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 16:50:10 (permalink)
    Not a problem
    The second thread is now merged with the original.
    Change the OP subject if you wish.
    #8
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 17:00:25 (permalink)
    How would I change the "OP"?
    I don't see any way to do this.
    Thanks.
    #9
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 17:01:20 (permalink)
    And could I copy the revised post to the top and delete the original?
    #10
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 17:08:10 (permalink)
    You may not delete a message but you may overwrite a message. Right now replies are using the subject line I created in message 5. There should be an edit option in the bottom right of your messages next to the message number. This will let you modify both the message text and subject.
    #11
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 17:25:27 (permalink)
    Thanks.
    #12
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 17:45:01 (permalink)
    I did find a reply in a similar thread that suggested adding
     
    LegacyAutomation=1
     
    to the [Options] section in %appdata%\Cakewalk\SONAR Platinum\TTSSEQ,INI
    The [Options] section is at the top of my TTSSEQ.INI but it may be anywhere in the file. If the section is not in the file create one.
    #13
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/03/15 18:27:12 (permalink)
    THAT WAS IT!
    Works perfectly now.
    THANKS SCOOK!
    #14
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/12/19 15:07:51 (permalink)
    Hello Scook,
     
    My HP Elitebook (Win 7), which served me well for 10 years, finally died.  Great laptop, very sad.
    So I got a new one, now with Win 10.
     
    But the previous problem has resurfaced: MIDI Reverb and Chorus settings are not retained when saving from work file to MIDI.  As per your previous advise, I found and modified the TTSSEQ.INI (C:\Users\David\AppData\Roaming\Cakewalkl\SONAR PLATINUM) to include the line "LegacyAutomation=1".  But the Reverb ad Chorus settings are still not saved in MIDI format.
     
    Does Win 10 behave differently than Win7?  I need to be able to open up a MIDI file made in Platinum with controllers 91 & 93 in place.  I'm really stuck and hope that you or some other user with experience going from Win 7 to Win 10 might help.
     
    Thanks.
    #15
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/12/19 15:57:32 (permalink)
    IDK, I am guessing I tested this before posting in March but cannot say for sure. If I did, it was on a Win10 machine. Testing today, it appears the LegacyAutomation setting is not working in either Platinum or CbB.
    #16
    dbenus
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/06/27 06:00:41
    • Status: offline
    Re: Losing Track Inspector Chorus and Reverb settings when saving MIDI file 2018/12/20 00:03:16 (permalink)
    Hmm.  The fix worked for Platinum in Win7.
    So am I out of luck?
    #17
    Jump to:
    © 2019 APG vNext Commercial Version 5.1