Hello,
I found an issue in the latest NAM A2 release on Windows.
The plugin fails to load IR files when the file path contains emoji characters (and possibly other non-ASCII Unicode characters).
Steps to reproduce
- Place a valid IR file in a folder whose path contains an emoji.
Example:
"C:\Users\User\Desktop\🎸\Mesa_OS_4x12_57_m160.wav"
- Open NAM A2.
- Try to load the IR.
Result
The plugin displays:
"Failed to load IR ... ???"
The path shown in the error dialog appears to have corrupted characters, suggesting an encoding issue.
Expected behavior
The IR should load normally regardless of Unicode characters in the path, or the plugin should provide a clear error message explaining the problem.
Additional information
- Windows 11
- The same IR loads successfully when moved to a path containing only ASCII characters (for example: "C:\IR\mesa.wav").
- The IR file itself is valid; only the file path changes.
This looks like a Unicode/UTF-8/UTF-16 path handling issue.
Thanks for your work on NAM A2.
Hello,
I found an issue in the latest NAM A2 release on Windows.
The plugin fails to load IR files when the file path contains emoji characters (and possibly other non-ASCII Unicode characters).
Steps to reproduce
Example:
"C:\Users\User\Desktop\🎸\Mesa_OS_4x12_57_m160.wav"
Result
The plugin displays:
"Failed to load IR ... ???"
The path shown in the error dialog appears to have corrupted characters, suggesting an encoding issue.
Expected behavior
The IR should load normally regardless of Unicode characters in the path, or the plugin should provide a clear error message explaining the problem.
Additional information
This looks like a Unicode/UTF-8/UTF-16 path handling issue.
Thanks for your work on NAM A2.