tenfoot
Just go to the synth properties drop down menu and de-select 'synth connected'. This will allow you to leave your template as it is and still free up the ram. It will also solve your wave export problem. When you wish to use the synth again  just reconnect it. If you save this setting in your project template your synth and midi tracks will be created and wating but will not be using any ram until you need them.

Nice in-place solution!

Keni

tenfoot
Just go to the synth properties drop down menu and de-select 'synth connected'. This will allow you to leave your template as it is and still free up the ram. It will also solve your wave export problem. When you wish to use the synth again  just reconnect it. If you save this setting in your project template your synth and midi tracks will be created and wating but will not be using any ram until you need them.

Nice in-place solution!

+1
 
Just make sure that the Unload Synths on Disconnect is checked in the Synth rack menu.   Otherwise, the synth will not dump the sample memory.
 
 

SimpleManZ
Curious, I tried to duplicate the issue here.
I start a new project with the Normal Template.
Load a soft synth; Record nothing; Freeze track does nothing.
Open PRV and put in a 1 bar note; Sonar Freeze the track as expected.

I also tried to reproduce using the TX16Wx sampler with multiple outputs and also found that Freeze does nothing when no MIDI data is present, which makes me wonder why the OP's project generates wave files.
 
--Ron
 
 

tenfoot
Just go to the synth properties drop down menu and de-select 'synth connected'. This will allow you to leave your template as it is and still free up the ram. It will also solve your wave export problem. When you wish to use the synth again  just reconnect it. If you save this setting in your project template your synth and midi tracks will be created and wating but will not be using any ram until you need them.

Where is this?
Using "Browser" and selecting "Synth Properties" it opens Kontakt (my synth).

rogeriodec

tenfoot
Just go to the synth properties drop down menu and de-select 'synth connected'. This will allow you to leave your template as it is and still free up the ram. It will also solve your wave export problem. When you wish to use the synth again  just reconnect it. If you save this setting in your project template your synth and midi tracks will be created and wating but will not be using any ram until you need them.

Where is this?
Using "Browser" and selecting "Synth Properties" it opens Kontakt (my synth).

 
Open Browser and select the synth tab
Make sure the synth you wish to disconnect is highlighted (Don't double click or the properties page will open)
At the top pf the browser next to the word Synth is a dropdown menu - click on it and uncheck synth connected
 

If the browser is open to the synth rack view all you need to do is to click the power button on the left of each synth to turn it off.
 
I use a custom template that has several synths in it as well but when I created the template I set all the synths to be off (disconnected as already mentioned).
 
Then I just turn them on when I am ready to use them. I makes no sense to me to freeze the synth if there is no data. The purpose of the freeze is to bounce the audio.
 
Instead just disconnect/turn off the synth till its needed.

 
 

SimpleManZ
Curious, I tried to duplicate the issue here.
I start a new project with the Normal Template.
Load a soft synth; Record nothing; Freeze track does nothing.
Open PRV and put in a 1 bar note; Sonar Freeze the track as expected.

I also tried to reproduce using the TX16Wx sampler with multiple outputs and also found that Freeze does nothing when no MIDI data is present, which makes me wonder why the OP's project generates wave files.
 
--Ron




Two possibilities suggested. 
1. The OP's project is more than zero bars long i. e. there are other audio or MIDI tracks and the freeze synth is creating an audio file the length of the project (longest track) that is silent.
2. The OP's MIDI tracks are not really empty and may contain controller or other values that he is not aware of.

rogeriodec

dcumpian
Instead of deleting them, can't they be archived to prevent this?
 

 
"Archive" does not freeze synth and thus does not release RAM (which in my case are at least 4 Gb of RAM when Kontakt is active).

Well, okay, but that wasn't your original question.
 
Just don't load the synth until you need it.
 
Regards,
Dan

tenfoot
Open Browser and select the synth tab
Make sure the synth you wish to disconnect is highlighted (Don't double click or the properties page will open)
At the top pf the browser next to the word Synth is a dropdown menu - click on it and uncheck synth connected

 
You were right tenfoot! This solution does exactly what I wanted at first, ie remove synth from RAM without losing any references and without consuming disk space.
Thank you very much!
 

slartabartfast
 
 

SimpleManZ
Curious, I tried to duplicate the issue here.
I start a new project with the Normal Template.
Load a soft synth; Record nothing; Freeze track does nothing.
Open PRV and put in a 1 bar note; Sonar Freeze the track as expected.

I also tried to reproduce using the TX16Wx sampler with multiple outputs and also found that Freeze does nothing when no MIDI data is present, which makes me wonder why the OP's project generates wave files.
 
--Ron




Two possibilities suggested. 
1. The OP's project is more than zero bars long i. e. there are other audio or MIDI tracks and the freeze synth is creating an audio file the length of the project (longest track) that is silent.
2. The OP's MIDI tracks are not really empty and may contain controller or other values that he is not aware of.

You should also be sure, because I created a new synth and now is the same that happened to you, ie, trying to Freeze Synth, does nothing if there is nothing on the tracks.
So should have possibly some hidden control or envelope that is causing this problem.
I will take more carefully next time.
 
Well, from all these various answers, I now have learned a number of alternatives that I did not know before.
 
I appreciate the efforts of all of you, thank you!

What scook said :-)
if you have even one midi track with some data on it Sonar has to freeze all outputs for the synth since we have no idea which midi track relates to what output.
However if it's freezing when there are zero midi tracks with data we could optimize that case

scook

rogeriodec
 
In my opinion, it is not at all difficult Sonar interpret if a track does not contain data and does not generate a "dumb" file.

SONAR has no idea what the synth is going to output in advance or that the output is not something the user wants. 

 To add to Scook's comment, some synths are sound generators that do not require any input whatsoever - they automatically generate soundscapes/rhythms/whatever as soon as they are instantiated. Plenty of examples in the Reaktor library, f'rinstance. It would be most unfortunate if Sonar simply failed to capture their output when frozen.