• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Save As creates unwanted subfolder when parent folder contains Turkish/Unicode characters (macOS)

ysonmezer

New member
I found a reproducible Save As issue in Fender Studio Pro on macOS and have already submitted it to Fender Support.


Normally, I keep several .song files in the same working folder so they can share the same Media, History and Cache structure.


With an ASCII-only parent folder, Save As works normally:


Project_CS_TEST/test.song


However, if I rename the exact same parent folder to:


Project_ÇŞ_TEST


and perform File > Save As > test2.song, Studio Pro creates:


Project_ÇŞ_TEST/test2/test2.song


instead of the expected:


Project_ÇŞ_TEST/test2.song


I tested this several ways:


  • Same Song, same folder contents, same Save As operation.
  • ASCII parent folder → works correctly.
  • Parent folder containing Turkish characters such as Ç / Ş → unwanted subfolder is created.
  • Unicode characters in the Song filename itself do not appear to cause the problem. For example, ğüşıöü.song saves correctly when the parent folder is ASCII-only.
  • Folder permissions were verified as Read & Write.

While inspecting an affected Song, I also noticed that visually identical path components could appear in composed/decomposed Unicode representations. That makes a Unicode path-normalization/comparison issue a possibility, although I cannot confirm the internal cause.


Current workaround:
Use ASCII-only names for the parent/project folder, for example:


Project_CS_TEST


Song filenames themselves can still contain Turkish characters based on my testing.


I have reported the issue to Fender Support.


If anyone using another language or character set can reproduce this with accented or other non-ASCII characters in the parent folder name, it would be useful to add your results here. That may help determine whether this is Turkish-specific or a broader Unicode path-handling issue.
 
Back
Top