[Solved] "Freeze Synth" bouncing audio even if empty tracks!

I think that if there is absolutely no information on the tracks of a synth, "Freeze Synth" should not generate any audio file, right?
But even with all tracks empty, when I use "Freeze Synth", Sonar generates a huge WAV file!
Does anyone know how to fix this?

What soft synth are you using?, so I can try and replicate.

slartabartfast
What are "the tracks of a synth?" 

The midi tracks that are associated to a Synth. 
For example, I have 4 midi tracks linked to an instance of Kontakt. All tracks are empty. I click "Freeze Synth" and a WAV file is created (bounced) in the audio folder. I think this file should exist only if there is at least one note in any track. But not when tracks are empty.

What does the wave file that was generated sound like?
 

rogeriodec

scook
Delete the empty tracks before freezing the synth or at least set the track inputs to none on the empty tracks.

This is not very friendly, right?

Keep in mind, you told SONAR where the synth output should go. You decided not to use the tracks. Then you told SONAR to freeze the synth. Now you want SONAR to remove empty waves after you instructed it to generate them. I suppose there could be another freeze option but it definitely would be a feature request. SONAR would have no idea in advance of freezing if there would be audio generated or if the empty tracks were created intentionally so the delete would happen after the freeze.

scook
 
Keep in mind, you told SONAR where the synth output should go. You decided not to use the tracks. Then you told SONAR to freeze the synth. Now you want SONAR to remove empty waves after you instructed it to generate them. I suppose there could be another freeze option but it definitely would be a feature request. SONAR would have no idea in advance of freezing if there would be audio generated or if the empty tracks were created intentionally so the delete would happen after the freeze.

I work with project templates, which have a series of tracks that are standard and possibly will be used in the new project.
But I do not want the Synth (Kontakt) load all the instruments, consuming a large portion of RAM, while I'm in the middle of project development and while I do not need these tracks.
Therefore, the best option is to freeze the synth until it is needed to use it.
Remove the tracks or change your references is not a good option.
Having a giant Wav file and completely blank (dua Sonar limitation) is also not a good option.
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.

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. MIDI data is going into some plug-in which SONAR hosts. SONAR does not know what the plug-in does with the data. You have instructed SONAR to catch the results into the tracks you have created. SONAR could only removed the empty waves after they were created and that would be a new feature request. The bottom line is SONAR is doing as it has been told. This may be a case where track templates may be more efficient than a large project template.

scook
SONAR has no idea what the synth is going to output in advance or that the output is not something the user wants. MIDI data is going into some plug-in which SONAR hosts. SONAR does not know what the plug-in does with the data. You have instructed SONAR to catch the results into the tracks you have created. SONAR could only removed the empty waves after they were created and that would be a new feature request. The bottom line is SONAR is doing as it has been told. This may be a case where track templates may be more efficient than a large project template.

I just want to free up RAM without losing all track settings and instruments within the Kontakt, also without occupying unnecessary disk space.

Keni
Why not simply save the synth as a track template...

Then remove it from the project, do your other work and load the track template when you actually get around to using the synth...?

So far I had not explored the potential of Track Template, but I now see that this is the most practical, flexible and elegant solution.
I grouped all tracks that were related to the synth in a track folder and I saved this folder as a template. Sonar has done the job well: saved all tracks made reference to the synth as well as the entire contents of synth (instruments within the Kontakt).
Now for all projects that use these same tools, I simply insert the track template and everything comes automatically.
Thank you very much Keni!

Glad I could help...

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!

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).

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.

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

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