Command Line Interface Not Working Properly
A tool for transcoding lossless audio files
Brought to you by:
tmkk
I am trying to use xld through the command line, however, I get the following warning/error.
2021-12-09 09:40:35.081 xld[28265:35143416] WARNING: NSTableView data source <XLDProfileManager: 0x125604860> implements tableView:writeRows:toPasteboard: which was deprecated in 10.4. Use tableView:writeRowsWithIndexes:toPasteboard: instead.
The command I used is as follows,
xld -o ~/Music -f aif test.flac
I addition to the above warning, when I enter the command the XLD GUI opens and asks me to choose a file (or path?). I was under the impression that I won't have to use GUI if I stick to the command line interface.
I always get the same output.
I am using xld-20211018.dmg
. I am using Monterey 12.0.1.
Hi, I'm also having problems with the command line, but they're a little different. I installed XLD via homebrew using
brew install xld
If I run this test command:
xld -o ~/Music -f aif test.flac
I get the following error
The very last line looks like it's having trouble passing the command line arguments to the app, so I just tried doing that manually using this command:
/Applications/XLD.app/Contents/MacOS/XLD --cmdline -o ~/Music -f aif test.flac
But I just get a similar (but different) error:
I'm on MacOS 10.15.7
I second you. I get exactly the same error. XLD 20211018, macOS Mojave and happens while using the CLI version in my AppleScript scipt inside Automator.
The command assembly is
do shell script "/usr/local/bin/xld -f " & Codec & " -o " & (quoted form of "$HOME/Music/iTunes/iTunes Media/Automatically Add to iTunes.localized/") & space & Profile & space & audfilepath
where Profile is --profile plus the profile's name as per the xld's manual, Codec is aif and audfilepath is a quoted Posix path. Either I last used this worflow a long time ago and programming faults of the latest update from the fall of the last year slipped through me, or (unlikely) something occurred that didn't drive my attention at all. I remember the command line counterpart working flaswlessly.
This problem should be fixed in the latest version 20230416.