trogluddite ·
After two days of headscratching I seem to have nailed down the cause of some spontaneous crashing in one of my big .osm's. The circumstances are rather unusual, so hopefully shouldn't affect too many people...
I'm doing some major ASM optimising, and for my particular design I'm using ASM primitives with a mixture of stream and mono inputs and outputs. Because there is no explicit mono4 data type, if all the outputs are monoout's, any streamin's end up as 'black' ambiguous inputs (see top diagram below). But that's not normally a problem, you can define a data type on a module input connector (as below). However under sertain circumstances (I don't quite know what they are yet), this still leaves the schematic prone to crashing when connecting audio or editing. A simple workaround is shown in the bottom diagram, using a dummy streamout so that you can explicitly define the data type. This has worked fine so far, but without knowing the true cause of the problem it's hard to know if it's infallible just yet.