Large number of variations lost after quick copying

Bug
, , ,
29

Hi @miropoly, the bug was reported in a lengthy set of emails with Martin at Polyend, starting January 2023, concluding June 2023 with a return of the product. There was sadly no progress.

31

Hi @alxzndr , I believe the correspondence from 2023 was about a different issue.

32

Hi @miropoly - No, this is one of the same issues, shown in the video below. There were around three issues in total.

Hereā€™s the video I sent to Martin in February 2023 - https://youtu.be/wieZATnwaZ4

Copy/pasting variations in this project file, the same one throughout all these bug reports is unusable. Iā€™ve had the same happen in other projects but canā€™t keep alpha testing for free. I tried pressing one pad at a time as you suggest above and tried setting the variation tracks to all be selected with one button press. Iā€™ll save, and variations will usually be corrupted even if they were playing fine beforehand.

33

Hello again,

This seems to me like a separate problem, with Step Page selection (16-32-48-64).

Thank you for sharing this additional info: weā€™ll keep this in mind when investigating this issue.

34

Hey @here,

iā€™ve sat down yesterday and tried to reproduce this myself. But i see now, that it appears difficult to narrow down the issue to what exactly is causing this.

For context:

  • Iā€™ve sat down and started with a fresh project.
  • Iā€™ve created 3 sample tracks and 3 midi tracks
  • Iā€™ve started to create variations for patterns
  • Iā€™ve started copying patterns and variations and changing things in them

At around 80 patterns i still couldnā€™t reproduce it.

So iā€™m wondering, is there anything iā€™m missing. Does anyone remember at what point they noticed this issue?

  • Was it after some action you did?
  • Was it after starting the device and/or loading a saved project?
  • Should i overload a single pattern with full 8 tracks?
  • Did you use 32-64 steps in your tracks?

For your information - iā€™m trying to create a minimal viable reproducable test-case. Meaning a way that i can run into this error reliably every single time.

So any additional information on things that youā€™ve done right before this happened, would be super useful! :heart:

35

@Sandroid Itā€™s been 18 months since I posted this. I couldnā€™t be a polyend customer/beta tester any more.

I received a message that a report about flickering knobs, again, it made the device unusable, has apparently been fixed 18 months after I reported it.

You guys need to open source this company or get funds to hire in more programmers. Iā€™ll check in in a year to see how the bug updates are coming, maybe get one secondhand.