Open mklaber opened 1 year ago
I think this is an edge case due to relative paths not getting resolved relative to the cwd of the instance that you launch from, but rather inside the already running instance. I think the solution is to resolve the relative path before passing it on to the running instance, but it will increase complexity abit because then the launched instance would have to parse the command line and then replace the path and then pass the new edited command line instead of the original one: https://github.com/mifi/lossless-cut/blob/17a2a8cf531065b7ef17268590fa90a57d852d3a/public/electron.js#L264
I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first
Operating System
MacOS 10
Steps to reproduce
sample_mpeg4.mp4
fromdir1
sample_iTunes.mov
fromdir2
Workaround that sometimes works (I can't reproduce it not working, but I've observed it...): use an absolute path to the file to open:
Expected behavior
At step 7, above,
sample_iTunes.mov
should have opened successfully (like step 3).Actual behavior
LosslessCut cannot find the file and displays a "The media you tried to open does not exist" error.
Share log
The relevant log information is:
NB: The logs indicate it's trying to open the file from
dir1
rather thandir2