Bug 408345

Summary:	Extract audio does not work if there is space in the path
Product:	[Applications] kdenlive	Reporter:	CzAndrew <hello>
Component:	Rendering & Export	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED FIXED
Severity:	normal	CC:	fritzibaby, julius.kuenzel
Priority:	NOR	Flags:	fritzibaby: Brainstorm+
Version First Reported In:	19.04.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:	20.12.3
Sentry Crash Report:

Description CzAndrew 2019-06-05 13:39:34 UTC

SUMMARY
Extracting audio does not work. 

STEPS TO REPRODUCE
1. Add a video file to the Project Bin.
2. Right click on the video file, choose Extract Audio, then Wav 48000Hz.
3. Kdenlive gives you an error message: Failed to create file. If I click on Show Log, then: "[NULL @ 00000258ebec0980] Unable to find a suitable output format for 'F:/2019-06-02'
F:/2019-06-02: Invalid argument"

OBSERVED RESULT
Kdenlive gives an error.

EXPECTED RESULT
The wav file should be extracted to the same folder where the input video file is.


SOFTWARE/OS VERSIONS
Windows: Win10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Workaround: Put the video file in a folder where no space charater is. (Should be no space characted in the path and in the filename)

Comment 1 Julius Künzel 2021-03-25 16:12:15 UTC

I cannot confirm on linux with 20.12.3

Can you please update to the latest version (20.12.3 at the moment, https://kdenlive.org/en/download/) and report here whether this is still happening?

Comment 2 emohr 2021-03-25 16:26:24 UTC

This is fixed with 20.12.3. Tested on Windows 7.

Clip in a folder with space in the name. Clip with space in the name and in a folder with space in the name. In both cases audio get extracted from the video clip without error message.

We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.

Comment 3 CzAndrew 2021-03-25 22:48:30 UTC

I confirm that the bug has been fixed. 
Tested on v20.12.3; Win10.