You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: