Quote:
Originally Posted by Mosu
Nice catch, thanks. I'll have to replace all characters Windows doesn't allow in file names before copying the title to the file name.
|
The problem may not be just that some characters are illegal in the Windows file system. In my tests, GUI doesn't allow you to create foo.mkv from foo.264 at all, when the File title is non-empty and not "foo", even if you explicitly type "foo.mkv" in the File destination editbox. In other words, on GUI, when --title is specified, you can't select a Destination that happens to be identical to the initial default Destination.
Example:
- When you create a new job on GUI and add a source file "D:\CD Image.flac", the Destination file "D:\CD Image.mka" is auto-selected. Type something in the File title editbox; the Destination file remains the same. In this state, you'd think "CD Image.mka" will be created when "Start multiplexing" is clicked...
- What will actually happen is different (already reported).
- Not only that, even if you manually type or select the Destination "D:\CD Image.mka" (suppose you do want to use that file name) after you type something in File title, GUI ignores it and still tries to create a Matroska file named after the File title. This behavior seems case-sensitive: GUI allows you to write e.g. "D:\CD Image.Mka" (capital M) from "D:\CD Image.flac" with an arbitrary --title.