I did what I thought was a thorough search for this question.
I'm using an SBLive (please don't laugh) which runs at it's own internal sample rate of 48000 Hz.
I like to use loops that have been pre-recorded at 44100 as audio clips in my projects.
Is there significant CPU cycles being used to upsample the pre-recorded audio clips to 48000 Hz while I'm tracking new audio tracks at 48000Hz?
I'm just curious, and somewhat of a DSP idiot, so please be gentle.
-Scott
Does T's internal re-sampling take up CPU cycles?
-
- KVRAF
- 4908 posts since 10 Aug, 2004 from Colorado Springs
-
- KVRAF
- 3335 posts since 18 May, 2003 from Sweden
Hi Scott,
I'm on Mac, and I didn't know much about SBLive, so I looked it up on the SoundBlaster website.
This card apparently supports every normally used sample rate from 8 to 96kHz! So, why would you want to use it at 48kHz, if your project is a CD at 44.1?
With few exceptions, sample rate conversion isn't too kind to the audio quality, so why don't you just set your project sample rate to 44.1 in Tracktion's Settings tab?
HTH,
Joey
I'm on Mac, and I didn't know much about SBLive, so I looked it up on the SoundBlaster website.
This card apparently supports every normally used sample rate from 8 to 96kHz! So, why would you want to use it at 48kHz, if your project is a CD at 44.1?
With few exceptions, sample rate conversion isn't too kind to the audio quality, so why don't you just set your project sample rate to 44.1 in Tracktion's Settings tab?
HTH,
Joey
-
- KVRAF
- 1884 posts since 9 Feb, 2004 from Rochester, MN
Creative cards are locked to 16bit/48khz in ASIO1, or 24/96 with ASIO2.
Tracktion does have to resample, and it's certainly not free, but depending on the algorithm used, it could vary from an unnoticeable amount per track to something that takes up 50% of your CPU.
Tracktion's approach seems to be closer to the former, probably using simple linear interpolation. Based on my very quickly put together test, I'd be surprised if it takes up more than 2% of your CPU for each clip it has to resample. It's probably even less than that.
Tracktion does have to resample, and it's certainly not free, but depending on the algorithm used, it could vary from an unnoticeable amount per track to something that takes up 50% of your CPU.
Tracktion's approach seems to be closer to the former, probably using simple linear interpolation. Based on my very quickly put together test, I'd be surprised if it takes up more than 2% of your CPU for each clip it has to resample. It's probably even less than that.
-
- KVRist
- 207 posts since 27 Mar, 2005 from Spain
Anything else you poke into one is resampled 'on the fly' - and not very well at that. This is just one very good reason to avoid them for audio work.Warmonger wrote:Creative cards are locked to 16bit/48khz in ASIO1, or 24/96 with ASIO2.
Graeme
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
There shouldn't be.rockstar_not wrote: Is there significant CPU cycles being used to upsample the pre-recorded audio clips to 48000 Hz while I'm tracking new audio tracks at 48000Hz?
It might add a little noise though, so if I were you when exporting the edit as an audio file, I'd be inclined to create a 44.1k render.
Someone shot the food. Remember: don't shoot food!