• SONAR
  • ISSUE with Soft synth templates input (changes to previous synth's output) (p.2)
2016/02/23 14:07:47
sonarman1
To make sure I also tried renaming it manually. Still the problem exists. Now I am wondering what settings does my old AUD.INI would have preserved. Should I retrieve it back. I guess I can ignore it.

Wait I do find few more INI files in the same folder. Will resting them help?
2016/02/23 14:10:12
sonarman1
EdiT
2016/02/23 14:11:05
scook
If you want to reset everything, holding the CTRL+SHIFT keys while starting SONAR will overwrite the files in your user folder and some registry entries, returning them to factory defaults
2016/02/23 14:13:45
sonarman1
Cool. I'll try that and get back to you :)
2016/02/23 14:27:59
sonarman1
Tried it with no use. Are you sure that will reset everything? Cos all of the INI files other than AUD seems unchanged with same old dates. I did get a pop up saying "SONAR will now personalise your user settings by copying application data files" when I opened holding down ctrl+shift.
2016/02/23 14:44:54
Kylotan
I don't think resetting your config will change anything; this just looks like a Sonar bug, plain and simple.
 
I have seen soft synth inputs get screwed up from time to time and I didn't know what caused it - this seems like a candidate as I often use track templates.
 
I've also seen track templates mess up drum maps quite significantly too.
2016/02/23 14:56:56
sonarman1
Oh gawd! I did renamed the entire app data folder as Sonar Platinum Backup and when I started sonar it did create a new app data folder itself. But no use, the problem remains.
2016/02/23 16:53:44
brundlefly
Kylotan
this just looks like a Sonar bug, plain and simple.

If that were true, I would expect to have seen dozens of threads like it by now, and I've seen none. It may be a bug, but hardly 'plain and simple'; clearly the OP's particular environment is a factor.
 

I've also seen track templates mess up drum maps quite significantly too.

 
Drum Maps are a whole different issue. Soft synth MIDI ports are assigned and numbered in the order they're inserted. If the new synth is on a different virtual port than when the template was originally saved, the map is going to be wrong - unavoidable, but easily corrected.
2016/02/23 19:51:02
robert_e_bone
I confess I never ever use simple instrument tracks, so if that plays any part in this, I will not have ever run across it.
 
I always manually insert my audio and midi tracks, because I like the deliberate nature of insert/name/route that makes sense in my head - anyways, everything always works for me, by doing this myself every time I ever insert tracks/synths.
 
Bob Bone
 
2016/02/24 01:18:09
sonarman1
Alright guys I will have to fresh install and see. I can't do it right now, I will have to wait a few days. Till then if anyone got any idea to solve this u are welcome.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account