Now that I know that 2x on = upsampling on, I have tested it again. And there is one thing that I don't find good: it seems to be a project settings. I mean that when I choose to turn upsampling on, I have to save my project and this choice is not global, there is no upsampling in other projects. This choice should be global: if I think that upsampling is good and my computer is powerful enough, I want it to be on every project.
 
I will try to save the 2x in the file that I use as a template every time I start a project.

It's definitely worth exploring. Technically upsampling has trade-offs, and performance can vary depending on the plugin, but my experience so far is that if I listen to a mix for a while while I have upsampling turned on and then turn it off I instantly hate it.

Upsampling on just sounds more open, has more smoothness and sheen, and sounds less "bunched up". I don't notice a big difference at lower frequencies, but the high mids and highs really sound different to me.

It's a serious enough difference in my experience that I'm purposefully unfreezing and refreezing any tracks that were frozen before I started using upsampling, and re-bouncing things that I thought were done but whose deadline hasn't passed yet. I'm also taking a serious review of my plugins and replacing 32-bit ones that aren't opening in jBridge with similar processors that can upsample. It may not sound exactly the same tonally, but even then then I tend to like the results more.

Peace,

Tunes

Also - and I'll update the original post to reflect this - upsampling can also be turned on for your softsynths. It's not just limited to audio FX. I'll be experimenting with this over the next few days as I work on some mixes.

Peace,

Tunes

If I select the upsample on render option does this mean that it won't affect my cpu usage and the upsampling is only done when exporting a track?

That is my understanding, although I've been assuming that the option to render also affects internal track bouncing and freezing tracks, not just exports. Another thing to clarify with Cakewalk support.

I tend to turn both on for each plugin so I can just use the "2x" button to turn it on and off depending on needed performance. I figured that it was kind of a pain to touch each plugin and I didn't want to have to wait until bouncing to find out that my computer was hitting a wall due to performance, then go back to add "Upsample on Playback" to each plugin to avoid it later.

Peace,

Tunes

I believe "Upsample on Render" would affect freeze, bounce and export.
 
PC modules can be set to upsample. It requires looking up the clsidPlug value for the plugin from the VST Inventory and adding the appropriate entries to Aud.ini.
 
I wrote a utility to view/edit existing Aud.ini entries but have not released it expecting CW to make the process easier. I can make it available although it is not much better than using notepad to update Aud.ini.
 

Whoa. Ninja level 1000 achieved, scook! That's awesome. I'd love to know more about what needs to be added. I'll dig in to my Aud.ini and see what I can see.

Hi,
Thanks a lot for this thread,my ears are so accurate that I was using the plug-in upsampling ( in the plug- in gui on top left) and didn't even notice the x2 knob in the mix quarter of the tool bar... Meaning I was convinced to have a super oversampled process while,well,nothing really happened.
So applying the insight I've discovered in this thread information I clicked the2x knob... Then problems begun.
Quite a lot of crashes ,.. Then I turned around and worked it out ,for me an important thing is that in my set-up,it is not good to enable oversampling option in direct x plugs.
But now everything is ok but I just want to mention that when I change the buffer size of the Layla 3 g in the asio pannel,everything is broken,so my turnaround is: Disable the 2x knob in the toolbar,change the buffer size then everything is fine.
Sorry for thoose confused explanations. Hope it will help.
All the best.
Olivier.

Good find with the Direct X plugins. I haven't used much in the way of Direct X in a long time, so I hadn't tested them.

I had my first crash earlier today, too. This was when trying to freeze a synth track with the synth set to upsample. Apparently the AAS Player synth is unhappy about the idea. So definitely a good idea to save often so you can backtrack if you run into a synth or plugin that isn't happy about receiving audio data that doesn't match the project's native sample rate. The experiment continues!

Peace,

Tunes

The Aud.ini details are in the help file http://www.cakewalk.com/D...mp;help=Mixing.26.html