Vst synth patches not saved in earlier version of Sonar Platinum

Author
Post
Essentials Only Full Version
tenfoot
Max Output Level: -53.5 dBFS
  • Total Posts : 2186
  • Joined: 2015/01/22 18:12:07
  • Location: Qld, Australia
  • Status: offline
2016/02/17 14:16:36 (permalink)

Vst synth patches not saved in earlier version of Sonar Platinum

Hi Everyone. 
 
Has anyone had trouble with a previous version of Sonar Platinum not saving vst synth patches? I loaded a project that I edited in the past couple of months with drum replacer only to find that all of the synths are empty -  when the project was saved the synth sounds were lost. All of the tracks were bounced to audio and the synths are disconnected,  archived and hidden,  so I didn't notice the missing patches until tonight as I wanted to edit and re-bounce a track.
 
I then checked the other 200 projects that I edited recently  and the patches are gone from all of them!  I have earlier backups with the synth sounds intact,  so it is not disastrous.  
 
I tested Manchester update and it is certainly saving the synth patches correctly.  Given the time frame,  I would say that it was one of the updates in the last 6 months. 
 
Just thought I would mention it in case anyone is using an older version and not realising that their synth Patches may not be saving correctly. 
post edited by tenfoot - 2016/02/17 14:30:54

Bruce.
 
Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
#1

9 Replies Related Threads
    Zargg
    Max Output Level: 0 dBFS
    • Total Posts : 10666
    • Joined: 2014/09/28 04:20:14
    • Location: Norway
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/02/17 14:51:58 (permalink)
    Hi. I cannot say that I have seen this behaviour on my end. Have opened three or four old projects ( as old as back to SONAR XL 2.2 and 4 Producer) the last couple of weeks, without any issues.
    But thanks for the head up. Is it any particular synth, or all?
    All the best.
    post edited by Zargg71 - 2016/02/17 15:06:23

    Ken Nilsen
    Zargg
    BBZ
    Win 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII
    Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
     
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/02/17 15:03:20 (permalink)
    The initial release of Z3ta 2.2 was failing to restore saved patches. If you saved a project with the default patch that loaded instead,  the saved patch selection and tweaks would be gone for good. But opening an old project with the current version of Z3ta+2 will not have a problem.
     
    Other than that, I'm not aware of a general issue with saving/restoring synth presets and patches.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #3
    tenfoot
    Max Output Level: -53.5 dBFS
    • Total Posts : 2186
    • Joined: 2015/01/22 18:12:07
    • Location: Qld, Australia
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/02/17 21:33:47 (permalink)
    Thanks for the responses guys.
     
    It is all Synths Ken.  The projects are not very old.  When I say earlier version of Sonar Platinum I meant towards the end of last year.  Sorry -  It was late last night and I was a little vague! 
     
    Any that had a patch in them had the default patch Brunddlefly.
     
    I wonder if it was an unusual set of conditions like saving the projects with the synths disconnected and the tracks hidden and archived? This would also mean people won't notice until they try to un-archive and edit the projects. I rarely do this myself - I just wanted to change the key of an arrangement. 
     
    I always install the updates as soon as they become available.  As timing would have it,  on one of the occasions that a second update was issued shortly after release I made some quick changes to this batch of files and resaved them the day the first release came out.  I probably should rethink that strategy:) 
     
    Anyway, good to know it has not affected everyone.  It is all history now -  onward and upward!
    post edited by tenfoot - 2016/02/17 21:52:27

    Bruce.
     
    Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
    #4
    Paul P
    Max Output Level: -48.5 dBFS
    • Total Posts : 2685
    • Joined: 2012/12/08 17:15:47
    • Location: Montreal
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/02/18 18:27:25 (permalink)
    tenfoot
    Any that had a patch in them had the default patch Brunddlefly.



    Bruce, the mention of z3ta+2 is very important because what you experienced is exactly what happened with the second to last version of z3ta+2.  There was a bit of an uproar in the Instruments forum about it.   So did your problem apply to only z3ta+2 presets, or with other synths as well ?  Are you now running z3ta+2 version 2.2.2 ?

    Sonar Platinum [2017.10], Win7U x64 sp1, Xeon E5-1620 3.6 GHz, Asus P9X79WS, 16 GB ECC, 128gb SSD, HD7950, Mackie Blackjack
    #5
    tenfoot
    Max Output Level: -53.5 dBFS
    • Total Posts : 2186
    • Joined: 2015/01/22 18:12:07
    • Location: Qld, Australia
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/02/18 20:53:07 (permalink)
    Hi Paul.  It was all synths -  Kontakt,  Sample tank 3, Superior Drummer,  Trillian and Zylenth 1.

    Bruce.
     
    Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
    #6
    FinnET
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2015/02/08 12:44:58
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/03/13 15:15:52 (permalink)
    This happened to me too recently. I'm mostly using the Halion Sonic VST. Looks like most my Projects have lost settings for the synth. Just the default sound patch on channel 1. This is a real disaster for me :-( Dont exactly know when this happened. More recent Project isn't affected but sadly most of my work is...
    #7
    tenfoot
    Max Output Level: -53.5 dBFS
    • Total Posts : 2186
    • Joined: 2015/01/22 18:12:07
    • Location: Qld, Australia
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/03/13 21:42:09 (permalink)
    FinnET
    This happened to me too recently. I'm mostly using the Halion Sonic VST. Looks like most my Projects have lost settings for the synth. Just the default sound patch on channel 1. This is a real disaster for me :-( Dont exactly know when this happened. More recent Project isn't affected but sadly most of my work is...


    I feel your pain FinnET!  I had to open older versions of my projects,  save the synth patches as presents,  then return to the later versions with the missing patches and restore them. I don't know which version of Sonar it happened in or what caused it  but it was isolated to a particularly large group of projects I was working on late last year and early this year.  Thankfully whatever it was hasn't happened in any version since. 

    Bruce.
     
    Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
    #8
    FinnET
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2015/02/08 12:44:58
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/03/14 15:07:36 (permalink)
    Looking brighter today tenfoot! Installed X3 again and opened some autosave-backups. Patches back! Took screenshots of the settings and manually put them in when back in Platinum. Worked! :-) But of course, this was an experience I'll rather be without... 
    #9
    tenfoot
    Max Output Level: -53.5 dBFS
    • Total Posts : 2186
    • Joined: 2015/01/22 18:12:07
    • Location: Qld, Australia
    • Status: offline
    Re: Vst synth patches not saved in earlier version of Sonar Platinum 2016/03/14 15:23:28 (permalink)
    FinnET
    Looking brighter today tenfoot! Installed X3 again and opened some autosave-backups. Patches back! Took screenshots of the settings and manually put them in when back in Platinum. Worked! :-) But of course, this was an experience I'll rather be without... 


    Glad you got them back!  Always good to have those old backups around:) 

    Bruce.
     
    Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
    #10
    Jump to:
    © 2025 APG vNext Commercial Version 5.1