Been discussing the arranger a bit over in the OT feature request threads and while exploring it as a means to get better muting behaviour/other performance options I ran into multiple crashes.
This same thing happened to me last week! Totally lost bank C too. Luckily I didn’t have to much put into bank C yet.
I wasn’t sure what I did but it definitely was something with the b column and setting the tempos to pattern. I think i manually set all the tempos in the b column now.
With the project above, next time I powered up it was bank A showing unavailable. Weird. It was all empty anyway as a test project - so I’m not sure if there was actual data loss (except original tempo)
That’s what I was doing when I crashed mine if I recall correctly it was after I “inserted” a new second row between the first row and an already existing row and went to the b row and changed the tempo to pattern… this was a week or so ago so I can’t be sure but pretty sure this is what I was doing.
That’s at least what I found while trying to replicate the issue.
Not with OT now but I believe you have to turn past ‘pattern’ to get to the manual bpms & I think that once or twice it crashed while doing that - the sequencer was running and I went into B column on the active row.
It crashed quite a lot, but I was trying lots of things. Now I can only replicate ‘reliably’ with the setup I posted above
Yes, might well be related to the introduction of the proj/pattern tempo feature.
Right! I remember seeing that now. Thought I’d put a crazy bpm on it. Didn’t have any trigs in place as I was just trying to replicate the crash at that point - so didn’t get to hear what it would sound like. I’m guessing it’s really just skipping that row…
maybe strange question. but could you try again and have pattern P15 and P16 with something written in them? If this would not fail the same way it would proof one particular suspicion i have - knowing the arranger file format in detail.
