You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But there appears to be an issue with both Bass.NET and ManagedBass when PInvoking the:
BASS_Mixer_ChannelSetMatrix
BASS_Mixer_ChannelGetMatrix
methods on the BassMix library.
Under .NET Framework/Core 2.0-2.2 the method works as expected, and you're able to set a float[,] matrix.
Under .NET Core 3.0, the same call using the same float[,] appears to succeed (returns true), but if you immediately GET the matrix to check it's state, it appears to be zeroed out - and the audio playback is silenced.
Might be worth checking to see what response (if any) we get from Ian@Un4Seen or Radio42 before we propose a fix.
In my post of the Bass Forum above, I have a proposed a workaround - but it requires a breaking change, so it's not ideal.
The text was updated successfully, but these errors were encountered:
I'm going to close this issue, as it appears the issue has been resolved now in later versions of the .Net Core 3.0 and 3.1 SDKs. I'm going to assume the issue was an undocumented bug in the SDK that has now been fixed.
Hi,
I've done some initial investigation, and logged the findings on the Bass Forums:
http://www.un4seen.com/forum/?topic=18712.msg131029#msg131029
But there appears to be an issue with both Bass.NET and ManagedBass when PInvoking the:
methods on the BassMix library.
Under .NET Framework/Core 2.0-2.2 the method works as expected, and you're able to set a float[,] matrix.
Under .NET Core 3.0, the same call using the same float[,] appears to succeed (returns true), but if you immediately GET the matrix to check it's state, it appears to be zeroed out - and the audio playback is silenced.
Might be worth checking to see what response (if any) we get from Ian@Un4Seen or Radio42 before we propose a fix.
In my post of the Bass Forum above, I have a proposed a workaround - but it requires a breaking change, so it's not ideal.
The text was updated successfully, but these errors were encountered: