Hello!
How can one convince the external USB module “Creative Sound Blaster SB1240” and "Audacity" to actually work with 24Bit/192kHz? fh is always exactly at 22k05Hz. Does win11 need a special driver or does the internal digital filter always take care of this limit?
It would be really nice if one practically didn't need any real measurement technology anymore, just a notebook, a bit of software and this external ADC / DAC even with an analog phono equalizer on board.
Does anyone know anything about this blaster?
kindly,
HBt.
How can one convince the external USB module “Creative Sound Blaster SB1240” and "Audacity" to actually work with 24Bit/192kHz? fh is always exactly at 22k05Hz. Does win11 need a special driver or does the internal digital filter always take care of this limit?
It would be really nice if one practically didn't need any real measurement technology anymore, just a notebook, a bit of software and this external ADC / DAC even with an analog phono equalizer on board.
Does anyone know anything about this blaster?
kindly,
HBt.
Strange:
the chipset does consist of the DAC AK4396 and the ADC CS5361, both are 192kHz 24bit deltasigma representatives.
It is clear that the band limit is 22k05Hz and I find that strange. Audacity clearly shows that it was also sampled at 192kHz, yet fh remains stubbornly stupid at 44k1Hz / 2 ..!
the chipset does consist of the DAC AK4396 and the ADC CS5361, both are 192kHz 24bit deltasigma representatives.
It is clear that the band limit is 22k05Hz and I find that strange. Audacity clearly shows that it was also sampled at 192kHz, yet fh remains stubbornly stupid at 44k1Hz / 2 ..!
@hbtaudio IMHO audacity does not talk to your soundcard driver directly (such in wasapi exclusive or asio), but via windows mixer (wasapi shared, the other windows methods audacity offers via PortAudio). IMO what happens in your setup is the following:
Audacity asks windows mixer to communicate at 192kHz. The mixer says "sure, I support 192kHz". The mixer receives the 192kHz from audacity, but it is configured to run at 44.1kHz internally + output to the soundcard (via the sound control panel). Therefore, it will silently resample 192 -> 44.1kHz and send the stream to the soundcard. The capture chain is just reversed: card 44.1kHz -> audio mixer resampling to 192kHz -> Audacity. IMO that's why you see the frequency response limited to 22k.
As @lcsaszar points out - the mixer needs to be switched to a frequency you want to actually use.
AFAIK Audacity does not support wasapi exclusive mode (though it would be simple to do as it uses Portaudio), nor is compiled with ASIO by default (binaries with compiled-in ASIO client library cannot be distributed officially without contracting with Steinberg).
Audacity asks windows mixer to communicate at 192kHz. The mixer says "sure, I support 192kHz". The mixer receives the 192kHz from audacity, but it is configured to run at 44.1kHz internally + output to the soundcard (via the sound control panel). Therefore, it will silently resample 192 -> 44.1kHz and send the stream to the soundcard. The capture chain is just reversed: card 44.1kHz -> audio mixer resampling to 192kHz -> Audacity. IMO that's why you see the frequency response limited to 22k.
As @lcsaszar points out - the mixer needs to be switched to a frequency you want to actually use.
AFAIK Audacity does not support wasapi exclusive mode (though it would be simple to do as it uses Portaudio), nor is compiled with ASIO by default (binaries with compiled-in ASIO client library cannot be distributed officially without contracting with Steinberg).