Mini MP3 File Names and File Order For Reliable Play Back, Both GPAD_API and Factory Test
@Yukti007 ya está trabajando en esto.
Desde el 22/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Describe the bug
A clear and concise description of what the bug is.
Short Summary of the expected behavior: I expect the playing of files from the SD card to follow understandable rules
Short Summary of the buggy behavior:
Lee asked an AI the following:
I am wanting to understand better the requirements for file naming for the SD card. I think have read conflicting explanations. One explanation focused on file names numerically incrementing. BUT another explication was that the order in which the files are written into the SD card alone mattered. I have not experimented with files in folder yet.
The AI came back with a plausible explanation which if true will change both our GPAD_API and Factory Test firmware.
https://share.google/aimode/lDzx5wVwoIhba4v0W
Summary of File Requirements
Both of the conflicting explanations you read are actually correct! They just apply to two completely different ways of using the DFPlayer Mini module. Because you haven’t experimented with folders yet, you are likely looking at the root directory of your SD card. The behavior of the TD5580A chip comes down to a fundamental rule: the chip cannot read alphabetical file names; it only knows index numbers. How those index numbers are determined depends entirely on which command style you use in your code.
Bottom Line
- The instructions for making SD card files in the factory test will have to change.
- The Factory Test will have to change
- The GPAD_API will have to change
During the transition I suspect we will have breaking changes.
Perhaps the root folder could continue FOR A LIMITED TIME to have files the old way, the order of written way, and then in organized folders we place files which can be managed by file names.
- Lenguaje dominante
- C++
- Estrellas
- 9
- Forks
- 6
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de PubInv/krake
-
web page publish and main loop share the MQTT send queuePosiblemente ocupada @Yukti007 la tomó hace 10 días. AbiertoHigh Priority regression test type: bug
-
USB and COM port share one command bufferPosiblemente ocupada @Yukti007 la tomó hace 10 días. AbiertoHigh Priority regression test type: bug
-
Firmware, Krake Loosing Broker Settings back to a DefaultPosiblemente ocupada @nk25719 la tomó hace 23 días. Abiertotype: bug
-
Hardware, LB0007 Not Playing Alarm FileQuizá libre de nuevo @nk25719 la tomó hace 30 días y no hay ningún pull request abierto. Abierto
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
Todos los issues de PubInv/krake
Issues similares
-
[mimalloc] update to 3.6.0Abiertocategory:port-update
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 2 días
-
MinGW build faillureAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
facebookresearch/faiss#5775 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Eval bug: minimax-m3: build_moe_ffn() drops the per-expert NVFP4 scale → garbled output (M3.1 Flash)Abiertobug-unconfirmed
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
secondlife/viewer#6507 ·
Los mantenedores suelen responder en 1 día
-
clang:frontend code-cleanup HLSL
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
llvm/llvm-project#235100 · 1 comentario ·
Los mantenedores suelen responder en 1 día