Been checking out different sample rates, advantages/disadvantages, quality of conversions etc.
 
What I found on some sites are to use specific software like SoundForge or WaveLab to convert before importing into daws. I mean strongly recommended to do that.
 
All major samplers I used have had different options for this.
Dimension has a sinc option for rendering etc.
And daws doing resampling usually have a handful of algos to choose from.
 
So what is Sonar using:
a) importing - a bit confused here since only bit depth is asked for
b) exporting downsampling like 48->44
c) exporting upsampling like 48->96
 
Thanks.
 
EDIT: Link to a useful article:
http://karma-lab.wikidot....g-a-sampling-frequency

Maybe another approach is to test the programs under discussion to see which ones do the best job of sample rate conversion. Here's one effort to do that, though they limit themselves to testing just 96K to 44.1K. No clue is given about what algorithms the programs use.

bvideo
Maybe another approach is to test the programs under discussion to see which ones do the best job of sample rate conversion. Here's one effort to do that, though they limit themselves to testing just 96K to 44.1K. No clue is given about what algorithms the programs use.

According to those tests, SONAR does extremely well compared to other DAWs. Given that Cakewalk uses iZotope algorithms for time-stretching, it wouldn't surprise me if they use iZotope's SRC algorithms as well. [Edit: Wrong guess, see post #11]

Thansk guys...
 
..but if it's actually the same algos as stretching...how about Artist- which of the qualities are there for import/export situations?
 
And some algos do a good job on certain music material - and less good on others.
That's why resampling algos are by choice, and a number of them to pick in the same app.
 
Reaper has got 10-12 or so, and various quality alternatives to run realtime or render situation.
 
One size does not fit everywhere.

SONAR uses high quality windowed sinc interpolation for SRC conversions on both import and export.

Engineers often use the term "FM" - Frickin' Magic - for any blackbox process they don't understand but that Just Works so there's no need to dig deeper. SONAR automatically resamples when needed (e.g. rendering a 48KHz sample library to 44.1KHz or importing a 44.1KHz file into a 96KHz project) and does it exceptionally well with no user input needed.
 
Is it iZotope code? Probably not. iZotope's company description states that they license DSP technology to ProTools, Logic and SONAR, but they explicitly list "dithering, noise reduction, time stretching, and audio enhancement". No mention of resampling algorithms. The time-streching code is in iZotope_Radius_x64.dll, but I see nothing with an iZotope name regarding resampling. Furthermore, Noel has described SONAR's sample-rate conversion as "custom", suggesting it was developed in-house.

Many thanks, Noel.
 
My concern has been since I noticed that default I had in Reaper made a 44k original reference track of a professional recording was resampled running the project in 48 - and it created peaks 1.6dB higher, actually overs then on a pro recording.
 
So it's obvious it's not all transparent.
 
And then thinking if importing 20 track from another daw - a tiny bit unwanted artfacts start adding up - and may be clearly noticable on a project.
 
It's like using a tiny bit worse preamp on every track - and what you end up with is clearly noticable.

lfm
a) importing - a bit confused here since only bit depth is asked for

SONAR let's you choose import bit depth because file bit depths can be mixed in the same project. But to avoid having to re-sample files on the fly, all files must use the same sample rate, and it's determined either by the sample rate of existing audio in the project or by the default rate for new projects you have set in preferences.
 
 

brundlefly

lfm
a) importing - a bit confused here since only bit depth is asked for

SONAR let's you choose import bit depth because file bit depths can be mixed in the same project. But to avoid having to re-sample files on the fly, all files must use the same sample rate, and it's determined either by the sample rate of existing audio in the project or by the default rate for new projects you have set in preferences.

 
Thanks.
Just assuming then, not knowing, that the very best algo is used for import, since not time or cpu critical. But since one algo might be better for certain frequency content - a choice would be nice.
 
In help file it mentions a range of quality settings for Audiosnap - and maybe platinum has a selection box for import, or?
 
Thought I might do an FR on this - but if in bigger version of Sonar then that would be kicking in open doors.
 

lfm
My concern has been since I noticed that default I had in Reaper made a 44k original reference track of a professional recording was resampled running the project in 48 - and it created peaks 1.6dB higher, actually overs then on a pro recording.
 
So it's obvious it's not all transparent.

If you look at the test results for Reaper referenced in post #2, you'll see that Reaper's algorithms aren't particularly good and certainly don't stack up to SONAR, Logic Pro X, etc. I don't know if they've improved since those tests were made, but if not, it's not surprising you wouldn't find them transparent. Really, the only reason to offer a choice of multiple algorithms is if there isn't one good one. That way you can choose the one that's "less bad."