Menu

#548 Command Line Interface Not Working Properly

Fixed
nobody
None
Medium
Defect
2023-04-17
2021-12-09
ankur
No

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.

Discussion

  • Morgan Morel

    Morgan Morel - 2022-06-07

    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

    2022-06-07 14:35:30.882 XLD[8831:150222] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** +[NSString stringWithUTF8String:]: NULL cString'
    *** First throw call stack:
    (
        0   CoreFoundation                      0x00007fff385d74d7 __exceptionPreprocess + 250
        1   libobjc.A.dylib                     0x00007fff711505bf objc_exception_throw + 48
        2   Foundation                          0x00007fff3abbc3f9 +[NSString stringWithUTF8String:] + 174
        3   XLD                                 0x00000001062eb264 cmdline_main + 8708
        4   XLD                                 0x000000010625e724 start + 52
        5   ???                                 0x0000000000000007 0x0 + 7
    )
    libc++abi.dylib: terminating with uncaught exception of type NSException
    /usr/local/bin/xld: line 11:  8831 Abort trap: 6           "${XLD_APP}/Contents/MacOS/XLD" --cmdline "$@"
    

    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:

    2022-06-07 14:37:27.565 XLD[8864:152354] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** +[NSString stringWithUTF8String:]: NULL cString'
    *** First throw call stack:
    (
        0   CoreFoundation                      0x00007fff385d74d7 __exceptionPreprocess + 250
        1   libobjc.A.dylib                     0x00007fff711505bf objc_exception_throw + 48
        2   Foundation                          0x00007fff3abbc3f9 +[NSString stringWithUTF8String:] + 174
        3   XLD                                 0x0000000102f27264 cmdline_main + 8708
        4   XLD                                 0x0000000102e9a724 start + 52
        5   ???                                 0x0000000000000007 0x0 + 7
    )
    libc++abi.dylib: terminating with uncaught exception of type NSException
    zsh: abort      /Applications/XLD.app/Contents/MacOS/XLD --cmdline -o ~/Music -f aif test.fla
    

    I'm on MacOS 10.15.7

     
    • scrutinizer

      scrutinizer - 2022-07-13

      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.

       
  • tmkk

    tmkk - 2023-04-17
    • status: New --> Fixed
     
  • tmkk

    tmkk - 2023-04-17

    This problem should be fixed in the latest version 20230416.

     

Log in to post a comment.