am afraid can rule out win10: had it running on a win10 pc here over night without a single error-log message. if you find other cases to clearly reproduce, please always send our way.
I found a way to reproduce it, but I don’t know if it’s related to the main issue or not.
If you set a large value and quickly change the iteration count, you can get an exception similar to the one described above. It seems that something happens at the ‘peak’ moment and an exception is thrown.
By the way, Win10 and exceptions themselves have not yet come up.
when i open this patch under Win 10, i see the exceptions immediately
ArgumentOutOfRangeException: "Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')"
ParamName: "index"
StackTrace:
System.ThrowHelper { internal static void ThrowArgumentOutOfRange_IndexMustBeLessException() { ... } }
VL.Audio.MatrixMixerSignal { protected virtual void FillBuffers(float[][] buffer, int offset, int count) { ... } }
VL.Audio.SingleSignal { protected virtual void FillBuffer(float[] buffer, int offset, int count) { ... } }
VL.Audio.MasterWaveProvider { public virtual int Read(byte[] buffer, int offset, int count) { ... } }
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
at VL.Audio.MatrixMixerSignal.FillBuffers(Single[][] buffer, Int32 offset, Int32 count)
at VL.Audio.SingleSignal.FillBuffer(Single[] buffer, Int32 offset, Int32 count)
at VL.Audio.MasterWaveProvider.Read(Byte[] buffer, Int32 offset, Int32 count)
Thinking about spread counts, I though of the sound particles help patch, as I was previously trying to use that example as a way of having sounds attached to my users trackers, and so just tried that again and that patch is broken in a different way and has an unspecified audio player error, on every create. So something is wrong under the hood, as that didn’t happen previously either. When using oscillators it used to click on add and remove.
Which also gives me the index errors now, but previously just clicked
My vl.audio version has no version number, is this correct?
I tried removing nugets and installing 113 again, still issues. Rebuilt the patch from scratch and it works without errors. I’ll try and rebuild my main patch in my app again
it looks like this when you’re running a package from source.
Again: VL.Audio is included with installs. Any custom installation will only confuse you.
1 Like
Damn! That would do it, left over from when I was trying to debug. Sorry about that. It does seem to be solved with the update. Which is good as rebuilding from scratch didnt work!