dougalex

@Helios.GI am not having any problems with scaling so not sure if display size or scaling settings is relevant to my topic, but to answer your question: I have 32" 4k display and a super wide screen (for Console View) connected to my Dell XPS17 laptop. Display scale setting in Sonar preferences is 100%

Anyone have this going on? Several times I have thought I was "not getting a particular floating window to appear", then I realized it was actually there, somewhere on my desktop, but very small (a small rectangle). I do NOT mean "minimized", I mean the window was "sized to a small rectangle" (i.e. the "restore" size was at the smallest possible size). Once I dragged the edges and sized it properly, I was all set.

Not sure if this is related but... I (thought I) was not getting a particular floating window to appear, then I realized it was there somewhere on my desktop, but very small (a little rectangle). I do NOT mean "minimized", I mean the window was sized to a tiny rectangle (as in the "restore" size was smallest possible size). Once I dragged the edges and sized it properly, I was all set.

My observations: I am using Sonar and it has option for "Instrument Track". If you have installed TTS-1 from a previous legacy Sonar installation, it is still there in Sonar. I have never noticed it taking "a lot of work to take a midi file and set it up with the correct sounds". How long does it take you?

I am curious to know what VST may have caused the problem? (I know this is not helpful for past issues but) For many years (decades) with all my audio and video projects, I use "save as" with incremented version numbers many times during the editing... so if any corruption occurs, it would never set me back that far.

Did you try opening in safe mode? Or try saving a new extra copy of the problem project file that has no audible playback, and delete all but one track to try to zero in on more troubleshooting.

Thanks for responding and explaining. My two cents: If I notice track colors "don't work with the theme I like best", then that just means I need to adjust my track strip colors. Because, to me, having the full strip displaying the color is definitely one of the the most helpful GUI elements to quickly/easily guide my eyes to "what I am looking for". (i.e. having the "full strip colored" is more important to me than "using the theme I like best")

I am optimistic that this is just a matter of time before the programmers work through their todo list... however they deem the priorities. I just now checked out out Tungsten, and since the highlights you mentioned are indeed more obvious in Tungsten, I now decided to just leave it on Tungsten unless/until I notice something that bugs me.

Very subjective of course... because for example, after taking 5 minutes to compare the Sonar themes, I chose Dark theme, then.... got right to work and never even thought about the GUI again. Not once. And interestingly, when I see the more colorful themes like the ones customized in the legacy Cakewalk, I find my thinking "Oh my! I could never look at that for a minute, much less all day!".

I think it would reduce many future questions/complaints if on next update the Preference to "Show Strip Colors" is set to default to being on (checked).

I do not have Faderport, but I can report that my X-Touch One has been working fine as surface controller in new Sonar.

I have the Mute Solo Record buttons. I cannot yet reproduce what you encountered.

I know that is all good information.... and appreciated. I just had hoped someone could confirm that this particular project must be corrupted because, the exported mix does not match the relative volume of the two tracks being heard right before the export. i.e. I am not talking about the overall level, I am talking how one of tracks exports at a different level thereby changing the mix (the balance between tracks, not the overall level)

I understand you are in a different situation, but... For "regular users who generally always upgrade to latest version", the subscription makes total sense AND I believe actually costs less over time.

Yes, same result. 😐

BTW, first, thanks for downloading the project and checking it out! Please understand the troubleshooting here: Step 1] I purposely made "MATT" drastically low in volume and "DOUG" loud in the mix. Step 2] I "Export Entire mix" and check the Export results, which, surprisingly, NOW (in the Export) "MATT" is now louder than "DOUG" I created a fresh new project with those two wav files and Export was fine. So I think something is corrupted in that one project (the one uploaded)

The plot thickens: Keep in mind the situation: I like my mix so I export it, but in the export, several tracks are much lower than I just heard in mix (NOT talking about overall mix level, it is relative levels of instruments in the mix) Use of Aux track seems to be involved I am using an Aux track to combine a left/right keyboard tracks to one fader. When I set the keyboard track back to Master, as opposed to Aux track, the bizarre problem (Export mix not same as heard before export) goes away. Also keep in mind, when I bypass the Aux track on the keyboards, the problem not only goes away on the keyboard track, but the problem goes away on the other affected tracks, which are UNRELATED to the use of Aux track on keyboard tracks.

But this is more like a corruption on this project: I have been mixing on Sonar for 20+ years and the export always has same mix (balance EQ effects) as the mix I had right before export. (i.e. the whole point of the DAW's existence 😐)

If you tried to open the cwz file, the files are on you computer. The only trick is you have to tell Sonar where they are (and good to select "reference from current location"). I confirmed this by going to another computer, downloaded and opened the CWZ file, responded to Sonar prompt for location of wav files, and it opened fine.

I use my usual: Entire Mix, 48k, 24bit The strange thing is I tested a fresh new project with those same wav files and it was fine. But the project I need is the one with all my mix and fixes. If my project will not export the mix properly because it is corrupted, that would be a first for me after 20+ years of using Cakewalk/Sonar. The CWZ file I posted has all tracks deleted except for two just to make it straightforward to see/hear the problem.

Yes just FYI 1] I had turned down the Master after the problem started to better compare the mix at same volume as the export 2] cwz files should include audio so not sure why no audio

I have a Sonar file that the relative level of two tracks sound like a completely balance between the two tracks when comparing the playback mix to the exported mix. Can anyone at Cakewalk or other users check this short two track project and explain what is going on? In playback mix I made the lead synth fairly low and the other track (Piano with swooshy pad) louder. But after export it is opposite result, the lead synth is louder. Here is link to CWZ (Cakewalk zip file) on Google Drive https://drive.google.com/file/d/16mL6kCymb4La5226j-tKQ7YoJrCgDeV2/view?usp=sharing

I changed my experiment to: Take a whole stereo mix played live without click and convert it to constant tempo that matches average tempo. So far my experimental results are: 1] Using Melodyne stand-alone to detect and "flatten" the tempo, then export results to wav, got me what I wanted quickly, albeit with some artifacts (presumably because it is stretching as opposed to slicing) 2] The best sounding results (and most feeling like I was in control) was when, in Sonar, I manually split the material where it drifted off, then using stretch (Control+shift) on various length sections to align the whole song to a constant tempo. (No noticeable artifacts). Only in a few instances did I have to split a measure down into the single beats and align them, was mostly four bar phrases. In other words, at least in some situations, it is best just to "manually do" what "audio snap is intended to do automatically".

Yes, that, and making sure average tempo, and resolution are set.

My next experiment will be: I will record a second track of me tapping along to the playback 4/4 downbeats using something like a sidestick sample. Then try the transfer that track to the transient pool, and copy that to the target track. If works well, then would take a lot less time than adding, disabling, moving transients that were detected from the actual source material.