dlbeswick

I've found that when "STOP_PLAYBACK_FOR_UPDATES" is defined in setup.c then this problem doesn't happen.

I thought I had better check again; I have now also reproduced the problem with the buzzmachines. Subjectively, it seems to happen way less often than with the simsyn. Simsyn...

Thanks Stefan. It sounds like you're right, if you're not having any luck upstream then this is the way to go. If there's anything you'd like me to help out...

Hello Autumn, I build master fairly regularly but haven't seen these problems... Is docs/Makefile.mak a generated file? It looks like it. Maybe you have some missing build dependencies. These lines...

Thanks heaps for the pointers -- I'll look into this

I think I did mean wave, yes. Does this song crash for you? ` crash-mtDavid2019-07-28T11:42:27Z2019-07-28T11:42:40Z125416 `

Backtrace: Thread 27 "Matilde-Tracker" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff955f9700 (LWP 9476)] (gdb) bt #0 0x0000000000000000 in () #1 0x00007fff96c4b8d3 in CTrack::NewNote(bool) (this=this@entry=0x555556bb16f8, oRetrig=oRetrig@entry=false) at ../../../Matilde/Tracker/Track.cpp:144 #2...

I think that assuming wave 0 is given to Matilde Tracker, then the vtbl is being overridden on Matilde/Tracker/CTrack.cpp:134 `m_pChannel->m_pInstrument=m_pMachine->m_Wavetable.GetInstrument( m_iInstrument );`

This calls CWavetableManager::GetInstrument -- probably easier to look there.

Hello all, I can see that the stack trace shows an exception somewhere in fluid synth; I wonder if this is due to my recent changes to the code in...