Tez

Typically I never save bounce data with the project which will change on further project work, I'll extract the current mix audio & close without saving which deletes the bounce data.. it didn't occur to me that deleted previously saved audio tracks persists when the project is again saved. So once again thanks for the info! Oh & CbB does the same, I guess I should have known....

You may well be correct, but try this, create an untitled project & keep it untitled, add an instrument, audio & midi tracks, record some midi & bounce the midi to audio. Check the Audio Data folder that's where untitled audio data is found and you'll see just the bounced track no preview files, and of course closing the untitled project without saving gets rid of the bounced track... Repeat the above but this time save as a named project with copy all audio checked and in the new audio folder you'll see just the bounced track no preview files. Delete the bounced track and re-bounce, save the project & both preview & bounce files appear but so does the previous bounce track which should be deleted. Now that ain't right unless I've made an error, don't think I did. Meanwhile I'll manually delete the useless preview files 😁

Once again thanks for the explanation, but closing the project without saving should get rid of all bounce generated files, only the bounce gets deleted while the "preview" lingers, that can't be right and as I stated "This did not happen with a single instrument midi track test project so it's not typical behavior" this is an anomalous glitch and the cause is a mystery to me...

Start Screen Issue: When Sonar is opened for the first time in a windows session the Start Screen is non-functional, Sonar has to be closed & reopened before the Start Screen functions normally. This maybe system related I wouldn't know.

Garbage in the Audio Folder: After a bounce to tracks, even if the project is not saved there are garbage wav files that have to be manually deleted and typically they are of the same size as the bounced track hogging storage with names like: b6365ed7-c7bd-4c51-842e-aa83510dd82a.wav b6365ed7-c7bd-4c51-842e-aa83510dd82a-aaf4056f1032fed006d8ff75ccb60f7f.wav This did not happen with a single instrument midi track test project so it's not typical behavior. but for the project where it occurred in Sonar when the same project was opened and bounced in CbB this did not happen....

I posted this in feedback but since the glitch occurs in CbB clearly it has nothing to do with the latest Sonar release. If any one has an idea what may cause the issue please share your insight...

I have a weird copy/paste glitch in a project as follows: In the PRV with Auto Focus on, if I copy a selected note from focused track switch the focus to another track for the paste using Paste Special. it list the starting track as the copy track, if then I cancel the paste special and immediately open Paste Special again it then shows the correct focused copy track. Strange & inconvenient, as it means for the project I can't safely use Ctrl-C on the copy track which correctly copies followed by Ctrl-V for the focused paste track. Somehow this is project related as it is not typical behavior, but what's causing it? Incidentally this problem also occurs for the project when opened in CbB...

Well, I guess I'm still having teething problems switching from Splat & CbB to Sonar. Regardless thanks so much, the end of project stop option is mostly what I wanted, I was going to request it, I saw the rewind option but somehow missed the stop 🙄 I might find a use for the start & end markers way down the road...

Project start & end makers work when 1st installed in a project, they appear to save with the project, but... On reopening the project they DON'T WORK and have to be cleared & re-installed.

@sjoens Thanks, now I have a copy & didn't have a link till now! I am familiar with how to bounce but the problem is that garbage wav files get left from the process which have to be manually deleted and there's a difference between files with 48000 , 44100 when imported into a second app like Ozone where the 48000 rate produces 2 files on an import command so I'm not sure if the import produces the second from the higher to lower rate, probably so, my mistake was the 2nd file wasn't dated it had lower sample rate appended to the name which got imported into the app gui, so nothing to do with CS but the garbage files still remain to be resolved. Thanks again...

@User 905133 because iZotope plugs authorization on another OS e.g. a macOS might behave differently from windows, I say might because I wouldn't KNOW... 🙄

When you bounce to track what wav files are produced in addition to the typically named "bounce file" and for the bounced file exactly what is its format as seems like its a wrapper for a dated wav file and if possible please explain this! Thank you verrry much 😁...

1. I bounced to tracks on a project I closed the project and did not save, in the Audio folder the bounced tracks disappeared but there were some additional wav files that get produced that don't get deleted, the same thing happens if the bounced track gets deleted and the project gets saved. These files have to then be manually deleted. 2. Shifting to another workspace and then trying to shift back to basic CS becomes unresponsive and has to be canceled.

So should have I 😁

I had a problem with iZotope plugins including Ozone all of which were OS authorized not iLok, that only got resolved when I installed iLok in order to establish the service running in background, since despite local authorization iZotope 1st checks for the iLok service & with no iLok it's a problem . This may not be relevant to your issue but I thought it was worth a mention 🥴 ...