David Baay

Gotta love the irony of that typo. ;^)

Project preview files are handled differently; they need to persist in order for preview to work so they don't require re-saving the project. I'm pretty sure this is working as designed. Also, I did a quick test, closing without saving after bouncing an instrument track with nothing else in a new project, and the two preview files were created as expectedand persisted after closing both the project and Sonar.

Those files are used by the Project Preview function of the Start Screen. Per the documentation they are created by default the first time you export; it doesn't mention bouncing, but Export and Bounce use the same code. This default preview creation will only happen once and the two files will initially have the same content; after that, the file with the longer name will be replaced with a copy of the exported/bounced file only if you pro-actively check the "Include Project Preview' box in the Mix and Render section. I'm not sure why, exactly, but the file with the shorter name seems to be kept indefinitely as an archive of the first export/bounce you perform while the file with the longer name will be the one that plays when you click the Project Preview playback. It's been requested previously to have control over the maximum length of the preview file as this can get to be an issue for users who work with hours-long recordings. For typical song-length projects, the extra space used isn't a huge deal, but I would probably opt to limit previews to 30 seconds myself, and not have one created by default.

Yes, clearly an issue with buffering the 130 (!) active lanes of MIDI on Track 4, compounded by all the split and slip-edited clips. Apply Trimming pretty much eliminates the issue. If you were to simply disable Non-Destructive MIDI Editing, I think you would not encounter this issue. Having it enabled means you effectively double the number of MIDI events that Sonar has to manage every time you split a clip.

You can do this with lanes of an Instrument track but when lanes are not showing, Sonar stacks the clips in the parent track rather than merging their content, and the order in which clips are stacked (i.e. what's on top) can be unpredictable/uncontrollable. When using MIDI lanes, I generally leave the lanes showing so it's clear what's in each lane, and what's soloed/muted. I have previously requested that Sonar visually merge MIDI clips in lanes (and scale them all the same) when lanes are not showing.

Some other differences: - Input to an Aux track is determined by its Input assignment (a Patch Point) and which tracks/buses are outputting/sending to the assigned Patch Point. - Input to a Bus is determined only by the Output/Send assignments of other tracks and buses (notwithstanding that both tracks and buses can get input from plugins in the FX bin). - Aux tracks have a Phase controls that buses do not. - Buses have Input Pan that Aux tracks do not (allowing you to alter panning ahead of the FX bin) - [Input] Gain on Aux tracks can add up to 18dB, Input Gain on Buses can add only 6dB. - Buses have a Waveform Preview function that can be toggled on/off, similar to the "confidence recording" trace shown on armed tracks during recording.

Rather than starting a new project from the template and trying to re-save that over the template, you need to open the template file directly and re-save after modification. It's always worked this way. EDIT: Oops, majorly misread that post, though you made it quite clear it was about Track Manager Presets. Carry on.

Two possibilities: 1. When you set an End marker, Sonar automatically enables Stop at Project End in Track View options, but that option can later be disabled, and the transport will keep running past the End marker. In that case, you just need to re-enable the option. 2. If you have a loop region that runs beyond the End marker, that will override the End marker and the transport will keep running to the end of the loop. Similarly, if the loop starts before the Start marker, playback will initially start at the marker, but when the end of the loop is reached, the tranport will go all the way back to the start of the loop. In that case, just disable looping.

Enable 'Group All Clips' in Record Options (right-click the Record button); this will ensure that clip/take edits are synced. To keep track controls in sync, you can either create a persistent control group for each control or hold Ctrl with both tracks selected (Quick Grouping) whenever you change anything. But a simpler approach would be to output the two track to an Aux track or a Bus, and use the Aux/Bus controls. This will also give you one common place to do automation.

I'm betting Count-in is enabled with a muted metronome bus.

No it's just a convenience feature to facilitate quickly switching between projects without having to deliberately close one before opening the next. And the feature has been around since before Sonar. I didn't actully think it was the default so it's a bit curious that you had it enabled. In any case, there has never been any particular issue with opening multiple projects or MIDI files at once; I do it all the time, and have not encountered any related delays. It's more likely the issue is related to the source or architecture of the files in question or to plugins, interface initialization or Start Screen/Browser setup. I have sometimes seen file-opening delays related to the Start Screen having a browse path on a network drive. Realtime Antivirus scanning by Windows Defender or other AV can also cause this as can having large archive files on your Windows desktop.

The forced MIDI channel setting on the track just re-writes the channel of recorded data on playback as it's sent to the output port. It would have no bearing on whether Find/Change (or any other editing operation) is successful. One of the keys to Select by Filter and Find/Change is that you have to start by selecting all or part of the clip to be processed. It's likely you didn't have the clip selected the first time.

Late to the party, but it seems highly unlikely the coding of the new build itself changed anything. More likely the installation process or some other event returned some config setting to default. My guess based on the symptoms would be that you previously had 'Remove DC Offset During Record' enabled under Preferences > Audio > Playback and Recording. Try enabling it now, and see if you get a similar result.

UseHardwareSamplePosition tells Sonar to use the position reported by the driver to determine the Now time rather than just keeping track internally. I don’t know details of the implementation but there can be conflicts

I can't reproduce this after multiple attempts with loop/punch at differet places in the timeline with different lengths (not always snapped to beats) and at various tempos. I still suspect this is related to your particular interface and driver mode; what is it? Maybe try enabling/disabling UseHardwareSamplePosition in Preferences > Audio > Config File (AUD.INI), depending on what is currently set. You should also try re-booting and/or power-cycling your interface if that isn't happening regularly. Your original post said offset was 7 measures while your last screenshot shows offset is two measure or less if I'm interpreting correctly. Is it that variable?