Bug 474788 - Render to network folder / UNC path not possible
Summary: Render to network folder / UNC path not possible
Status: RESOLVED DUPLICATE of bug 451413
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (other bugs)
Version First Reported In: 23.08.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-22 14:42 UTC by mb_kde-bugs
Modified: 2026-01-15 18:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Render to UNC path fails.. (29.45 KB, image/png)
2023-09-22 14:42 UTC, mb_kde-bugs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mb_kde-bugs 2023-09-22 14:42:27 UTC
Created attachment 161804 [details]
Render to UNC path fails..

SUMMARY
Using UNC path notation, to render a file directly to a network folder does not work.
The path to file will be created on the root of the installation drive of Kdenlive, not respecting the \\server\ UNC notation.

STEPS TO REPRODUCE
1. Open render dialog and use "\\my-windows-nas\e$\tmp\my-rendered-video.mp4" as output file.
2. Start rendering

OBSERVED RESULT
The finished file be located on the LOCAL drive instead of the network folder.
The resulting path to the file is "D:\e$\tmp\my-rendered-video.mp4" for me (since Kdenlive is running from "D:\bin\av\kdenlive\.." I guess).
You can already see in the rendering dialog, that the path is messed up somehow, since the output file is displayed as:
"/e$/tmp/my-rendered-video.mp4". I just found the resulting folders + file by accident on the root of local drive D:\.

EXPECTED RESULT
The resulting file should be written to the network location I specified, not a random local drive.
\\my-windows-nas\e$\tmp\my-rendered-video.mp4

SOFTWARE/OS VERSIONS
Windows: Win10 Pro
Comment 1 aristsakas 2026-01-15 18:33:47 UTC

*** This bug has been marked as a duplicate of bug 374855 ***
Comment 2 aristsakas 2026-01-15 18:37:07 UTC

*** This bug has been marked as a duplicate of bug 451413 ***