Tested today for WF-PRO 13.3.11 in KDE(X11)@Debian12 to work fine:
Edit Audio File - Basic editing operations...
This applies the chosen action correctly.
Edit Audio File - Launch this wave file in its default application...
This opens the default application as configured in KDE/Linux for the XDG MIME type handling of WAV file without problems, there changes are applied and saved to the WAV file and closing that app returns to WF, in WF the changes are found to have been applied to the audio clip (to the file having initially been imported as a copy to the project and carrying the audio of the clip, and subsequently having been edited externally).
Although not being a friend of finding other characters than ASCII letters or numbers or underscore in a file name, I tested for you that both procedures also work fine when exchanging all underscores in my file name to spaces. I did not test to introduce spaces into the directory path, though. However, your error message does not state that the file wouldn't have been found, so it anyway does not look like a problem of path and file name resolution.
Please, what is the output of the following command? Note that your /path/filename has to be placed in quotes ( ' ' ) because of the spaces present in your particular /path/filename.
Edit Audio File - Basic editing operations...
This applies the chosen action correctly.
Edit Audio File - Launch this wave file in its default application...
This opens the default application as configured in KDE/Linux for the XDG MIME type handling of WAV file without problems, there changes are applied and saved to the WAV file and closing that app returns to WF, in WF the changes are found to have been applied to the audio clip (to the file having initially been imported as a copy to the project and carrying the audio of the clip, and subsequently having been edited externally).
Although not being a friend of finding other characters than ASCII letters or numbers or underscore in a file name, I tested for you that both procedures also work fine when exchanging all underscores in my file name to spaces. I did not test to introduce spaces into the directory path, though. However, your error message does not state that the file wouldn't have been found, so it anyway does not look like a problem of path and file name resolution.
Please, what is the output of the following command? Note that your /path/filename has to be placed in quotes ( ' ' ) because of the spaces present in your particular /path/filename.
Code:
xdg-mime query default $(mimetype -M -b '/path/filename')Statistics: Posted by talby — Wed Jan 29, 2025 10:07 pm