hi cardin, ryan from the patchwork team here. apologies for the lack of response, this report somehow slipped through the cracks in reaching our team and didn’t receive proper attention. we’re going to update some of our processes to fix this gap and prevent it from happening again.
we have seen this issue happen internally, but only very intermittently, so the bug is logged, but I don’t believe it has been prioritized appropriately given the severity. I just tried to reproduce the issue and did not see it, but I have experienced it in the past, so I know that it is still lurking. you can “work around” it by changing the length as you’ve noted, or by closing/reopening the device with the arrow buttons, but acknowledged that this is not an acceptable workaround.
a fix for this issue is being investigated now. apologies for hitting this major stumbling block right out the gate with basic patchwork usage.
hey cardin! an update on this one: the suspected cause of the bug has been identified, and a fix should be showing up in the 31.00 release. it ended up being a low-level physics bug that for some reason the note sequencer was particularly good at reproducing in certain scenarios.
Amazing! Thanks for the update Ryan!
I’m still holding out hope for a totally UEFN driven interface but I NEED to have dynamic music in my current solo project. I was trying fading stems to avoid using patchwork but it isnt those Zelda type dynamics i’m going for, more so a dynamic evolution of Metroid 2’s weird ambient soundtrack.
Anyway, the rambling is my way of saying thanks and im excited.