TAGGING OF THE FORUM (How-To: Report bugs and request features)

Announcements
,
1

Note: If you are making a Bug Report, please include the firmware of your unit in the body of your post. Thanks.

Hey all,

We will be reviewing and tagging the all Bug Reports with the following tags:

Here is an explanation of each tag:

  • under-investigation - This bug is waiting to be reproduced so that we can verify if the bug is present or not.

  • in-dev-timeline - This bug is on our list of things to do, but will not be addressed in the next upcoming release.

  • in-progress - We are working on the bug actively to fix for an upcoming release. If it is not in the next release, usually it will be in the one following.

  • beta - This request has been implemented in the latest beta version.

  • fixed - This bug has been fixed in the current official released version of the firmware.

  • not-a-bug - This means the bug posted was proven to not be a bug. For example, if the “bug” is being caused by external factors other than the unit. Another example is if the expected behavior of the unit in that scenario is mistakenly considered a bug.

  • not-reproducible - This bug was not reproducible by our testing team, you may need to give more information about your settings or revise the steps given.

  • duplicate - The bug posted is a duplicate of another posting and will most likely be moved, closed, or deleted.

  • resolved - The bug posted was resolved in a matter that did not require a software fix

Please note, we will only be tagging the report made in the original post. Additional bug reports made in the comments of a thread will not be considered while tagging.

If it is a batch request in the original post, we will tag as batch and ask user to please repost as individual reports, this helps keep track of progress on requested bugs.

We will be tagging Feature Requests as following:

Here is an explanation of each tag:

under-consideration - We have seen your request and will respond soon whether or not we will be implementing the request.

in-dev-timeline - This request is on our list of things to do, but will not be addressed in the next upcoming release

in-progress - We are working on the request to implement for an upcoming release. If it is not in the next release, usually it will be in the one following.

med-long-term - we plan on implementing this in the future.

beta - This request has been implemented in the latest beta version.

implemented - This request has been implemented in the current official released version of the firmware.

duplicate - The request posted is a duplicate of another posting and will most likely be deleted.

considered - We have looked over the request but will not be implementing it. This is subject to change.

Please note, we will only be tagging the request made by OP in the first post. Requests made in the process of the discussion of the request(s) will not be considered while tagging.

If it is a batch request by OP, we will tag as batch and ask user to please repost as individual requests, this helps keep track of progress on requested features.

This is in the hopes of both reviewing all the requests made and also giving a little more clarity on what we are planning on doing.

As always,

Keep Rockin’ :sunglasses:

Please include as much of the following information as you can in your Bug Reports:

  • Description: What actually happened?
  • Version Number: x.x.x
  • Steps To Reproduce:
  • Expected vs actual Behavior:
  • Visual proof : Photo, video, audio

Song configuration:

  • Song saved: SD | Aeros
  • Record: Mono | Stereo
  • Track button action: RPO | ROP
  • Number of tracks: 6x6 | 2x2
  • Quantize: on | off
  • Count in: 0 | 1 | 2 | 3
  • Sync rule: start & length | length | off

Other important info:

  • Change song part: Immediate | End of measure | End of Loop
  • Stop song: Immediate | End of measure | End of Loop
  • With equipment : BeatBuddy | Midi maestro | other

Thanks!

4 Likes