COMING UP - Real-time resampling..

So yet another new feature is coming up in Platinum.... So what is it? Do people need this? (Top of their list?).

https://www.cakewalk.com/.../Rolling-Updates#start

I welcome this. For me, the non-realtime nature of the upsampling as it currently stands is a bit too cumbersome, workflow-wise, to be all that useful. For one thing, A/Bing the difference is a horribly long winded process. If you can just switch it quickly in and out, that becomes really useful.

Well this was a long thread ! ;)

I was expecting huge gasps of excitement!

That's more like it ;)

Adq
Offline upsampling has no much sense without real-time upsampling, because if there is real difference, it is often so huge, that sounding changes significantly, and if one set up some sound without upsampling, it would very often suit worse with upsampling, just because it would sound very different, I think so.

For the time being, you'll want to freeze the synth with upsampling applied before mixing.

Interesting... if upsampling a 44.1k project, does it unconditionally get downsampled on the master output? What if the project is being exported at the sample rate of 88.2? Will the master output be downsampled and then re-upsampled?

yevster
Interesting... if upsampling a 44.1k project, does it unconditionally get downsampled on the master output?

 
You don't really upsample an entire project per se (nor do you necessarily need to), you upsample/render/downsample a track or clip that contains a plug-in when you render it to audio.
 
The advantage of real-time upsampling is you can determine whether the upsampling process makes a difference or not (most of the time it doesn't, but when it does...). Upsampling/rendering/downsampling back down takes more time than simply rendering, so you don't want to do it unless you need to.
 
I have a few projects that use multiple plug-ins that benefit from upsampling. When I bounce down to two tracks, it takes a lot longer as the individual tracks are upsampled/rendered/downsampled during the rendering process. The audible results are definitely worth it, but I wouldn't want to spend the time if it wasn't necessary.
 
 
 

Noel Borthwick [Cakewalk]

yevster
Interesting... if upsampling a 44.1k project, does it unconditionally get downsampled on the master output? What if the project is being exported at the sample rate of 88.2? Will the master output be downsampled and then re-upsampled?

If exporting a 44.1 project at 88.2 yes because other plugins in the project are still being rendered at 44.1.
However it doesn't make much sense to export to a higher sample rate since you aren't going to get any gains. Upsampling there is only done at the final stage. A

Then, since individual tracks can be upsampled, wouldn't it make sense to upsample as far down the mixing chain as possible? Why not downsample only on the busses that contain plugins that can't handle the higher sample rate? Then, if no downsampling occurs before the master bus, the project need only be downsampled to the export rate.
 
This is particularly important in Sonar as, unlike StudioOne and Cubase, the sample rate for a project is immutable. A project created for CD at 44.1Khz cannot be easily re-mixed for video release at 48khz, or for any higher sample rates. Upsampling that goes maximally far up the routing graph could ameliorate that deficiency.

Correct this is at the plugin level not bus or track.
What you are talking about is a completely different request. To resample at a project level.