Hi @cavitas , thanks for taking the time to report these issues and apologies that you had to experience them. Before we continue, please take read How to report bugs for future reports and do not report two issues into same topic. This creates confusion and will just delay processing them. Having separate reports gives us opportunity to discuss specific bugs and understand better what’s going on, and finally deliver fixes faster. Would you be so kind to report them separately? If not, I will close this issue here and log it internally if we are able to reproduce it. Please let me know what you think.
Hi, @miropoly. Thanks for fast reply. This is interesting problem because second bug i get only after first bug. Maybe if first bug be fixed second doesn’t appear. I can edit the post, leaving only the first error, if the second one appears after the fix, I’ll just create a new thread with a bug, is it okay for you?
Hi @cavitas , thanks for writing back. Sorry but this wasn’t clear from the bug description or reproduction steps above. Thanks for explaining… in this case we’ll analyse the report as is and get back to you. Cheers
Hello @borsuk, Thank you for helping again.
I recorded a new video so that you can track as much as possible how bugs pop up and what steps I take.
Brief description of timing:
0:00 Creating a new project
0:07 - 0:55 Adding samples from the pack
0:58 I noticed that the memory spent on the sample jumped from 30% to 54% , although this sample takes up 15kb
1:00-1:28 I play this “strange” sample several times and check that it is normal.
1:30 Playing the nearest samples
1:32 I draw my attention to the appearance of “bug 1 - high-frequency sound” - when the sample ends, a pronounced high-frequency sound appears.
1:38 I turn off the sound by tapping the volume potentiometer. (I tried how long this sound plays, the maximum I endured was half a minute)
1:40-2.07 I create a simple track from samples.
2:09 I start doing duke nuken on the track.
2:15 I noticed the appearance of “bug 2 - samples that I did not add”, on a sample that dramatically consumed a lot of memory.
2:35-3.06 I decide to see what kind of sample is used. I understand for sure that I did not add this sample.
3:07 Checking the status of the sample memory. To find that sample. Bug2 appear
3:32 I’m checking this sample from the pack. Bug1 appear
Conclusions: I have an opinion that the bugs are somehow connected with the conversion of samples Since it played sounds in bug2 that I used a couple of days ago.
And thank you for continuing to develop this wonderful product.
@cavitas Thank you for such a detailed reproduction and the video.
I managed to reproduce both issues.
Now we will do our best to resolve it and notify you when it’s ready.