ffmpeg / melt via remote machine

[Lars]

Ok... found it.


Problem was that nfs has not propagated the change.

So I changed the ffmpeg script to:

---

#!/bin/bash
ssh videoprocessor "/usr/bin/ffmpeg $@"
RC=$?
ls -al `dirname ${@:$#}` >/dev/null
exit $RC

---

The "ls -la" will reread the directory (nfs) where the output file will 
be found and then kdenlive finds the output.

Lars


On 08.10.2017 10:28, Lars wrote:
>
> Hi,
>
>
> I'm using kdenlive on my laptop using linux.
>
>
> On a second machine with I've got more powerful hardware.
>
> I use it for the complete rendering of the project via script at the end.
>
> The second machine has the same nfs-Shares and same kdenlive related 
> software installed as the laptop.
>
>
> Last night I had an idea processing the proxy clips on the remote machine.
>
> This morning I've written two short scripts to do so:
>
>
> remote_melt.sh
> ---
> #!/bin/bash
> # CURRENTTMP is accessible on both machines via nfs
> REMOTE=videoprocessor
> CURRENTTMP=`grep currenttmpfolder ~/.config/kdenliverc | cut -d"=" -f2 
> | sed "s#/tmp\\\$##"`
> TMP_MLT=$CURRENTTMP$1
> cp $1 $TMP_MLT
> shift
> ssh $REMOTE "/usr/bin/melt $TMP_MLT $@"####
> ---
>
>
> remote_ffmpeg.sh
> ---
> #!/bin/bash
> ssh -t videoprocessor "/usr/bin/ffmpeg $@"
> ---
>
>
> In kdenlive I switched the settings for "FFmpeg" and "Melt path"  to 
> the new scripts.
>
> This is working BUT it shows an error after generating the proxy clips.
>
> This means the proxy clips are generated and the scripts are exiting 
> with returncode 0.
>
> If I schedule to generate proxy clips again they are directly found.
>
>
> Anyone who can guide me to prevent the error?
>
>
> Kind regards,
>
> Lars
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20171008/20ec7fe8/attachment.html>