Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log file ends up in ~/ and not where files are placed #2

Open
38github opened this issue Aug 1, 2018 · 1 comment
Open

Log file ends up in ~/ and not where files are placed #2

38github opened this issue Aug 1, 2018 · 1 comment

Comments

@38github
Copy link

38github commented Aug 1, 2018

When encoding with Deadbeef the log file always ends up in ~/ and not where the files are placed. I do not know if it is lossywav's fault, Deadbeef's or mine but it doesn't happen on Windows.

@MoSal
Copy link
Owner

MoSal commented Aug 2, 2018

When --stdout is passed, lossywav does not know where the files will be placed. So the log file will
be saved in the working directory where lossywav executed from.

If %o is a full path, then you can wrap lossywav with a script that will change the working directory
before executing lossywav.

This could work (untested):

echo '#!/bin/env bash\n\ntarget_dir="${1##*/}"\nshift\ncd $target_dir\nlossywav $@' > /tmp/wrap_lossywav
chmod +x /tmp/wrap_lossywav

Then replace lossywav in Deadbeef with /tmp/wrap_lossywav %o. If that works, move wrap_lossywav to a permanent place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants