tildearrow

It appears you're using the noise mode macro, which has quirky and difficult to simulate behavior on DefleMask legacy. I'll take a look at it regardless, as it seems the...

Issue fixed for 0.5, hoping this does not cause regressions.

It appears there were regressions... See #260

Wooooooow that will require a rewrite of the playback routine, dropping Defle compatibility in the process. I might implement it using another way, but this looks too difficult.

The problem with arp schemes is that it would require a restructuring of the way macros are stored in order to make space for a "formula" value, and it would...

Storage. Furnace represents the loop and release positions as variables in a DivInstrumentMacro: ```C++ // this is getting out of hand struct DivInstrumentMacro { String name; int val[256]; unsigned int...

Additionally, we run into another issue: differing arpeggio macro implementations. Furnace treats most macros equally - the same code is used to run these and they don't take any parameters....

> Firstly, thank you for taking the time to thoroughly explain things. I know that some people would rather be dismissive than have to explain everything. It's rather difficult for...

Whoops

I am going to close this suggestion as won't fix because I am changing the arpeggio code in a way that may or may not be further incompatible with 0CC's...