A NOTE ON BUG REPORTING

sticky maybe?

i see bugs posted here and hear that folks report them to jj.

PLEASE NOTE THAT THE ENGLISH/JAPANESE TRANSLATION IS SOMETIMES CLUMSY.

for that reason, it's very important to be as simple as possible and to report them in a specific way.

ie, say there was a bug that caused a banana to appear on screen and not leave. you would report it like this.

1 - load project.
2 - enter step edit
3 - hit mode/pad 17
4 - record a new sample
5 - BUG: a banana appears on screen and doesn't leave til you reboot.

note that even very simple steps have been detailed and that the part with the BUG has the word BUG in caps.

this is the best way to have bugs reported. it is most coherent and successful.

major props to all beta testers.

Nice, thanx man. I'll be sure to do that when I report a bug. I haven't reported 1 yet cause I honestly wasn't sure of a good way to communicate it in an clear, comprehensive way. This way makes much sense and seems effective.

yeah i know there are a bunch of folks who want to help but don't really know how. glad to help.

How many times must I report the PAD TO NOTE ASSINGN thing?

i recieved an email from jj and he said he's not going to change it on purpose, just to bug you. we laughed at you behind your back. j/k he'll do it one, be patient.

Correcting the spelling would be the best addition to the JJOS so far.

i fuct a dyslexic girl once, her great tits distracted me from her poor spelling, the moral of the story: features over perfection.

Mr modnaR wrote:i fuct a dyslexic girl once, her great tits distracted me from her poor spelling, the moral of the story: features over perfection.

werd!

Mr modnaR wrote:i fuct a dyslexic girl once, her great tits distracted me from her poor spelling, the moral of the story: features over perfection.

Tits are great.

me, i prefer girls with tourettes

JJ already lists the way to post a bug correctly. Did he/she/they contact you to inform you that the forum beta testers are posting bugs incorrectly?