I am not sure anything is to be gained by converting a 16bit source track to 24bit. Of course SONAR will import files based on it preference settings including importing 16bit audio as 24bit. Internally the SONAR will process both 16 and 24bit clips the same.
 
WRT changing the Audio Driver Bit Depth setting, it could be one driver is affecting the other. SONAR will only operate at a bit depth common to both drivers. What happens if only one of the interfaces is enabled when the Wave Profiler is run? Given that both SONAR and Studio One operate the same, is there a possibility that Samplitude is misreporting the setting?

Brando
Sorry - but I don't believe that a 16 bit wave file imported to Samplitude at 24 bits sounds better at all. It's louder, or you have a different pan setting, or maybe a plug is affecting something. What you describe is not possible, IMO. What do you think Samplitude is adding to convert 16 bits to 24 besides 0's?

my thought also, i did check volume, settings etc.....looks w/o anything.....the highs a much clearer, snare tighter....its a puzzle

scook
I am not sure anything is to be gained by converting a 16bit source track to 24bit. Of course SONAR will import files based on it preference settings including importing 16bit audio as 24bit. Internally the SONAR will process both 16 and 24bit clips the same.
 
WRT changing the Audio Driver Bit Depth setting, it could be one driver is affecting the other. SONAR will only operate and a bit depth common to both drivers. What happens if only one of the interfaces is enabled when the Wave Profiler is run? Given that both SONAR and Studio One operate the same, is there a possibility that Samplitude is misreporting the setting?

I do not know, first I thought was, that internal realtek is keeping exclusive right over 24 bit, but the same happens with creative usb x fi eternal, which is 24 bit. I will, try now my  v 100 studio to see what happens. But, again with analogy it must be that something, perhaps Samplitude is or keeping possession of 24 bit, or for same reason, win 10 has a glitch, or lenovo is somehow mandating 16 bit, for reasons know to them. I will check with my other laptop

the other laptop is working , with x1. wave profilles scans and sees 24 bit. in wasapi and wdm.
so again we are at, or samplitide or win 10, or lenovo.
 
plese not, i always changed drivers for testing. when in samplitude i would use wdm, and in soanr asio, vice versa, jus to make sure one is not holding driver

i made a mistake here, assuming that sonar could lock into asio, wdm, wasapi, mme.. and conflict with another program, if they use the same driver, like flash, etc.. My mistake, was, that  a program, but a sound card conflict was an issue, ....so to be precise, when changing a sound card, disable everything, especially, if you have internal card, in playback, recording, microphone, what you hear, all that is in segments for the removed card....then go to advanced, and set to 24 bit..
 
i hate to say this to myself, but feel pretty stupid right now

let me give  you  example..if you have a microphone in recording and its set to 16 bit, and your line out is 24 bit, you could have sonar with wave profiler telling you you have to change to 16...that happened to me
 

Correct, because there is only one audio driver setting for bit depth in SONAR Preferences used for both input and output.

Perhaps alter thread title as may be misleading.
 
Just a thought..