can't access sample browser when preview is used quickly
Closed this issue · 16 comments
Report
- go to sample browser
- double click to open sample browser
- Repeat previewing various samples.
- The preview will no longer play.(NG)
- When I try to EXIT and reenter, the browser does not open.(NG)
It looks from 3/1
SHA-1: 58f6ab9
samples
drums.zip
Builds.zip
Thanks for reporting this.
I have been able to reproduce it by downloading your drum samples and then trying to preview samples as rapidly as possible. Will need to investigate further to try to find whats causing it, likely some sort of race condition as the streaming code used for preview isn't used in any other part of the audio playback in picotracker.
- freeze device, I've talked about this before #66. It's a critical error. It's impossible to work with.
- freeze device, I've talked about this before #66. It's a critical error. It's impossible to work with.
In my testing this issue does not cause a freeze of the device and matches the symptoms of the original report here.
- freeze device, I've talked about this before #66. It's a critical error. It's impossible to work with.
In my testing this issue does not cause a freeze of the device and matches the symptoms of the original report here.
If you have pre-loaded already samples and arranged them, then you run this problem, then you get a message about browser not being able to load, and if you try to save the project, you get a device freeze.
If you have pre-loaded already samples and arranged them, then you run this problem, then you get a message about browser not being able to load, and if you try to save the project, you get a device freeze.
Sure, but that is not what this issue is tracking.
If you have pre-loaded already samples and arranged them, then you run this problem, then you get a message about browser not being able to load, and if you try to save the project, you get a device freeze.
Sure, but that is not what this issue is tracking.
I mean, this bug will live on indefinitely.
If you run this issue from an issue and then try to save the project, you will get a freeze, I realize that these are two different issues, but can you check this in yourself and confirm the issue ?
I'm sorry for confuse you.
This issue is not about release version (only repository master).
I checked the source code and found where it happen, so this issue is from this month.
I think the sample browser is very difficult part to make, and there are some problems.
Let's isolate the problems one by one and check them out.
@paasukusai no all good, your report is very well done and it was easy to reproduce the issue. But I don't think the cause was the change to show file sizes unless you have tried a build before that commit and the issue does not occur there?
@paasukusai no all good, your report is very well done and it was easy to reproduce the issue. But I don't think the cause was the change to show file sizes unless you have tried a build before that commit and the issue does not occur there?
Both problems exist in all versions, but it appears slightly less frequently than in this version.
Let me share the build removed the point.
This build seems ok.
(but sorry, I don't understand the source code yet..
If I find out anything more, I will share it.
Yes you may think that this fixes the problem, but unfortunately it doesn't, if you pre-listen to samples in the browser for longer periods of time, you get this. It seems to me that picotracker doesn't clear memory after pre-listening.
@paasukusai thanks very much again for the very detailed bug report! 👍🏻
and thanks also for adding the suggested changes. When I get a chance, I'll look at the file size code and see if/why it makes a difference to preview playback causing issues.
@democloid yes all good. I'm not sure how its linked to the changes, I suspect maybe something to do with reading the filesizes from the sdcard, but I'll need to debug it properly. I'll try to get to it soon, as I find especially the filesize display if not the flash remaining an invaluable feature. I might try to tackle this as part of adding the FS in #171