Expand Command Line Interface

[GoogleCodeExporter]

Hello

Would like the CLI to be expanded to have all the GUI features

Thanks

Original issue reported on code.google.com by ade.hal...@gmail.com on 21 May 2012 at 6:33

[GoogleCodeExporter]

Implementing all features is difficult, but the latest update has an ability to 
output compressed formats.

Original comment by tmkkmac on 9 Jun 2012 at 12:49

• Changed state: Started

[GoogleCodeExporter]

Thanks for adding the compressed formats to the CLI, I'm using it to convert 
FLAC to ALAC, works very well. 

How about adding a '-p: profile' option that takes as much info as it can from 
the profile, e.g. I could have a profile called mp3_cbr which has all my 
settings and then my command would be 'xld -p mp3_cbr'

Original comment by ade.hal...@gmail.com on 4 Oct 2012 at 9:06

[GoogleCodeExporter]

Profile reading is implemented in the latest update (--profile).

Original comment by tmkkmac on 14 Oct 2012 at 7:10

[GoogleCodeExporter]

Cool, that was quick!

I think it would be better not to convert to wav or to throw an error if the 
profile is not found, and the same with -f, e.g. if I type -f alax by mistake 
it will convert to wav

Also, can we stop it converting if already in that format e.g 

  xld dir1/file1.flac -f flac -o dir1/file1.flac

crashes the cmd as I presume it's converting and then trying to move to the 
same location/file

but if it was -o dir2/file1.flac then I also wouldn't want that converted as 
it's already flac (maybe add an option for this)

Original comment by ade.hal...@gmail.com on 18 Oct 2012 at 11:35

[GoogleCodeExporter]

now getting a 'cannot execute binary file' for any cmd I try and run

Original comment by ade.hal...@gmail.com on 19 Oct 2012 at 1:21

[GoogleCodeExporter]

Update to Comment 5 - during my testing I'd somehow managed to turn the xld 
command into a ogg file!!
changed it back and all is well!

Original comment by ade.hal...@gmail.com on 19 Oct 2012 at 2:51

[GoogleCodeExporter]

and would it be possible to stop this example - i have a mp3 at 192 kbps and my 
cmd is xld --profile mp3_320, which will convert to 320kbps. Could we either 
stop this or have an option?

Original comment by ade.hal...@gmail.com on 19 Oct 2012 at 3:38

[GoogleCodeExporter]

Such a thing should be done on shellscript side...

Original comment by tmkkmac on 19 Oct 2012 at 4:01

[GoogleCodeExporter]

to do that and use the --profile would (I think) involve parsing the plist for 
the values, alternatively the cmd could be expanded e.g. -f mp3 --bitrate 320 
--samplerate 44100 etc

Original comment by ade.hal...@gmail.com on 19 Oct 2012 at 5:13

[GoogleCodeExporter]

I mean check input file's extension in the shellscript, and skip it if it is 
the same as destination format.

Original comment by tmkkmac on 19 Oct 2012 at 6:03

[GoogleCodeExporter]

if using --profile, the destination format isn't known until the file is created

Original comment by ade.hal...@gmail.com on 19 Oct 2012 at 8:15

[GoogleCodeExporter]

?
You know that which destination format the selected profile uses.

Original comment by tmkkmac on 19 Oct 2012 at 8:25

[GoogleCodeExporter]

This is kind of true if it's me running it and manually.

But, I would like to use the cmd in a cross platform python application that 
can automatically convert. 
This application allows the user to automatically convert by using the ffmpeg 
cmd if installed based on app config options (format, vbr/cbr, bitrate etc)
I thought it would be a good idea for us osx users to be able to use the xld 
cmd instead of ffmpeg and just have them enter their xld profile to use in the 
config

The problem with the xld cmd (as it stands) is it doesn't have all the the 
options, e.g. for mp3 there's no option for vbr/cbr, bitrate etc and it also 
seems to be linked to the last gui profile entered

So, in my app if I want to use --profile I would need to either read the plist 
to get the options before conversion, or convert to a temp file then analyse 
and compare that to the input file

Would be good if the cmd could be expanded for more options and also have a 
--sanity option that checks syntax and doesn't allow transcodes etc

Original comment by ade.hal...@gmail.com on 19 Oct 2012 at 6:41

[GoogleCodeExporter]

I didn't assume such a purpose.

Anyway, currently I have no plan to expand xld interface to accept options for 
each output format (it is quite boring work for me). Option to skip converting 
when src/dest format is the same may be implemented in the future, but priority 
is low.

Original comment by tmkkmac on 19 Oct 2012 at 7:30

[GoogleCodeExporter]

I cant seem to get --profile to work from the command line.  I create a profile 
in the gui, (multiple output formats, v0, v2, and 320) and when I do 'xld 
--profile Big3 filename.flac' it just spits out the wav file in the local 
directory.  Am I doing something wrong? I have the latest version of xld as of 
today.

Original comment by ryanasl...@ryanaslett.com on 17 Nov 2012 at 6:39

[GoogleCodeExporter]

A profile with multiple output isn't supported in CLI.

Original comment by tmkkmac on 17 Nov 2012 at 6:49

[GoogleCodeExporter]

Is it possible to have the destination directory support, in --profile 
implementation ?

Original comment by boisseau...@gmail.com on 22 Nov 2012 at 5:19