You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If my UTF8 pull request will be accepted, there will be another encoding problem with FMODex and mp3 filenames.
In my case kyrillic mp3 filename. FMOXex can't find that file because of the encoding issue.
I couldn't find a solution for that. But I have a possible workaround.
My proposal for a workaround:
Always make a temporary copy of the mp3 file inside the song folder with a static filename. This file should then be used for FMODex. After the edit session, the temporary mp3 file has to be deleted.
What do you think about it? Or do you have a solution for that problem?
The text was updated successfully, but these errors were encountered:
There is also a problem, if the mp3 file is saved in a folder with kyrillic folder name. So my workaround has to be adapted. The temporaly mp3 file has to be saved somewhere else. Maybe to the default temp folder of the OS.
If my UTF8 pull request will be accepted, there will be another encoding problem with FMODex and mp3 filenames.
In my case kyrillic mp3 filename. FMOXex can't find that file because of the encoding issue.
I couldn't find a solution for that. But I have a possible workaround.
My proposal for a workaround:
Always make a temporary copy of the mp3 file inside the song folder with a static filename. This file should then be used for FMODex. After the edit session, the temporary mp3 file has to be deleted.
What do you think about it? Or do you have a solution for that problem?
The text was updated successfully, but these errors were encountered: