Outputs file does not exist error when trying to read a file created by 0cc-FamiTracker with all extended sound sources

[Leafeon2020]

As the title says, when I load a 0cc file with all the extended sound sources that can be put on the NES made with 0cc-FamiTracker, it outputs an error that the file does not exist, even though it does exist.
I tried with directories consisting entirely of ASCII characters, including an existing problem report of not being able to open directories containing non-ASCII characters, but still could not open them.
The 0cc files we tried cannot be posted here because they were released for a fee, but neither FamiTracker 0.5.0 Beta 5 nor Dn-FamiTracker 0.5.0.2 can open them.
As for the music, it is 0cc here.
https://www.youtube.com/watch?v=YCPlypjqXCQ

---

Execution Environments
Host Name:                 DESKTOP-51INB84
OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22631 N/A Build 22631
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          USER
Registered Organization:   
Product ID:                [DELETED]
Original Install Date:     2023/02/21, Tue 5:32:32
System Boot Time:          2024/08/20, Tue 5:36:00
System Manufacturer:       Micro-Star International Co., Ltd.
System Model:              MS-7D91
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 183 Stepping 1 GenuineIntel ~3500 Mhz
BIOS Version:              American Megatrends International, LLC. 1.E0, 2024/08/12
Windows Directory:         J:\WINDOWS
System Directory:          J:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume2
System Locale:             ja;Japanese
Input Locale:              ja;Japanese
Time Zone:                 (UTC+09:00) Osaka, Sapporo, Tokyo
Total Physical Memory:     32,540 MB
Available Physical Memory: 7,779 MB
Virtual Memory: Max Size:  65,308 MB
Virtual Memory: Available: 21,462 MB
Virtual Memory: In Use:    43,846 MB
Page File Location(s):     G:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-51INB84
Hotfix(s):                 4 Hotfix(s) Installed.
                           [01]: KB5042099
                           [02]: KB5012170
                           [03]: KB5027397
                           [04]: KB5041585
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

[nyanpasu64]

dn-ft cannot handle filenames with Unicode characters not in your Windows ansi/etc. locale. 0cc-ft attempted to add unicode support, to varying degrees of success (some of their builds had behavioral issues with corrupted strings, which may have been fixed), and a recent private ft 0.5.0 beta build had unicode too (i did not test deeply).

you can switch your computer to japanese locale, or rename the files to ascii.

[Leafeon2020]

Perhaps I am not explaining myself well enough, but I am running in a Windows environment where everything is in Japanese (the environment is just changed to English with the chcp command and output).

chcp 437
systeminfo | clip

I have already verified all the causes you are thinking of, because the same error was output in a directory consisting entirely of ASCII characters, H:\Users\USER, based on existing reports that it outputs an error when non-ASCII characters are included.

The only other thing I haven't tried is to set the Windows settings to English. I have not tried this method yet because I usually use software that is supposed to be in Japanese.

[Gumball2415]

could potentially be a locale issue?

[Gumball2415]

The 0cc files we tried cannot be posted here because they were released for a fee, but neither FamiTracker 0.5.0 Beta 5 nor Dn-FamiTracker 0.5.0.2 can open them.

I obtained the module file from Chiyoko directly, and it seems to be named .ftm but contains 0CC-formatted data. 0CC-formatted data may be why FamiTracker cannot read it, especially multichip and/or 5B data.