-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anbernic 35XX plus: stutters on high BPM value #100
Comments
I can assert that this issue is not present on PocketCHIP, Raspberry Pi 3 |
Do you mean this build? #96 |
@purelygrey yes, #96 |
@igavrilov thanks! Have you tried Knulli with performance governor or stock? I had to roll back from MuOS baked because I had constant stutters in Breath of Fire on SNES, which doesn't happen on Knulli at all, I wonder if the governor is to blame. I'll test the build out |
Alright, Knulli is 64bit so I have to build it with the appropriate toolchain. The executable I shared above won't work. |
@igavrilov could you please share an archive with your lgpt setup on MuOS? |
@purelygrey here you go. You can install it using Archive Manager from Update muOS to BAKED, the app doesn't work on REFRIED for some reason 🤷 A weird thing happened: last time I used it on muOS the default key mappings worked well but this time I had to set different mapping. Anyway the app works fine (on low BPM) and the problem I described in the issue persists. I've got troubles with building LGPT using Knulli toolchain unfortunately. Almost got to the end, still trying but got stuck on linking step. I am not very experienced in cross-compile things so If you (or anyone else) were able to build the app with the Knulli toolchain - I'd appreciate any kind of instructions/hint/directions to follow. |
What's the error in the linking step? |
I can confirm the problem on my 35XX Plus, it definitely stutters when it's over 150 bpm on MuOS Baked. It also skips on lower BPM, but way less so it's not as noticeable (tested on about 72bpm).
|
Have you tried any of the ones from Simoteks build yesterday? https://github.com/simotek/LittleGPTracker/releases/tag/1.4.2_Test4 |
@djdiskmachine No more errors after I updated to the latest master and used @simotek's toolchain 🎉 |
Fabtastic news! Have fun piggin' |
I meant no more build errors. Just tried Piggy 1.4.2 on Knulli - no stutters, works smoothly (except slightly wrong key mapping). |
Since I have MuOS Baked on hand I tried the @simotek's build as well, and it's doesn't stutter, awesome! I managed to caught it skipping, but it did that only once so far, it's been roughly 10 minutes, and I went for a reality check on my V90 and I caught it skipping just once as well - maybe it's some sort of quirk in the track, I don't know. However I hear some strange tempo instabilities in my test track, like it's dragging or rushing sometimes, I'm recording audio right now for an a/b test |
Turns out I'm not mad, and the same project lags a little bit on RG35XX Plus on MuOS baked, compared to BITTBOY build on Powkiddy v90, by the end of the track it gets pretty noticeable that the former is lagging behind. Also stereo channels are reversed on it for some reason (Pan 00 is right, 7F is left). Very strange, because if anything it should be the other way around, v90 is very underpowered in comparison Here's how the lag looks like after about 1:50, roughly 29ms Here are the recordings if you want to take a look at them And the project file I'm using: In any case it is a lot better now than it was before, and can be considered usable, which is very good! |
Ok, so 32-bit executable stutters, 64-bit executable works almost perfect. I believe the issue can be closed with a resolution: use 64-bit executable on muOS. muOS is actually 64bit:
|
Thank you for testing and reporting your findings! |
Sometimes its a bit confusing because i've noticed that some of the OS's are using a 64bit kernel with a 32bit userspace. |
OS: muOS 2405.2 Baked Beans
LGPT: 1.4.1-1
Prerequisites
Issue details
First of all I would appreciate if someone will confirm the issue is:
The text was updated successfully, but these errors were encountered: