Reply to thread

Message

<blockquote data-quote="Sebastiii" data-source="post: 1034644" data-attributes="member: 60104">From old friend of mine, we could have some explanation <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />WASAPI drivers and/or audio HW defines the max buffer size in bytes, so that is why different audio formats have different max buffer lenghtsBASS library seems to be not so nice when it reports just an unknown error with a failure on buffer initializationIt surely would assume WASAPI would return AUDCLNT_E_INCORRECT_BUFFER_SIZE in those cases but that 100% sure of course it seems BASS hides that error from MP&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="Sebastiii, post: 1034644, member: 60104"] From old friend of mine, we could have some explanation :) WASAPI drivers and/or audio HW defines the max buffer size in bytes, so that is why different audio formats have different max buffer lenghts BASS library seems to be not so nice when it reports just an unknown error with a failure on buffer initialization It surely would assume WASAPI would return AUDCLNT_E_INCORRECT_BUFFER_SIZE in those cases but that 100% sure of course it seems BASS hides that error from MP :) [/QUOTE]

Verification