dougalex

Ah yes, I see the confusion is: Project template vs track template I think the screenshot from the manual that you posted was about project templates, so I thought you were talking about project templates.

insert the template into an existing project? I think you open a template, not "insert the template into an existing project". Maybe I totally misunderstood what you are doing. Maybe you have to make a short video to fully demonstrate the issue.

As test, I saved a template with envelopes and then opened the template. Seems like I have the envelope data saved with template:

If the Template is not giving you want you expect, can you just save it as a regular project? (Then save as new name to avoid changing your basic reusable project)?

Summary from Perplexity.ai: To ensure your Automation data is included in templates: Draw or record automation envelopes explicitly in the tracks. Verify that all desired automation lanes are visible and properly configured before saving the project as a template. More: In Cakewalk Sonar, when you save a project as a template, automation data, including envelopes, can be transferred. However, there are some nuances: Automation Envelopes: Automation envelopes that are drawn with nodes (manually or through automation recording) are saved in the template. This includes volume, pan, and parameter changes for soft synths or effects. If the envelopes are not explicitly drawn or recorded (e.g., they exist only as remote control data or MIDI CC messages), they might not be saved as part of the template unless converted into visible automation lanes. Remote Data: Remote data (e.g., MIDI CC messages sent from external controllers) is not directly saved in the template unless it is recorded into a track or converted into automation envelopes. If you are using a controller like the Novation ReMOTE SL or similar, you would need to save its configuration separately as a MIDI remote template or SysEx dump, as described in guides for controllers24. Template Behavior: Templates save all project parameters and settings that are part of the project file, including automation envelopes with nodes. However, dynamic data like live controller input needs to be recorded or explicitly added as an envelope to persist in the template. Envelopes created with nodes (manually drawn or recorded) are saved in templates and projects, ensuring automation data is transferred. However, live remote data (e.g., MIDI CC messages) must be recorded into tracks or converted into visible automation envelopes for persistence in templates

Are you saying you saved a template and it did not save the Automation that you wanted to include in the template?

Maybe I am not understanding the question, but: Clip Automation: Only affects individual clips (Volume shows as red envelope in Audio clips, Velocity shows as violet in Midi clips) Track Automation: Affects all clips in track (and is AFTER any existing Clip Automation)

I have used Sonar for almost 25 years now. From time to time, I go on youtube and search for the old tutorials and tip and tricks on Sonar. I cannot believe how much I still learn because there are so many great features and work flow advances that already existed many years ago... and the features still work the same way in the newest version... so all of the old videos are as helpful today as they were many years ago. Just check out the depth of midi editing features in this fantastic tutorial (definitely not just for beginners!)

Thanks for the comments. I just started over and retried using the steps I distilled in my prior post, and I finally got that 8 bar synth phrase done very quickly. It seems that my problem was that I was using a time resolution for the threshold... the eighth-note resolution, which would seem logical. HOWEVER, I found that was what made impossible to get the expected results when fine tuning the threshold. It seems that "All" is the way to go, and the other time resolutions only work well if the original material was played very close to a constant tempo (e.g. played listening to a click). Overall, I am just trying to take the necessary baby steps, and learn this AudioSnap tool because, when I "have it down", I very curious to try and hear what it sounds like when used on a multitrack live recording that was NOT played to a click... i.e. find out what is really possible and practical. Thank you for your input!

I am testing AudioSnap by trying to quantize a melody played without click (a short mono synth lead with sharp attack, playing a clear repeating rhythm, mostly downbeats and some eighth notes). I think some of the key methods I am learning are: 1] Basic start: Align start of clip to beginning of measure and set tempo that is a good average, that hopefully at least works for the first bar or so. Turn on playback click. 2] Resolution: Start with resolution "All" 3] Threshold: Given a choice between "having extra phantom transients", and "missing transients", go with "having extra phantom transients". (easier to see and disable extra transients, than it is to see and add missing transients) 4] Fix major drift: At the point where the free form playing starts to drift badly off the set average tempo, make a multiple selection of markers from there to the end, and move the set of markers to adjust for the drift. Listen forward and repeat that process of moving multiple markers forward or backward, as necessary. 5] Quantizing: Quantize, and fix remaining notes that may have gotten got quantized to wrong beat, if any.

In Cakewalk Sonar AudioSnap, the transient markers seem to detect all the obvious transients, and also also adds transients where no transient exists. If you try to eliminate non-existent transients using the threshold, then you lose a lot of the transients that are needed. It always seem to require a tedious time consuming manual process to get the transients correctly marked. How is that "I can detect transients properly" better than whatever algorithm AudioSnap is using? Why would I have to go through do so many manual fixes (e.g. disable extra transients, insert missing transients). Has anyone found any tricks to get reasonably good "transient detection" in AudioSnap?

FIXED!? OMG I was suspicious of Steinberg, but since NO Steinberg was showing in device manager, I never looked in add/remove programs. (DOH!) So, after all this (life sucking hours 😫), apparently all along it was the Steinberg that somehow got installed on Dec 17 that was the problem. I uninstalled it (and the older one)... and everything seems back to normal.

Current status: If I disable x32 audio driver in Device Manager, I can run Cakewalk and Sonar without problem AND Cakewalk/Sonar are using the x32 driver even though driver is disabled in Device Manager. BUT then Windows cannot use the driver because it is disabled. So I enable x32 audio driver in Device Manager for playing YouTube or Media Player, but then Cakewalk and Sonar are back to same problem (stuck in loop testing audio drivers upon launch). Looks like I am now in a one-or-the-other situation now. Used to be fine before this morning.

Thank you for leading me in the right direction! Just what I needed! Just curious... When this happens, Cakewalk or Sonar seems to be trying endlessly in a loop to configure audio interface or driver, making it hard for user to intervene and address more easily. I actually found random clicks will work if you hit it just at right moment between the loops (of the looping driver configuration routine). Maybe in the future, there could be a loop count that then allows the user intervene more easily???

I am uneasy deleting in RegEdit, but if I want to be brave... are you saying, (if it was your computer), you would just go for it and "right-click, delete" the folders named: Steinberg Generic Lower Latency ASIO Driver 64bit" AND Steinberg Generic Lower Latency ASIO Driver 64bit" (and presumably that also deletes their subfolders)?