May 10May 10 Dont know how many folks have tried using this. It seems like a cool idea but it lacks execution. It expects you to name the folder the way it wants you to. If you have a different folder structure then it expect good luck getting this to work. I have spent hours on the stupid config.yml filefilesystem: firmware_folder: bios roms_folder: library n64: paths: - "Nintendo 64/roms" - "Nintendo 64/Europe"system: platforms: Nintendo 64: n64ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more detailsINFO: [RomM][scan][2026-05-10 00:28:44] Found 27 platforms in the file systemINFO: [RomM][scan][2026-05-10 00:28:44] Folder n64[Nintendo 64] identified as Nintendo 64 🎮WARNING: [RomM][scan][2026-05-10 00:28:44] ⚠️ No firmware found for Nintendo 64[Nintendo 64]ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more detailsAlthough if I go look for the roms they exist in the docker containerIf I change roms_folder: to something that doesnt exitsIt will kind of work it will find 8 platforms and all the roms under those 8 platforms. This is extremely buggy software.I cant recommend this one unless your starting from scratch and willing to use the folder structure/names they appear to have hard coded into the system.
May 10May 10 On 7/12/2024 at 4:21 PM, Eazyeeee said:Hey! I am having issues with it detecting my roms. My file structure seems to be correct because it detects the platforms it is in, but not the roms itself.for example:It detects the Xbox 360 folder and knows what platform it is in, but not the ROM, Lollipop Chainsaw.Is there any troubleshooting steps I am not picking up?Same problem I had. Support appears to be non existent Edited May 10May 10 by xokia
May 10May 10 Author 26 minutes ago, xokia said:Same problem I had. Support appears to be non existentHey @xokiaDid you catch any of the posts in this thread (above) prior to your claim of “non existent support”?There is an active community of very knowledgeable and respectful people, including the developers and contributors to this great project. They’ll help you out if you take some time to repeat your needs in the Discord channel. OFFICIAL ROMM SUPPORTDiscord - RomM -support
May 10May 10 4 hours ago, Eurotimmy said:Hey @xokiaDid you catch any of the posts in this thread (above) prior to your claim of “non existent support”?There is an active community of very knowledgeable and respectful people, including the developers and contributors to this great project.They’ll help you out if you take some time to repeat your needs in the Discord channel.OFFICIAL ROMM SUPPORTDiscord - RomM -supportthere documentation is pretty clear they expect a rigid file structure. So you must bend to the will of the tool and not use the folder structure you want. You must use the folder structure they want you to use.https://docs.romm.app/latest/Getting-Started/Folder-Structure/?utm_source=copilot.com#folder-organizationI dont know the magic dance required to post a question. Like I said getting support is not easy for this app Edited May 10May 10 by xokia
May 10May 10 39 minutes ago, xokia said:there documentation is pretty clear they expect a rigid file structure. So you must bend to the will of the tool and not use the folder structure you want. You must use the folder structure they want you to use.https://docs.romm.app/latest/Getting-Started/Folder-Structure/?utm_source=copilot.com#folder-organizationI dont know the magic dance required to post a question. Like I said getting support is not easy for this appWhich one is your username in discord?Maybe there is something wrong with it, you should be able to post in support
May 10May 10 5 hours ago, zurdi15 said:Which one is your username in discord?Maybe there is something wrong with it, you should be able to post in supportLooks like it's a terms of service issue. You must accept the terms of service, I can post on my phone I got the pop up but not a pc web browser. I get no pop up for terms of service on the PC. I am not going to try an type out the issue on a phone. This app RomM app isn't worth the hassle. They have chosen a rigid file structure with their "new" rollout. You used to be able to give it a path. n64:paths:- "Nintendo 64/roms"- "Nintendo 64/Europe"For whatever reason they abandoned that and went with this new rigid structure which is inflexible. Some of my rom directories have no "roms" folder at all and are just flat.nes:paths:- "Nintendo Entertainment System"This would also violate their current folder structure requirement since you must have one or the other. I spent a day trying to get it to work. If you are just starting out and you are ok with their rigid file structure then this app will probably work fine. If you have an already established collection or roms/emulators then this app in its current form will not work. Edited May 10May 10 by xokia
May 10May 10 1 minute ago, xokia said:It's a terms of service issue. You must accept the terms of service I can post on my phone but not a pc web browser. I get no pop up for terms of service on the PC. I am not going to try an type out the issue on a phone. This app RomM app isn't worth the hassle. They have chosen a rigid file structure with their "new" rollout. You used to be able to give it a path. n64:paths:- "Nintendo 64/roms"- "Nintendo 64/Europe"For whatever reason they abandoned that and went with this new rigid structure which is inflexible. Some of my rom directories have no "roms" folder at all and are just flat.nes:paths:- "Nintendo Entertainment System"This would also violate their current folder structure requirement since you must have one or the other. I spent a day trying to get it to work. If you are just starting out and you are ok with their rigid file structure then this app will probably work fine. If you have an already established collection or roms/emulators then this app in its current form will not work.This is far from be true.I'm the founder of RomM and one of the current main devs and the supported folder structure didn't change since v1.0. Maybe its a skill issue?You are clearly using AI to fill the config or just lying because what you are posting never was supported as a config value, the config to bind folders to plarforms is totally different.Happy to help if you want to give RomM a chance at some point! Edited May 10May 10 by zurdi15 Typo
May 10May 10 8 minutes ago, zurdi15 said:This is far from be true.I'm the founder of RomM and one of the current main devs and the supported folder structure didn't change since v1.0. Maybe its a skill issue?Happy to help if you want to give RomM a chance at some point!This is pretty easy to duplicate and testemulatorjs:cache_limit: nullcontrols: {}debug: falsedisable_auto_unload: falsedisable_batch_bootup: falsenetplay:enabled: falseice_servers: []settings: {}I have a bunch of excludes dont think its relevant for this discussion.filesystem:firmware_folder: biosroms_folder: library #this picks up all 27 specified platforms but 0 romssystem:platforms:Nintendo 64: n64versions: {}roms are located here:- "Nintendo 64/roms"- "Nintendo 64/Europe"It's entirely possible a skill issue but everything I can find points to a rigid file structure requirement.Run a scan 0 are picked upThe "ERRORs" also point to the same file structure issue.ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more detailsINFO: [RomM][scan][2026-05-10 00:28:44] Found 27 platforms in the file systemINFO: [RomM][scan][2026-05-10 00:28:44] Folder n64[Nintendo 64] identified as Nintendo 64 🎮WARNING: [RomM][scan][2026-05-10 00:28:44] ⚠️ No firmware found for Nintendo 64[Nintendo 64]ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more detailsThe only way I can get it to semi work is to change. roms_folder: roms -> does not actually existI also specified 27 platforms and it only picks up 8.Then it will pick up- "Nintendo 64/roms" but not - "Nintendo 64/Europe"It does not like to be told what files to look in for a specific system.I even tried to enable debug to see if it would tell me the directories it was looking in and debug does nothing.scan:debug: trueautodetect: trueexport_gamelist: falseI thought this might be a cool way to download files to my AYN thor so I only set up the platforms that I have on my AYN thor and excluded all the other platforms. But nope unfortunately this doesnt appear to presently possible unless I am willing to change my entire directory structure. Edited May 11May 11 by xokia
May 10May 10 8 minutes ago, xokia said:This is pretty easy to duplicate and testemulatorjs:cache_limit: nullcontrols: {}debug: falsedisable_auto_unload: falsedisable_batch_bootup: falsenetplay:enabled: falseice_servers: []settings: {}I have a bunch of excludes dont think its relevant for this discussion.filesystem:firmware_folder: biosroms_folder: library #this picks up all 27 specified platforms but 0 romssystem:platforms:Nintendo 64: n64versions: {}roms are located here:- "Nintendo 64/roms"- "Nintendo 64/Europe"It's entirely possible a skill issue but everything I can find points to a rigid file structure requirement.Run a scan 0 are picked upThe "ERRORs" also point to the same file structure issue.ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more detailsINFO: [RomM][scan][2026-05-10 00:28:44] Found 27 platforms in the file systemINFO: [RomM][scan][2026-05-10 00:28:44] Folder n64[Nintendo 64] identified as Nintendo 64 🎮WARNING: [RomM][scan][2026-05-10 00:28:44] ⚠️ No firmware found for Nintendo 64[Nintendo 64]ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more detailsThe only way I can get it to semi work is to change. roms_folder: roms -> does not actually existI also specified 27 platforms and it only picks up 8.Then it will pick up- "Nintendo 64/roms" but not - "Nintendo 64/Europe"It does not like to be told what files to look in for a specific system.I even tried to enable debug to see if it would tell me the directories it was looking in and it does nothing.scan:debug: trueautodetect: trueexport_gamelist: falseAparte from this, that is already very useful, I would need to know how your library structure is in the host and how are you mounting them into docker.The docker compose will be so helpful too, at least de volume bind block Edited May 10May 10 by zurdi15 Typo
May 10May 10 docker run -d --name='romm' --net='romm' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="hidden" -e HOST_CONTAINERNAME="romm" -e 'DB_HOST'='192.168.0.12' -e 'DB_PORT'='3306' -e 'DB_NAME'='romm' -e 'DB_USER'='romm' -e 'DB_PASSWD'='hidden' -e 'ROMM_AUTH_SECRET_KEY'='hidden' -e 'IGDB_CLIENT_ID'='' -e 'IGDB_CLIENT_SECRET'='' -e 'SCREENSCRAPER_USER'='' -e 'SCREENSCRAPER_PASSWORD'='' -e 'MOBYGAMES_API_KEY'='' -e 'STEAMGRIDDB_API_KEY'='hidden' -e 'RETROACHIEVEMENTS_API_KEY'='' -e 'REFRESH_RETROACHIEVEMENTS_CACHE_DAYS'='' -e 'LAUNCHBOX_API_ENABLED'='false' -e 'PLAYMATCH_API_ENABLED'='false' -e 'HASHEOUS_API_ENABLED'='false' -e 'FLASHPOINT_API_ENABLED'='false' -e 'HLTB_API_ENABLED'='false' -e 'ROMM_DB_DRIVER'='mariadb' -e 'DB_QUERY_JSON'='' -e 'REDIS_HOST'='' -e 'REDIS_PORT'='' -e 'REDIS_USERNAME'='' -e 'REDIS_PASSWORD'='' -e 'REDIS_DB'='' -e 'REDIS_SSL'='' -e 'DISABLE_CSRF_PROTECTION'='false' -e 'DISABLE_DOWNLOAD_ENDPOINT_AUTH'='false' -e 'DISABLE_USERPASS_LOGIN'='false' -e 'SESSION_MAX_AGE_SECONDS'='' -e 'KIOSK_MODE'='false' -e 'OIDC_ENABLED'='false' -e 'OIDC_PROVIDER'='' -e 'OIDC_CLIENT_ID'='' -e 'OIDC_CLIENT_SECRET'='' -e 'OIDC_REDIRECT_URI'='' -e 'OIDC_SERVER_APPLICATION_URL'='' -e 'OIDC_TLS_CACERTFILE'='' -e 'WEB_SERVER_CONCURRENCY'='' -e 'WEB_SERVER_KEEPALIVE'='' -e 'WEB_SERVER_MAX_REQUESTS'='' -e 'WEB_SERVER_MAX_REQUESTS_JITTER'='' -e 'WEB_SERVER_TIMEOUT'='' -e 'WEB_SERVER_WORKER_CONNECTIONS'='' -e 'FORCE_COLOR'='' -e 'NO_COLOR'='' -e 'DISABLE_EMULATOR_JS'='false' -e 'DISABLE_RUFFLE_RS'='false' -e 'YOUTUBE_BASE_URL'='' -e 'UPLOAD_TIMEOUT'='' -e 'SCAN_TIMEOUT'='' -e 'SCAN_WORKERS'='' -e 'TASK_TIMEOUT'='' -e 'TASK_RESULT_TTL'='' -e 'SEVEN_ZIP_TIMEOUT'='' -e 'ENABLE_RESCAN_ON_FILESYSTEM_CHANGE'='false' -e 'RESCAN_ON_FILESYSTEM_CHANGE_DELAY'='' -e 'ENABLE_SCHEDULED_RESCAN'='false' -e 'SCHEDULED_RESCAN_CRON'='' -e 'ENABLE_SCHEDULED_UPDATE_SWITCH_TITLEDB'='false' -e 'SCHEDULED_UPDATE_SWITCH_TITLEDB_CRON'='' -e 'ENABLE_SCHEDULED_UPDATE_LAUNCHBOX_METADATA'='false' -e 'SCHEDULED_UPDATE_LAUNCHBOX_METADATA_CRON'='' -e 'ENABLE_SCHEDULED_CONVERT_IMAGES_TO_WEBP'='false' -e 'SCHEDULED_CONVERT_IMAGES_TO_WEBP_CRON'='' -e 'ENABLE_SCHEDULED_RETROACHIEVEMENTS_PROGRESS_SYNC'='false' -e 'SCHEDULED_RETROACHIEVEMENTS_PROGRESS_SYNC_CRON'='' -e 'LOGLEVEL'='INFO' -e 'SENTRY_DSN'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon='' -p '8383:8080/tcp' -v '/mnt/user/pool5/games/Arcade/':'/romm/library/':'ro' -v '/mnt/user/appdata/romm/resources':'/romm/resources/':'rw' -v '/mnt/user/appdata/romm/assets':'/romm/assets/':'rw' -v '/mnt/user/appdata/romm/config':'/romm/config/':'rw' -v '/mnt/user/appdata/romm/redis-data':'/redis-data':'rw' -v '/mnt/user/pool6/games':'/romm/library2':'ro' 'rommapp/romm:latest'Nothing fancyYou only need a single directory of files to replicateroms are located here:- "library/Nintendo 64/roms"- "libary/Nintendo 64/Europe"all other systems are similar or flatatari would be flat"library/Atari 2600/" Edited May 10May 10 by xokia
May 14May 14 On 5/10/2026 at 12:22 PM, zurdi15 said:Aparte from this, that is already very useful, I would need to know how your library structure is in the host and how are you mounting them into docker.The docker compose will be so helpful too, at least de volume bind blockNo luck?
June 6Jun 6 They have custom folder management on the roadmap: https://github.com/rommapp/romm/issues/2050
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.